- Home
- Resources
- Integrations
- Appointlet
Appointlet Zapier integrationAutomate Appointlet with Zapier.
The Appointlet Zapier integration gives you 12 triggers and 2 searches. Every booking, cancellation, approval or tag in your scheduling pages can start a Zap the second it happens, and the work then lands in the other tools your team already uses.
Verified Trustpilot reviews · AI, automation & growth agency
What the Appointlet Zapier integration is for
Appointlet handles the booking side of your meetings: the scheduling page, the requests, the reminders. Zapier listens to it. Each time a meeting is booked, approved, moved, cancelled or tagged, Appointlet tells Zapier, and Zapier carries that news into the rest of your tools without anyone copying a name or a time slot by hand.
Three outcomes come back again and again.
A pipeline that knows who booked. Meeting Scheduled or Attendee Scheduled starts the Zap, and the next step creates the person in your CRM or adds them to a mailing list. Sales sees the demo before the prospect shows up.
A calendar that stays honest. Meeting Rescheduled and Meeting Cancelled push the change wherever the original slot was recorded, so a dead meeting does not sit in a report.
An approval flow with a paper trail. When you review requests before accepting them, Meeting Approved and Meeting Declined let the outcome reach the right person, and Meeting Tagged sorts meetings by the labels you give them.
What Zapier does not do for Appointlet: there are no actions at all. A Zap cannot create, move or cancel a meeting inside Appointlet; it can only react to what happens there and look up meetings or attendees with its two searches. The same app on the other platform has its own page, the Appointlet Make integration, and Make vs Zapier compares the two tools.
Zapier vocabulary in one minute
Seven words do the heavy lifting on this page. Plain definitions first.
- Zap
- The automation you build on Zapier: one trigger, followed by one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event, and nothing runs before it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, here always in another app.
- Task
- The unit Zapier bills: one action the Zap completes successfully. Your plan allowance is a count of those tasks.
- Polling vs instant
- Zapier checks a polling trigger on a timer. An instant trigger is pushed by the app itself as soon as the event takes place.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops that run otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps after it can use what it found.
What an Appointlet Zap costs
Bookings arriving cost nothing. Only the action that follows, in another app, uses a task when it succeeds.
- Premium appNo, free plan accepted
- Free plan100 tasks a month, two-step Zaps
- Triggers12 instant, 0 polling
- BilledEach successful action, on its own
Appointlet is not a premium app, so it works on the free plan: 100 tasks a month, unlimited Zaps, and two steps per Zap (one trigger, one action). A second action, a filter or a search step makes it a multi-step Zap, which needs a paid plan. Every action that succeeds is counted separately, so sending a booking to your CRM and to your team chat costs two tasks per meeting. An action that fails is not counted.
Connect your Appointlet account to Zapier
- 01
Start from the Apps page
In Zapier, open Apps and click + Add connection. A connection is your Appointlet account linked to Zapier once, then reused by every Zap that listens to it.
- 02
Pick Appointlet
Search for Appointlet in the dialog, select it, and click Add connection. Appointlet opens in a new tab, and that is where the sign-in happens, with your Appointlet credentials rather than your Zapier ones.
- 03
Sign in and allow access
Log in to the Appointlet account that owns the scheduling pages you want to watch, then grant Zapier access. You need your own account, plus access to any organization you do not own but want a Zap to follow.
Your first Zap: every booked demo reaches sales
GoalWhen someone books through your scheduling page, create the contact in your CRM and warn the team.
- 01
Build: choose the trigger
Create a Zap, pick Appointlet and the Attendee Scheduled event, then select your Organization. This trigger also fires when someone joins an existing meeting.
- 02
Test with a real booking
Run the test: Zapier pulls the three most recent items from your account. Book a test slot first if your page is new, so there is something real to map.
- 03
Send the person to your CRM
Add your CRM as the action app and map the attendee details the trigger test brought back into its contact fields. That is one task per booking.
- 04
Tell the team
Add a second action in your team chat to post the booking. It makes the Zap multi-step, so a paid plan is needed from here.
- 05
Test, then Publish
Test each step, check that the contact and the message really arrived, then click Publish to switch the Zap on for good.
Appointlet triggers on Zapier
12 events start a Zap when something happens in Appointlet, and 12 of them are instant: the app calls Zapier straight away, whatever your plan.
Attendee Approved
Instant triggerIn Zapier“Triggers when an attendee scheduling request is approved.”
Fires once you accept a person's request to book, on pages where requests wait for your approval. The run carries that attendee, not the whole meeting, which suits flows centred on one guest.
Attendee Cancelled
Instant triggerIn Zapier“Triggers when an attendee cancels.”
Starts the Zap when a guest cancels their place. In a group session, the meeting itself may continue for the others; this event is about one person leaving it.
Attendee Declined
Instant triggerIn Zapier“Triggers when an attendee scheduling request is declined.”
Reacts when you turn down a person's booking request. It closes the loop on approval pages, where silence would otherwise leave the applicant guessing.
Attendee Reminded
Instant triggerIn Zapier“Triggers after a reminder is sent to an attendee.”
Runs right after Appointlet sends a reminder to a guest. It lets you piggyback on Appointlet's own reminder timing instead of building a schedule in Zapier.
Attendee Scheduled
Instant triggerIn Zapier“Triggers when an attendee schedules a meeting or joins an existing one.”
Triggers when a person books a meeting or joins one that already exists. It is the right entry point whenever the guest matters more than the slot.
Meeting Approved
Instant triggerIn Zapier“Triggers when a meeting is approved.”
Goes off when a meeting that was waiting for approval gets accepted. It looks at the meeting as a whole, which makes it the cleaner choice for one-to-one calls.
Meeting Cancelled
Instant triggerIn Zapier“Triggers when a meeting is cancelled.”
Fires as soon as a meeting is cancelled. The whole slot is gone, which is what you want to mirror in the tools that recorded it.
Meeting Declined
Instant triggerIn Zapier“Triggers when a meeting is declined.”
Starts when you decline a meeting request. Paired with the approval trigger, it gives you both outcomes of a review process.
Meeting Rescheduled
Instant triggerIn Zapier“Triggers when a meeting is rescheduled.”
Reacts when a meeting moves to another time. Without it, every copy of the original slot in other tools quietly goes out of date.
Meeting Scheduled
Instant triggerIn Zapier“Triggers when a meeting is scheduled.”
Each new booking of a meeting starts this one. It reads the booking as one event, which fits one-to-one pages and keeps the Zap simple.
Meeting Tagged
Instant triggerIn Zapier“Triggers when a meeting is tagged.”
Fires whenever a tag is put on a meeting. Tags become a way to steer meetings by hand: you label one, the Zap does the rest.
Meeting Untagged
Instant triggerIn Zapier“Triggers when a tag is removed from a meeting.”
Runs when a tag is removed from a meeting. It is the reverse switch of the tagging trigger, useful to undo what a tag set in motion.
Appointlet searches on Zapier
2 search steps look for data that already exists in Appointlet, so a later step can use it.
A search step looks up something that already exists so later steps can use it. In the action list, searches appear at the bottom under SEARCH, and some fields offer + Add search step to insert one right before. Any search makes the Zap multi-step, so it needs a paid plan. How strict a match has to be is up to Appointlet, not Zapier. Neither search offers a find-or-create variant.
Find Attendee
SearchIn Zapier“Finds an attendee.”
Looks up a person who booked through your Appointlet pages and hands their details to the steps that follow.
Find Meeting
SearchIn Zapier“Finds a meeting.”
Retrieves a meeting from Appointlet so a later step can reuse what the search returns.
The three settings every search exposes
- Successful if no search results are found?On its default, a search that finds nothing stops the Zap there and the steps depending on it are skipped. Turned on, the Zap goes on without a result.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Neither Appointlet search offers it, so this box never shows up here.
- If multiple search results are found?Three options when several items match: keep the first one, the default, stop the Zap, or pass every match on to the next step.
When an Appointlet Zap breaks
Zapier links no help article to Appointlet. The failures below come from how Zapier behaves in general, applied to booking flows.
With twelve triggers that sound alike, check first that the Zap listens to the right event. The Zapier troubleshooting page goes further on the general cases.
Past bookings never show up
A Zap only reacts to bookings made after you publish it. Meetings already in your calendar are not picked up; bringing them over is a separate job.Approval events that never fire
Approved and Declined only happen on pages that ask for approval. On a page that books directly, those Zaps stay silent forever.Group sessions eating tasks
Attendee Scheduled runs once per guest. A group session with many sign-ups means as many runs, and each successful action is a task.A rush of bookings held back
If a launch or a migration creates a huge batch of meetings at once, Zapier's flood protection can hold those runs back.
Need help automating Appointlet with Zapier?
A person reads every message.



