Campaign Call → Make Call
AI-generatedOverview
This node enables making AI-powered voice calls through the TalqOver platform, specifically supporting calls via campaigns with custom data. It is designed to initiate outbound calls that are handled by predefined campaigns, allowing users to personalize each call with dynamic information such as customer details or order context.
Common scenarios include:
- Automated marketing or sales outreach where calls are managed by a campaign.
- Customer support callbacks personalized with customer-specific data.
- Surveys or appointment reminders where contextual information enhances the call experience.
For example, you can trigger a call to a customer’s phone number using a specific campaign ID and pass a JSON payload containing the customer's name, ID, and product interest to tailor the conversation dynamically.
Properties
| Name | Meaning |
|---|---|
| Campaign ID | The unique identifier of the campaign that will handle the call. Found in your TalqOver dashboard under Campaigns. |
| Phone Number | The phone number to call, which must be in international format (e.g., +1234567890). |
| Payload | Custom JSON data passed to the campaign for personalization during the call. Examples include customer info, order details, appointment data, or survey context. |
| Webhook URL | (Optional) URL to receive notifications when the call is completed. |
| Metadata | (Optional) Additional metadata in JSON format to associate with the call for tracking or logging purposes. |
Output
The node outputs JSON data representing the response from the TalqOver API after initiating the call. This typically includes details about the created call instance such as call identifiers, status, timestamps, and any other relevant metadata returned by the API.
If a webhook URL is provided, call completion events can be tracked externally, but this node itself outputs only the immediate API response upon call creation.
No binary data output is produced by this node.
Dependencies
- Requires an active TalqOver API credential configured in n8n with at least the base URL and authentication token.
- The node makes HTTP POST requests to the TalqOver API endpoints to create calls.
- Proper network access to the TalqOver API endpoint is necessary.
- If using webhook URLs, ensure the receiving endpoint is publicly accessible and can handle incoming POST requests.
Troubleshooting
- Invalid phone number format error: The phone number must strictly follow the international E.164 format starting with a plus sign (+) followed by country code and subscriber number (e.g., +1234567890). Ensure no spaces or invalid characters are included.
- API authentication errors: Verify that the API credentials are correctly set up and have not expired or been revoked.
- Network connectivity issues: Confirm that your environment can reach the TalqOver API base URL without firewall or proxy restrictions.
- Malformed JSON in Payload or Metadata: Ensure that the JSON fields are valid and properly formatted; otherwise, the API may reject the request.
- Webhook URL failures: If call completion notifications are not received, check that the webhook URL is correct, publicly reachable, and responds with appropriate HTTP status codes.