Make the routine parts of your business happen without anyone doing them.
An automation engine that works with all of your operational data inside Calisto Pro. Pick what starts it, then drag the steps that follow onto the canvas. Test it against real sample data before you turn it on.
The Automation App for Workflows
Triggers, actions, branches, delays, and native connectors across every app. Test it against real data before you turn it on.
Flow Builder
A trigger, then actions, branches, and delays.
Connectors
Seventeen native connectors across Calisto Pro.
Templates
Start from a working flow instead of a blank canvas.
Reliability
Schedules, retries, and a circuit breaker.
Activity
Every run, every step, and what it returned.
Sequences
Multi-step message sequences on their own clock.
Start with a trigger. Add a step on any connection.
An empty canvas asks for one thing: the event that starts the flow. Pick it and the graph scaffolds itself.
Every connection carries a plus
Add the next step exactly where it belongs.
Right-click any node
Configure, duplicate or delete it. Undo walks back every change.
Branch, wait, carry the data
A condition splits Yes from No. A delay parks the run for minutes, hours or days, then resumes it. Values from earlier steps resolve at run time.
Test before it goes live
Run it against sample data first. A test never touches the execution log or the counters.
Seventeen native connectors. No middleware to maintain.
A native connector already understands the record it is handed, so a step reads the booking rather than a copy of it. Nine apps both start a flow and take an action, five only start one, three only act.
Past those, Zapier and Make reach whatever they already reach, and a custom HTTP connector or an outbound webhook to any URL covers the rest.
Eighteen ways to start. Or a blank canvas.
Fifteen single-action recipes and three full multi-step chains, organized under Guest Experience, Operations, Revenue, and Alerts.
The builder reconstructs the whole chain
Open a template and the delays and branches come back with it. Edit freely from there.
The template underneath stays put
The one you customised for a single property has not quietly become the company default.
Building the automation is the easy part. The hard part is keeping it running reliably when you’re not watching.
What happens when a rule keeps failing.
Automation is easy to demonstrate and hard to leave running. These six settings are how a chain survives a deploy, a connector that rejects every call, and a schedule that has to fire on time.
Schedules, not just events
Start a rule on a fixed interval or a cron expression. A tick that lands late still runs the occurrence it owed you.
Only during business hours
A scheduled run that comes due outside your business hours is held until they open, not thrown away.
Retries and backoff
Set how many retries and how long between them. A retry re-runs the payload the original was given.
Circuit breaker
Choose how many consecutive failures are too many. Past that the rule flags itself errored and stops burning attempts.
Told, not discovered
Email the owner when a rule errors, send a daily execution digest, or both.
Log retention
Decide how many days of history to keep, and whether full trigger payloads are stored with each run.
Every run. Every step. Every failure.
A rule you cannot see running is a rule you cannot trust. The status board carries active rules, today's executions, success rate, errored rules, and fourteen days of volume.
Execution Log
Every run in order, with its rule, when it fired, the condition outcome, duration and retries. Filter to success, failed, skipped, waiting or timeout.
Execution Detail
One row for every step the chain actually walked, with the branch it took and the error if there was one. Retry replays the original payload, not whatever the data looks like today.
Errors
Failed and timed-out runs in one queue. Open a row for the full trace and retry from there.
Analytics
Executions, success rate, average duration and active rules over thirty days, with a most-fired-rules table that drills into the rule.
Multi-touch cadences, shared across the platform.
A rule fires once on an event. A sequence works a contact over days.
One list, whoever built it
Every cadence built anywhere on the platform lands in the same list, against the same records.
A step is an action and a wait
Each step sends an email, places a call, or creates a task, after a delay you set in days.
Reorder without losing anyone
Contacts already partway through keep a sensible current step rather than starting again.
Enrollment you can read
One row per contact: where they are, what state they are in, and when the next touch lands.
Where Automations touches everything else.
3 of these 6 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.
Bookings
A reservation that is made, moved or cancelled is a trigger, and the run reads the reservation itself rather than a copy.
Signal
A device reading out of range starts a chain in the same run history as everything else.
Orderflow
An order reaching a state can start a chain, and a step can move it on.
A step that sends mail sends it as your account, through the same sending domain your people use.
Deals
A chain can create or advance a record on the pipeline instead of asking somebody to remember to.
Purview
The selected purview scopes what a chain can see and what it is allowed to write.
No setup cost. Pay when you start using.
Workflow automation for every app you run.
Included with Calisto Commerce or Calisto Ops.
Recommended for you
Works well together.
Calisto Bookings
Included with Commerce or Ops
Reservations, inventory, contacts, tickets, and scheduling
Learn more →Calisto Signal
Calisto Orderflow
Calisto Mail
Calisto Deals
Calisto Purview
Included with every Calisto account
Account configuration and data rules.
Learn more →Everything included in Calisto Automations.
- Visual canvas with drag-and-drop step placement
- Multi-step chains (not just trigger-action pairs)
- Yes/No branching with eleven condition operators (equals, not equals, greater than, less than, greater or equal, less or equal, contains, starts with, ends with, exists, does not exist)
- Delays that survive (minutes, hours, or days, parked and resumed automatically)
- Data mapping between steps with insertable tokens, resolved to real values at run time
- Test runs against sample data before activation
- Test-run result per step: the trigger payload that fired, the action status and duration, the raw output, and the error in full
- Test runs stay out of the execution log and off the counters
- Drafts that never execute until activated
- Undo for every structural change
- Duplicate, configure, or delete any node
- Rules list with name search, status filters (active, paused, draft, errored), and per-row edit, pause, resume, and delete
- Rule detail with total fires, errors, consecutive errors, and full execution history
- Bookings (triggers + actions)
- Orderflow (triggers + actions)
- Dispatch (triggers + actions)
- Registry (triggers + actions)
- Listings (triggers + actions)
- Inventory (triggers + actions)
- Docs (triggers + actions)
- Sheets (triggers + actions)
- Slides (triggers + actions)
- Signal (triggers)
- Voice (triggers)
- Payments (triggers)
- Tickets (triggers)
- Schedule (triggers)
- Campaigns (actions)
- Concierge Escalation (actions)
- Forms (actions)
- Zapier integration
- Make integration
- Custom HTTP connector (POST/PUT, bearer/basic auth, custom headers, body template)
- Custom outbound webhooks to any URL
- 18 pre-built templates (15 single-action, 3 multi-step chains)
- Categories: Guest Experience, Operations, Revenue, Alerts
- New Automation landing with the template gallery and a build-from-scratch option
- Full chain reconstruction in the builder (delays, branches intact)
- Edit freely without modifying the template
- Searchable by name
- Multi-touch cadences shared across the platform
- Step types: email, call, task
- Per-step delays in days (first step defaults to no wait, later steps to two days)
- Branch labeling for follow-up paths, persisted across reloads
- Status filters (active, paused, completed, failed) with live counts
- Steps, enrollment, reply rate, meeting rate, and bounce rate on every row
- Performance funnel (delivered → opened → replied → meeting booked)
- Per-contact enrollment tracker with status and next touch, searchable by contact or status
- Reorder steps without losing enrolled contacts
- Event-triggered rules (fire on an event)
- Fixed-interval scheduled rules
- Custom cron expressions
- Due means the expression matched any minute since the rule last ran, so a late tick never skips an occurrence
- Business-hours restriction (runs held, not discarded)
- Business hours are the account business hours, edited once and read by every app that uses them
- Configurable retry count and backoff interval
- A retry is a real re-run against the original trigger payload, carrying its own retry count into the log
- Circuit breaker with consecutive failure threshold
- A tripped rule flips to errored, appears under the errored filter and on the status board, and stops burning attempts
- Auto-pause on error (optional; leave it off and a success resets the consecutive-failure counter)
- Error email notifications
- Daily execution digest
- Notification recipient required and validated at save, not silently ignored
- Configurable log retention (days and payload storage)
- Status board with active rules, executions today, success rate, and error count
- Fourteen-day execution volume chart, top-firing rules, and recent runs on the board
- Full execution log with status filters (success, failed, skipped, waiting, timeout)
- Waiting is a chain parked at a delay, still alive and due to resume
- Per-run step-by-step trace with the step, its type, its status, the branch it took, duration, and the error
- Retry Now replays the trigger payload the run was originally given, not the current data
- Error queue with retry-from-trace capability, and a clean board rather than an empty table at zero failures
- Thirty-day analytics with executions and errors by day
- Most-fired-rules ranking
Questions about Calisto Automations
Any event the platform already emits, which is most of what happens in a working day: a booking confirmed, an order paid, a finding raised, a shift missed. You are not wiring webhooks between products that do not know each other.
Yes, and you should. An automation runs against sample data first, so you see the branch it takes and the values it maps before anything touches a live record.
Seventeen native connectors ship with it, and anything beyond those goes out over a signed webhook. The native ones matter more than the count suggests, because they already understand the records rather than passing JSON around.
The run stops at the failed step and keeps its state, so you can see which record it was on and what it had already done rather than guessing whether the automation half-ran.
It is part of Core. The pricing section on this page reads the live catalogue and is the authority on anything chargeable.
Yes. The definitions export with the rest of the account, so the logic you built is not trapped in the builder.