LeadTable

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

Actions14

Overview

This node integrates with the LeadTable API to manage and retrieve lead data associated with marketing campaigns. Specifically, the "Lead" resource's "Get by Campaign" operation fetches all leads linked to a selected campaign for a given customer. This is useful in scenarios where you want to analyze or process leads generated from specific marketing efforts.

Practical examples include:

  • Retrieving all leads from a particular campaign to feed into a CRM system.
  • Exporting campaign leads for reporting or follow-up actions.
  • Automating workflows based on lead data from targeted campaigns.

Properties

Name Meaning
Customer Name or ID Select or specify the customer whose campaigns you want to access. The list is dynamically loaded from available customers.
Campaign Name or ID Select or specify the campaign under the chosen customer to get leads from. The list depends on the selected customer.
Page Page number for paginated results (default: 1). Useful for navigating through large sets of leads.
Limit Maximum number of leads to return per page (minimum 1, default: 50). Controls the batch size of returned results.

Output

The node outputs an array of JSON objects representing leads retrieved from the specified campaign. Each item corresponds to a lead with its associated data fields as provided by the LeadTable API.

If binary data were involved (not applicable here), it would be included in the binary property, but this operation returns only JSON lead data.

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 base URL: https://api.lead-table.com/api/v3/external).
  • Proper permissions and valid credentials are necessary to access customer and campaign data.

Troubleshooting

  • Invalid Campaign Selection: If the campaign parameter is invalid or not properly selected (e.g., placeholder values like "no-customer-selected"), the node throws an error prompting to select a valid campaign after choosing a customer.
  • Authentication Errors: A 403 status code indicates authentication failure. Verify that the API key and email credentials are correct and active.
  • Empty Results: If no leads are returned, ensure that the selected campaign actually contains leads and that pagination parameters are set correctly.
  • API Request Failures: Network issues or incorrect API endpoint configurations can cause request failures. Check connectivity and credential settings.

Links and References

Discussion