Actions25
Overview
This node integrates with the EspoCRM API to perform operations on CRM entities. Specifically, for the Contact resource and the Get operation, it retrieves a single contact record by its unique ID. This is useful when you need to fetch detailed information about a specific contact stored in EspoCRM.
Common scenarios:
- Fetching contact details to enrich customer data in workflows.
- Retrieving a contact's information before updating or processing it further.
- Integrating EspoCRM contacts into other systems by pulling their data dynamically.
Example:
You have a workflow that triggers when a new order is placed, and you want to retrieve the customer's contact details from EspoCRM using their Contact ID to personalize communications or verify information.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. This is required to specify which contact record to get from EspoCRM. |
Output
The node outputs an array of JSON objects representing the retrieved contact(s). For the Get operation on a Contact, the output will be a single JSON object containing all available fields of the specified contact as returned by the EspoCRM API.
The structure typically includes standard contact fields such as name, email, phone number, address, and any custom fields defined in your EspoCRM instance.
If the node supports binary data (not indicated here), it would represent attachments or files related to the contact, but this operation primarily returns JSON data.
Dependencies
- Requires an active connection to an EspoCRM instance via an API key credential configured in n8n.
- The node uses the EspoCRM REST API; therefore, the EspoCRM server must be accessible from where n8n runs.
- No additional external services are needed beyond EspoCRM itself.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: The node requires a valid contact ID; ensure the ID exists in EspoCRM.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network connectivity: Ensure n8n can reach the EspoCRM server URL.
Error messages:
"The operation "get" is not supported for resource type "contact": This indicates a misconfiguration; confirm the resource and operation selections.- API errors like
404 Not Foundusually mean the Contact ID does not exist. - Timeout or connection errors suggest network or server availability problems.
To resolve these, double-check input parameters, credentials, and network settings.