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 resources such as applications, documents, document types, tags, and tag values. Specifically, for the Document resource with the Get Many operation, it retrieves multiple documents from the CRM system. Users can optionally filter these documents by an application ID.

Typical use cases include:

  • Fetching all documents related to a specific application for review or processing.
  • Bulk retrieval of documents for reporting or data synchronization tasks.
  • Automating workflows that require access to document metadata stored in Exante CRM.

For example, a user might want to retrieve all documents linked to a particular loan application to verify submitted paperwork before approval.

Properties

Name Meaning
Environment Selects the API environment to connect to: Production, Staging, or Custom.
Custom API URL (Shown only if Environment is "Custom") The base URL for the custom API endpoint.
Custom Auth URL (Shown only if Environment is "Custom") The OAuth2 token endpoint URL for authentication.
Application ID (Optional) Filter documents by this application ID to retrieve only documents related to it.

Output

The node outputs an array of JSON objects representing documents retrieved from the Exante CRM API. Each item corresponds to one document's data structure as returned by the API.

  • The json field contains the document details such as document ID, type, associated application, metadata, and other relevant fields.
  • If no documents match the filter criteria, the output will be an empty array.
  • The node does not output binary data for this operation.

Dependencies

  • Requires an API key credential configured with OAuth2 authentication to access the Exante CRM API.
  • Supports connecting to predefined environments (Production, Staging) or a custom API URL with a corresponding custom OAuth2 token endpoint.
  • No additional external dependencies beyond the Exante CRM API and proper credential setup.

Troubleshooting

  • Missing or invalid Application ID filter: If filtering by application ID, ensure the ID is correctly specified; otherwise, the node may return no documents.
  • Custom environment configuration errors: When using a custom environment, both the Custom API URL and Custom Auth URL must be provided and valid URLs.
  • Authentication failures: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions to read documents.
  • API rate limits or network issues: The node implements retry logic with exponential backoff on failures, but persistent network or API errors will cause execution errors.
  • Error messages like "Operation getAll not supported for resource document": This indicates a mismatch between selected resource and operation; verify correct selections.

Links and References

  • Exante CRM API Documentation (example placeholder link)
  • OAuth2 Authentication Guide for Exante CRM
  • n8n Documentation on Creating Custom Nodes and Using Credentials

Discussion