Actions14
- Campaign Actions
- Customer Actions
- Lead Actions
- Table Actions
- Webhook Actions
Overview
This node integrates with the LeadTable API to manage customers, campaigns, leads, tables, webhooks, and authentication. Specifically, for the Customer - Create operation, it allows users to create a new customer record in the LeadTable system by providing essential details such as the customer's name and an optional description.
Common scenarios where this node is beneficial include:
- Automating the onboarding of new customers into a CRM or lead management system.
- Integrating customer creation into workflows that gather data from forms, external databases, or other applications.
- Streamlining marketing or sales processes by programmatically managing customer entities.
Practical example:
- When a new client signs up on a website, this node can be used to automatically create a corresponding customer entry in LeadTable, enabling further campaign and lead management downstream.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the customer (e.g., "Acme Corporation"). This is a required field. |
| Description | Optional description of the customer, allowing additional context or notes about them. |
Output
The node outputs JSON data representing the newly created customer object as returned by the LeadTable API. This typically includes fields such as the customer's unique ID, name, description, creation date, and any other metadata provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential and associated email address for authenticating requests to the LeadTable API.
- The node expects the LeadTable API base URL, defaulting to
https://api.lead-table.com/api/v3/externalif not configured otherwise. - Proper configuration of these credentials within n8n is necessary for successful API communication.
Troubleshooting
- Authentication errors (HTTP 403): These occur if the API key or email is incorrect or missing. Verify that the credentials are correctly set up in n8n.
- Validation errors: If the "Name" property is empty or invalid, the API may reject the request. Ensure all required fields are properly filled.
- API connectivity issues: Network problems or incorrect base URL settings can cause failures. Confirm network access and correct endpoint configuration.
- Unexpected API errors: The node surfaces error messages returned by the API. Review the message for clues and consult LeadTable API documentation or support if needed.
Links and References
- LeadTable API Documentation (hypothetical link based on API domain)
- n8n Expressions Documentation – for dynamic parameter usage in workflows