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 - Remove operation allows users to remove previously attached webhooks from either an agency-wide level or a specific campaign (table) level.

Typical use cases include:

  • Cleaning up webhook subscriptions when they are no longer needed.
  • Managing webhook lifecycle programmatically within automation workflows.
  • Ensuring that outdated or incorrect webhook URLs do not receive event notifications.

For example, if you have set up a webhook to listen for new leads on a particular campaign but want to stop receiving those notifications, you can use this operation to remove that webhook URL from the campaign or agency layer.

Properties

Name Meaning
Webhook URL The exact URL of the webhook to be removed. This is the endpoint that was previously registered to receive webhook events.
Topic Name or ID The webhook topic/event type to remove. Options include: newLead, changeStatus, updateLead, deleteLead, and newTable (the latter only available at agency layer).
Layer The scope where the webhook is attached. Options:
- Agency: Applies to all campaigns under an agency.
- Table: Applies to a specific campaign/table.
Agency ID Required if the layer is Agency. The unique identifier of the agency from which to remove the webhook.
Customer ID - Related Name or ID Required if the layer is Table. The customer associated with the campaign/table. Can be selected from a list or specified via expression.
Campaign ID - Table Name or ID Required if the layer is Table. The specific campaign or table from which to remove the webhook. Can be selected from a list or specified via expression.

Output

The node outputs JSON data representing the response from the LeadTable API after attempting to remove the webhook. Typically, this will be a confirmation of success or details about any error encountered.

No binary data output is produced by this operation.

Example output JSON might look like:

{
  "success": true,
  "message": "Webhook removed successfully"
}

or in case of failure:

{
  "error": "Failed to remove webhook: Authentication failed"
}

Dependencies

  • Requires an API key credential and associated email configured in n8n to authenticate requests against the LeadTable API.
  • The node communicates with the LeadTable external API endpoint (default base URL: https://api.lead-table.com/api/v3/external).
  • Proper permissions and valid credentials are necessary to remove webhooks.

Troubleshooting

  • Common Issues:

    • Removing a webhook with incorrect or missing parameters (e.g., wrong webhook URL, invalid topic, or missing IDs) will cause failures.
    • Attempting to remove a newTable topic webhook on the Table layer instead of the Agency layer will throw an error.
    • Authentication errors due to invalid API key or email will prevent successful removal.

  • Error Messages:

    • "Failed to remove webhook: Authentication failed": Check that your API key and email credentials are correct and have sufficient permissions.
    • "newTable events are only supported on Agency level. Please change Layer to Agency.": Change the layer property to "Agency" when removing newTable topic webhooks.
    • Network or API errors will be logged with status codes and messages; verify connectivity and API availability.

  • Resolution Tips:

    • Double-check all required fields are correctly filled.
    • Ensure the webhook URL exactly matches the one used during attachment.
    • Confirm the topic and layer combination is valid.
    • Verify credentials and API access rights.

Links and References

Discussion