Surense icon

Surense

Interact with Surense API

Actions36

Customer → Get a Customer

AI-generated

Overview

This node integrates with the Surense API, allowing users to interact with various Surense resources such as customers, activities, contacts, and more. Specifically, for the "Customer" resource and the "Get a Customer" operation, it retrieves detailed information about a single customer by their unique identifier (UUID). This is useful in scenarios where you need to fetch up-to-date customer data for processing, reporting, or further automation within your workflows.

Practical examples include:

  • Fetching customer details before updating records in a CRM.
  • Retrieving customer information to personalize communications.
  • Using customer data to trigger conditional workflow branches.

Properties

Name Meaning
מזהה לקוח The customer ID in UUID format used to specify which customer's details to retrieve.

Output

The node outputs JSON data representing the customer details retrieved from the Surense API. The structure typically includes all relevant fields of the customer record as defined by the API, such as name, contact information, status, source, and other metadata.

If the node encounters an error during execution and "continue on fail" is enabled, it outputs an object containing an error field with the error message.

No binary data output is indicated.

Dependencies

  • Requires an active connection to the Surense API via an OAuth2 API credential.
  • The node depends on proper configuration of this API authentication within n8n.
  • No additional external dependencies are required beyond the Surense API access.

Troubleshooting

  • Common issues:

    • Invalid or missing customer ID (UUID) will cause the API call to fail.
    • Authentication errors if the OAuth2 credentials are not set up correctly or have expired.
    • Network connectivity problems preventing access to the Surense API.

  • Error messages:

    • Errors returned from the API are passed through; typical messages might indicate invalid IDs or permission issues.
    • If "continue on fail" is disabled, the node will stop execution on errors; enabling it allows workflows to continue while capturing error details in the output.

  • Resolutions:

    • Verify the customer ID is correct and in UUID format.
    • Ensure OAuth2 credentials are valid and refreshed.
    • Check network settings and API endpoint accessibility.

Links and References

Discussion