SmartLeadInstall

Overview

This node integrates with the SmartLead API to manage email marketing campaigns, leads, email accounts, analytics, smart delivery tests, webhooks, and smart sender domains. Specifically, for the Email Accounts resource with the Add to Campaign operation, it allows users to add an existing email account to a specified campaign. This is useful in scenarios where you want to assign or associate particular email accounts to campaigns for sending emails or managing warmup settings.

Practical example:

• You have multiple email accounts configured in SmartLead and want to include one or more of these accounts into a specific email campaign to start sending emails from those accounts as part of that campaign.

Properties

Note: The "Email Account ID" property is required but not explicitly listed in your provided properties snippet; it is used internally by the node when performing this operation.

Output

The node outputs JSON data representing the response from the SmartLead API after adding the email account to the campaign. The output structure typically includes details about the updated campaign-email account association or confirmation of the addition.

• The json output field contains the API response data under a data property.
• No binary data output is involved in this operation.

Example output JSON structure (simplified):

{
  "data": {
    "email_account_id": "string",
    "campaign_id": "string",
    "status": "string",
    ...
  }
}

Dependencies

• Requires an active SmartLead API key credential configured in n8n for authentication.
• The node makes HTTP requests to the SmartLead API endpoint at https://server.smartlead.ai/api/v1.
• Proper permissions on the API key are necessary to modify email accounts and campaigns.

Troubleshooting

• Invalid Campaign ID or Email Account ID: If either ID is incorrect or does not exist, the API will return an error. Verify IDs before running the node.
• Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
• JSON Parsing Errors: Although this operation does not require JSON input beyond simple parameters, other operations might fail if JSON inputs are malformed.
• API Rate Limits: Excessive requests may lead to rate limiting; consider adding delays or handling retries.
• Network Issues: Connectivity problems can cause request failures; verify network access to the SmartLead API.

Common error message example:

• "Invalid JSON in ..." — indicates malformed JSON input in other operations, not typical for this operation.
• "Unauthorized" — check API credentials.
• "Not Found" — verify campaign and email account IDs.

Links and References

• SmartLead API Documentation (hypothetical link based on base URL)
• n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)
• SmartLead official website for further product details and support.

If you need summaries for other resources or operations, feel free to ask!