Actions74
- šÆ Campaign Management Actions
- š„ Lead Management Actions
- š§ Email Accounts Actions
- š Analytics & Stats Actions
- š Smart Delivery Actions
- Get Region Provider IDs
- Create Manual Placement Test
- Create Automated Placement Test
- Get Spam Test Details
- Delete Tests in Bulk
- Stop Automated Test
- List All Tests
- Get Provider Report
- Get Geo Report
- Get Sender Account Report
- Get Spam Filter Report
- Get DKIM Details
- Get SPF Details
- Get rDNS Report
- Get Sender Account List
- Get Blacklists
- Get Domain Blacklist
- Get Spam Test Email Content
- Get Email Reply Headers
- Get Schedule History
- Get IP Details
- Get Mailbox Summary
- Get Mailbox Count
- Get All Folders
- Create Folder
- Get Folder by ID
- Delete Folder
- š Webhooks Actions
- šØ Smart Senders Actions
Overview
The "Add to Campaign" operation in the Lead Management resource allows users to add one or multiple leads to a specified email marketing campaign using the SmartLead API. This node is useful for automating lead ingestion into campaigns, enabling targeted email outreach and follow-up sequences.
Typical scenarios include:
- Importing new leads collected from forms or CRM systems into an active email campaign.
- Batch adding multiple leads at once to scale marketing efforts.
- Automating lead management workflows by integrating with other data sources.
For example, you can provide a single lead's details or an array of leads in JSON format, and this node will add them to the chosen campaign identified by its ID.
Properties
| Name | Meaning |
|---|---|
| Campaign ID | The unique identifier of the campaign to which leads will be added. |
| Lead Data | Lead information in JSON format. Can be a single lead object or an array of lead objects (max 350 per batch). Example: Single lead: { "email": "john@example.com", "first_name": "John", "last_name": "Doe", "company": "Example Corp" } or Multiple leads: [ {...}, {...} ]. |
| Additional Fields | Collection of optional fields including: - Limit: Number of results to return (used in some operations). - Offset: Number of results to skip. - Status: Campaign status filter with options: Active, Paused, Stopped. (Note: These additional fields are generally used in other operations but available here as part of the schema.) |
Output
The node outputs the response from the SmartLead API call under the json field. This typically contains the data returned by the API after adding leads to the campaign, such as confirmation of added leads or any relevant metadata.
The output is structured as an array of JSON objects representing the API response data. If multiple input items are processed, each item's result is included separately.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the SmartLead API.
- The base URL for API requests is
https://server.smartlead.ai/api/v1. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Invalid JSON in Lead Data: If the provided lead data JSON is malformed, the node throws an error indicating invalid JSON. Ensure that the lead data is correctly formatted JSON before running the node.
- API Authentication Errors: Failure to authenticate with the SmartLead API usually indicates missing or incorrect API credentials. Verify that the API key credential is configured properly.
- Batch Size Limits: The node supports up to 350 leads per batch. Sending more than this may cause errors or rejected requests.
- Campaign ID Issues: Providing an incorrect or non-existent campaign ID will result in API errors. Double-check the campaign ID value.
- Network or API Downtime: Network issues or SmartLead API downtime can cause request failures. Check connectivity and service status if errors persist.
Links and References
- SmartLead API Documentation (Assumed based on base URL; verify actual documentation link)
- n8n Documentation on Creating Custom Nodes
- JSON formatting guides for preparing lead data payloads