Actions37
- 🎯 Campaign Management Actions
- 👥 Lead Management Actions
- 📧 Email Accounts Actions
- 📊 Analytics & Stats Actions
Overview
This node integrates with the SmartLead API to manage email marketing campaigns. Specifically, the 🎯 Campaign Management - Get All operation retrieves a list of email campaigns from the SmartLead platform. It allows users to fetch multiple campaigns with optional filtering by status, pagination through limit and offset parameters.
Typical use cases include:
- Fetching all active email campaigns to monitor or analyze their performance.
- Retrieving paused or stopped campaigns for review or reactivation.
- Integrating campaign data into dashboards or other automation workflows.
For example, a marketing team could use this node to automatically pull all active campaigns every day and update their internal reporting system.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional filters and pagination controls: |
| - Limit | Number of results to return (default 100) |
| - Offset | Number of results to skip before starting to collect results (default 0) |
| - Status | Filter campaigns by status; options are: Active, Paused, Stopped (default: Active) |
Output
The output is a JSON array where each item represents a campaign object returned by the SmartLead API. The exact structure depends on the API response but typically includes campaign details such as ID, name, status, schedule, and other metadata.
No binary data is output by this operation.
Example output snippet (simplified):
[
{
"id": "campaign_123",
"name": "Spring Sale Campaign",
"status": "ACTIVE",
"created_at": "2024-01-10T12:00:00Z",
...
},
{
"id": "campaign_456",
"name": "Winter Promo",
"status": "PAUSED",
"created_at": "2023-12-01T08:30:00Z",
...
}
]
Dependencies
- Requires an API key credential for authenticating with the SmartLead API.
- The node uses the base URL
https://server.smartlead.ai/api/v1. - No additional environment variables are needed beyond the API authentication setup in n8n.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Request limits or offsets that exceed available data may return empty arrays.
- Network connectivity problems can cause request failures.
Error messages:
"401 Unauthorized": Check that the API key credential is correctly configured and valid."404 Not Found": Usually means the endpoint or resource does not exist; verify the resource and operation selection."400 Bad Request": Often caused by invalid parameter values; ensure limit, offset, and status are set properly.
To resolve errors, verify API credentials, check parameter values, and ensure network access to the SmartLead API endpoint.
Links and References
- SmartLead API Documentation (hypothetical link)
- n8n documentation on API integrations