Actions37
- π― Campaign Management Actions
- π₯ Lead Management Actions
- π§ Email Accounts Actions
- π Analytics & Stats Actions
Overview
This node integrates with the SmartLead API to manage leads, campaigns, email accounts, and analytics for email marketing automation. Specifically, the Lead Management - Get by Email operation allows users to retrieve detailed information about a lead using their email address. This is useful in scenarios where you want to look up a leadβs profile or status quickly based on their email, such as verifying if a lead exists before adding them to a campaign or checking their subscription status.
Practical examples:
- Fetching lead details to personalize follow-up emails.
- Checking if a lead is already unsubscribed before sending new campaigns.
- Retrieving lead data to sync with other CRM systems.
Properties
| Name | Meaning |
|---|---|
| Email Address | The email address of the lead to look up. |
| Additional Fields | Optional parameters to refine the query: |
| - Limit | Number of results to return (default 100). |
| - Offset | Number of results to skip (default 0). |
| - Status | Filter leads by campaign status; options are Active, Paused, or Stopped (default Active). |
Output
The node outputs JSON data representing the lead(s) found by the specified email address. The structure typically includes lead details such as contact information, campaign participation, status, and possibly message history depending on the API response.
If multiple leads match (depending on API behavior), an array of lead objects is returned. Each object contains fields relevant to the lead's profile and campaign engagement.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the SmartLead API via an API key credential configured in n8n.
- The node makes authenticated HTTP requests to
https://server.smartlead.ai/api/v1. - Proper API permissions must be granted to access lead data.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid or non-existent email address may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors from the API (e.g., 404 Not Found if the lead does not exist) will be surfaced as node execution errors.
- If "Continue On Fail" is enabled, errors will be returned as JSON objects with an
errorfield describing the issue.
Resolutions:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Ensure the email address input is valid and properly formatted.
- Check network connectivity and SmartLead service status.
Links and References
- SmartLead API Documentation (assumed URL based on baseURL)
- n8n Documentation on HTTP Request Node for understanding request handling
- General best practices for email marketing and lead management