Instantly icon

Instantly

Interact with Instantly API

Actions15

Overview

This node interacts with the Instantly API to retrieve detailed information about a specific lead. The "Get Lead" operation fetches data for one lead identified by its unique ID or selected from a list of leads. This is useful in scenarios where you want to enrich your workflow with up-to-date lead details, such as contact information, status, or other metadata stored in Instantly.

Practical examples include:

  • Fetching lead details before sending a personalized email.
  • Retrieving lead information to update CRM records.
  • Using lead data to trigger conditional logic in automation workflows.

Properties

Name Meaning
Lead The lead to operate on. You can select a lead from a searchable list or specify the lead by its unique ID (UUID format).

The "Lead" property supports two modes:

  • From List: Search and select a lead from existing leads.
  • By ID: Provide the lead's UUID directly (must match the pattern ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$).

Output

The output is a JSON array containing the lead's data as returned by the Instantly API. Each item corresponds to one lead object with all available fields provided by the API, such as name, email, status, and any custom attributes.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Instantly API.
  • The node makes HTTP GET requests to the /api/v2/leads/{leadId} endpoint.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Invalid Lead ID Format: If the lead ID does not match the UUID regex pattern, the node will reject it. Ensure the ID is correctly formatted.
  • Lead Not Found: If the specified lead ID does not exist, the API may return an error or empty response. Verify the lead exists in Instantly.
  • API Rate Limits: Excessive requests might be throttled by the Instantly API. Implement retry logic or reduce request frequency.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Limitations on Pagination: Although pagination is implemented for listing leads, the "Get Lead" operation fetches a single lead only.

If the node is set to continue on fail, errors will be returned as JSON objects with an error field describing the issue.

Links and References

Discussion