Actions14
- Campaign Actions
- Customer Actions
- Lead Actions
- Table Actions
- Webhook Actions
Overview
This node integrates with the LeadTable API to manage customer data within the LeadTable system. Specifically, for the Customer resource and Get Many operation, it retrieves a paginated list of customers from the LeadTable platform.
Typical use cases include:
- Fetching multiple customers for reporting or synchronization purposes.
- Automating workflows that require bulk access to customer information.
- Integrating customer data into other systems or dashboards.
For example, you might use this node to pull all customers page by page (using pagination) and then process or analyze their data in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Page | Page number for pagination. Determines which page of results to retrieve. Default is 1. |
| Limit | Maximum number of customer records to return per request. Minimum value is 1. Default is 50. |
Output
The node outputs an array of JSON objects representing customers. Each object typically includes fields such as customer ID, name, creation date, and possibly other metadata provided by the LeadTable API.
Example output structure (simplified):
[
{
"_id": "customer-id-123",
"name": "Acme Corporation",
"createdAt": "2023-01-15T12:34:56Z",
// ... other customer fields
},
{
"_id": "customer-id-456",
"name": "Another Customer",
"createdAt": "2023-02-20T08:22:10Z"
}
]
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential and associated email configured in n8n credentials for authenticating with the LeadTable API.
- The node makes HTTP requests to the LeadTable API endpoint (default base URL:
https://api.lead-table.com/api/v3/external). - Proper network connectivity to the LeadTable API service is necessary.
Troubleshooting
Authentication errors (403 Forbidden):
If the node returns an authentication error, verify that the API key and email credentials are correctly set and valid.Empty or no customers returned:
This may indicate that there are no customers available under the authenticated account or that pagination parameters are incorrect. Check thePageandLimitvalues.Invalid pagination parameters:
Ensure thatPageis a positive integer andLimitis at least 1. Invalid values may cause unexpected results or errors.API request failures:
Network issues or API downtime can cause request failures. Review error messages logged by the node for details.
Links and References
- LeadTable API Documentation (hypothetical link based on context)
- n8n Documentation - Credentials
- n8n Expressions Guide
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.