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 Pause operation under the Lead Management resource allows users to pause a lead's activity in a given campaign. Pausing a lead typically means temporarily halting any ongoing automated email sequences or interactions for that lead without removing them from the campaign.

Common scenarios where this is useful:

  • Temporarily suspending communication with a lead due to external factors (e.g., lead requested a temporary hold).
  • Managing leads who are on hold before resuming engagement later.
  • Controlling campaign flow dynamically based on lead status changes.

Practical example:
You have an active email campaign and want to pause a specific lead’s participation because they requested a break from emails. Using this node’s Pause operation, you specify the campaign ID and lead ID to pause their activity without deleting or unsubscribing them.


Properties

Name Meaning
Campaign ID The unique identifier of the campaign in which the lead is participating.
Lead ID The unique identifier of the lead to be paused within the specified campaign.
Additional Fields (Not applicable for Pause operation; present for other operations)

Output

The node outputs JSON data representing the response from the SmartLead API after attempting to pause the lead. This typically includes details about the lead’s updated status or confirmation of the pause action.

The output structure is an array of JSON objects, each corresponding to an input item processed. Each object contains the API response data under the json field.

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 the base URL: https://server.smartlead.ai/api/v1.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Campaign ID or Lead ID parameters will cause the API request to fail.
    • Network connectivity problems can prevent successful API calls.
    • Insufficient permissions or invalid API credentials may result in authorization errors.
  • Common error messages:

    • "404 Not Found": The specified campaign or lead does not exist. Verify IDs.
    • "401 Unauthorized": Authentication failed. Check API key validity and permissions.
    • "400 Bad Request": Parameters are malformed or missing. Ensure required fields are correctly set.
  • Resolution tips:

    • Double-check that the Campaign ID and Lead ID correspond to existing entities in SmartLead.
    • Confirm that the API key credential is correctly configured and has necessary access rights.
    • Review network settings and proxy configurations if requests time out or fail to connect.

Links and References

  • SmartLead API Documentation (Assumed typical location; replace with actual if known)
  • n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)
  • General best practices for managing leads in email marketing campaigns (various marketing automation resources)

Discussion