Actions25
Overview
This node integrates with the EspoCRM API to perform various operations on CRM entities dynamically. Specifically, for the "Dynamic" resource and the "Get" operation, it retrieves a single record of a specified entity type by its record ID.
Common scenarios where this node is useful include:
- Fetching detailed information about a specific CRM record when you know its unique ID.
- Integrating EspoCRM data retrieval into automated workflows, such as syncing contact or lead details with other systems.
- Dynamically accessing custom or standard entity records without hardcoding entity types.
Example: You want to retrieve a particular "Opportunity" record from EspoCRM by its ID to update your sales dashboard automatically.
Properties
| Name | Meaning |
|---|---|
| Entity Type Name or ID | The type of entity to interact with (e.g., Account, Contact, Opportunity). Choose from a list or specify an ID using an expression. |
| Record ID | The unique identifier of the record to retrieve within the specified entity type. |
Output
The node outputs a JSON array where each item corresponds to the retrieved record(s). For the "Get" operation on the "Dynamic" resource, the output is a single JSON object representing the requested record's fields and values as returned by the EspoCRM API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "record-id",
"name": "Record Name",
"field1": "value1",
"field2": "value2",
...
}
Dependencies
- Requires an active connection to an EspoCRM instance via an API key credential configured in n8n.
- Uses EspoCRM REST API endpoints corresponding to the selected entity type and record ID.
- The node depends on internal helper functions to make authenticated HTTP requests to EspoCRM.
Troubleshooting
Common issues:
- Invalid or missing record ID will cause the API request to fail.
- Specifying an incorrect or unsupported entity type may result in errors or empty responses.
- Network connectivity problems or incorrect API credentials will prevent successful communication with EspoCRM.
Error messages:
"The operation "get" is not supported for resource type "dynamic": This indicates a misconfiguration; ensure the resource is set to "dynamic" and operation to "get".- API errors returned from EspoCRM (e.g., 404 Not Found) usually mean the record ID does not exist or access is denied.
Resolution tips:
- Verify the entity type and record ID are correct and exist in EspoCRM.
- Check that the API credentials are valid and have sufficient permissions.
- Use expressions carefully to ensure dynamic values resolve correctly.