Zapier
Coming soonNot available yet. This page describes a feature we are still building, so it is not in your dashboard today. Everything below is what it will do when it ships.
Zapier connects Botvee to thousands of other apps. Start a Zap the moment you get a new lead, a chat finishes, a support ticket is opened or a booking is made, and send it to your spreadsheet, your CRM, Slack or anywhere else. You can also add a lead or open a ticket in Botvee from any other app.
Before you start
- A Zapier account — Free works, though a free plan checks for new items less often
- An API key from Botvee — You make it in the steps below. It is how Zapier proves it may use your account
How to set it up
- 1
Open the window
Go to Dashboard → Integrations → Zapier
- 2
Make a key
Give it a name, choose “All AI Agents” or one agent, and click “Create key”
- 3
Copy it
The key is shown once. Botvee keeps only a fingerprint of it, so copy it now
- 4
Add Botvee in Zapier
In a Zap, choose Botvee as the app. When Zapier asks you to connect, paste the key
- 5
Pick what should happen
Choose a trigger (what starts the Zap) or an action (what Botvee should do)
What you can do
- New Lead — Starts when a lead is captured
- New Order — Starts when an order arrives from a connected Shopify or WooCommerce store, with the customer, the items, the total and whether it is paid
- New Chat Started — Starts the moment a visitor writes to an agent on any channel, with the first message and a link to the chat
- COD Order Confirmed — Starts when a cash-on-delivery order is confirmed, by the customer or by an approved upfront payment
- COD Order Cancelled — Starts when a customer cancels a cash-on-delivery order
- COD Payment Uploaded — Starts when a customer sends a payment screenshot, with the amount and transaction read from it and whether the automatic checks passed
- Human Handoff Requested — Starts when a chat needs a person: the customer asked, the AI agent handed it over, or Botvee escalated it, with the customer’s last message, the agent, the channel and a link to the chat
- New Finished Conversation — Starts when a chat has finished (quiet for 30 minutes), with the topic, the customer’s first question and a link to the chat
- New Support Ticket — Starts when a ticket is opened
- New Booking — Starts when a booking is made
- Create Lead — Adds a lead to an agent. A lead that already has that email is completed, not duplicated
- Create Support Ticket — Opens a ticket in Support Tickets, and your team is notified as usual
All agents, or one agent
- A key for “All AI Agents” — Works with every agent. A Zap can narrow a trigger to one agent, and picks the agent when it creates a lead or ticket
- A key for one agent — Works with that agent only: it sees only that agent’s leads, chats, tickets and bookings, and what it creates goes to that agent
- Use one key per purpose — For example one for your sales Zaps and one for a client’s agent, so you can revoke one without touching the other
Authentication and public API
Zapier calls Botvee’s production API over HTTPS. Every request carries the API key as an Authorization: Bearer header. Keys are created by the customer, shown once, stored by Botvee only as a SHA-256 hash, and can be revoked at any time. A workspace key can use agent_id to select an agent; a one-agent key is restricted to that agent.
| Purpose | Method and endpoint |
|---|---|
| Test connection and label | GET /api/v1/me |
| List agents available to the key | GET /api/v1/agents |
| New leads | GET /api/v1/leads |
| New orders | GET /api/v1/orders |
| COD order decisions | GET /api/v1/cod-orders?status=CONFIRMED or CANCELLED |
| COD payment uploads | GET /api/v1/cod-payments |
| Human handoffs | GET /api/v1/handoffs |
| New chats | GET /api/v1/chats |
| Finished conversations | GET /api/v1/conversations |
| Support tickets | GET /api/v1/tickets |
| Bookings | GET /api/v1/bookings |
| Create a lead | POST /api/v1/leads |
| Create a support ticket | POST /api/v1/tickets |
GET endpoints return JSON arrays ordered newest first and every item has a stable id that Zapier uses for deduplication. List endpoints accept limit and, for workspace keys, agent_id. Date and time values use ISO 8601 with a timezone. POST endpoints accept JSON. Errors use { error: { code, message } }; an invalid or revoked key returns HTTP 401 and an out-of-scope agent returns HTTP 403.
Good to know
- Zapier checks for new items every few minutes (every 1 to 15 depending on your Zapier plan)
- You can have up to 20 keys. Each shows when it was last used
- Click “Revoke” on a key and every Zap using it stops working straight away
- Test chats are never sent
- Zapier actions use no credits
Troubleshooting
- Zapier says the key is invalid — It was revoked, or copied with a space. Make a new key
- A Zap finds nothing — The chat may not have finished yet (it needs 30 quiet minutes), or the key is limited to a different agent
- Create Ticket says Support Tickets is switched off — Turn it on in Dashboard → Explore Features
- “Say which agent” — A key for all agents needs the agent chosen in the Zap
Can’t find what you are looking for? Contact support

