Actions15
- Account Actions
- Analytics Actions
- Campaign Actions
- Lead Actions
Overview
This node integrates with the Instantly API to update the interest status of one or more leads. It is useful in sales and marketing automation workflows where you want to programmatically track and manage the engagement stage of leads, such as marking them as "Interested," "Meeting Booked," or "Not Interested." For example, after a lead responds positively to an outreach email, this node can update their status to "Interested" automatically, helping keep your CRM or lead management system up to date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Interest Status | The new interest status to assign to the lead(s). Options: Out of Office, Interested, Meeting Booked, Meeting Completed, Closed, Not Interested, Wrong Person, Lost |
| Lead IDs | Comma-separated list of lead IDs that you want to update with the selected interest status |
Output
The node outputs JSON data representing the result of the update operation for each lead ID provided. Each output item corresponds to one input item and contains either the updated lead information or an error message if the update failed.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Instantly API.
- Needs network access to Instantly's REST API endpoints.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Providing invalid or empty lead IDs will cause the update to fail.
- Using an interest status value outside the allowed options will result in errors.
- Exceeding API rate limits or providing invalid API credentials will cause authentication errors.
- If the limit on the number of lead IDs is too large (not shown explicitly but common in APIs), the request might be rejected.
Error Messages:
- Errors returned from the Instantly API will be propagated, typically indicating issues like "Lead not found," "Invalid interest status," or "Authentication failed."
- If the node throws an error about exceeding limits, reduce the number of lead IDs per execution.
- To handle intermittent failures, enable the "Continue On Fail" option in the node settings to allow partial success.
Links and References
- Instantly API Documentation (generic link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General best practices for managing lead statuses in CRM systems