cituro Zapier integrationAutomate cituro with Zapier.
The cituro Zapier integration gives you 3 triggers, 3 actions and 4 searches, all on the free plan, and every trigger is instant. Here is what each operation does for a business that takes bookings, what it costs in tasks, and where a cituro Zap goes wrong.
Verified Trustpilot reviews · AI, automation & growth agency
What the cituro Zapier integration is good for
cituro is online scheduling software: customers book appointments themselves, and the business keeps its calendar and customer list in one place. Linked to Zapier, cituro starts an automation the moment a booking or a customer record appears or changes, and it lets other tools create, update, find or delete customers in it.
Three outcomes come up most naturally. A customer list your other tools can trust: New Customer and Updated Customer send every new or edited record onward the instant it happens. Bookings that reach the rest of the business: New Booking tells another tool an appointment was made, without anyone forwarding it. Customer records managed from outside: Find Customer by Email spots an existing customer, then Update Customer changes the newsletter or blocked setting, or Create Customer adds a new one.
What Zapier does not do here: every action works on customers, none on bookings. You cannot create, move or cancel an appointment through Zapier, only react to a new one. There is also no trigger for a cancelled or changed booking. On the plus side, all three triggers are instant, so the Zap starts right away whatever your plan.
The same app is also on Make: the cituro Make integration covers it there, and Make vs Zapier is there if you are still choosing a platform.
Zapier words in one minute
Seven terms come back on every Zapier page. Here they are once, in plain English.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event.
- Action
- What the Zap does once it has started: the step that creates, updates or deletes something for you.
- Task
- The unit Zapier bills: one action your Zap completed successfully. The quota on your plan counts those.
- Instant vs polling
- An instant trigger is reported by the app itself the moment it happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so later steps can use what it found.
What a cituro Zap really costs
cituro is not a premium app, so it runs on Zapier's free plan. That plan only builds two-step Zaps, though: one trigger, one action.
- Free plan100 tasks per month, unlimited Zaps
- Free plan stepsOne trigger and one action
- cituro on freeYes, not a premium app
- BilledEach successful action, never the trigger
The trigger never costs a task. Each action that succeeds counts once; a failed action is not billed. A Zap that flags each suspicious new customer uses one task per customer it updates, and nothing for the ones the filter lets through. The filter itself, or any of the four searches, makes the Zap multi-step, so it needs a paid plan. Because all three cituro triggers are instant, the interval grid below never slows them down; it only applies to polling apps you add to the Zap.
Connect your cituro account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your cituro account linked once, then reused by every step that touches cituro.
- 02
Pick cituro and confirm
Search for cituro in the dialog, select it and click Add connection. You need a working cituro account at this point, with access to the customer list the Zap will read or change.
- 03
Sign in and grant access
Log in to cituro in the tab that opens and allow Zapier in. If the Zap will update or delete customers that someone else manages, your user needs write access to them.
Your first Zap: block fake sign-ups
GoalWhen a new cituro customer signs up with an address from a throwaway domain, the record is marked as blocked so it cannot book.
- 01
Set the trigger
Create a Zap, choose cituro and the New Customer event, then select your connection. This trigger is instant, which the editor shows with a lightning bolt.
- 02
Test on a real customer
Run the test: Zapier brings back the three most recent customers from your account. Pick one so the next steps are mapped on real data rather than a guess.
- 03
Add the filter
Click the plus icon, add a Filter, and set the email, a text rule such as ends with, and the domain you want to stop. This step makes the Zap multi-step, so a paid plan.
- 04
Add Update Customer
Add cituro with Update Customer. Map the customer ID from the trigger into ID, the one required field, and switch Blocked on.
- 05
Test, then publish
Test with a dummy customer, open cituro and check the record is blocked. When the result is right, click Publish to switch the Zap on.
cituro triggers: 3 instant events
3 events start a Zap when something happens in cituro, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.
New Booking
Instant triggerIn Zapier“Triggers when a new booking is created.”
Starts your Zap the moment an appointment is booked in cituro. It is the only booking-related operation in this integration, so it is how the rest of your tools learn that someone has reserved a slot.
New Customer
Instant triggerIn Zapier“Triggers when a new customer is created.”
Fires when a customer record is created in cituro, so each new person on file can be passed on as soon as they appear. It is the starting point for any Zap that greets, checks or copies new customers.
Updated Customer
Instant triggerIn Zapier“Triggers when a customer is updated.”
Reacts each time a cituro customer record changes, for example a newsletter choice or a block. It keeps other tools aligned with what the front desk edits during the day.
cituro actions: create, update, delete customers
cituro gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Customer
ActionIn Zapier“Creates a Customer”
Adds a customer to cituro. First name and last name are required; you can also set the Newsletter and Blocked options.
Delete Customer
ActionIn Zapier“Deletes a Customer”
Removes a customer from cituro using their ID. It is the only field the action needs.
Update Customer
ActionIn Zapier“Updates a Customer”
Changes an existing cituro customer, identified by its ID. Among other settings, you can switch Blocked on or off; a blocked customer cannot book appointments.
cituro searches: 4 ways to find a customer
4 search steps look for data that already exists in cituro, so a later step can use it.
A search step looks up something that already exists and hands it to the next steps. Searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not clean.
Find Customer by Email
SearchIn Zapier“Reports the customers list filtered by a specified mail address.”
Looks for cituro customers matching an email address. Email is the most reliable key you will usually have from another tool.
Find Customer by Last Name
SearchIn Zapier“Reports the customers list filtered by a specified last name.”
Returns the customers whose last name matches the one you give. Handy when a phone booking gave you a name but no email.
Get Customer by ID
SearchIn Zapier“Gets the corresponding customer for the specified id.”
Fetches exactly one customer from their cituro ID. It is the precise lookup when an earlier step already carries that identifier.
Search Customer
SearchIn Zapier“Searches for customers. Without search criteria, the unfiltered customer list is the result. Limited to 10 entries (sorted in descending order by creation date).”
Searches customers, optionally by the Blocked and Newsletter settings. With no criteria, it returns the unfiltered list, capped at 10 entries, newest first.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. cituro offers no such variant on any of its four searches, so it does not apply here.
- If multiple search results are found?Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a cituro Zap breaks
Zapier links no help article to cituro and lists no cituro-specific limit beyond the 10-entry cap on Search Customer. What follows comes from how Zapier itself behaves.
Four cases are worth knowing before you publish. If yours is not here, the Zapier troubleshooting page takes over.
An update that updates itself
Updated Customer plus Update Customer in one Zap: each change starts a new run, which makes a new change. The loop keeps going and eats your task count.Existing customers stay out
A Zap only reacts to bookings and customers created after you publish it. The existing list is never sent; moving it is a separate job.A bulk import floods the Zap
Importing a large customer list into cituro can fire New Customer for a huge batch at once, and Zapier's flood protection may hold it back.Search Customer stops at 10
Without criteria, Search Customer returns only the 10 most recently created customers. A Zap counting on the full list will miss the rest.
Need help automating cituro with Zapier?
A person reads every message.
