# Zapier

[**Zapier**](https://zapier.com) connects thousands of apps without code. The
[42min app on Zapier](https://zapier.com/apps/42min/integrations) can start a
Zap when someone books, reschedules or cancels a meeting, and a Zap can book or
cancel meetings in 42min and look up bookings for its later steps.

In 42min, the app has its own page under
[**Integrations → Zapier**](/360/integrations/zapier), which also shows whether
your account is connected.

<Callout type="tip">
Would rather run your automations on your own server? The
[n8n node](/help/integrations/n8n) does the same kind of work, and your booking
data stays on your own infrastructure.
</Callout>

## What it does

**Triggers** start a Zap when something happens in 42min:

- **Booking Created**: a new meeting is booked.
- **Booking Rescheduled**: a booking moves to a new time.
- **Booking Canceled**: the invitee or the host cancels a booking.
- **Booking No-Show**: an attendee is marked as a no-show.

**Actions** let a Zap change something in 42min:

- **Create Booking**: books a meeting on one of your event types at the time
  you choose.
- **Cancel Booking**: cancels a booking, with an optional reason.

**Searches** look up 42min data for later steps:

- **Find Booking**: finds the most recent booking for an attendee's email
  address.
- **Find Event Type**: finds an event type by its slug.

## Connect your account

1. In Zapier, create a Zap and choose **42min** for a trigger or an action.
2. When Zapier asks for an account, connect a new one. A 42min window opens.
3. Sign in to 42min if you are not signed in already, check the permissions,
   and approve.

Zapier asks for permission to:

- read your profile
- view your event types and check availability
- view bookings, and create, cancel, reschedule and edit them
- view and manage webhooks, which is how its triggers hear about new bookings

A connection belongs to the person who approves it. Anyone who wants to build
their own Zaps connects their own 42min account.

## Build your first Zap

1. Open [42min on Zapier](https://zapier.com/apps/42min/integrations) and create
   a Zap.
2. Pick a 42min trigger, for example **Booking Created**, and connect your
   account.
3. Test the trigger. Zapier loads a few recent bookings, so you can map their
   fields in the steps that follow.
4. Add the next step, such as a new row in Google Sheets or a message in Slack,
   and publish the Zap.

Booking fields use the same names as the 42min API. If a field is unclear, look
it up in the [bookings reference](/help/api/bookings).

## See or remove the connection

Your Zapier connection is listed on
[**Integrations → Zapier**](/360/integrations/zapier), with the date it was
connected and when Zapier last used it. Admins also find it under
[**API → Connected apps**](/360/api?tab=connectedApps).

To stop using Zapier:

1. **Turn off your 42min Zaps in Zapier.** Turning a Zap off tells 42min to stop
   sending it bookings.
2. **Click Disconnect** on the Zapier page in 42min. Zapier loses access to your
   account right away.

<Callout type="warning">
Disconnecting does not switch off Zaps that are still on. They can keep
receiving new bookings, so turn them off in Zapier before you disconnect.
</Callout>

## Things worth knowing

**The app is free, and Zapier's plan limits still apply.** Zapier counts the
work your Zaps do against your Zapier plan, not against 42min.

**Create Booking makes a real booking.** It goes through the same steps as a
booking made on your booking page: the invitee gets a confirmation email, and
the meeting is added to the host's connected calendar. Test with your own email
address first.

**Cancel Booking is real too.** The booking is canceled the same way the cancel
link in a confirmation email cancels it, so the usual cancellation emails go
out and the time becomes free again.

## Where to look next

- [42min on Zapier](https://zapier.com/apps/42min/integrations), with ready-made
  app pairings
- [n8n](/help/integrations/n8n), if you would rather host the automation
  yourself
- [Webhooks](/help/api/webhooks), to receive booking events in your own code
