SmartLead

Comprehensive SmartLead API integration for email marketing automation

Actions37

Overview

This node integrates with the SmartLead API to manage email accounts, campaigns, leads, and analytics for email marketing automation. Specifically, the Reconnect Failed operation under the Email Accounts resource attempts to reconnect an email account that previously failed to connect. This is useful in scenarios where an email account connection was lost or interrupted, and you want to restore its functionality without recreating the account.

Practical examples:

  • Automatically retry connecting an email account after temporary network issues.
  • Restore email sending capabilities for accounts that were disconnected due to authentication errors.
  • Maintain continuous campaign execution by ensuring all email accounts are active.

Properties

Name Meaning
Email Account ID The unique identifier of the email account to reconnect.
Additional Fields A collection of optional parameters:
- Limit Number of results to return (used in other operations, not relevant here).
- Offset Number of results to skip (used in other operations, not relevant here).
- Status Campaign status filter with options: Active, Paused, Stopped (used in other operations).

For this specific operation ("Reconnect Failed" on "Email Accounts"), only Email Account ID is required and used.

Output

The node outputs JSON data representing the response from the SmartLead API after attempting to reconnect the specified email account. The structure typically includes details about the email account's current state post-reconnection attempt.

Example output JSON structure (simplified):

{
  "id": "string",
  "email": "string",
  "status": "string",
  "lastConnectionAttempt": "timestamp",
  "message": "string"
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the SmartLead API.
  • The node makes HTTP requests to https://server.smartlead.ai/api/v1.
  • Proper configuration of the API credential within n8n is necessary for successful requests.

Troubleshooting

  • Common Issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Providing a non-existent or incorrect Email Account ID will result in errors indicating the account was not found.
    • Network connectivity problems can prevent the node from reaching the SmartLead API endpoint.

  • Error Messages:

    • "401 Unauthorized": Check that the API key credential is valid and has proper permissions.
    • "404 Not Found": Verify the Email Account ID is correct and exists in your SmartLead account.
    • "500 Internal Server Error" or timeouts: Retry later or check SmartLead service status.

  • Resolution Tips:

    • Ensure the Email Account ID is copied exactly as provided by SmartLead.
    • Confirm API credentials are up to date and correctly configured in n8n.
    • Test network connectivity and proxy settings if applicable.

Links and References

Discussion