Zapier connects Check Cherry to thousands of other apps without any code. Most businesses use it to stop retyping the same information in two places: new leads land in your CRM automatically, payments log themselves to a spreadsheet, and your team gets a Slack message the moment a booking is confirmed.
This article covers everything the integration can do. If you just need to get connected, see connecting Check Cherry to Zapier.
How a Zap works
Every Zap is built from two halves: a trigger and one or more actions. The trigger is the thing that happens. The action is what gets done about it. Read together, a Zap is just a sentence - "when this happens, do that."
The part people miss is that Check Cherry can sit on either side of that sentence. It can be the app that starts a Zap, or the app a Zap writes into.
| Check Cherry's role | What it means | Example |
|---|---|---|
| Trigger | Something happened in Check Cherry, and you want another app to know about it. Information flows out. | A new lead is added in Check Cherry, so Zapier creates a contact in Mailchimp. |
| Action | Something happened somewhere else, and you want it recorded in Check Cherry. Information flows in. | Someone fills out a Facebook lead ad, so Zapier creates a lead in Check Cherry. |
A Zap has exactly one trigger, but it can have as many actions as you need. One new booking can post to Slack, add a row to a spreadsheet, and create a task for your team, all from the same trigger.
Connect your account
Triggers: what starts a Zap
A trigger is the thing that happens in Check Cherry to kick off a Zap. There are twelve, and all of them are instant - Check Cherry pushes the data to Zapier as it happens rather than making Zapier check on a schedule.
Leads and users
| Trigger | When it fires |
|---|---|
| New Lead Is Added to Check Cherry | Someone submits a contact form, abandons a booking partway through, or you add a lead by hand. |
| New User Is Added to Check Cherry | A client or staff account is created - by manual entry, an invitation, a new booking, or an accepted proposal. |
Bookings and proposals
| Trigger | When it fires |
|---|---|
| New Event Is Added to Check Cherry | A booking is confirmed - through self-booking, by a client accepting a proposal, or entered manually. |
| Event Is Updated in Check Cherry | Any change to an existing booking. |
| Event Is Marked as Complete by Check Cherry | A booking is marked complete after the event. |
| New Proposal Is Added to Check Cherry | A proposal is created through self-booking or entered manually. |
Payments
| Trigger | When it fires |
|---|---|
| New Payment Is Recorded in Check Cherry | A client pays, puts down a deposit, or an admin records a payment manually. The payload includes the amount, method, client, and the booking it applies to. |
Staffing
| Trigger | When it fires |
|---|---|
| Staff Is Assigned to a Booking in Check Cherry | A team member is assigned to work an existing booking. |
Appointments and checklists
| Trigger | When it fires |
|---|---|
| New Appointment | A sales call, consultation, or planning meeting is booked. |
| Appointment Is Updated | An existing appointment is changed. |
| New Checklist Item Is Created | A checklist item is added to a booking or lead. |
| Checklist Item Is Updated | A checklist item changes, including being checked off. |
Actions: what Zapier can do inside Check Cherry
Actions run in the other direction. Something happens in another app, and Zapier creates or looks up a record in Check Cherry.
Create records
| Action | What it does |
|---|---|
| Create Lead | Adds a lead with contact info, event details, and budget. |
| Create Proposal | Adds a proposal with customer data, package selection, and pricing. |
| Create Confirmed Event | Adds a confirmed booking with customer details, pricing, venue, and event specifics. |
Look records up
| Action | What it does |
|---|---|
| Check Availability | Confirms whether a date and time is open, optionally for a specific package or add-on. |
| Find Lead | Searches by ID, email, origin, or type. |
| Find Event or Proposal | Searches by ID, status, date range, or free text. |
| Find Payment | Searches by date range or booking. |
| Find User | Searches by role or free text. |
| Find Appointment | Searches by date range or free text. |
| Find Checklist Item | Searches by filter, text, or record type. |
| Find or Create Lead | Looks for a matching lead and creates one only if there isn't one already. |
Automations worth building first
| What you want | Trigger | Then |
|---|---|---|
| Every new lead in your CRM or email list | New Lead Is Added | Create or update a contact in Mailchimp, ActiveCampaign, HubSpot, or Flodesk. |
| Leads from Facebook or your website in Check Cherry | Facebook Lead Ads, Wufoo, WordPress, or your form tool | Find or Create Lead in Check Cherry. |
| A running record of every payment | New Payment Is Recorded | Add a row in Google Sheets, or create a sales receipt in QuickBooks Online. |
| Your team notified when a booking lands | New Event Is Added | Post a message to a Slack channel. |
| Review requests that send themselves | Event Is Marked as Complete | Send an email or trigger your review platform. |
| Staffing changes on your team's radar | Staff Is Assigned to a Booking | Post to Slack, or add the shift to a shared calendar. |
Two things specific to Check Cherry
Leads that arrive through Zapier are tagged
Any lead created by a Zap gets an origin of Zapier. That means you can treat those leads differently from the ones that come through your booking engine - most usefully, by sending them their own automated message.
New lead triggers are delayed slightly
The New Lead trigger waits about a minute before firing. Leads from an incomplete booking wait roughly twenty minutes, which gives the client a chance to come back and finish checking out. If they do finish, you get a booking instead of a stale "someone abandoned their cart" alert.
When a Zap isn't working
Turn on enhanced logging from the Integrations page, run the Zap again, and look at the request logs to see exactly what Check Cherry sent or received. Enhanced logging stays on for one week and then switches itself off.
Watch it in action
For a longer walkthrough, watch our Zapier automation webinar.