SmartLead

Comprehensive SmartLead API integration for email marketing automation

Overview

The "Get Message History" operation under the "Lead Management" resource in this node fetches the message history of leads associated with a specific campaign. This is useful for users who want to review past communications between their email marketing campaigns and individual leads, enabling better tracking of engagement and follow-up actions.

Typical scenarios include:

  • Reviewing all messages sent and received for leads within a campaign.
  • Auditing communication history to improve campaign strategies.
  • Troubleshooting lead responses or issues by examining message logs.

For example, a marketing manager might use this operation to pull the entire message history of leads in a campaign to analyze response rates or identify leads that require manual follow-up.

Properties

Name Meaning
Campaign ID The unique identifier of the campaign whose lead message history you want to retrieve.
Additional Fields Optional parameters to customize the request:
- Limit Number of message history results to return (default 100).
- Offset Number of results to skip before starting to collect the output (default 0).
- Status Status filter for the campaign; options are Active, Paused, or Stopped (default Active).

Output

The output JSON contains an array of message history records related to leads in the specified campaign. Each record typically includes details such as message content, timestamps, sender/receiver information, and status metadata.

If binary data were involved (e.g., attachments), it would be summarized accordingly, but this operation focuses on textual message history.

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 successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing Campaign ID will cause the API call to fail.
    • Network connectivity problems can prevent reaching the SmartLead API endpoint.
    • Insufficient permissions or expired API credentials may result in authentication errors.
  • Error Messages:

    • Errors returned from the API will be captured and can appear as error objects in the node output if "Continue On Fail" is enabled.
    • Typical error messages include "Unauthorized" (check API key), "Not Found" (verify Campaign ID), or "Bad Request" (invalid parameters).
  • Resolutions:

    • Verify the Campaign ID is correct and exists in your SmartLead account.
    • Ensure the API key credential is valid and has required permissions.
    • Check network access and proxy settings if applicable.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion