LeadTable Trigger
Overview
This node triggers workflows based on events from the LeadTable platform, which manages leads and campaigns. It listens for specific LeadTable events either globally across an entire agency or scoped to a particular campaign (table). When an event occurs, such as a new lead creation or lead status change, the node activates the workflow with the event data.
Common scenarios include:
- Automating follow-up actions when a new lead is created.
- Tracking changes in lead status to update CRM systems.
- Monitoring updates or deletions of leads.
- Receiving notifications when new campaigns (tables) are created at the agency level.
Practical example: Automatically send a welcome email when a new lead is created in a specific campaign, or log lead updates centrally for reporting.
Properties
| Name | Meaning |
|---|---|
| Webhook Level | Choose the scope of events to listen for: - Agency (Global): Receive events from all campaigns in your agency. - Table (Specific Campaign): Receive events only from a specified campaign/table. |
| Event Name or ID | The specific LeadTable event that triggers the webhook. Options include: - New Lead Created - Lead Status Changed - Lead Updated - Lead Deleted - New Table Created (only for Agency level) |
| Customer Name or ID | (Shown only if "Webhook Level" is "Table") Select or specify the customer ID owning the campaign to monitor. |
| Campaign Name or ID | (Shown only if "Webhook Level" is "Table") Select or specify the campaign/table ID to monitor for events. |
| Include Lead Details | Whether to automatically fetch full lead details from the API when the webhook is triggered. If enabled, the node makes an additional API call to retrieve detailed lead information. |
| Enable Debug Logging | Enables detailed logging of request and response data (with sensitive API keys redacted). Useful for troubleshooting issues during webhook creation, deletion, or event handling. |
Output
The node outputs JSON data representing the event payload received from LeadTable. This includes fields such as:
event: The event type (e.g., "newLead", "changeStatus").campaignID,customerID: Identifiers for the campaign and customer related to the event.leadID,leadName,leadEmail: Basic lead information.timestamp: The event timestamp.leadDetails: (Optional) Full lead details fetched from the API if "Include Lead Details" is enabled.leadDetailsError: (Optional) Error message if fetching lead details failed.timestampFormatted: ISO string representation of the event timestamp.
The output is structured as a single-item array containing this enriched event object.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the LeadTable API.
- Needs network access to the LeadTable API endpoints.
- Uses n8n's HTTP request helper to interact with the LeadTable REST API.
- Requires configuration of credentials including base URL, API key, and email for authentication.
Troubleshooting
- Webhook Creation Errors: May occur if the selected event is incompatible with the webhook level (e.g., "newTable" event requires Agency level). Ensure correct webhook level and event combination.
- Webhook Deletion Fallback: Due to API limitations, deleting webhooks for some events uses a fallback method that may not fully remove the webhook immediately.
- Lead Details Fetch Failures: If "Include Lead Details" is enabled but fetching fails, the error message is included in the output under
leadDetailsError. Check API credentials and network connectivity. - Debug Logging: Enable debug logging to see detailed request/response logs (API keys redacted) to diagnose issues.
- Missing Customer or Campaign IDs: When using "Table" webhook level, ensure valid customer and campaign IDs are selected or provided via expressions.
Links and References
- LeadTable API Documentation (implied by usage)
- n8n Expressions Documentation (for dynamic property values)
- n8n Webhook Node Guide (general webhook concepts)
If you need further details about other operations or resources, please provide their names.