Πίσω

AI Workflows

Build no-code multi-step automations that act on your data

intermediate6 minΕνημερώθηκε στις 2026-06-22

Overview

AI Workflows let you chain AI actions and connected integrations into reusable, no-code automations. Use them for tasks too complex for Autopilot but too frequent to do by hand — for example, confirming checkout time, scheduling the cleaning, and creating a restock task from a single trigger. You decide which steps run automatically and which need approval.

AI Workflows let you chain AI actions and connected integrations into reusable automations — without code. Use them for things that are too complex for Autopilot but happen too often to do by hand.

Examples:

  • "When a 5-star review comes in, post it to our team Slack and tag the cleaner who turned the unit."
  • "When a maintenance task gets a 'plumbing' label, send the contractor a Gmail message."
  • "On every checkout, generate a summary of the stay and email the property owner."

Anatomy of a workflow

A workflow has three pieces:

  1. Trigger — the event that starts it (new review, new task, message arriving, schedule, etc.)
  2. Steps — what to do next: ask the AI to extract something, send a message, or call a connected integration. A step can also stop the workflow early when a condition is met (for example, stop if the message turns out to be spam, or if required data isn't available).
  3. Approval gate (optional) — pause a step and wait for a teammate to approve before continuing

Each step's output is available to the next step, so you can chain reasoning across calls.

Triggers

Workflows can start from a wide range of events — there are dozens of trigger types covering reservations, guest messages, tasks, cleanings, reviews, payments, calendar events, voice calls, and more, plus a schedule trigger for time-based runs. Pick the one that matches the event you want to react to.

Building a workflow

Open AI Workflows from the side menu. Click + New Workflow, pick a trigger, then add steps. You can:

  • Preview a workflow against your data before turning it on (dry run) — read-only steps run for real, and steps that would change data show you what they'd do instead of doing it
  • Test-run the whole workflow end to end in an isolated execution
  • Backfill an existing workflow against past reservations

Connected integrations

Steps can act on outside services through connected integrations rather than arbitrary API calls. Anything you've connected — Slack, Gmail, and other supported toolkits — becomes available as a step. Connect the integration first, then reference its actions when building a step.

Approvals and notifications

If a step requires a human in the loop, the workflow pauses at that step and the assigned teammate gets a push notification (workflow_approval). When they approve, the workflow resumes from that step; if they reject it, the remaining steps are skipped. You can also enable or disable an entire workflow at any time with a single toggle — a disabled workflow stops matching its trigger.

What's next?

Χρειάζεστε βοήθεια;

Η ομάδα μας είναι εδώ για να απαντήσει στις ερωτήσεις σας και να σας βοηθήσει να πετύχετε.