Apps and tools
Zapier and Make
Connect bidi to thousands of apps without code: new leads, tickets and form submissions as triggers, contacts and messages as actions.
Being published
The bidi apps for Zapier and Make are built and are going through each directory's review. Until they appear there, connect with a plain webhook: it works today and the data is the same.
Zapier
The bidi app for Zapier is a thin client over API v2 and its webhooks. Its triggers are instant: switching a Zap on subscribes its hook URL to one event through POST /api/v2/webhooks, and every delivery's X-Bidi-Signature is checked before the Zap runs. Switching the Zap off unsubscribes.
| What it does | bidi underneath |
|---|---|
| New lead: a lead captured in a chat | lead.created, GET /leads |
| New ticket: a conversation that became a helpdesk ticket | ticket.created, GET /tickets |
| Form submitted: a form the assistant asked a visitor to fill in | form.submitted, GET /agents/{agent_id}/submissions |
| Create or update a contact | POST /contacts |
| Send a message to a conversation and get the assistant's reply | POST /agents/{agent_id}/chat |
| Search leads (Make) | GET /leads |
With a plain webhook, today
No code needed: in Zapier create a Zap with the trigger Webhooks by Zapier > Catch Hook, copy the hook URL it gives you, paste it as a bidi endpoint and tick lead.created. Send a test event from bidi to see the hook answer, then leave your own details in the widget once so Zapier learns the fields from a real lead, and map data.name, data.contact and data.interest to your CRM, sheet or chat tool. Make's Custom webhook and n8n's Webhook node work the same way. The bidi apps for Zapier and Make add instant triggers and ready actions on top.
Recipe: every new lead into your CRM or a sheet
Make
The bidi app for Make offers the same triggers as Watch modules, the same two actions and a Search Leads module. Switching a scenario on attaches a dedicated webhook through POST /api/v2/webhooks, and each Watch module runs only for deliveries of its own event type. Make cannot keep a signing secret per webhook, so a Make scenario does not check the signature: its hook URL, which Make keeps secret, is what protects it.
What you need
A workspace on the Team plan or above, and a key from Settings > Developers > API keys with leads:read, tickets:read, webhooks:write, contacts:write, chat and agents:read. Each subscription shows in Settings > Developers > Webhooks with its delivery log, and counts toward the workspace's 10 endpoints.
Language
Zapier and Make show an app in one language and do not translate it, so the apps' labels and help are English. What flows through them is untouched: an Arabic lead, ticket subject or reply arrives in Arabic.