It watches the whole
operation, not the calendar
This is the engine that runs the whole cycle of service. It listens to more than 30 things that happen in your business, from a form submitted to a task going overdue to a part dropping below its reorder point, and acts on the same data model. No connectors, no per-task fees, nothing to authenticate. You build it — not a developer, not a support ticket.
A form submitted. A task overdue. A part below par. An SLA about to breach.
Most automation tools listen to the booking, because the booking is the only thing their system holds. This one listens to the operation, in the language the operation actually happens in — and because reservations, tasks, forms, crews, parts and owners live in one system, every trigger already knows its context. No field mapping, no lookups, no middleware.
- Operational signals — a portal ticket crossing its SLA threshold, a part dropping to its reorder point, an issue reported, an owner approving or declining a task, or any signal the system records
- The work itself — a task created, assigned, completed, overdue or failed; a subtask added or ticked off
- Forms and the field — an inspection submitted, or a specific answer on it matching a condition you set
- Guests and stays — a checkout, a stay cancelled or re-dated, a guest message arriving
- Owners and pipeline — a lead created, a CRM stage changed, a field updated
- The clock — daily, hourly, or a set interval before something is due
One failed inspection, end to end
This is a single workflow, built in the visual canvas by the person who runs the crews. Nothing here is a support ticket, a developer task, or a connector plan.
- A housekeeper submits the inspection form and marks it failed
- A re-inspection task is created on the same property, high priority
- The property manager is notified — in the app and by SMS
- A condition checks whether a guest arrives tomorrow
- Only if one does, the crew gets a text; otherwise it waits for the morning list
- Every step above is a trigger, a condition and four actions — assembled, not coded
- WhenInspection form submitted — result: failed
- ThenCreate task — Re-inspection, high priority
- ThenNotify the property manager (app + SMS)
- Only ifA guest arrives tomorrow
- ThenText the crew
Describe the workflow. AI builds it.
Type what you want in plain English and the AI Architect drafts the complete workflow — trigger, conditions, actions — resolved against your actual properties, people, forms, and email templates. It validates every reference before you activate, so nothing points at a task type that doesn't exist.
- Generated workflows arrive as editable drafts — review, tweak, activate
- Semantic validation flags broken references before they ever run
- Every workflow tracks versions, run counts, and last success or failure
Half your automations are already running
Some things shouldn't need a workflow at all. When a reservation lands, the turnover clean schedules itself. Before check-in, the guest's smart lock code is created and the thermostat moves to comfort mode; after checkout, both reverse. A guest message about a problem is flagged as an issue by AI on its own. Native beats configured.
- Housekeeping auto-scheduled from every active reservation — real-time trigger plus an hourly safety net
- Smart lock codes and thermostat setpoints tied to check-in and checkout
- Guest messages about problems — the AC, the hot tub, a lockout — flagged as operations issues by AI
You can see what fired, what worked, and what didn't
An automation nobody can audit is one nobody leaves switched on. Every execution is written down: which trigger fired it, what the payload was, how long it took, and the result of each action in order — succeeded, failed or skipped, with the reason.
- Per-run detail: the trigger, the workflow version that ran, start and finish, and duration
- Per-action results — how many succeeded, how many failed, how many were skipped, and which
- Workflows are versioned, so a run tells you which version of the logic produced it
- A history that explains why a workflow did not fire, which is the question you actually ask at 7am
- Create task — Re-inspectionSucceeded
- Notify property managerSucceeded
- Text the crewSkipped
2 succeeded · 0 failed · 1 skipped — no guest arriving tomorrow
The whole automation stack, included
Replaces the $30/mo automation tool, the connector plan priced per task, and the hours spent re-authenticating broken zaps.
Native triggers
Reservations, task events, form submissions, CRM stage moves, and schedules — every event in the platform can start a workflow.
Branching logic
If / else-if / else conditions with and/or logic, plus delays in minutes, hours, or days between steps.
Live variables
Drop guest, property, owner, task, and reservation fields into any message — pulled from the record, never re-keyed.
Execution history
Every run logged with per-action status, duration, and results. When a workflow doesn’t fire, the history tells you why.
Outbound webhooks
Push events to any external URL with custom headers, method, and retries — the outside world can listen in.
Beyond messaging
Actions go past email and SMS: send owner service agreements for signature or drop a gift card to a guest, straight from a workflow.
Not another PMS. The vacation rental ecosystem.
One login. One bill. Unlimited users. Priced per property. No seat fees, no setup fee, no contract, and no booking fee on your direct site. 14-day free trial — no charge until it ends.