Send bookings, orders and leads to 10,000+ apps with Zapier

Your Secretary books appointments, takes orders and collects leads all day. Zapier lets each of those moments start something in the rest of your tools: a contact in your CRM, a message in Slack, a row in your accounts, a welcome email. Zapier now connects more than 10,000 apps, and Ordina can feed any of them.

Here is how the connection works, how to set it up in about five minutes, and six Zaps worth building first.

How Ordina connects to Zapier

Ordina connects through Webhooks by Zapier, Zapier's own tool for receiving events from any service. There is no separate Ordina app to search for in Zapier's directory: you start a Zap with a webhook trigger, and Ordina sends events to it.

Two things to know before you start:

• On Zapier, Webhooks by Zapier is a Premium app, so it needs a paid Zapier plan.
• On Ordina, Zapier is part of the Business plan, at $39 a month or $390 a year.

Set it up in five steps

1. Create the Zap. In Zapier, click Create, then Zap. For the trigger, choose Webhooks by Zapier and the event Catch Hook. Zapier shows an address starting with hooks.zapier.com. Copy it.
2. Paste it in Ordina. In your dashboard, open Integration, then Zapier. Paste the address, give it a name if you like ("New bookings to HubSpot"), and choose the events under Run the Zap when.
3. Send a test. Tap Send a test in Ordina, then Test trigger in Zapier. Zapier shows exactly what Ordina sent, field by field.
4. Build the action. Map those fields into the app you want: a CRM contact, a Slack message, a spreadsheet row.
5. Publish. Turn the Zap on. The last setup step in Ordina turns green when a real event reaches it.

Which events you can send

Everything sends all of these. Each one carries the booking or order, the client and the payment, with your business name and handle.

You can also pick events about your Secretary and connected apps: a conversation finished (with what came of it, such as booked, lead or abandoned), an intake completed, and the events for connected actions. These are only sent when you pick them by name; Everything does not include them, so an existing Zap never changes under you.

Six Zaps worth building first

1. New bookings into your CRM

Trigger on booking made. In HubSpot, Pipedrive or Google Contacts, find or create the contact by email, then log the appointment with the service, date and time. Add booking cancelled to a second Zap that updates the same record.

2. Leads to your team's chat

Trigger on new lead. Post the customer's name, contact and message to a Slack or Microsoft Teams channel, so someone can follow up while the lead is warm. The Secretary already answered what it could; this is for the questions it passed to your team.

3. Payments into your books

Trigger on payment received. Add a row to your bookkeeping sheet, or create a sales receipt in your accounting app, with the amount, currency and reference. If you only want a live spreadsheet, the built-in Google Sheets integration (also on Business) does that without a Zap.

4. Reviews where you can see them

Trigger on new review. Send five-star reviews to a channel the whole team reads, and send anything under four stars to the owner by email.

5. A follow-up after every visit

Trigger on booking completed. Add the customer to an email sequence in Mailchimp or another email tool, such as aftercare tips or a "book your next visit" reminder a few weeks later. Make sure your sequence respects your customers' consent and your local rules on marketing email.

6. Abandoned bookings to a follow-up list

Pick a conversation finished, then add a Zapier Filter step that continues only when the outcome is abandoned. Each run is a conversation where someone started a booking or order and stopped. The event holds no contact details, so use the conversation and booking ids it carries, or simply create a task for your team to look it up in Messages.

Looking up data from a Zap

A Zap can also read from Ordina. Use Zapier's Webhooks GET action on https://www.useordina.com/api/v1/appointments or /api/v1/orders, with the header Authorization: Bearer and an API key from Integration, API keys. That is handy for a daily digest, such as "tomorrow's confirmed appointments" sent to your phone each evening.

Good to know

• If a Zap is off, Ordina tries again up to five more times, over about 15 hours, then marks the event failed. Publish the Zap and new events go through.
• Pause a Zap from Ordina to stop sending without deleting it.
• Make, n8n and Pipedream work the same way: add their webhook address under Integration, Webhooks instead.
• Developers can verify every delivery with the signing secret. See our guide to webhooks, intakes and outcome events.

FAQ

Is there an Ordina app in the Zapier directory?

No. Ordina connects through Webhooks by Zapier: you start a Zap with the Catch Hook trigger and paste its address into Ordina under Integration, Zapier.

Do I need a paid Zapier plan?

Yes. Webhooks by Zapier is a Premium app on Zapier, so it needs a paid Zapier plan. On Ordina, Zapier is part of the Business plan.

Can Zapier create bookings in Ordina?

No. Zaps can receive events and read appointments and orders. Bookings, orders and payments are made through your booking page, your Secretary and your dashboard, so they always follow your availability and payment settings.

Does Ordina work with Make or n8n?

Yes. Add their webhook address under Integration, Webhooks, pick the events, and send a test. The events are the same as for Zapier.

Which plan includes Zapier?

The Business plan, at $39 a month or $390 a year. Every new account starts with a 7-day free trial of Pro, and you can move to Business from your dashboard at any time.