> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.uplisting.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Trigger Zap on check out

# Trigger Zap on check out

A common requirement is to trigger an event or action based on a guest checking out.

It is possible to create Zaps that trigger based on a booking checking-out (or checking-in) using the `Booking Update`trigger. [What triggers a booking update?](https://uplisting.crisp.help/en/article/zap-triggers-62qjy7/)

## How to set up a Zap to trigger when a guest checks-out

The first step is to trigger the Uplisting Booking Updated event.

![Uplistings booking update event](https://files.readme.io/2d124e1-image.png)
  Uplistings booking update event
</Image>

### Create a filter

Next, we need to add a Zapier filter step. This filter will ensure the trigger only fires or causes an action based on specific attributes. [Check out this guide](https://uplisting.crisp.help/en/article/zap-triggers-62qjy7/) to see what booking updates trigger a booking updated event. For example, a booking update is triggered if the guest's email address is updated. We don't want to trigger this Zap when a guest's email is updated, only when a guest checks out.

Checking what booking statuses are available ([here](https://uplisting.crisp.help/en/article/zap-triggers-62qjy7#booking-status), we can see there are two that may be relevant:

1. `checked_out`\
   A booking is `checked_out`when a user manually selects the "Check guest out" button on a booking.\
   ![](https://files.readme.io/e42234a-image.png)
2. `needs_check_out`\
   A booking status is set to `needs_check_out` at 12am UTC on the day of checkout. This means a guest has not necessarily checked out of your property when the booking update event for this status is triggered.

> ℹ️ When to use each status?
> If you rely on manually checking guests out, use the `checked_out`status. If you don't manually check guests out use the `needs_check_out` status, or use both (as we have in the screenshot below).

> 🚧 Add a Zapier Delay action is using `needs_check_out`
> A booking status is set to `needs_check_out` at 12am UTC on the day of checkout. This means a guest has not necessarily checked out of your property when the booking update event for this status is triggered.
>
> If you are using the `needs_check_out`status add a Zapier Delay action as a third step if you want the action to take place after the guest has actually checked out.

Create a filter similar to what is shown in the image below.

![](https://files.readme.io/e344a2e-image.png)

Finally, create your action. This could be to send an email, an sms, add a row to a spreadsheet or one of 1000 other potential actions.