Instantly

Overview

This node integrates with the Instantly API to perform operations on various resources, including Leads. Specifically, the "Get" operation for the Lead resource retrieves detailed information about a single lead identified by its unique ID. This is useful in scenarios where you want to fetch up-to-date data about a specific lead from your marketing or sales campaigns, such as retrieving contact details, status, or other metadata.

Practical examples include:

• Fetching lead details before sending a personalized email.
• Retrieving lead information to update CRM records.
• Using lead data to trigger conditional workflows based on lead attributes.

Properties

The "Lead" property supports two modes:

• From List: Search and select a lead from a dropdown populated dynamically via the API.
• By ID: Enter the lead's UUID manually, validated against the standard UUID regex pattern.

Output

The node outputs JSON data representing the lead's details as returned by the Instantly API. The structure typically includes fields such as the lead's first name, last name, email, ID, and potentially other metadata related to the lead.

If multiple items are processed, the output is an array of JSON objects, each corresponding to one lead's data.

No binary data output is indicated for this operation.

Dependencies

• Requires an API key credential for authenticating with the Instantly API.
• The node depends on the Instantly API endpoints, specifically /api/v2/leads/list for listing leads and presumably /api/v2/leads/{id} or similar for fetching individual lead details.
• Proper configuration of the API credential within n8n is necessary for successful requests.

Troubleshooting

• Invalid Lead ID Format: If the lead ID does not match the UUID format, the node will reject it. Ensure the ID is a valid UUID string.
• API Request Failures: Network issues or invalid API credentials may cause errors when fetching lead data. Verify API keys and network connectivity.
• Empty Lead Selection: When using the "From List" mode, if no leads appear, check that leads exist in the Instantly account and that the API has permission to access them.
• Error Messages: Errors thrown by the node will include messages from the Instantly API or internal request failures. Enabling "Continue On Fail" allows the workflow to proceed despite individual item errors, returning error details in the output JSON.

Links and References

• Instantly API Documentation (general reference for API endpoints)
• UUID Format Explanation

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.