Actions39
- Campaign Actions
- Campaign Statistic Actions
- Client Actions
- Email Account Actions
- Lead Actions
- Master Inbox Actions
- Webhook Actions
Overview
The node interacts with the Smartlead.ai API to manage and retrieve data related to campaigns, leads, email accounts, statistics, master inbox messages, webhooks, and clients. Specifically, for the Master Inbox resource with the Get Message History operation, it fetches the message history of a specific lead within a campaign.
This functionality is useful in scenarios where you want to review all past communications with a lead in a given campaign, enabling better context for follow-ups or analysis of engagement history. For example, sales or marketing teams can use this to track email threads and responses associated with a lead to tailor their outreach strategy.
Properties
| Name | Meaning |
|---|---|
| Campaign ID | The unique identifier of the campaign from which to fetch the lead's message history. |
| Lead ID | The unique identifier of the lead whose message history is being retrieved. |
Output
The output is a JSON array representing the message history for the specified lead in the campaign. Each item in the array corresponds to a message or communication event in the thread, including details such as timestamps, message content, sender/receiver info, and status.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Smartlead.ai API.
- The node uses the base URL
https://server.smartlead.ai/api/v1for all API calls. - 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 call to fail.
- Authentication errors if the API key credential is not set up correctly.
- Network connectivity issues may prevent reaching the Smartlead.ai API endpoint.
Error messages:
- Errors returned by the API (e.g., 404 Not Found) typically indicate that the campaign or lead does not exist or the IDs are incorrect.
- Authentication failures will result in unauthorized errors; verify the API key credential.
- If the node throws a generic error, ensure that required parameters are provided and valid.
Links and References
- Smartlead.ai API Documentation (Assumed link, please verify with actual documentation)
- n8n Documentation on HTTP Request Node for understanding API integrations.