LeadTable

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

Actions14

Overview

This node integrates with the LeadTable API to manage marketing campaigns and related data. Specifically, the Campaign - Get Many operation retrieves multiple campaigns associated with a selected customer. This is useful for workflows that need to list or process all campaigns under a particular customer account.

Common scenarios include:

  • Fetching all campaigns for a customer to display in a dashboard.
  • Automating reporting or analytics on campaign performance.
  • Using campaign lists as input for further lead management or data enrichment steps.

Example: A marketing automation workflow could use this node to get all campaigns for "Acme Corporation" and then iterate over each campaign to pull leads or update statuses.

Properties

Name Meaning
Customer Name or ID Select the customer to get campaigns for. Choose from a dropdown list of customers or specify an ID using an expression.

Output

The node outputs a JSON array where each item represents a campaign belonging to the specified customer. Each campaign object typically includes:

  • name (string): The campaign's name or occupation field if the name is missing.
  • value (string): The unique identifier of the campaign.
  • description (string, optional): Additional info such as the number of leads in the campaign.

The output structure allows easy iteration over campaigns in subsequent workflow nodes.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential and email address configured for authenticating with the LeadTable API.
  • The node makes HTTP requests to the LeadTable external API endpoint (default: https://api.lead-table.com/api/v3/external).
  • Proper permissions on the API key are necessary to access customer and campaign data.

Troubleshooting

  • No campaigns found: If the selected customer has no campaigns, the node returns a placeholder item indicating no campaigns are available.
  • Invalid customer selection: Selecting an invalid or empty customer ID will cause the node to return an error or no results.
  • Authentication errors: If the API key or email is incorrect or lacks permissions, the node throws an authentication failure error.
  • API request failures: Network issues or API downtime can cause request failures; check logs for HTTP status codes and error messages.
  • Error loading campaigns: The node may return an error item with details if the API response is malformed or unexpected.

To resolve common errors:

  • Verify the API key and email credentials.
  • Ensure the customer ID is valid and selected before running the node.
  • Check network connectivity and API service status.
  • Review error messages logged by the node for specific causes.

Links and References

Discussion