Surense icon

Surense

Interact with Surense API

Actions36

Lead → Get a Lead

AI-generated

Overview

The node named "Surense" provides integration with the Surense API, allowing users to interact with various resources such as Leads, Contacts, Customers, and more. Specifically, for the "Lead" resource and the "Get a Lead" operation, this node fetches detailed information about a single lead identified by its unique ID (UUID format). This is useful in scenarios where you want to retrieve up-to-date lead data from Surense for further processing, reporting, or automation within an n8n workflow.

Practical examples include:

  • Fetching lead details to enrich customer profiles.
  • Retrieving lead status or source information before triggering follow-up actions.
  • Integrating lead data into CRM systems or marketing automation tools.

Properties

Name Meaning
מזהה ליד The lead ID in UUID format used to specify which lead to retrieve. Example: 123e4567-e89b-12d3-a456-426614174000

Output

The output of the node contains a JSON object representing the lead's data retrieved from the Surense API. This typically includes all available fields related to the lead, such as contact information, status, source, interests, and other metadata managed by Surense.

If the node encounters an error during execution and "Continue On Fail" is enabled, the output will contain an error message inside a JSON object under the error key.

No binary data output is indicated in the provided 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.
  • Proper configuration of the Surense OAuth2 credentials in n8n is necessary for successful API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing lead ID: Ensure the lead ID is provided in UUID format.
    • Authentication failures: Verify that the OAuth2 credentials are correctly set up and have not expired.
    • API rate limits or network errors: Check connectivity and Surense API usage limits.

  • Error messages:

    • If the lead ID is invalid or not found, the API may return an error message which will be surfaced in the node output if "Continue On Fail" is enabled.
    • Authentication errors will typically indicate invalid credentials or token expiration; re-authenticate the API connection.

Resolving these usually involves verifying input parameters, refreshing credentials, and ensuring network access.

Links and References

Discussion