Exante CRM icon

Exante CRM

Interact with Exante CRM API to manage applications, documents, and more
Join our community

Actions11

Overview

This node integrates with the Exante CRM API, enabling users to manage various CRM entities such as applications, documents, tags, and document types. Specifically, for the Document - Get operation, it retrieves a single document by its unique identifier.

Typical use cases include:

  • Fetching detailed information about a specific document stored in the CRM.
  • Automating workflows that require document data retrieval for processing or reporting.
  • Integrating document data into other systems or processes via n8n automation.

For example, you might use this node to get a contract document by its ID after an application is approved, then send it via email or archive it.

Properties

Name Meaning
Environment Selects the API environment to connect to: Production, Staging, or Custom (custom URLs).
Custom API URL When using a custom environment, specify the base API URL here (e.g., https://api.example.com). The /api prefix is added automatically.
Custom Auth URL When using a custom environment, specify the OAuth2 token endpoint URL for authentication.
Document ID The unique identifier of the document to retrieve. This is required for the "Get" operation on the Document resource.

Output

The node outputs JSON data representing the requested document's details as returned by the Exante CRM API. The structure typically includes all relevant fields of the document entity, such as metadata, content references, status, timestamps, and related application IDs.

If multiple items are processed, the output is an array of objects each containing a json property with the document data.

The node does not output binary data for this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests to the Exante CRM API.
  • Supports connecting to predefined environments (Production, Staging) or a custom API URL with corresponding custom OAuth2 token endpoint.
  • Relies on the Exante CRM API being accessible and properly configured for the selected environment.

Troubleshooting

  • Missing Document ID: If the Document ID property is empty, the node will throw an error indicating that the Document ID is required. Ensure this field is filled with a valid document identifier.
  • Invalid Custom URLs: When using the custom environment option, both the Custom API URL and Custom Auth URL must be provided and valid URLs. Omitting these or providing invalid URLs will cause errors.
  • Authentication Failures: Errors related to obtaining or refreshing the access token may occur if the API credentials are incorrect or expired. Verify the API key or OAuth2 credentials setup.
  • API Connectivity Issues: Network problems or incorrect environment selection can lead to failed API calls. Confirm network access and correct environment choice.
  • Unexpected API Errors: The node retries failed requests up to three times with exponential backoff. Persistent failures will return error details in the output JSON under an error field.

Links and References

Discussion