Talknbox VE

Integracja z Talknbox VE API
Join our community

Actions20

Overview

This node integrates with the Talknbox VE API to manage contacts among other resources. Specifically, the Contacts - Update operation allows users to update an existing contact's details such as phone number and tags. This is useful in scenarios where contact information changes or needs correction, for example updating a customer's phone number or modifying their associated tags for segmentation.

Practical examples:

  • Updating a contact's phone number after they provide a new one.
  • Adding or removing tags to categorize contacts dynamically based on recent interactions.

Properties

Name Meaning
Contact ID The unique identifier of the contact to update.
Contacts Payload A collection of contact fields to update. Supports multiple entries but only the first is used in update operation. Contains:
- Phone: The new phone number.
- Tags: Comma-separated list of tags to assign to the contact.

Output

The node outputs a JSON object representing the response from the Talknbox VE API after updating the contact. This typically includes the updated contact data or confirmation of the update.

Example output structure (simplified):

{
  "id": "contact-id",
  "phone": "updated-phone-number",
  "tags": ["tag1", "tag2"]
}

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

  • Rate limiting errors (HTTP 429): The node automatically retries up to 3 times with delay based on the x-ratelimit-reset header. If errors persist, consider reducing request frequency.
  • Invalid Contact ID: If the provided Contact ID does not exist, the API will return an error. Verify the Contact ID before running the update.
  • Malformed tags: Tags must be comma-separated strings; empty or invalid tags may cause unexpected behavior.
  • Missing required fields: Ensure that the Contact ID is provided and at least one field (phone or tags) is set in the payload.

Links and References

Discussion