Talknbox VE

Integracja z Talknbox VE API
Join our community

Actions20

Overview

This node integrates with the Talknbox VE API, providing various operations across multiple resources such as calls, campaigns, contacts, agents, queues, reports, and webhooks. Specifically for the Webhooks - Delivery operation, it sends webhook event data to the Talknbox VE platform by making a POST request to the /v1/webhooks/deliveries endpoint. This operation is useful for delivering webhook events received externally into the Talknbox system for processing or logging.

Practical scenarios include:

  • Forwarding webhook events from external services into Talknbox for real-time event handling.
  • Delivering event payloads with associated metadata like event ID, type, timestamps, and security signatures.
  • Integrating Talknbox with other systems that emit webhook events, enabling centralized event management.

Properties

Name Meaning
Event ID Identifier of the webhook event. Optional string to uniquely identify the event.
Event Type Type/category of the event being delivered. This is a required string property.
Event Timestamp Timestamp when the event occurred. Optional string representing the event time.
Event Payload JSON object containing the detailed data of the event.
Webhook ID Optional identifier of the webhook that triggered the event.
Webhook Timestamp Optional timestamp when the webhook was sent.
Webhook Signature Optional security signature for verifying the webhook authenticity.

Output

The node outputs a JSON object representing the response from the Talknbox VE API after delivering the webhook event. The structure typically includes an ok field indicating success or may contain error details if the request failed.

Example output JSON structure:

{
  "ok": true
}

If an error occurs and "Continue On Fail" is enabled, the output will contain an error message in the JSON field:

{
  "error": "Error message here"
}

The node does not output binary data for 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 for rate limiting (HTTP 429) with up to 3 attempts.
  • No additional external dependencies beyond the Talknbox VE API and n8n's HTTP request helper.

Troubleshooting

  • Rate Limiting (HTTP 429): The node automatically retries after waiting for the reset time specified by the API. If you still encounter rate limit errors, consider reducing request frequency or increasing limits on the Talknbox side.
  • Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
  • Invalid Payload or Missing Required Fields: The eventType property is required; missing it will cause errors. Verify all required fields are provided and payload JSON is valid.
  • Network or API Errors: The node throws errors if the API is unreachable or returns unexpected responses. Check network connectivity and API status.
  • If "Continue On Fail" is enabled, errors will be returned in the output JSON for easier debugging without stopping workflow execution.

Links and References

Discussion