EspoCRM icon

EspoCRM

Interact with EspoCRM API

Actions25

Overview

This node integrates with the EspoCRM API to perform various operations on CRM entities. Specifically, for the Account resource with the Get operation, it retrieves a single account record by its unique ID. This is useful when you need to fetch detailed information about a specific account stored in EspoCRM.

Common scenarios include:

  • Retrieving customer or client account details before processing orders.
  • Fetching account data to display or update in other systems.
  • Integrating EspoCRM account data into workflows that require account verification or enrichment.

Example: Given an Account ID, the node will call the EspoCRM API to return all available fields of that account as a JSON object.

Properties

Name Meaning
Account ID The unique identifier of the account to retrieve. This is a required string input.

Output

The output is a JSON array where each element corresponds to one retrieved account record (in this case, always one). Each element contains the full account data as returned by the EspoCRM API, including all standard and custom fields associated with that account.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "id": "123",
    "name": "Acme Corporation",
    "email": "contact@acme.com",
    "phone": "123-456-7890",
    "address": "123 Main St",
    "...": "..."
  }
]

Dependencies

  • Requires an active connection to an EspoCRM instance via an API key or authentication token configured in n8n credentials.
  • The node depends on the EspoCRM REST API being accessible and properly configured.
  • No additional external services are required beyond EspoCRM itself.

Troubleshooting

  • Error: "The operation 'get' is not supported for resource type 'account'"
    This indicates a misconfiguration or unsupported operation. Verify that the Resource is set to "Account" and Operation to "Get".

  • API Authentication Errors
    Ensure the API credentials are correctly set up in n8n and have sufficient permissions to read account data.

  • Invalid Account ID
    If the provided Account ID does not exist or is malformed, the API will return an error. Double-check the ID value.

  • Network or Connectivity Issues
    Confirm that the EspoCRM server URL is reachable from the n8n environment.

  • Continue On Fail Behavior
    If enabled, errors during execution will be captured in the output as error messages instead of stopping the workflow.

Links and References

Discussion