Talknbox VE

Integracja z Talknbox VE API
Join our community

Actions20

Overview

This node integrates with the Talknbox VE API, allowing users to manage various resources such as calls, campaigns, contacts, agents, queues, reports, webhooks, and system information. Specifically, for the Contacts - Get operation, it retrieves detailed information about a single contact by its unique Contact ID.

Typical use cases include:

  • Fetching contact details to enrich workflows with up-to-date contact information.
  • Using contact data to trigger further actions or decisions in automation processes.
  • Integrating Talknbox VE contact management into broader CRM or communication workflows.

Example: You have a workflow that triggers when a new call is received, and you want to fetch the caller's contact details from Talknbox VE to personalize your response or log the interaction.

Properties

Name Meaning
Contact ID The unique identifier of the contact to retrieve. This is required to specify which contact's details to fetch.

Output

The node outputs a JSON object representing the contact's data as returned by the Talknbox VE API. This typically includes fields such as contact ID, phone number, tags, and any other metadata associated with the contact.

The output structure is:

{
  "id": "string",
  "phone": "string",
  "tags": ["string", "..."],
  // ... other contact fields as provided by the API
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Talknbox VE API.
  • The base URL for the API is configurable via credentials.
  • The node uses HTTP requests with automatic retry logic on rate limiting (HTTP 429).

Troubleshooting

  • Error: Contact not found — Ensure the Contact ID provided exists in Talknbox VE.
  • Authentication errors — Verify that the API key credential is correctly configured and has necessary permissions.
  • Rate limiting (HTTP 429) — The node automatically retries after waiting; if persistent, consider reducing request frequency.
  • Invalid Contact ID format — Make sure the Contact ID is properly URL-encoded and valid.

Links and References

Discussion