LeadTable

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

Actions14

Overview

This node integrates with the LeadTable API to manage leads within campaigns and customers. Specifically, the Update Description operation for the Lead resource allows users to update the textual description of an existing lead by providing its ID and a new description.

Common scenarios where this node is beneficial include:

  • Automatically updating lead descriptions based on external data or events.
  • Enriching lead information in bulk workflows.
  • Keeping lead profiles up-to-date with notes or status changes.

For example, after qualifying a lead through a form submission, you could use this node to update the lead’s description with additional context or comments.

Properties

Name Meaning
Lead ID The unique identifier of the lead to update.
Description The new description text to set for the specified lead.

Output

The node outputs JSON data representing the response from the LeadTable API after updating the lead description. This typically includes confirmation of the update and possibly the updated lead object.

The output is structured as an array of JSON objects, each corresponding to an input item processed. There is no binary data output for this operation.

Example output snippet (conceptual):

[
  {
    "success": true,
    "leadId": "12345",
    "description": "Updated description text"
  }
]

Dependencies

  • Requires an API key credential and associated email address for authenticating with the LeadTable API.
  • The node uses the LeadTable API base URL, defaulting to https://api.lead-table.com/api/v3/external if not overridden.
  • Proper configuration of credentials in n8n is necessary to authenticate requests.

Troubleshooting

  • Authentication errors (403): If you receive an authentication failure error, verify that your API key and email are correctly configured in the node credentials.
  • Invalid Lead ID: Ensure the Lead ID provided exists in the system; otherwise, the API may return an error or empty response.
  • Empty or missing description: The description field is required; leaving it empty will cause the node to throw an error.
  • API request failures: Network issues or incorrect base URLs can cause request failures. Check connectivity and credential settings.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion