Actions12
Overview
This node integrates with the Wortic CRM API to manage client records among other resources like leads and calendar events. Specifically, the "Client" resource with the "Get" operation allows users to retrieve detailed information about a single client by specifying its unique record ID.
Common scenarios for this node include:
- Fetching client details to display or process in workflows.
- Integrating client data retrieval into automated pipelines for reporting or synchronization.
- Using client information as input for further operations such as updates or invoicing.
For example, a user might use this node to get a client's contact information by providing the client's ID, then use that data to send personalized emails or update related records.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the client record to retrieve. This is required to specify which client to fetch from the CRM. |
Output
The node outputs JSON data representing the client record retrieved from the Wortic CRM API. The structure of the JSON corresponds directly to the client data returned by the API, typically including fields such as client name, email, and any other stored attributes.
No binary data output is produced by this operation.
Example output JSON (simplified):
{
"id": "12345",
"name": "Acme Corporation",
"email": "contact@acme.com",
...
}
Dependencies
- Requires an API key credential for authenticating with the Wortic CRM API.
- The node expects the base URL of the Wortic API to be configured in the credentials.
- HTTP POST requests are made to the API endpoint with JSON payloads.
Troubleshooting
- Missing or invalid ID: If the "ID" property is not provided or incorrect, the API will likely return an error indicating the record was not found. Ensure the correct client ID is used.
- Authentication errors: If the API key credential is missing, expired, or invalid, authentication will fail. Verify the API key and credential configuration.
- API connectivity issues: Network problems or incorrect API URL settings can cause request failures. Confirm the API URL and network access.
- Unexpected API responses: If the API changes or returns unexpected data, the node may not behave as expected. Check the API documentation and update the node or workflow accordingly.
Links and References
- Wortic CRM API Documentation (refer to official Wortic API docs for detailed endpoints and data structures)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are handled within n8n)