Overview
This node integrates with the 8Thsense API to perform CRUD (Create, Read, Update, Delete) operations on four main resource modules: Contact, Company, Case, and User. It allows users to create new records, update existing ones, delete records, retrieve a single record by ID, or list multiple records from these modules.
Common scenarios include:
- Automating contact or company data management by creating or updating records based on external triggers.
- Fetching user or case information for reporting or further processing in workflows.
- Deleting obsolete or incorrect data entries programmatically.
- Querying lists of entities with optional query parameters for filtering.
Practical example:
- Automatically create a new Contact in 8Thsense when a form is submitted.
- Update a Case's status or assigned user based on workflow logic.
- Retrieve details of a specific Company by its ID for enrichment or validation.
Properties
| Name | Meaning |
|---|---|
| Module | Selects the resource module to operate on. Options: Contact, Company, Case, User. |
| Method | The HTTP method / operation to perform. Options: Create (POST), Delete (DELETE), Get One (GETONE), List (GET), Update (PATCH). |
| ID | The unique identifier of the item to be used in the API call. Required for Update, Delete, and Get One operations. |
| Fields (metadataUi) | Key-value pairs representing the data fields to send in Create or Update requests. Available fields depend on the selected Module and include typical attributes like name, email, phone, status, etc. Values can be strings, dates, numbers, or selectable options depending on the field. |
| Type of Data | For Update and List operations, specifies the type of data to send. Currently supports only "Query" (query parameters). |
| Query Parameters (arguments) | Key-value pairs to specify query parameters for GET or PATCH requests, allowing filtering or other query-based modifications. |
Output
The node outputs the JSON response returned by the 8Thsense API for the requested operation. This typically includes the created, updated, retrieved, or deleted resource data as JSON objects.
If the API returns binary data (not indicated in this implementation), it would be handled accordingly, but this node focuses on JSON responses.
Dependencies
- Requires an API key credential for authenticating with the 8Thsense API.
- The base URL and authorization token are obtained from the configured credentials.
- The node uses standard HTTP methods (GET, POST, PATCH, DELETE) to interact with the API endpoints corresponding to the selected module.
Troubleshooting
- Failed to fetch users/procedures/etc.: Indicates issues retrieving dynamic option lists for certain fields. Check API credentials and network connectivity.
- Unexpected response format: The API response did not match expected JSON array structure; verify API endpoint availability and correctness.
- Failed to parse metadata value: Occurs if a metadata field value is expected to be JSON but is malformed. Ensure that JSON strings are correctly formatted.
- API request errors: Errors during the API call will throw descriptive messages. Common causes include invalid IDs, missing required fields, or authentication failures. Verify input parameters and API credentials.
- Missing ID for operations requiring it: Update, Delete, and Get One require an ID parameter. Omitting it will cause errors.
Links and References
- n8n Documentation - Expressions
- 8Thsense API documentation (not provided here; consult your API provider for detailed docs)