LeadTable

Integration with LeadTable API (powered by agentur-systeme.de)
Join our community

Actions14

Overview

This node integrates with the LeadTable API to manage webhooks related to lead and campaign events. Specifically, the Webhook - Attach operation allows users to register a webhook URL for specific event topics at different organizational layers (Agency or Table). This enables automated notifications or data synchronization when certain events occur, such as new leads being created or lead statuses changing.

Common scenarios include:

  • Automatically triggering workflows in n8n when a new lead is added to a campaign.
  • Receiving updates when lead information changes.
  • Monitoring creation of new tables (campaigns) at the agency level.

Practical example:

  • A marketing team wants to update their CRM whenever a new lead is generated in a specific campaign. They can attach a webhook to the "newLead" topic on the table layer for that campaign, providing their CRM's webhook URL. When a new lead appears, the CRM receives the data instantly.

Properties

Name Meaning
Customer Name or ID Select a customer from the list or specify an ID via expression. Required when attaching a webhook on the table layer to identify which customer's campaigns are relevant.
Campaign Name or ID The ID of the campaign to attach the webhook to (required for the table layer). Choose from the list or specify an ID using an expression.
Webhook URL The URL endpoint where webhook events will be sent. Must be a valid URL accepting incoming POST requests.
Topic Name or ID The event topic to listen for. Options include: "newLead", "changeStatus", "updateLead", "deleteLead", and "newTable" (the latter only available on Agency layer). Choose from the list or specify an ID via expression.
Layer The organizational level to attach the webhook to:
- Agency: applies to all campaigns under the agency.
- Table: applies to a specific campaign/table.

Note: The property newTableNotice is a notice shown if the user tries to attach a "newTable" event webhook on the table layer, which is not supported.

Output

The node outputs JSON data representing the response from the LeadTable API after attempting to attach the webhook. This typically includes confirmation details about the webhook registration.

The output structure is an array of JSON objects corresponding to each input item processed. Each object contains the API response fields, which may include status, IDs, or error messages if applicable.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential and associated email for authenticating with the LeadTable API.
  • The node uses the LeadTable external API endpoint (default: https://api.lead-table.com/api/v3/external).
  • Proper network connectivity to the LeadTable API and the specified webhook URL is necessary.
  • The user must configure credentials with a valid API key and email address.

Troubleshooting

  • Error: "newTable events are only supported on Agency level. Please change Layer to Agency."
    Occurs if trying to attach a "newTable" topic webhook on the table layer. Solution: Change the Layer property to "Agency".

  • Authentication failures (HTTP 403)
    Indicates invalid or missing API key/email credentials. Verify the API key and email configured in the node credentials.

  • Failed to load customers or campaigns
    May happen if the API key lacks permissions or network issues occur. Check credentials and internet connection.

  • Invalid campaign or customer selection
    If the campaign dropdown shows "no-customer-selected" or "no-campaigns-found", ensure a valid customer is selected first, then pick a campaign.

  • Webhook URL errors
    Ensure the webhook URL is reachable and correctly formatted. The receiving server should accept POST requests.

Links and References

If you need further details on other operations or resources, feel free to ask!

Discussion