Exante CRM icon

Exante CRM

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

Actions11

Overview

This node interacts with the Exante CRM API to manage various CRM entities, including tag values. Specifically, the Tag Value - Get Many operation retrieves multiple tag values from the CRM system, optionally filtered by an object ID.

This operation is useful when you want to fetch all tag values associated with certain objects (e.g., applications or documents) in bulk. For example, you might use it to:

  • Retrieve all tags linked to a specific application or document for reporting or processing.
  • Synchronize tag data between Exante CRM and another system.
  • Analyze or filter CRM records based on their associated tags.

Properties

Name Meaning
Environment Selects the API environment to connect to: Production, Staging, or Custom API URL.
Custom API URL When using a custom environment, specify the base API URL here (the /api prefix is added automatically).
Custom Auth URL When using a custom environment, specify the OAuth2 token endpoint URL for authentication.
Object ID Filter Optional numeric filter to retrieve only tag values associated with a specific object ID.

Output

The output consists of an array of JSON objects representing tag values retrieved from the Exante CRM API. Each item corresponds to one tag value record, containing fields such as tag name, text value, date value, object ID, and model type.

If no input items are provided, the operation executes once and returns all matching tag values (optionally filtered by object ID).

No binary data output is produced by 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 corresponding custom authentication URL.
  • The node uses internal helper classes for managing authentication tokens and making API requests.

Troubleshooting

  • Missing or invalid credentials: Ensure that the API key credential is properly set up and authorized to access the Exante CRM API.
  • Custom environment errors: If using a custom API URL, both the Custom API URL and Custom Auth URL must be provided; otherwise, the node will throw an error.
  • Invalid Object ID filter: The Object ID filter must be a valid number if specified; otherwise, it will be ignored.
  • API connectivity issues: Network problems or incorrect URLs can cause failures; verify the environment URLs and network access.
  • Unexpected errors: The node retries failed requests up to 3 times with exponential backoff. Persistent failures will return error details in the output JSON under an error field.

Links and References

Discussion