Automations
Triggers
Every trigger that runs today — schedules, chat, email, Inbox, calendar, tasks, bookings, websites and webhooks — and what the beta, alpha and planned badges mean.
On this page
A trigger is the event that starts an automation. This page lists the triggers that run today. The step palette also shows triggers marked beta, alpha or planned; only live ones are dependable.
What the badges mean#
| Badge | Meaning |
|---|---|
| live | Runs today and is covered by tests |
| beta | Fires, but its details may still change |
| alpha | Early; it may not fire reliably. Do not build anything important on it |
| planned | Shown so you can see what is coming; it does not run |
An Admin can hide alpha and planned tools from the palette in Settings.
Live triggers#
Time#
| Trigger | Starts when |
|---|---|
| Schedule matched | A time of day is reached, optionally only on certain days or on one exact date, in the time zone you set |
| Profile updated | A member updates their profile |
Chat#
| Trigger | Starts when |
|---|---|
| New message / New group message / New direct message | A message is posted |
| Someone was mentioned · Someone replied to a message | A mention or a reply |
| New attachment message · New poll message | A message carries a file or a poll |
| Direct message created · Group updated | A conversation is started or changed |
| Conversation resolved · Conversation state updated | A conversation is resolved or its state changes |
| Message opened · Message expired | A message is read, or a disappearing message expires |
| Message delete pending · Message delete undone · Message deleted | The stages of deleting a message |
Email and Inbox#
| Trigger | Starts when |
|---|---|
| New email | An email arrives in a connected mailbox |
| Inbox updated | Something in the Inbox changes |
| Attention item picked up or parked · Attention item settled · Attention action run | An item in Triage is worked, closed or acted on |
Calendar and tasks#
| Trigger | Starts when |
|---|---|
| Event created · Event updated · Event deleted | A calendar event changes |
| Task created · Task updated · Task completed · Subtask updated | A task changes |
Bookings#
Booking made, Booking approved, Booking rescheduled, Booking cancelled, Customer checked in, Booking completed and Customer did not show. They carry the booking’s reference, type, status and times, never the customer’s name. See Bookings.
Websites#
| Trigger | Starts when |
|---|---|
| Property went down · Property came back up | A monitored site goes down or recovers — once per outage |
| Monitor reports down / up / slow / a status (every check) | Every five-minute check that reports that state — use these only when you want repeated alerts |
| Property connected · Page changed · Page published · Form appeared · Site issue appeared · Element deployed | Changes Web Elements detects on a connected site |
From outside Unobits#
Webhook received starts the automation when another system calls its webhook address. See Webhooks in and out.
Beta triggers#
Finance: Payment received, Payment failed, Payment refunded, Expense submitted, Expense approved, Expense rejected and Expense reimbursed.
Not yet dependable#
Triggers for projects, invoices, inventory stock, CRM records, socials, calls, forms and connections are alpha or planned. Some pages elsewhere in Unobits suggest automations built on them — for example low-stock alerts in Inventory — but they should not be relied on until they are marked live.