Actions39
- Campaign Actions
- Campaign Statistic Actions
- Client Actions
- Email Account Actions
- Lead Actions
- Master Inbox Actions
- Webhook Actions
Overview
This node interacts with the Smartlead.ai API to manage campaigns, leads, email accounts, and related entities. Specifically, the "Remove Email Account" operation under the "Campaign" resource allows users to remove one or more email accounts from a specified campaign. This is useful when you want to disassociate certain email accounts from a campaign, for example, if those accounts are no longer active or should not be used for sending emails in that campaign.
Practical examples:
- Removing compromised or inactive email accounts from a campaign to maintain deliverability.
- Managing campaign resources by dynamically adjusting which email accounts participate in a campaign.
- Automating cleanup of email accounts linked to campaigns based on external triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| Campaign ID | The unique identifier of the campaign from which email accounts will be removed. |
| Email Account IDs | A comma-separated list of email account IDs to remove from the campaign (e.g., "2907, 2908"). |
Output
The output is a JSON array representing the response from the Smartlead.ai API after attempting to remove the specified email accounts from the campaign. The exact structure depends on the API's response but typically includes confirmation of removal or details about the updated campaign-email account associations.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Smartlead.ai API.
- The base URL for API requests is
https://server.smartlead.ai/api/v1. - The node uses HTTP DELETE method with a JSON body containing the email account IDs to remove.
Troubleshooting
Common issues:
- Providing invalid or non-existent campaign ID or email account IDs will likely result in errors from the API.
- Improperly formatted email account IDs string (e.g., missing commas or extra spaces) may cause parsing errors.
- Lack of proper API authentication or expired credentials will cause authorization failures.
Error messages:
- Errors returned from the API will be propagated, often indicating invalid parameters or permission issues.
- If the node throws an error about request failure, verify the campaign ID and email account IDs are correct and that the API key is valid.
Resolution tips:
- Ensure the campaign ID exists and is accessible with your API credentials.
- Format the email account IDs as a comma-separated string without trailing commas or invalid characters.
- Check that the API key credential is correctly configured and has necessary permissions.
Links and References
- Smartlead.ai API Documentation (Assumed endpoint documentation)
- n8n Documentation on HTTP Request Node for understanding API calls and authentication setup.