In-app automations: trigger, condition, action
What you did by hand every day becomes a rule that runs itself. You choose what starts it, which conditions must hold and what happens next — with no code and no colleague who has to remember to send the message.
What an automation is made of
Triggers from the app's own life
New account, form submitted, booking confirmed, subscription about to lapse, entering a geographic zone — or simply a fixed hour.
Conditions that filter
Run the rule only for a given segment, only on working days, or only when a value crosses a threshold you set.
Concrete actions
Send a notification, update a record, move an item to another state, assign a task to a colleague, or call an external webhook.
Delays and chained steps
Wait two hours, a day or a week between steps and build entire onboarding or win-back sequences.
A full run log
See every execution, the data it started from and why a step stopped — debugging without guesswork.
Test before you switch it on
Run the rule against a test record, check each step's result, then enable it for everyone.
You assemble the rule from three blocks: what triggers it, which conditions must hold, which actions run. Rules execute on the platform's servers, so they work even when the app is closed. Pause, duplicate or edit them at any time, with no new store release.
Frequently asked questions about automations
Let rules do the repetitive work
Pick a plan and automate the one thing you repeat daily — the rest follows naturally.