> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reservation and appointment events

> Platform events for new and modified reservations and appointments, reservation labels, and agent runs timed to check-in or check-out, with every filter they offer.

These events start an internal agent when a reservation or appointment is created or changes, when a label is added to a reservation, or at a set time around a stay. See [Platform events](https://docs.conduit.ai/build-your-agent/agents/internal-agents/platform-events/overview.md) for how to add a trigger.

| Event | Runs when | Filters |
| - | - | - |
| [New reservation](#new-reservation) | A reservation is created. | Inbox |
| [Reservation modified](#reservation-modified) | A reservation changes. | Inbox, Reservation changes |
| [Reservation label added](#reservation-label-added) | A label is added to a reservation. | Label, Inbox |
| [Check-in](#check-in-and-check-out) | A set time before or after a reservation's check-in. | Timing, Inbox, Run for all reservations |
| [Check-out](#check-in-and-check-out) | A set time before or after a reservation's check-out. | Timing, Inbox, Run for all reservations |
| [New appointment](#new-appointment) | An appointment is created. | Inbox |
| [Appointment modified](#appointment-modified) | An appointment changes. | Inbox, New status |

## New reservation

Runs when a reservation is created in Conduit, for example when your PMS syncs a new booking.

| Filter | Options |
| - | - |
| **Inbox** | Only run for reservations in this inbox. Empty runs for every inbox. |

**Example task:** "A new reservation came in. If the stay is 7 nights or longer, check the listing's Knowledge for a weekly cleaning add-on and create a task for the housekeeping team to offer it."

## Reservation modified

Runs when a reservation changes. Add rules under **Reservation changes** to pick which changes matter. The agent runs when at least one rule matches. With no rules, it runs on any supported change.

| Filter | Options |
| - | - |
| **Inbox** | Only run for reservations in this inbox. Required once you add a rule. |
| **Reservation changes** | Up to 20 rules. Each rule picks a field and a check. |

Each rule watches one of these fields:

| Field | Checks |
| - | - |
| **Status** | **Changed**, or **Changed to** a status |
| **Paid** | **Changed**, or **Changed to** **Paid** or **Unpaid** |
| **Check-in**, **Check-out** | **Changed** |
| **Property**, **Assigned sub-unit** | **Changed** |
| **Guest count**, **Children**, **Infants**, **Pets** | **Changed** |
| **Total price** | **Changed** |
| **Guest name**, **Guest email**, **Guest phone**, **Guest note** | **Changed** |

**Changed to** for **Status** offers: Confirmed, Modified, Cancelled, Declined, Unconfirmed, Pending, Awaiting Verification, Awaiting Payment, Expired, Inquiry, Inquiry Pre-approved, Booking Request, Owner Stay, Checked In, Checked Out and Unknown. Which statuses you see in practice depends on your PMS.

**Example task:** "This reservation was just cancelled. Find open tasks for the stay, cancel the cleaning ones, and post a summary to #housekeeping in Slack."

## Reservation label added

Runs when a label is added to a reservation.

| Filter | Options |
| - | - |
| **Label** | Only run when this label is added. |
| **Inbox** | Only run for reservations in this inbox. Required once you pick a label. |

Labels make a good hand-off point. When a teammate adds a "Late arrival" label, an internal agent can pick it up and rearrange that day's check-in tasks.

## Check-in and check-out

**Check-in** and **Check-out** run the agent once per reservation, a set time before or after that date. Conduit checks for due reservations every hour. Unlike other events, you can add these several times to one agent, each with its own timing.

| Setting | What it does |
| - | - |
| **Timing** | How long before or after check-in or check-out to run, such as "5 days before check-in". Pick a number, a unit, and **Before** or **After**. The default is 5 days before. |
| **Inbox** | Optional. Only run for reservations in this inbox. **Any inbox** when empty. |
| **Run for all reservations** | Also run for reservations booked after the trigger time already passed. For example, a reservation created 1 day before check-in still runs a "2 days before check-in" trigger. On by default. |

These triggers have no event to mock, so **Mock event** and **Run now** don't apply. To test, chat with the agent about a specific reservation instead.

**Example task:** "Check-in is 14 days away. If the reservation has no arrival time, send the guest one WhatsApp message asking for it. Don't message guests who already replied about their arrival."

## New appointment

Runs when an appointment is created.

| Filter | Options |
| - | - |
| **Inbox** | Only run for appointments in this inbox. Empty runs for every inbox. |

## Appointment modified

Runs when an appointment changes.

| Filter | Options |
| - | - |
| **Inbox** | Only run for appointments in this inbox. Required once you pick a status. |
| **New status** | Only run when the appointment changes to this status: Awaiting response, Confirmed, Cancelled, Completed, No show or Rescheduled. **Any status** runs on every change. |

**Example task:** "This appointment was marked as a no show. Send the contact one friendly message offering to rebook, and add a note to the conversation."


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.