SmartLead icon

SmartLead

Comprehensive SmartLead API integration for email marketing automation

Overview

The "Get Message History" operation in the Lead Management resource of this SmartLead node fetches the message history for leads associated with a specific campaign. This allows users to retrieve all past communications (messages) exchanged with leads within that campaign.

This operation is beneficial in scenarios where you want to analyze or audit the communication history with leads, track engagement, or integrate lead messaging data into other workflows or CRMs. For example, a marketing automation workflow could use this to pull message histories and trigger follow-up actions based on past interactions.

Properties

Name Meaning
Campaign ID The unique identifier of the campaign for which to fetch the lead message history.
Additional Fields (Not applicable specifically for this operation; included in general lead operations.)

Note: For this operation, only the Campaign ID is required as input.

Output

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

The node returns this data under the json output field as an array of objects representing each message entry.

No binary data output is involved in this operation.

Dependencies

  • Requires an active API key credential for the SmartLead API.
  • The node makes authenticated HTTP requests to the SmartLead API endpoint at https://server.smartlead.ai/api/v1.
  • Proper permissions on the API key to access lead and campaign data are necessary.

Troubleshooting

  • Invalid Campaign ID: If the provided campaign ID does not exist or is incorrect, the API will likely return an error or empty results. Verify the campaign ID is correct.
  • API Authentication Errors: Ensure the API key credential is valid and has the required permissions.
  • JSON Parsing Errors: Not applicable here since no user JSON input is parsed for this operation.
  • Empty Results: If no message history exists for the campaign, the output will be an empty array.
  • Network Issues: Connectivity problems can cause request failures; check network and API availability.

Links and References

Discussion