Actions14
- Campaign Actions
- Customer Actions
- Lead Actions
- Table Actions
- Webhook Actions
Overview
This node integrates with the LeadTable API to manage tables (campaigns) associated with customers. Specifically, the Create Table operation allows users to create a new table (which can be considered a campaign) for a specified customer. This is useful in scenarios where you want to programmatically organize leads or campaigns under different customers within LeadTable.
Practical examples include:
- Automatically creating a new lead capture campaign table when onboarding a new client.
- Setting up multiple campaign tables for different marketing funnels or sales initiatives linked to a customer.
- Managing campaign metadata such as funnel links, lead deletion permissions, and pre-qualification settings dynamically via workflows.
Properties
| Name | Meaning |
|---|---|
| Customer Name or ID | The identifier of the customer for whom the new table (campaign) will be created. You can select from a list of existing customers or specify an ID using an expression. |
| Occupation | The name of the table or campaign, e.g., "Website Leads 2024". This serves as the title or label for the new table. |
| Additional Fields | A collection of optional fields to customize the table's behavior and configuration: - Delete Leads: Boolean flag to enable/disable the ability to delete leads. - Funnel Link: Optional URL related to the campaign funnel. - Override Values: JSON array to override default values during manual lead creation. - Pre-Qualify: Boolean flag indicating if leads should be pre-qualified. - Status: JSON array defining various status options for leads. - Table And Profile Config: JSON array configuring table and profile fields. |
Output
The node outputs a JSON array representing the response from the LeadTable API after creating the table. This typically includes details about the newly created table such as its ID, name, associated customer ID, and any other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential and email configured for authenticating with the LeadTable API.
- The node makes HTTP requests to the LeadTable external API endpoint (default:
https://api.lead-table.com/api/v3/external). - Proper permissions on the API key are necessary to create tables for customers.
Troubleshooting
- Authentication Errors: If you receive errors related to authentication (e.g., 403 Forbidden), verify that your API key and email credentials are correct and have sufficient permissions.
- Invalid Customer ID: Ensure the selected customer ID exists and is valid. Using an invalid or empty customer ID will cause the API request to fail.
- Malformed JSON in Additional Fields: When providing JSON arrays for fields like Override Values, Status, or Table And Profile Config, ensure the JSON syntax is correct to avoid parsing errors.
- API Request Failures: Network issues or incorrect base URLs can cause request failures. Confirm connectivity and that the base URL is correctly set if customized.
- Error Messages: The node surfaces detailed error messages from the API, which often include HTTP status codes and descriptive text. Use these messages to diagnose issues.
Links and References
- LeadTable API Documentation (official API docs referenced in the node description)
- n8n Expressions Documentation — for using expressions in property fields
- LeadTable Integration Node GitHub Repository (for source code reference and updates)