SmartLead

Comprehensive SmartLead API integration for email marketing automation

Overview

This node integrates with the SmartLead API to manage leads within email marketing campaigns. Specifically, the Delete operation under the Lead Management resource allows users to remove a lead from a specified campaign. This is useful for cleaning up campaign lists by removing contacts who are no longer relevant or have requested removal.

Practical scenarios include:

  • Removing bounced or invalid leads from an active campaign.
  • Deleting leads who opted out or unsubscribed outside of automated flows.
  • Managing campaign audience dynamically by deleting leads that no longer fit targeting criteria.

Properties

Name Meaning
Campaign ID The unique identifier of the campaign from which the lead will be deleted.
Lead ID The unique identifier of the lead to delete from the specified campaign.
Additional Fields (Not applicable for Delete operation; present in other operations)

Output

The output JSON contains the response data returned by the SmartLead API after attempting to delete the lead. Typically, this will confirm successful deletion or provide error details if the operation failed.

The structure is generally:

{
  "data": {
    // API response fields confirming deletion status or related info
  }
}

No binary data is output by this operation.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or missing Campaign ID or Lead ID parameters will cause request failures.
    • Network connectivity problems can prevent API communication.
    • Insufficient permissions or expired API keys may result in authorization errors.
  • Error messages and resolutions:

    • "404 Not Found": The specified campaign or lead does not exist. Verify IDs.
    • "401 Unauthorized": Authentication failed. Check API key validity and configuration.
    • "400 Bad Request": Parameters are malformed or missing. Ensure required fields are correctly set.
    • If the node throws an error but Continue On Fail is enabled, the error message will be included in the output JSON for that item.

Links and References

Discussion