Build steps that run on their own, and see every run.
Say what starts it and what should happen next, test it on a real event, and answer any run that fails, at your desk or on your phone.
Every automatic act in your business, in one place
What starts it, what it does and what it did, for every Calisto app you use.
Build
Steps, branches, loops and waits.
Connectors
Your Calisto apps, and the outside.
Your Apps’ Rules
Every message an app sends on its own.
Sequences
Follow a person until they act.
Runs
Every run, step by step.
On a Phone
Switch on, answer, retry.
Build an automation step by step, or describe it
Pick what starts it, then add steps: an action, a branch that runs every route that matches, a loop over a list, a delay, a wait for something to happen. Or write a sentence, and the steps are laid out as a draft for you to review.
Describe It
Say what should happen; every step is laid out for you to check, and nothing switches on from a sentence.
What should this automation do?
Templates
Ready-made automations by category: open one, adjust it and switch it on.
Automation
Ready-made automations. Pick one, adjust it, switch it on.
Test on Real Events
The unsaved automation runs on one of its trigger’s last three events.
Versions
Every save is a version, and every run keeps the version it ran.
Dates and Schedules
Days before or after a date in your records, or on your own clock.
Only When
Filters checked before anything runs, and only the first time for each record.
If a Step Fails
A step can carry its own route for when it fails.
Values From Earlier Steps
Each step can use what started it and what earlier steps produced, or a value you name.
What should this automation do?
Start from one Calisto app, and act in another
Your Calisto apps are built-in connectors: what one announces can start an automation, and what only it can do is a step. A rule pinned to one record, a form or a document, runs for that record alone.
Built-In Connectors
Every Calisto app an automation can start from or act on.
| Connector | Role | Triggers | Actions |
|---|---|---|---|
| Stays | Starts and acts | 27 | 27 |
| Salon | Starts and acts | 22 | 22 |
| Fit | Starts and acts | 35 | 27 |
| Payments | Starts and acts | 33 | 20 |
| Dispatch | Starts and acts | 28 | 27 |
| Deals | Starts and acts | 14 | 14 |
| Ledger | Starts and acts | 13 | 19 |
| Forms | Starts and acts | 8 | 20 |
| Sign | Starts and acts | 14 | 17 |
| Reputation | Starts and acts | 17 | 17 |
| Inbox | Starts and acts | 6 | 16 |
| Desk | Starts and acts | 16 | 15 |
Change every message your apps send by themselves
A booking confirmation, a payment reminder, a notice to your team: each is a rule here, switched on where the app always sent it. The switch in the app and the rule are one thing. Paused, it stays paused.
Automation
Steps that run by themselves when something happens in your business.
| Automation | When | Then | Last 7 days | Last run | Status | |
|---|---|---|---|---|---|---|
| Email each guest who books a table online their confirmationOnline reservation confirmed | Online reservation confirmed | Email the guest their confirmation | 312 | 10/11/2026 12:41 | Active | Pause |
| Tell each guest who asks for a table online that their request arrivedTable requested | Table requested | Email the guest that the request arrived | 46 | 10/11/2026 11:58 | Active | Pause |
| Tell the floor an hour before each reservationBefore or after a reservation | Before or after a reservation | Tell the floor the party is coming | 298 | 10/11/2026 12:30 | Active | Pause |
| Tell the team about every new reservationNew reservation taken | New reservation taken | Tell the team about the reservation | 341 | 10/11/2026 12:44 | Active | Pause |
| Tell the team when a table is double-bookedTable double-booked | Table double-booked | Tell the team about the double booking | 3 | 08/11/2026 20:15 | Active | Pause |
| Tell the floor when a guest is running lateGuest running late | Guest running late | Tell the floor the guest is late | 27 | 09/11/2026 21:05 | Active | Pause |
| Offer a freed table to the waitlistA table’s time came free | A table’s time came free | Offer the table to the waitlist | 58 | 10/11/2026 12:12 | Active | Pause |
| Ask each client to reconfirm their table the day beforeBefore a reservation its client has not confirmed | Before a reservation its client has not confirmed | Ask the client to reconfirm | 199 | 10/11/2026 10:00 | Active | Pause |
Your Own Words
Change what a shipped message says, or add a step after it.
Follow up with a person until they act
A sequence sends its steps on its own clock and stops when the person replies, signs, accepts or pays, as you choose. Proposals, Sign, Deals, Campaigns and Ledger build theirs on the same screens, and every one runs here.
Automation
Every multi-touch cadence across the platform: steps, enrollments, and run status.
| Sequence | Starts | Steps | Steps Due | Enrolled | Reply Rate | Status |
|---|---|---|---|---|---|---|
| Before your safari | Booking confirmed | 4 | 11 | 38 | 42% | Active |
| After your stay: share your sightings | Checked out | 3 | 6 | 52 | 31% | Active |
| Group safari proposals | Proposal sent | 5 | 4 | 9 | 56% | Active |
| Lodge partnership agreements | Document signed | 3 | 2 | 5 | 40% | Active |
| Overdue deposits | Invoice overdue | 4 | 3 | 7 | 71% | Active |
| Travel agents: new season rates | Manual | 3 | 14 | 64 | 23% | Active |
| Returning guests: the migration | Deal won | 2 | 0 | 18 | 50% | Paused |
Enrollments
Automation
| Contact | Sequence | Current step | Status | Next action | Actions |
|---|---|---|---|---|---|
| Marcus Delgado | Home exercise check-ins | Step 2 of 4 | Active | Next: 11/11/2026 09:00 | PauseSkip StepStop |
| Priya Raman | Home exercise check-ins | Step 3 of 4 | Active | Next: 11/10/2026 16:30 | PauseSkip StepStop |
| Dana Whitfield | Come back for your next visit | Step 1 of 3 | Paused | Paused | ResumeSkip StepStop |
| Luis Ortega | Overdue invoice reminders | Step 2 of 3 | Active | Next: 11/12/2026 10:00 | PauseSkip StepStop |
| Hannah Brooks | Come back for your next visit | Step 2 of 3 | Active | Next: 11/13/2026 09:00 | PauseSkip StepStop |
| Tom Nakamura | New patient welcome | Step 1 of 2 | Active | Next: 11/10/2026 18:00 | PauseSkip StepStop |
| Grace Okafor | Home exercise check-ins | Step 4 of 4 | Active | Next: 11/15/2026 09:00 | PauseSkip StepStop |
Who is in each sequence and their next step, with pause, skip and stop.
Payment Reminders, With Ledger
Overdue invoice reminders On
An overdue invoice’s reminders with its pay link, ended when it is paid.
Marketing, With Campaigns
Aula experimental: as próximas semanas On
A marketing sequence keeps consent, the unsubscribe link and quiet hours.
Results by What It Chases
Sequences
Venue hire contracts
Venue hire contracts
| Sequence | Starts | Enrolled | Opened | Signed |
|---|---|---|---|---|
| Venue hire contracts | On send | 64 | 91% | 73% |
| Catering partner agreements | On send | 12 | 100% | 83% |
| Photographer releases | Before expiry | 21 | 86% | 62% |
| Exhibitor terms | On open | 33 | 94% | 70% |
| Yacht charter waivers | On send | 18 | 89% | 78% |
Opened, replied, signed, accepted or paid, on each sequence.
Draft the Whole Sequence
Sequence Builder
Draft a complete follow-up sequence for an audience, then edit and create it.
Pick who it is for, its channels and how long it runs, then edit every step before it is created.
Watch every run, and answer the ones that fail
Each run opens to every step, what it received and what it returned. Retry runs the failed step again, Skip carries on, and an answer is taken once. An automation that keeps failing is paused after errors and you are told.
Housekeeping task on checkout
Failed2026/11/10 10:140.7 sv3Kamogawa Ryokan · KyotoOpen AutomationRun againRetry failed stepSkip it & continueNeeds an Answer
The failed runs nobody has answered yet.
Automation
Every time an automation ran: what it received, what each step did.
| Automation | When | Result | Took | Version |
|---|---|---|---|---|
| Send the job report when a job is finished | 2026-11-10 15:42 | Failed | 1.2 s | v5 |
| Overdue task escalation | 2026-11-10 14:05 | Failed | 0.4 s | v2 |
| Tell me about an urgent ticket | 2026-11-10 11:31 | Timed out | 30 s | v1 |
| Thank the customer when their order arrives · 2 parts | 2026-11-10 09:18 | Failed | 0.9 s | v3 |
| Remind me before a follow-up is due | 2026-11-09 17:00 | Failed | 0.3 s | v4 |
| Give each new inquiry to me | 2026-11-09 12:47 | Failed | 0.6 s | v2 |
| Text the customer when the van is on its way | 2026-11-09 10:20 | Failed | 0.8 s | v6 |
| Tell me about a declined payment | 2026-11-09 08:56 | Failed | 0.5 s | v1 |
| Monday morning: the week ahead | 2026-11-08 08:00 | Timed out | 30 s | v2 |
| Ask for a review after a job is closed | 2026-11-08 16:35 | Failed | 0.7 s | v3 |
Retries and Business Hours
Automatic retries with a wait between them; a schedule held until you open.
Settings
Retries and Pausing
Switch an automation off when it keeps failingDaily Summary
Yesterday’s runs by email, on your own calendar day.
Settings
Notifications
Email when a run fails or an automation is switched offEmail a daily summary of yesterday's runs412 runs on 09/11/2026. Succeeded: 99.3% · Errors: 7 · Switched on: 18 · Paused after repeated failures: 0
| Automation | Runs | Errors |
|---|---|---|
| Email each guest who books a stay online their confirmation | 64 | 1 |
| Tell the front desk an hour before each guest arrives | 58 | 1 |
| Housekeeping task on checkout | 51 | 1 |
| Text the guest before arrival | 47 | 2 |
| Give a guest their door code when the stay is confirmed | 44 | 2 |
Amounts by Permission
A run’s money shows only to people your money settings allow.
Keep or refund the deposit when a stay is canceled
Succeeded10/11/2026 08:261.1 sv2Karen Hills Safari Lodge · NairobiOpen AutomationRun againAnalytics
Runs, successes, failures and the average run by day, with the automations that run most.
Analytics
How often your automations run, and how well
Runs by Day
Failures by Day
| Automation | When | Runs | Failed | Succeeded |
|---|---|---|---|---|
| Salon: thank the client after their visit | Appointment finished | 612 | 3 | 99,5% |
| Remind each client before their appointment | Before or after an appointment | 548 | 5 | 99,1% |
| Tell the team about every new appointment | New appointment taken | 497 | 1 | 99,8% |
| Offer a freed time to the waitlist | A time came free | 211 | 2 | 99,1% |
| Win back a client who went quiet | Client went quiet | 164 | 4 | 97,6% |
| Tell the team when a client is running late | Client running late | 92 | 1 | 98,9% |
Automation
Every time an automation ran: what it received, what each step did.
| Automation | When | Result | Took | Version |
|---|---|---|---|---|
| Send the job report when a job is finished | 2026-11-10 15:42 | Failed | 1.2 s | v5 |
| Overdue task escalation | 2026-11-10 14:05 | Failed | 0.4 s | v2 |
| Tell me about an urgent ticket | 2026-11-10 11:31 | Timed out | 30 s | v1 |
| Thank the customer when their order arrives · 2 parts | 2026-11-10 09:18 | Failed | 0.9 s | v3 |
| Remind me before a follow-up is due | 2026-11-09 17:00 | Failed | 0.3 s | v4 |
| Give each new inquiry to me | 2026-11-09 12:47 | Failed | 0.6 s | v2 |
| Text the customer when the van is on its way | 2026-11-09 10:20 | Failed | 0.8 s | v6 |
| Tell me about a declined payment | 2026-11-09 08:56 | Failed | 0.5 s | v1 |
| Monday morning: the week ahead | 2026-11-08 08:00 | Timed out | 30 s | v2 |
| Ask for a review after a job is closed | 2026-11-08 16:35 | Failed | 0.7 s | v3 |
Switch automations on and answer failures from a phone
Home, Automations and Connectors are the phone’s tabs. A template is switched on from its card, a failed run is retried or skipped where you are, and the flow reads on the phone while the desk builds it.
Where Automations touches everything else.
5 of these 8 connections are in your plan today; the others are their own apps.
Bookings
Every confirmation, reminder and team notice a booking sends is a rule here, and a booking’s start or end can start one of yours.
Inbox
A customer’s message can start a rule that replies, answers from your knowledge base, assigns or escalates.
Desk
Ticket and conversation routing, missed targets and the satisfaction survey are Desk’s rules, run here.
Campaigns
A marketing step sends through Campaigns, with consent, the unsubscribe link and quiet hours.
Deals
A new lead can be assigned, pooled or tagged by a rule, and a signed contract can move its deal.
Ledger
An overdue invoice’s payment reminders are a sequence, and the books change only through a rule you made.
Signal
An alert can start a chain that waits for someone to answer it, then escalates if nobody does.
Equipo
A step posts to a team channel, or opens a work order’s own Hub with its people.
No setup cost. Pay when you start using.
Rules, sequences and runs across every app.
Calisto Ops
Rules that start from your Calisto apps, a schedule or a date and act across them all, every app’s automatic messages as rules, sequences that follow up until a person acts, and every run on record.
Included with Calisto Ops.
Recommended for you
Works well together.
Calisto Bookings
Calisto Inbox
Calisto Desk
Calisto Campaigns
Calisto Engage
Lists and consent per channel, emails built from blocks, sends at each person’s best hour, sequences and announcements, and what each campaign earned, credited to the click.
Learn more →Calisto Deals
Calisto Commerce
The CRM: leads routed and claimed, a pipeline on your own stages, quotes as versions and the contracts they become, people and companies, the day’s follow-ups, the handoff after the sale, commissions and the forecast.
Learn more →Calisto Ledger
Calisto Ops
Double-entry books set up your way, every Calisto app’s money posted to them, invoices and who owes, supplier bills read and matched, receipts as expenses, the bank reconciled, money held for others, and the statements your accountant files from.
Learn more →Calisto Signal
Calisto Ops
Sensors, trackers, locks and cameras on one fleet, an alert inbox, incidents with their playbooks, and rules through Automations.
Learn more →Calisto Equipo
Included with your Account
Public and Private Hubs, group chats and direct messages, threads, voice and video, polls, approvals and the files each Hub keeps, with every member of the business in it.
Learn more →Recommended for
The industries that run Automations, and what each of them runs it for.
Hotels & ResortsAutomations
Confirmation, upsell, and release chains that fire themselves
Hotels & Resorts on Calisto →Serviced ApartmentsAutomations
Confirmation fires five things without a human reviewing
Serviced Apartments on Calisto →Short-Term RentalsAutomations
Turnover, code, and statement chains that run themselves
Short-Term Rentals on Calisto →Bar & LoungeAutomations
Win-back, event invites, and price changes on schedule
Bar & Lounge on Calisto →Coaching & TrainingAutomations
Check-ins and follow-ups that send while you coach
Coaching & Training on Calisto →Gym ManagementAutomations
Freezes, retries, and win-backs that run themselves
Gym Management on Calisto →Spa & WellnessAutomations
Consent expiry, recall, and aftercare that fire themselves
Spa & Wellness on Calisto →Medical AestheticsAutomations
Consent expiry, touch-up recall, and aftercare that fire themselves
Medical Aesthetics on Calisto →Salons & BarbersAutomations
Rebooking, reminders and win-backs that fire themselves
Salons & Barbers on Calisto →Live Music & FestivalsAutomations
Rain delay, headliner overrun, and release protocols
Live Music & Festivals on Calisto →Marathons & EnduranceAutomations
The finish line triggers four systems
Marathons & Endurance on Calisto →Artists & TalentAutomations
Unsigned contracts release holds automatically
Artists & Talent on Calisto →Sports Agents & AthletesAutomations
Follow-ups with clubs and sponsors that fire by rule
Sports Agents & Athletes on Calisto →Venue ManagementAutomations
A guest count change updates order, invoice, and roster
Venue Management on Calisto →Stadiums & ArenasAutomations
A capacity change updates the event sheet, invoice, and roster
Stadiums & Arenas on Calisto →Event & Production RentalsAutomations
A signature reaches the warehouse by itself
Event & Production Rentals on Calisto →Public GolfAutomations
Frost delays and course notices that reach every booking
Public Golf on Calisto →Recreation & Vehicle RentalAutomations
Engine hours, geofence breaches, and blocks that act
Recreation & Vehicle Rental on Calisto →Tours & ExperiencesAutomations
One confirmation moves six things at once
Tours & Experiences on Calisto →Attractions & ParksAutomations
Waiver reminders and out-of-service blocks that act themselves
Attractions & Parks on Calisto →Home & Field ServicesAutomations
On-my-way texts and overdue invoices that chase themselves
Home & Field Services on Calisto →Property & Home InspectionAutomations
Agreements, reminders and reports that send themselves
Property & Home Inspection on Calisto →Coworking SpacesAutomations
A failed card fires dunning, suspension, and door revocation
Coworking Spaces on Calisto →Content CreatorsAutomations
Fulfilment and welcome sequences that route themselves
Content Creators on Calisto →Graphic Designers & ArtistsAutomations
Revision limits, reminders, and delivery notices
Graphic Designers & Artists on Calisto →Online RetailersAutomations
Returns, restocks, and reorders that run themselves
Online Retailers on Calisto →In-Person RetailersAutomations
Thresholds that raise the order without a manager
In-Person Retailers on Calisto →Everything included in Calisto Automations.
- A trigger, then a chain of steps: action, branch, loop, wait, delay and transform
- A branch tries its routes in order and runs every route that matches; the fallback runs when none does
- A loop runs its steps for each item of a list, up to 500, and gathers what each pass returned
- A wait holds the run until something happens to the same record, up to 30 days, with its own path when time runs out
- A delay waits a set time, or until a set time before or after a date in the data
- Each action can carry its own path for when it fails
- Each step reads the trigger’s facts and what earlier steps returned
- Filters on the trigger are checked first: an event that fails them starts nothing and logs nothing
- Word lists (contains any, starts with any, is one of) and number comparisons in filters
- Only the first time for each record, where the trigger names one
- A rule pinned to one record (a form, a document, a proposal, a portal) runs for it alone, made on that record’s own screen
- Before it can be switched on, every problem is named in your language; a draft may have problems
- A chain that loops back on itself is refused at save
- Every save is a version; restore writes a new one
- Test runs the unsaved automation on one of its trigger’s last three events, or on data you paste; nothing is logged
- Describe It: write a sentence and the steps are laid out as a draft to review; nothing is switched on from a sentence
- Templates: ready-made automations to adjust and switch on; a template you hid stays hidden and one you edited keeps your edits
- Save an automation as a template; duplicate, pause, resume, delete and Run Now from its row or in bulk
- Drafts never run
- Anything a Calisto app announces, from a booking finished to an alert raised
- A schedule: every few minutes, hours, days or weeks, at a time and day, or a custom schedule
- Schedules run on your business’s own time zone, and every due run is kept even when it ran late
- Only during business hours: a run due outside them is held until you open
- A date in your records: days before or after a stay, an appointment, a renewal, an invoice or a contract date; a moved date moves the run
- A record made inside the window still gets its run, never before the rule was switched on
- Webhook received: each automation has its own address; its token is shown once and a new address stops the old one
- Your Calisto apps are built-in connectors: what each announces and what only it can do
- Each connector’s page lists its triggers and actions, and whether it starts automations, acts, or both
- Notify a person: a named person, the record’s assignee, your admins or your owners, by each person’s own notification settings, held until their next shift when they are off
- Send a service message: an email, an SMS or a WhatsApp a customer expects, from your business, sent once per run
- Approvals: a run waits for a decision on a request in the approval engine and branches on it
- Custom HTTP: a POST or PUT to your own endpoint with authentication and body; headers on a saved webhook
- Custom Webhooks: saved endpoints with a Test button; tokens kept encrypted and shown masked
- Two outside automation platforms take a step from a rule
- A product’s own button runs a catalog action without a rule (Sign’s reminders), logged like any run
- Third-party actions run only from a rule
- Every automatic message to a customer, every assistant that answers one and every notice to your team is a rule here
- An app’s own switch for one is the rule: switched off, it is paused and your edits are kept
- Shipped rules are written once, the first time they are needed, and switched on as the app always worked
- A setting your organization locks in Purview or Blueprint is read-only here too
- Inbox: route new conversations, the away message outside business hours, the 24/7 backup that answers from your knowledge base when the team is away, alerts, and the client portal’s notices
- Bookings and every app that takes bookings: confirmations, arrival and no-show notices, walk-in texts, the no-show fee and releasing an unconfirmed booking (both off until you turn them on)
- Desk, Dispatch, Voice, Reputation, Campaigns, Registry, University, Fit, Endurance, Payments, WiFi, Direct, Legal, Circle, Deals, Tickets, Live, Listings, Identity, Navigator, Forms, Sign, Proposals and Ledger, each with its own rules
- Access, Assure, Signal, Display, Kiosks, Station, Sites, Depot, Apps, Ethos, Orbit, Agenda, Workforce, Ads and Inventory notices
- Orderflow: tag, route and stage orders, set an order’s priority, ship a customer’s ready orders together and ask for a review after delivery
- Display: put a screen on the TVs for a while from what Access sees, and any alert on chosen TVs
- Equipo: post to a team channel, or open a work order’s or task’s own Hub with its people
- Stays: quote and confirm a guest’s airport transfer, with the driver’s task in Dispatch
- Direct: win back former members and offer an upgrade with a code for one fan
- Scheduled reports in Access, Ads, Impreta, Kiosks, Ledger, Reputation and Workforce are rules on their report
- The website and app chat’s assistant is one rule per site; its status is the chat’s own switch
- Sequences, Enrollments, Rules, Templates and Runs are one workspace, the same in Deals, Proposals, Sign, Campaigns, Bookings and Ledger
- A sequence sends its steps on its own clock and stops when the person acts
- A new sequence is off until it has a step
- Its results match what it chases: messages delivered, opened and replied; a proposal viewed and accepted; a document opened and signed; an invoice paid
- Payment reminders, with Ledger: an overdue invoice’s customer is followed up with its number, balance in its own currency, due date and pay link, ended when it is paid, voided or written off
- Marketing sequences send through Campaigns, with consent, the unsubscribe link, the weekly limit and quiet hours
- Draft a whole sequence from a description, review it and create it
- Enrollments: pause, resume, skip the next step or stop, with each person’s timeline
- Runs: one row per run, filtered by result
- A run opens to every step, what it received and what it returned, the routes it took and each item of a loop
- Retry runs the failed step again when the run kept where it stopped, otherwise from the start
- Skip and continue; Run Again on a run that did not fail
- A failed run is answered once, whoever answers first; the answered run links to the run its answer started
- Needs an Answer is the failed runs nobody has answered; Failed is every failure
- Automatic retries with a growing wait, per automation or your default
- Paused after errors: an automation that keeps failing is paused at your threshold; switching it on starts the count again
- A run waiting on a delay stops there when its automation is switched off
- Each event is taken once, so a run after a restart never sends twice
- Amounts in a run show only to people your money settings allow to see sales or costs
- Analytics: runs, success rate, failures, average run and automations switched on, by day, over a range you pick, with the automations that run most
- The Status Board: recent runs, automations on, runs and failures today, sequences running
- Settings: retries, failure emails, the daily summary’s recipient, and how long run history is kept
- The daily summary covers yesterday on your own calendar day
- Calisto’s search finds automations and sequences by name
- Tabs: Home, Automations and Connectors, then Analytics and Settings
- The flow reads on the phone; it is built on the desk
- Switch an automation on, a draft included
- Turn a template into a live automation or a draft from its card
- Answer a failed run: Retry, Skip or Turn Off
- Connectors, Custom Webhooks with create, edit and Test, and Analytics, each made for the phone
- Push buttons: Retry and Turn Off on a failed run, Turn On on one paused after errors, done in the background
- Shortcuts: Needs an Answer, New Automation, Automations, Sequences and Runs
- Words shared to Automations land in Describe It
- Home, the workspace, every run and New Automation open with no signal, from what you choose to keep on the device
- A template switched on with no signal is kept and sent when you are back online
- Widgets: Needs an Answer and Runs Today, with no amounts
- A double tap or a lost connection never makes a second automation, webhook, sequence or enrollment
- Rules and runs cover the whole business, every place included
- An automation inside one app switches on under that app; one that spans apps, or uses an outside connector or Custom HTTP, needs Automations
- Calisto Agency owners write their own rules for their homes from their Agency home
Questions about Calisto Automations
Anything a Calisto app announces: a booking confirmed or finished, a message from a customer, a new lead, an order delivered, a payment declined, an alert. Also a schedule on your own clock, a date in your records (two days before a stay, a month after a visit) and a webhook from another tool.
Yes. Test runs the automation as it stands, saved or not, on one of the last three real events of its trigger or on data you paste. Its actions run for that one event and nothing is logged.
Through three doors. Custom HTTP sends a request to your own endpoint. An automation that starts on Webhook received has its own address that any tool can post to. And a step can hand work to one of two outside automation platforms. There is no public API.
The run stops at that step and keeps where it stopped. It waits under Needs an Answer: Retry runs the failed step again, Skip carries on, and only one answer is ever taken. Automatic retries and pausing a rule that keeps failing are settings.
No. Every automatic message an app sends to a customer, every assistant that answers one and every notice to your team is a rule you can open, change or pause. A switch in the app and the rule are the same thing.
The price box on this page reads the live catalog. Automations is sold per user on its own, and it is included with any Calisto Ops plan. An automation that stays inside one app switches on under that app; one that spans apps, or uses an outside connector or Custom HTTP, needs Automations.