> ## 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.

# Automations

> Create tasks automatically from reservations, stays, vacancies or a repeating schedule, and control what happens to existing tasks when you change an automation.

An automation creates tasks for you. It holds **when** a task is created and for which properties. What the task contains comes from a [template](https://docs.conduit.ai/operations/templates.md) or from a custom task you define in the automation.

![The Automations list with type, category, schedule, priority, assignee, properties and status columns](https://mintcdn.com/conduit-58d85182/wEiM_ZX0dp8c2DPe/images/operations-automations-list.png?fit=max\&auto=format\&n=wEiM_ZX0dp8c2DPe\&q=85\&s=1f2cfcba721ac857b7bce9e29381c267)

## Create an automation

1. Go to **Operations > Automations** and click **New automation**
2. Enter an **Automation name**
3. Under **Create tasks**, choose what each task contains (see [Task source](#task-source))
4. Under **Applies to**, pick the templates and properties
5. Under **When**, choose a **Trigger** and set its timing (see [Triggers](#triggers))
6. For **New reservation** and **During a stay**, optionally add **Only if** conditions
7. Click **Create automation**

### Task source

* **Template**: pick one or more templates under **Applies to**. Each template makes its own task, and the task gets the template's category, checklist and defaults
* **Custom task**: define the task in the automation itself: title, description, checklist, **Status**, **Priority**, **Assignee**, **Category**, due time, charge rate, estimated time and custom fields. A category is required

### Applies to

Pick the properties the automation runs for. Leave it empty to run for every property. When you use templates, you can only pick properties those templates apply to, and each template only makes tasks at its own properties.

## Triggers

| Trigger | Creates a task | Example |
| - | - | - |
| **New reservation** | At a set time before or after a check-in or check-out | Departure clean 1 hour after check-out |
| **During a stay** | On full days of a stay, once or every few days | Mid-stay clean every 4 days |
| **During a vacancy** | On full vacant days between stays, once or every few days | Flush the toilets every 7 days while vacant |
| **Repeating** | On a fixed calendar schedule | Pool service every Friday at 9:00 AM |

### New reservation

**Scheduled for** sets the time: an amount in **minutes**, **hours** or **days**, **before** or **after** one or more reservation events:

* **Check-in (no turn)** and **Check-in (turn)**
* **Check-out (no turn)** and **Check-out (turn)**

A **turn** is a same-day turnover: another booked stay checks out the day this one checks in, or checks in the day this one checks out. Pick both versions of an event to cover every reservation, or one to target only turns or only non-turns. For example, a "Back-to-back clean" automation can use only **Check-out (turn)**.

Conduit uses the reservation's check-in or check-out time from your PMS. If the reservation has no time, it uses the property's check-in and check-out times, and if those are missing too, 4:00 PM for check-in and 11:00 AM for check-out.

### During a stay

* **Create the first task** a number of days after **Check-in**. Check-in and check-out days don't count
* Turn on **Repeat during the stay** and set **Repeat every** to keep creating tasks every few days until the guest checks out

### During a vacancy

A vacancy is a stretch at a property with no check-in, check-out or occupied night. Full vacant days start the day after check-out and end before the next check-in, in the property's timezone. A booking in any unit of a property ends that property's vacancy.

* **Create the first task** a number of days after **Check-out**
* Turn on **Repeat while vacant** and set **Repeat every** to keep creating tasks every few days until the next check-in

Upcoming vacancy tasks adjust when reservations change.

### Repeating

![Editing a repeating automation that uses two templates and runs daily at 9:00 AM](https://mintcdn.com/conduit-58d85182/wEiM_ZX0dp8c2DPe/images/operations-edit-automation.png?fit=max\&auto=format\&n=wEiM_ZX0dp8c2DPe\&q=85\&s=451d9d730db92207dd2d9c10c9bd7794)

* **Repeat**: **Daily**, **Weekdays**, **Weekly**, **Monthly**, **Yearly** or **Custom**. Custom lets you set the **Frequency** and **Every** (for example, every 2 weeks)
* **Starts**: the first date
* **Days of the week**: for weekly schedules
* **On the**: for monthly schedules, either the same day number (such as the 15th day) or the same weekday (such as the third Tuesday)
* **Time**: in the workspace timezone
* **End repeat**: **Never** or **On date**

Repeating automations make one task per property for each date. If neither the automation nor its templates name any properties, they make one task with no property.

**Reschedule or skip if property is occupied** moves a repeating task off days when guests are in the property:

* **Reschedule to the** **next** or **previous** **fully vacant day** (the task needs a full day), **checkout** (it needs half a day), or **checkout or checkout (turn)** (it's quick)
* **Skip if nothing is available within** a number of days, weeks or months. If no matching day fits that window, that date's task is skipped. The window can't be longer than the time between repeats, so tasks don't overlap

### Only if conditions

**New reservation** and **During a stay** automations can run only for reservations that match conditions on: **Number of Nights**, **Days Vacant Before Check-in**, **Number of Guests**, **Number of Children**, **Number of Infants**, **Number of Pets**, **Booking Channel**, **Source**, **Person Type**, **Reservation Status**, **Total Price** or a reservation custom field.

For example, a "Deep clean after long stays" automation can run only when **Number of Nights** is greater than 7.

### Existing reservations

When you create a **New reservation** or **During a stay** automation, **Create tasks for existing current and future reservations matching the automation** is checked. For **During a vacancy**, the option is **Create tasks for existing vacancies matching the automation**. Uncheck it to only create tasks for reservations that come in from now on.

## How scheduling works

* **Tasks follow reservations.** When a reservation's dates change, Conduit moves its open tasks to match and keeps the same time of day. When a reservation is cancelled, Conduit closes its open tasks
* **People win over automations.** If someone set a task's date by hand, Conduit doesn't move it. It notes the reservation change in the task's activity instead
* **Repeating tasks are made 60 days in advance.** When you create a repeating automation, Conduit previews how many tasks it creates over the next 60 days
* **Stay and vacancy tasks** are due at the due time you set, or 9:00 AM by default
* **Blocked dates without a guest**, such as maintenance blocks, don't get tasks of their own. They still count as occupied for vacancies, turns and occupied-day rescheduling

## Edit, disable or delete an automation

Click an automation to edit it. You can't change its **Trigger** after you create it. When you save changes, choose:

* **Keep existing tasks**: only new tasks use the changes
* **Update upcoming tasks**: applies the saved details and schedule, creates missing tasks, and removes tasks that no longer match

When you disable or delete an automation, Conduit shows how many upcoming tasks it made and asks whether to **Keep upcoming tasks** or **Delete upcoming tasks**.

* Started, completed, past and manually rescheduled tasks stay unchanged in every case
* Re-enabling a repeating automation recreates tasks you deleted when you disabled it. Re-enabling other automations doesn't


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