LeadTable

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

Actions14

Overview

This node integrates with the LeadTable API to manage webhook events related to leads and campaigns. Specifically, the Webhook - Poll operation allows users to poll for webhook events on a specified topic within a campaign for a given customer. This is useful for scenarios where you want to periodically check for new or updated lead data, status changes, deletions, or new table creations without relying on push notifications.

Practical examples include:

  • Automatically fetching new leads added to a campaign.
  • Monitoring changes in lead statuses to trigger follow-up workflows.
  • Detecting when a new campaign table is created at the agency level.
  • Polling for updates or deletions of leads to keep your CRM synchronized.

Properties

Name Meaning
Customer Name or ID Select or specify the customer whose campaign's webhook events you want to poll.
Campaign Name or ID Select or specify the campaign under the chosen customer to poll webhook events from.
Topic Name or ID The specific webhook event topic to poll for. Options include:
- New Lead
- Change Status
- Update Lead
- Delete Lead
- New Table Created (Agency level only)

Output

The node outputs JSON data representing the webhook events retrieved from the LeadTable API for the specified campaign and topic. Each item corresponds to an event payload containing details such as lead information, status changes, or table creation metadata depending on the topic polled.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential and associated email address for authenticating with the LeadTable API.
  • The node uses the LeadTable external API endpoint (default: https://api.lead-table.com/api/v3/external).
  • Proper configuration of credentials in n8n is necessary to access customer, campaign, and webhook data.

Troubleshooting

  • Invalid Customer or Campaign Selection:
    If the customer or campaign is not properly selected, the node will throw an error prompting to select valid entries. Ensure that the customer is selected first, then choose a campaign from the dynamically loaded list.

  • Authentication Errors:
    Errors with status code 403 indicate authentication failure. Verify that the API key and email configured in the credentials are correct and active.

  • Unsupported Topic-Layer Combination:
    Attempting to poll the "newTable" topic on a non-agency layer will result in an error. This event is only available at the agency level.

  • API Request Failures:
    Network issues or invalid parameters may cause API request failures. Review the error messages logged by the node for details and verify all input parameters.

Links and References

Discussion