Reachkit icon

Reachkit

Interact with the Reachkit API

Actions20

Lead → Get

AI-generated

Overview

The node interacts with the Reachkit API to manage and retrieve data related to various resources, including leads. Specifically, for the Lead - Get operation, it fetches detailed information about a single lead identified by its Lead ID within a specified campaign. This is useful in scenarios where you need to access or verify lead details programmatically, such as integrating lead data into CRM systems, automating follow-ups, or analyzing lead engagement.

Practical examples:

  • Retrieving a lead's contact and status information before sending a personalized email.
  • Fetching lead details to update records in an external database.
  • Validating lead existence and attributes during automated workflows.

Properties

Name Meaning
Campaign ID The unique identifier of the campaign to which the lead belongs.
Lead ID The unique identifier of the lead to retrieve detailed information about.

Output

The output contains a JSON object representing the lead's data retrieved from the Reachkit API. This typically includes all relevant fields associated with the lead, such as contact information, status, timestamps, and any custom attributes defined in the campaign context.

If the node supports binary data output (not indicated here), it would represent attachments or files related to the lead, but this is not evident from the provided code snippet.

Dependencies

  • Requires an active connection to the Reachkit API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://reachkit.ai/api/v1.

Troubleshooting

  • Missing or invalid Campaign ID or Lead ID: Ensure both IDs are correctly provided and correspond to existing entities in Reachkit.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network issues or API downtime: Check network connectivity and Reachkit service status.
  • Unexpected response structure: Confirm that the API version matches the node’s expectations; updates in the API might require node updates.

Links and References

Discussion