What you’ll build
By the end of this guide, you’ll have:- the Vobiz node installed in n8n and connected to your Vobiz account;
- a workflow that calls a phone number and speaks a message;
- your Vobiz number answering incoming calls from n8n, with a message, call forwarding, a key-press menu or voicemail.
What’s in the Vobiz node
Prerequisites
- Vobiz account → sign up at vobiz.ai, as shown in Set up your accounts
- Vobiz phone number - the caller ID for your calls, and the number that answers incoming calls → Buy a phone number
- Your Auth ID and Auth Token - on the Vobiz Console Dashboard, under API credentials
- n8n account - n8n Cloud or self-hosted n8n. Installing the node needs the Owner or Admin role in n8n.
- Self-hosted n8n only: n8n must be reachable from the internet over HTTPS, so Vobiz can send call events to it.
- WhatsApp only: a WhatsApp channel on your Vobiz account → WhatsApp prerequisites
Set up your accounts
You need a Vobiz account for calls and numbers, and an n8n account to build the workflows. Skip a step if you already have that account.




Install the Vobiz node
These steps use n8n Cloud. On self-hosted n8n, install it as a community node.
Open the nodes panel
Search for Vobiz
Vobiz in Search nodes…. Vobiz appears with a verified badge next to its name. Select it.

Click Install node
See what's in it


Install as a community node
A community node is an n8n node published on npm instead of built into n8n. The Vobiz node’s npm package is@vobiz-ai/n8n-nodes-vobiz. On self-hosted n8n, install it by that name. You need the Owner or Admin role.
Enter the package name
@vobiz-ai/n8n-nodes-vobiz.Accept the notice
Install

@vobiz-ai/n8n-nodes-vobiz with its 2 nodes, Vobiz and Vobiz Trigger.

Vobiz in the nodes panel and select Vobiz. Node details shows Installed and Via npm. Select On call answered, then connect your Vobiz account.

Connect your Vobiz account
The Vobiz node signs in to Vobiz with your Auth ID and Auth Token. You save them once in n8n as a Vobiz API credential, and every Vobiz node can use it.Open the trigger
Click Connect to Vobiz


Open API credentials
Copy both values
MA_), then the one next to Auth Token. The eye icon shows the Auth Token.
Paste your credentials
https://api.vobiz.ai, and Allowed HTTP Request Domains as it is.Save

X-Auth-ID and X-Auth-Token headers. To work as a sub-account, create another Vobiz API credential with that sub-account’s Auth ID (SA_…) and Auth Token.Ready-made workflows
Import one of these 20 workflows instead of building it node by node. Each file uses placeholders only, such as+91XXXXXXXXXX for phone numbers, and carries no credentials. A Setup note inside each workflow says what to fill in.
Copy the link
Import it into n8n
Follow the Setup note
Publish
Simple and medium
Advanced
Make your first call
When a call is answered, Vobiz asks a web address - the Answer URL - what to do next. The Vobiz Trigger with Source: Calls is that address: it replies with your message in VobizXML, so you don’t write XML or run a server.Open the trigger
Vobiz, select Vobiz, and under Triggers select On call answered.Write the message
This is a reminder that your appointment is tomorrow at 10 am. Choose a Voice and a Language.Choose what happens next
Publish the workflow
/webhook/, not /webhook-test/.
Start a second workflow
Add Make a call
vobiz, select Vobiz, and under Actions select Make a call.Fill in the call
call_uuid.
A call between two people
n8n can’t talk on a call itself, so Vobiz rings two phones and connects them: first the one in To, then the one in Connect To.- Point Answer URL at your Vobiz Trigger’s Production URL, as above.
- Put your own phone (or your agent’s) in To, and the person to talk to in Connect To. Both can come from your data, such as
{{ $json.phone }}from a sheet or CRM row. To ring several numbers, separate them with commas: they all ring, and the first to answer is connected. - Leave Message empty to connect straight away, or set one, such as Connecting you to Asha, to hear it first.
Answer incoming calls
The same Vobiz Trigger can answer calls to your Vobiz numbers.n8n-call-answered-…, and links your numbers to it. When you unpublish the workflow, it removes the application and releases the numbers.
Start workflows from call events
Choose the events in the trigger’s Trigger On. Tick several to handle them in one workflow, and use an If or Switch node onevent to branch.
vobiz field with the full request Vobiz sent. To get a voicemail’s audio, pass its recording_id to Vobiz → Download a recording.
Act on every call on your account
The Vobiz Trigger fires for calls that go through it. To act on every call on your account - including calls on numbers used by other setups, such as a CRM integration - check Vobiz on a schedule:Schedule Trigger
Get many call records
Remove Duplicates
{{ $json.uuid }}, so each call is passed on only once. The first run passes on every call it finds.{{ $json.recording_id }}, then Vobiz → Download a recording to get the audio.
- Channel - your WhatsApp number on Vobiz, from the list.
- To - the customer’s number, with its country code.
- Message Type - Text (default), Image, Audio, Video, Document, Sticker or Template. Media types take a Media URL; a Template takes the approved template and its Body Variables.
- Trigger On - Message Received (a customer messages you; the default) and/or Message Status Changed (a message you sent was sent, delivered, read or failed).
- Channel - optional. Limits the trigger to one WhatsApp number; leave it empty for every channel on the account.
Sub-accounts and KYC
A sub-account is a separate account under yours, with its own Auth ID (SA_…), Auth Token, numbers and call records. Its usage is billed to your main account. Manage sub-accounts with your main account’s credential (MA_…).
- Choose the events in Trigger On: KYC Started, Documents Submitted, KYC Completed, KYC Failed, Link Expired or Link Revoked. KYC Completed and KYC Failed are selected by default.
- Publish the workflow, open the trigger and copy its Production URL.
- On Start verification for a sub account, paste it into Options → Webhook URL. Vobiz then reports that customer’s KYC to the trigger.
All Vobiz actions
Manage, update or remove the node
Installed packages are listed under Settings → Community nodes. You need the Owner or Admin role.Open Settings
Open Community nodes
@vobiz-ai/n8n-nodes-vobiz and its version.- Update: when a new version is available, an Update button appears on the package. On n8n Cloud, n8n reviews each new version before it’s offered.
- Uninstall: open the package’s Options menu (three dots), select Uninstall package and confirm. Unpublish the workflows that use the Vobiz Trigger first, so it releases its numbers, its Vobiz application and its WhatsApp subscriptions.
Security
- Your Auth ID and Auth Token stay in n8n’s encrypted credential store and are sent only to Vobiz. Download a recording sends your credential only to Vobiz hosts.
- Call events to the Vobiz Trigger (Calls) are checked against Vobiz’s
X-Vobiz-Signature-V3(or V2) header, signed with your Auth Token. Forged events are refused, and so are unsigned ones while Require Vobiz Signature is on. See Validating webhooks (callbacks). - WhatsApp events are checked with a secret created for each subscription. Unsigned or forged events are refused.
- KYC events (Sub-Account KYC) are checked against Vobiz’s
X-Vobiz-Signatureheader, signed with your main account’s Auth Token. - A new sub-account’s Auth Token appears only in the output of Create a sub account. n8n keeps it in that run’s execution data, so save it to a credential and limit who can see executions.
Troubleshooting
- You have the Member role: only an Owner or Admin can install the node. Ask them to follow Install the Vobiz node.
- n8n Cloud: check that Verified community nodes is on under Instance settings in the Cloud console.
- Self-hosted n8n: install it as a community node.
- The Answer URL is the trigger’s Test URL, or the trigger’s workflow isn’t published. Publish it and use the Production URL.
- For a menu or voicemail that goes silent after the message: the workflow isn’t published, so Vobiz’s follow-up gets no answer.
- If n8n’s log says a request was refused: it had no Vobiz signature, your Vobiz account sends call events without a signature. Turn off Require Vobiz Signature on the trigger.
- Self-hosted n8n needs a public address. Vobiz sends events over the internet, so set
WEBHOOK_URLto n8n’s public HTTPS address (n8n guide), then use the trigger’s Production URL. This works automatically on n8n Cloud. - The public address changed (for example, a tunnel that gets a new address on every restart): unpublish and publish your trigger workflows again, so Vobiz uses the new address.
Next steps
- Learn what Vobiz can say and do on a call: VobizXML, for the trigger’s Custom XML option.
- Understand calls: Make a call in the Vobiz API reference describes the request Make a call sends.
- Work with call data: Call detail records and Recordings.
- Set up WhatsApp: WhatsApp getting started.
- Explore n8n: n8n’s community node docs.