How to Connect Airbnb to Zapier, Make or Slack
The short answer
Airbnb does not give hosts a way to connect to Zapier. Its connections are kept for approved software partners, and we could not find an official Airbnb app in Zapier’s directory when we checked in October 2026.
What you can do is use the one thing Airbnb does send you: the booking confirmation email. Airflow reads that email, turns it into a booking, and then sends a message to any web address you choose each time a booking is created, changed or cancelled. Zapier, Make and n8n all give you such an address. From there the booking can go anywhere those tools reach.
The same route works for Booking.com and Vrbo, and for direct bookings taken on your own booking page.
How it works
- The channel emails you. Airbnb sends its usual confirmation.
- Airflow reads it. Forward the email to your listing’s Airflow address, or connect your inbox and Airflow picks it up itself. The booking appears on your Airflow calendar.
- Airflow tells your other system. Within about a minute it sends a message to the web address you added.
- Your automation runs. Zapier, Make or n8n receives the booking and carries out the steps you set up.
First, check what Airflow already does
Several things people reach for Zapier to do are built into Airflow. Use the built-in one where it exists: there is nothing to set up in a second tool and nothing to keep in step.
| You want | Built into Airflow | Reach for Zapier when |
|---|---|---|
| A row per booking in a spreadsheet | Google Sheets export | You keep your log in Airtable or Notion |
| Invoices in your accounts | Xero, QuickBooks, Sage and FreshBooks | Your accounts are in something else: each message carries the booking’s money lines |
| Emails to guests before and after a stay | Guest email automations | You message guests from a CRM or an SMS tool |
| A checklist for each clean | Checklists for cleaners | Your cleaners already work in another app |
| Bookings on your own calendar | Google and Outlook calendar connections, and a calendar link for anything else | You need the entry created without pressing Sync |
| Guests on a mailing list | Mailchimp | Your list is somewhere else |
Connect out is for the other case: your team already lives in a tool Airflow does not connect to, and you want the booking to arrive there.
Eight things worth building
Each one starts with a message from Airflow. “When” is the event that starts it.
| What it does | When | What your tool does |
|---|---|---|
| Tell the team where they already talk | New booking | Posts the listing, dates and guest count to a Slack or Teams channel |
| Text the cleaner | New, changed, cancelled | Sends an SMS through Twilio or a similar service |
| Plan each turnover | New, changed, cancelled | Creates a task in Trello, Asana or Todoist due on check-out day, and moves or removes it later |
| Keep a base, not a sheet | New, changed, cancelled | Adds and updates a record in Airtable or Notion, linked to your own tables |
| Remind the day before | New booking | Waits until the day before check-in, then reminds whoever prepares the place |
| Flag short notice | New booking | Alerts you only when check-in is within the next seven days |
| Feed your own system | New, changed, cancelled | Sends the booking to a CRM, an owner dashboard or software you wrote yourself |
| Invoice in another accounting system | New booking, payment received | Creates an invoice from the booking’s money lines in Zoho Books, FreeAgent or another system, and marks it paid when the payment arrives |
Narrowing it down
Every message carries the listing, the channel and the dates, so your tool can filter on them: only Airbnb bookings, only one listing, only stays of a week or more. In Zapier this is a Filter step, in Make a filter on the route, in n8n an If node.
Changes and cancellations are the useful part
Most Airbnb-to-Zapier methods only catch a new booking. That is enough to create a cleaning task. It is not enough to keep the task right.
Airflow also sends a message when the dates, the guest count or the total change, and when a booking is cancelled. Each message carries the same booking reference, so your automation can find the task, calendar entry or row it made earlier and move it or remove it. Without that, a cancelled stay leaves a cleaner booked for a turnover that is not happening.
A practical way to build it: make three small automations, one per event, that all look up the same reference.
A worked example: a Slack message to your cleaner
- In Zapier, create a Zap with the trigger Webhooks by Zapier and the event Catch Hook. Zapier gives you a web address.
- In Airflow, open Connections and choose the External automations tab. Choose Add an address, paste the address from Zapier, and tick New booking.
- Press Send test event. Zapier receives a sample booking so you can see the fields.
- Add the action Slack: Send Channel Message and build the message from the fields, for example: New booking at listing name: check-in to check-out, adults adults. Clean on check-out.
- Turn the Zap on.
Using a different tool? The same steps are written out for n8n and for Make.
Automations that wait
A reminder the day before check-in is built with your tool’s own waiting step: Delay Until in Zapier, Sleep in Make, Wait in n8n. Airflow sends its message when the booking is made; the waiting happens on their side.
One thing to build in: a waiting automation does not know the booking was cancelled afterwards. Either have your cancellation automation remove the task the reminder points to, or have the reminder check the booking log before it sends.
What each message contains
The event type, your listing, the booking reference, the channel it came from, check-in and check-out dates, nights, the number of guests, the total, the payout and the status. It also carries the money lines: accommodation, cleaning fee, other fees, taxes, discounts and what the channel kept.
The guest’s name, email and phone are not sent unless you switch that on for the address. Once sent, the other system holds your guests’ details, so only switch it on when the automation needs them. The full format is in the Connect out guide.
The limits
- It is one way. Airflow can tell your other systems what happened on Airbnb. It cannot change anything on Airbnb: no prices, no replies to guests, no blocked dates beyond the usual calendar link.
- Four events only. A booking created, changed or cancelled, and a payment received on a booking you collect yourself. Airbnb pays you outside Airflow, so an Airbnb payout is not a payment event. Nothing is sent for a refund, a review or a guest message.
- It starts from today. Bookings already in your account when you add your first address are not sent as new.
- It is as fast as the email. With a connected inbox the message follows the confirmation by a minute or two. If you forward emails by hand, it waits for you.
- It carries what the email carries. Airbnb hides the guest’s email address, so nothing can pass it on. Guest follow-up works best for direct bookings.
- It is not an Airbnb integration. Airflow is not an Airbnb partner and does not sign in to your Airbnb account. It reads the emails Airbnb sends you.
What it costs
Each booking sent out uses one automated task from your allowance, the first time it is delivered. Later changes to that booking, its cancellation, payments on it, a second address, test events and failed deliveries are free. Connect out is part of the Growth plan and above; see pricing.
Get started — see plans and pricing.