Actions15
- Account Actions
- Analytics Actions
- Campaign Actions
- Lead Actions
Overview
This node integrates with the Instantly API to add a lead to a specified campaign. It is useful for marketing automation workflows where you want to programmatically enroll leads into email or outreach campaigns based on triggers or data from other systems.
Typical use cases include:
- Automatically adding new contacts collected from forms or CRM systems into targeted campaigns.
- Personalizing campaign messages by including custom fields and personalized text per lead.
- Managing lead lists dynamically without manual intervention.
For example, after capturing a lead's information via a web form, this node can add that lead to a specific campaign in Instantly, optionally customizing the message and setting custom field values for better targeting.
Properties
Name | Meaning |
---|---|
Campaign | The campaign to which the lead will be added. Choose from a searchable list or specify by ID. |
The email address of the lead to add. | |
First Name | The lead's first name. |
Last Name | The lead's last name. |
Personalization | A personalization message for campaign-specific messaging to customize communication. |
Custom Fields | Custom key-value pairs for additional campaign personalization. You can add multiple fields, each with a name and value. |
Output
The node outputs JSON data representing the result of the operation. This typically includes confirmation details about the lead being added to the campaign or any error messages if the operation failed.
The output JSON structure corresponds to the Instantly API response for adding a lead to a campaign, which may include identifiers, status, and any relevant metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Instantly API.
- Needs network access to Instantly's REST API endpoints.
- Uses internal helper functions to make HTTP requests and handle pagination (though pagination is not relevant for this operation).
- The node depends on n8n's resource locator UI components to select campaigns and email accounts.
Troubleshooting
- Invalid Campaign ID or Email: If the campaign ID or email is incorrect or missing, the API call will fail. Ensure these are correctly provided.
- API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify the API key is set up properly in n8n credentials.
- Rate Limits or Quotas: The Instantly API may enforce rate limits; hitting these could cause errors. Implement retry logic or reduce request frequency.
- Custom Field Format Issues: Custom fields must be provided as key-value string pairs. Incorrect formatting may cause the API to reject the request.
- Required Fields Missing: Email, first name, last name, and campaign are required. Omitting any will likely cause errors.
If the node throws errors, check the error message included in the output JSON for clues, and verify all required parameters are correctly set.
Links and References
- Instantly API Documentation (general reference for API endpoints)
- n8n documentation on Creating Custom Nodes
- n8n community forums for troubleshooting and examples
This summary is based solely on static analysis of the provided source code and property definitions.