Skip to content

Zapier, Make and Pipedream

Connect Vocenya to thousands of apps without code: instant triggers for leads, calls, bookings and chats, and actions for leads, AI calls and blocking.

Vocenya works with Make and Pipedream today, and its Zapier app is coming soon. All three use the same pieces of the public API, so anything you can build in one you can build in the others:

  • Connection: an API key from Developers. Give it only the scopes the automations need (listed below). A vk_test_ key works too and only sees test data.
  • Triggers are instant. Turning one on creates a webhook endpoint for that one event (you will see it on the Developers page, described as "Zapier", "Make" or "Pipedream"), and turning it off deletes it.
  • Actions call the same endpoints as your own code would, with the same compliance checks.

Triggers

Trigger Webhook event Scopes
New lead lead.created webhooks:manage, leads:read
Call completed call.completed webhooks:manage, calls:read
Missed call call.missed webhooks:manage, calls:read
New booking booking.created webhooks:manage, bookings:read
Chat handed off chat.handed_off webhooks:manage, chats:read
Outbound call completed outbound_call.completed webhooks:manage, outbound:read (included in outbound:write)
Message taken (Zapier) message.taken webhooks:manage, calls:read
Chat lead captured (Zapier) chat.lead_captured webhooks:manage, chats:read, leads:read
New chat message (Zapier) chat.message.created webhooks:manage, chats:read

Zapier and Pipedream read the full record from the API when a trigger fires, so you can map every field the API returns. Make passes on the webhook's data (ids, statuses, times and contact details); add a Make an API Call module (for example GET /calls/{id}) when a scenario needs more. HIPAA-mode accounts never get transcripts, summaries, lead reasons or chat messages on any platform.

Actions and searches

Action Endpoint Scopes
Create lead POST /leads leads:write (and outbound:write for an AI callback)
Place an outbound AI call POST /outbound-calls outbound:write
Add to Do-Not-Call list POST /do-not-call dnc:write
Block a caller POST /blocked-callers dnc:write
Find lead by phone or email GET /leads leads:read
Reply to chat (Zapier) POST /chats/{chat}/messages chats:write
Find call by phone (Zapier) GET /calls?phone_number= calls:read
Find booking by phone (Zapier) GET /bookings?phone_number= bookings:read

Outbound calls only go to people who agreed to be called by AI. Vocenya checks every call against Do-Not-Call lists, calling hours where the number is, daily limits and the consent on record, exactly as described in Outbound calls. A refused call stops the run with the reason (Zapier shows it as "stopped" rather than an error), and a call outside calling hours waits for the next allowed time.

Zapier

The Vocenya Zapier app is coming soon: it is not listed in Zapier yet. Once it is, search for Vocenya when you add a step to a Zap, connect with your API key, and pick a trigger or action. Find or Create Lead is available as a single step. The Zapier app also has Message Taken, Chat Lead Captured and New Chat Message triggers, a Reply to Chat action and Find Call and Find Booking searches. Call Completed and Missed Call leave out spam calls unless you switch on Include Spam Calls?, and New Chat Message only fires for visitor messages by default, so a Zap that replies never answers itself. Connections made with a test key are labelled "(test)".

Make

Add the Vocenya app to a scenario. The Watch modules (New Leads, Completed Calls, Missed Calls, New Bookings, Chat Handoffs, Completed Outbound Calls) are instant triggers. Actions are Create a Lead, Place an Outbound AI Call, Add to Do-Not-Call List, Block a Caller, Search Leads and Make an API Call.

Pipedream

Search for Vocenya in a workflow's trigger or step picker. Sources check each delivery's Vocenya-Signature against the endpoint secret before they emit an event, so a forged request never starts a workflow.

Troubleshooting

  • "Missing scope": edit the key on the Developers page and add the scope the step names, or create a new key and reconnect.
  • A trigger stopped firing: check the endpoint and its recent deliveries on the Developers page. A disabled or deleted endpoint receives nothing; turning the trigger off and on again creates a fresh one.
  • Rate limits: every platform shares your key's limit of 120 requests a minute and retries after Retry-After.