Every order, booking, appointment, ticket and completed call can reach Zapier seconds after the caller hangs up, through the AskSiya REST API and outbound webhooks. A listed AskSiya app in the Zapier directory is still in progress, so for now you wire it yourself with a Catch Hook.
Search the Zapier app directory for AskSiya and you will not find us. There is no published one-click integration, and no pre-built triggers or actions with our name on them. That app is being built; we will not pretend it shipped.
What is live right now is the plumbing underneath it: an authenticated REST API and outbound webhooks that fire the moment a call ends. Zapier consumes both with tools it ships itself, Webhooks by Zapier for the push route and a scheduled Zap for the pull route. The setup below is real and takes about twenty minutes.
This is the one almost everybody wants: something happens on the phone, and a second later it is in Zapier.
order.created, booking.created, appointment.created, appointment.cancelled, ticket.created, call.completed.One Zap can serve every event and branch on the X-AskSiya-Event header, or you can filter inside Zapier. The API and webhooks guide lists every header we send, including X-AskSiya-Signature for verifying deliveries in a code step.
Some people would rather not expose a webhook URL, or want one batch an hour instead of a ping per event.
Build a Zap with a Schedule by Zapier trigger, add a Webhooks by Zapier GET action pointed at an AskSiya list endpoint, and send your key in an Authorization: Bearer <key> header. Pass a since parameter so each run pulls only what is new.
The endpoints, the since, limit and cursor parameters and a working example are in the developer guide. Keep the schedule to once a minute at most; webhooks are faster and cheaper on your task count anyway.
| AskSiya event | What teams do with it |
|---|---|
order.created | Fire a kitchen printer, or append a row to a Google Sheet the owner reads over coffee. |
booking.created | Add the stay to a PMS spreadsheet and drop a line in the front desk Slack channel. |
appointment.created | Create the event in Google Calendar and open a matching record in the CRM. |
appointment.cancelled | Text the owner so the slot gets refilled before it goes cold. |
ticket.created | Open a job in the maintenance tracker, and page the on-call tech if urgent. |
call.completed | Attach the transcript to a CRM record, or roll the day into a digest email. |
On the roadmap: a listed Zapier app with proper triggers and actions. We build connectors in the order customers ask for them, but we will not put a date on it. Tell us what you would connect and we will tell you where it sits.
The API and outbound webhooks are included on every plan, starting with Starter at $29/mo for 150 included minutes. No automation tier, no per-request fee.
Your plan decides which records exist to send. Restaurant order taking is +$49/mo, hotel room booking +$49/mo, table reservations +$29/mo, the property ticket desk +$29/mo. All four are free on Pro, and free on every plan during early access. Full ladder on the pricing page.
New to this? The phone side matters more than the plumbing. Pizza shops and property managers see the payback first, and the missed-call calculator shows why. The integrations hub has the rest of the guides.
Not yet. If you search the Zapier app directory for AskSiya you will not find a listed app, and there are no pre-built AskSiya triggers or actions. Building and publishing that app is in progress, and we will not put a date on it.
What works today is the do-it-yourself route on this page: our outbound webhooks into a Webhooks by Zapier Catch Hook, or a scheduled Zap that calls the AskSiya REST API. Both are live in production and neither one requires a listed app.
No. The Catch Hook route is copy and paste: Zapier gives you a URL, you save that URL on the Integrations page of your AskSiya dashboard, you make one test call so a real payload arrives, then you drag fields into whatever action you want. Most people are done inside twenty minutes.
You only need someone technical if you want to verify the webhook signature in a code step, or if you are building your own service instead of using Zapier. The developer guide covers both.
We retry. Any delivery that does not get a 2xx response, or that times out, is retried after 1 minute, 5 minutes, 15 minutes, 1 hour, 6 hours and 24 hours, then given up on. That is a bit over 31 hours of cover.
If a delivery is missed entirely, nothing is lost from your records. Everything Siya captured is still in your dashboard and still readable from the list endpoints with a since parameter, so you can backfill the gap.
Any of them. The API and outbound webhooks are included on every plan, starting with Starter at $29/mo for 150 included minutes, with no automation tier and no per-request fee.
What changes by plan is which records exist to send. Restaurant order taking is +$49/mo, hotel room booking +$49/mo, table reservations +$29/mo and the property ticket desk +$29/mo. All four are free on Pro and free on every plan during early access, so during early access every event on this page is available on Starter. See the pricing page.
Partly, and only if you build that half yourself. AskSiya has no native two-way sync with any POS or PMS, so there is no AskSiya action that writes into those systems. What we give you is a reliable trigger: the moment an order or a booking exists, Zapier knows about it with every field Siya captured.
What happens next depends on what your POS or PMS exposes. Plenty of operators stop at a spreadsheet, a printed ticket or a Slack alert, because that already removes the retyping. See the Toast and Cloudbeds guides, or ask us what is realistic for your stack.