Surense icon

Surense

Interact with Surense API

Actions36

Customer → Get Customer Portfolio History

AI-generated

Overview

The node named "Surense" provides an interface to interact with the Surense API, enabling automation workflows to perform various operations on multiple resources such as Customers, Activities, Contacts, Documents, and more. Specifically, for the Customer resource and the Get Customer Portfolio History operation, this node fetches historical portfolio data related to a specified customer.

This functionality is useful in scenarios where you need to track or analyze changes in a customer's portfolio over time, such as financial advisors monitoring client investments, account managers reviewing customer engagement history, or automated reporting systems generating portfolio summaries.

Example use cases:

  • Automatically retrieving a customer's portfolio history to update dashboards.
  • Triggering alerts based on portfolio changes detected in the history.
  • Integrating customer portfolio data into CRM or ERP systems for enriched customer profiles.

Properties

Name Meaning
מזהה לקוח Customer ID in UUID format; uniquely identifies the customer whose portfolio history is requested.

Output

The node outputs an array of JSON objects corresponding to the results of the executed operation(s). For the "Get Customer Portfolio History" operation, each output item contains the portfolio history data of the specified customer in JSON format.

If an error occurs during execution and the node is configured to continue on failure, the output will include an object with an error field describing the issue.

No binary data output is indicated by the source code.

Dependencies

  • Requires an active connection to the Surense API via OAuth2 authentication (an API key credential).
  • The node depends on internal helper modules for operation execution and pagination, but these are bundled within the node.
  • No additional external dependencies or environment variables are explicitly required beyond the OAuth2 credential setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Customer ID (UUID) may cause the API call to fail.
    • Authentication failures if the OAuth2 token is expired or misconfigured.
    • Network connectivity problems preventing access to the Surense API.

  • Error messages:

    • Errors thrown by the API or network issues will be caught and can be output as JSON with an error message if "Continue On Fail" is enabled.
    • To resolve errors, verify the correctness of the Customer ID, ensure valid OAuth2 credentials, and check network connectivity.

Links and References

Discussion