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 operation retrieves detailed information about a single tag value by its unique ID.

Typical use cases include:

  • Fetching metadata or details of a specific tag value associated with CRM objects.
  • Integrating tag value data into workflows for reporting, validation, or further processing.
  • Automating retrieval of tag values to synchronize with other systems or databases.

For example, you might use this node to get the details of a tag value that categorizes a customer or application, then use that data downstream in your automation.

Properties

Name Meaning
Environment Selects the API environment to connect to: Production, Staging, or Custom API URL.
Custom API URL (Shown only if Environment is Custom) The base URL of the custom API (the /api prefix is added automatically).
Custom Auth URL (Shown only if Environment is Custom) The OAuth2 token endpoint URL for authentication.
Tag Value ID The unique identifier of the tag value to retrieve (required).

Output

The output contains a JSON object representing the retrieved tag value's details as returned by the Exante CRM API. This typically includes fields such as the tag name, associated object ID, model type, text or date values, and any other metadata related to the tag value.

If multiple items were processed (e.g., via input items), the output will be an array of such JSON objects, each corresponding to one tag value.

The node does not output binary data.

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 custom OAuth2 token endpoint.
  • The node internally manages OAuth2 token acquisition and refresh using the provided credentials and URLs.

Troubleshooting

  • Missing Tag Value ID: If the "Tag Value ID" property is empty, the node throws an error indicating this field is required. Ensure you provide a valid ID.
  • Invalid Custom URLs: When using the Custom environment, both the Custom API URL and Custom Auth URL must be provided; otherwise, the node will error out.
  • Authentication Failures: Errors during token acquisition usually indicate misconfigured credentials or incorrect auth URLs. Verify your API key and OAuth2 settings.
  • API Errors: If the API returns errors (e.g., tag value not found), these are surfaced in the node output as error messages.
  • JSON Parsing Issues: Not applicable for this operation but relevant for other operations involving JSON input.

Links and References

Discussion