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 outbound calls and other telephony-related resources. Specifically, the Create Outbound operation under the Calls resource initiates an outbound phone call to a specified phone number. This operation can optionally associate the call with a campaign and decide whether the call should be recorded.
Typical use cases include:
- Automating outbound calls for marketing or customer support campaigns.
- Initiating calls programmatically from workflows based on triggers or events.
- Recording calls for quality assurance or compliance purposes.
For example, a user might configure this node to call a customer’s phone number automatically when a new lead is added to a CRM system, optionally linking the call to a marketing campaign and enabling call recording.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number to call. Must be provided in a valid format. |
| Campaign ID | (Optional) Identifier of the campaign to associate the outbound call with. |
| Record | Boolean flag indicating whether the call should be recorded (true or false). |
Output
The node outputs a JSON object representing the response from the Talknbox VE API after attempting to create the outbound call. This typically includes details about the initiated call such as call ID, status, and any metadata returned by the API.
If the call creation is successful, the output JSON will contain confirmation and call details. In case of failure, the output may include an error message describing what went wrong.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential to authenticate with the Talknbox VE API.
- The base URL for the API is configurable via credentials.
- The node handles HTTP requests internally and respects rate limiting by retrying after waiting if a 429 status code is received.
Troubleshooting
- Rate Limiting (HTTP 429): If too many requests are sent in a short time, the API may respond with a rate limit error. The node automatically retries up to two times after waiting for the specified reset time.
- Invalid Phone Number: Providing an incorrectly formatted phone number may cause the API to reject the request. Ensure the phone number is valid and includes country codes if required.
- Missing or Invalid Credentials: The node requires valid API authentication credentials. Errors related to authentication indicate that the API key or token is missing or incorrect.
- API Errors: Other errors from the API will be passed through as error messages in the node output. Review the error message for details and verify parameters accordingly.
- 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
- Talknbox VE API Documentation (Assumed URL; replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- General best practices for Handling API Rate Limits
This summary focuses solely on the "Calls" resource with the "Create Outbound" operation as requested.