Actions20
- Calls Actions
- Campaigns Actions
- Contacts Actions
- Agents Actions
- Queues Actions
- Reports Actions
- Webhooks Actions
Overview
This node integrates with the Talknbox VE API to manage and retrieve information about calls. Specifically, the Get Call operation fetches detailed information about a single call using its unique Call ID. This is useful in scenarios where you need to obtain call metadata or status for further processing, reporting, or decision-making within an automation workflow.
Practical examples:
- Retrieve details of a specific outbound or inbound call to log call duration, status, or outcome.
- Use call information to trigger follow-up actions such as sending notifications or updating CRM records.
- Monitor call activity by fetching call data dynamically during workflow execution.
Properties
| Name | Meaning |
|---|---|
| Call ID | The unique identifier of the call to retrieve. |
Output
The node outputs a JSON object containing the full response from the Talknbox VE API for the requested call. This typically includes all available call details such as call status, timestamps, phone numbers involved, duration, and any other metadata provided by the API.
If the call is not found or an error occurs, the output will contain an error message describing the issue.
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) errors.
Troubleshooting
Common issues:
- Invalid or missing Call ID will cause the API request to fail.
- Network connectivity problems or incorrect API base URL configuration can prevent successful requests.
- Rate limiting may temporarily block requests; the node retries automatically but repeated failures indicate excessive usage.
Error messages:
"error": "Call not found"— Verify that the Call ID is correct and exists in the system."error": "Authentication failed"— Check that the API key credential is valid and has necessary permissions.- HTTP 429 errors are handled internally with retries; persistent rate limit errors suggest reducing request frequency.
Links and References
- Talknbox VE API Documentation (example link, replace with actual if available)
- n8n HTTP Request Node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/