Connect VeraDial to Zapier
VeraDial's native Zapier app starts workflows as soon as Vera finishes an event. Generate a narrow one-time API key in VeraDial, connect it on Zapier, and choose whether the Zap should run for every phone line or one exact line.
By Graham Thomson · Updated August 9, 2026
1. Generate your Zapier key
Zapier connections are included with Vera Plus. Sign in at app.veradial.com, open Dashboard → Integrations, and choose Generate API Key in the Zapier section. The mobile app offers the same key control under Manage Vera → Webhooks & Zapier.
- Give the key a recognizable label if prompted.
- Copy the full vdk_ key immediately; VeraDial shows it only once.
- The key works only with VeraDial's Zapier triggers. It is not a general VeraDial API key.
- If you lose the full value before connecting, revoke that key and generate a replacement.
2. Connect VeraDial on Zapier
Open the VeraDial app in Zapier, start a Zap, and choose VeraDial as the trigger app. When Zapier asks you to connect an account, paste the vdk_ key you just copied.
- Use the Open VeraDial on Zapier button in the dashboard or visit zapier.com/apps/veradial/integrations.
- Zapier tests the key and labels the connection with your VeraDial account.
- Keep one connection for a set of related Zaps, or create separately labeled keys when you need an easy revocation boundary.
3. Choose an instant trigger
VeraDial exposes four instant triggers. Each can watch all of your VeraDial phone lines or one selected line, and Zapier provides a representative sample while you build the workflow.
- New Screened Call: caller details, reason, urgency, requested action, and Vera's summary.
- New Voicemail: caller number, duration, and transcription status.
- New AI Text Reply: the customer, reply mode, and message body Vera sent.
- New Appointment Booked: caller details, reason, and confirmed start and end time.
4. Add the action and test the Zap
Choose what should happen next—add a Google Sheets row, notify Slack, create a CRM task, send an email, or use another Zapier action. Test with Zapier's sample, then publish the Zap.
- Start with New Screened Call → Google Sheets or Slack for a simple lead log.
- Use New Voicemail → email or Slack for an on-call alert.
- Use New Appointment Booked → your follow-up system after Vera confirms a slot.
- Run a real VeraDial event after publishing and confirm the destination receives the expected fields.
Privacy, duplicates, and revocation
Native Zapier triggers deliberately send operational event fields, not every piece of account content. Deliveries are at least once, so a lost success response can cause the same event to run a Zap more than once.
- Call transcripts, voicemail transcription text, and audio recordings are not sent through the native Zapier app.
- Use the event id as a correlation key when duplicate side effects would be harmful.
- Revoking a key in VeraDial immediately disconnects every Zap subscription created with that key.
- A revoked key cannot be recovered; generate a new one and reconnect the affected Zaps.
FAQ
Do I need Webhooks by Zapier?
No. Choose the native VeraDial app on Zapier and use its instant triggers. Custom signed webhooks are a separate option for Make, n8n, or your own endpoint.
Can the Zapier key place calls or change my VeraDial account?
No. The vdk_ key is limited to VeraDial's Zapier connection, trigger subscriptions, line picker, and samples. It is not a general-purpose or action-taking credential.
Why can't I see my full Zapier key again?
VeraDial stores only a secure hash and a short display prefix. If the one-time value was not copied, revoke that key and generate a replacement.
Can one Zap watch only one VeraDial number?
Yes. Choose a specific Phone Line while configuring the trigger. Leave it on All lines for an account-wide workflow.
Hear Vera in action.
Play a short sample call, follow the transcript, and move into a personalized live demo when you're ready.