Actions24
- 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 scenarios where you want to programmatically track and manage the engagement level or sales pipeline stage of leads within your marketing or sales automation workflows. For example, after a lead attends a meeting or expresses interest, you can update their status to reflect this progress automatically.
Practical examples:
- Automatically mark leads as "Meeting Booked" when a calendar event is created.
- Update multiple leads to "Not Interested" based on campaign responses.
- Close leads as "Closed" once a deal is finalized.
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 an input item and contains either the updated lead information or an error message if the update failed.
If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs an error object with a message describing the failure.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Instantly API.
- The node depends on the Instantly API endpoints for leads management.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Providing invalid or non-existent lead IDs will result in errors or no updates.
- Incorrectly formatted lead IDs (not comma-separated) may cause request failures.
Error messages:
- Errors from the Instantly API will be surfaced in the output JSON under an
errorfield. - If the node fails to fetch leads or update statuses, check the API key validity and network connectivity.
- To handle partial failures gracefully, enable "Continue On Fail" so the workflow continues processing other items.
- Errors from the Instantly API will be surfaced in the output JSON under an
Links and References
- Instantly API Documentation (generic link, replace with actual if available)
- n8n documentation on Creating Custom Nodes