Actions39
- Campaign Actions
- Campaign Statistic Actions
- Client Actions
- Email Account Actions
- Lead Actions
- Master Inbox Actions
- Webhook Actions
Overview
This node integrates with the Smartlead.ai API to manage clients, campaigns, leads, email accounts, and related entities. Specifically, for the Client - Add operation, it allows users to add a new client to the Smartlead system by specifying arbitrary client details as key-value pairs.
Typical use cases include automating client creation workflows in marketing or sales automation pipelines where new client records need to be programmatically added to Smartlead. For example, after collecting client information from a form or CRM, this node can push that data into Smartlead to create a client profile without manual entry.
Properties
| Name | Meaning |
|---|---|
| Client Details | A collection of key-value pairs representing the client's attributes (e.g., name, email). Multiple details can be added. |
The "Client Details" property is a fixed collection allowing multiple entries, each with:
- Key: The name of the detail to set (e.g., "name", "email").
- Value: The corresponding value for that detail.
Output
The node outputs JSON data representing the response from the Smartlead API after attempting to add the client. This typically includes the newly created client object with its assigned properties and identifiers as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Smartlead.ai API.
- Requires an API authentication credential configured in n8n to authorize requests.
- The base URL used for API calls is
https://server.smartlead.ai/api/v1.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing incomplete or incorrect client details may result in API validation errors.
- Network connectivity problems can prevent successful API communication.
Error messages:
- Errors returned from the API are passed through; typical messages might indicate missing required fields or invalid data formats.
- If the node throws a generic error, verify that all required client details are provided and that the API key is valid.
Resolution tips:
- Double-check the API key configuration in n8n credentials.
- Ensure all mandatory client fields expected by Smartlead are included in the "Client Details".
- Review the API documentation for required client fields and data formats.
Links and References
- Smartlead.ai API Documentation (hypothetical link for reference)
- n8n Documentation on Creating Custom Nodes