Most teams have a few jobs they do by hand every time. An Action is marked done, so someone tells the lead. A date comes round, so someone changes a field. A job needs a sign-off, so someone sends a message and waits. The jobs are small, but they are easy to forget, and nobody can see afterwards whether they happened.
Saphion now has Automations. An Automation is a rule that starts when something happens in your work and then does the steps you chose. Every run is recorded, so you can always see what it did, and you can test a rule on a real record before you switch it on.
What an Automation does
A rule has two parts. The first says what starts it. The second is a list of steps, run in order.
It can start when a record is made or changed, when a field changes to a value you name, or when an item starts matching conditions you set. It can start when someone is assigned, when a date arrives, or on a schedule such as every working day. It can start when a person presses a button on an item. A connected account can start one too: something happens in a mail folder or a drive, and the rule runs.
The steps cover the usual work. Set a field. Create an Action, or find or create one. Send a notification, post an update, or assign people. Tell the person who holds a Role, such as a Project’s lead. Wait for a length of time, a date, or for something to happen. Carry on only if a condition matches. Repeat the steps for each item an earlier step found. Ask Beacon to do something in words, within the tools you allow. A later step can use what an earlier step found or made.
Test it before it runs
A new Automation is saved switched off. Open its Test tab, choose a record to test on, and choose Test. Saphion shows what the Automation would do to that record, step by step, under the words “Test only: nothing was changed”. Nothing is sent and nothing is changed.
When you are happy with the plan, turn the rule on. If you would like to see it work once first, a switched-off rule can Run it for real: you read the steps and anything it would send, then it runs once on the record you tested and stays switched off.
If a step sends something through a connected account, turning the rule on first lists each send: the account it goes from, who receives it and what it says. You allow exactly that list. If you later change what it sends, the rule pauses until you turn it on again, so a new message is never sent under an old yes.
See every run
Run history lists every run, newest first, as one line: the Automation, what it did, who it ran as and when. A red count on the tab shows the runs that need attention, so a failed run does not hide.
Open a run to see each step and what it did to which item, each condition it decided, and each wait it went through. A run that left work undone can be run again, and what it already did is not done twice.
Ask someone to approve
Add the step Ask for approval and the Automation stops there and waits. You choose who it asks: a named person, the people in a field such as an Action’s Assignee, or whoever holds a Role on the item’s Project.
The request appears under Waiting on you. The person chooses Approve, and the Automation carries on down the branch for approval. Or they choose Return with a reason, and it carries on down the branch for a return. The reason is kept with the run, and a later step can use it, for example to post it as an update. Only someone who was asked can answer.
This replaces approval chains, which came out in v0.11.1. An Action now has five plain statuses, and an approval is a step in a rule you can see and change.
Where to start
Open Automations in the sidebar and choose New Automation. Choose Blank to build your own, or Start from a starter to begin from a ready-made rule. You choose what it should use and give it a name, and you get your own Automation to change. Changing the starter later never changes one you made from it.
Update when a field matches
Wait, then update
When an Action is marked done, ask its Project lead to approve
There are other places to begin. Automate in a Board’s More actions menu shows the rules for that Board. A Project’s settings list its rules. Automate this account in a connected account’s menu starts a rule that listens to that account. A Button field puts a button on every item of a Board that runs one Automation on that item.
Ask Beacon to make one
You do not have to build the rule yourself. Ask Beacon in plain words: “When an Action is marked done, ask the Project lead to approve it.” Beacon can make, change, test and run Automations as you could, and it can read the run history to tell you why a run stopped. A new Automation is saved switched off. Where a rule sends something automatically, Beacon asks you first with a card saying what it will send, and Beacon never turns that on without you.
Who can use it, and what it can reach
An Admin manages Automations for the whole Organisation. On a Project, its Editors and Managers manage that Project’s Automations. Anyone who can open an item and use a Button field can press it, without permission to manage Automations.
An Automation only does what the person who turned it on could do. Its steps are checked again at every run, so a step never reaches further than that person’s access. If they lose that access, the rule pauses and says why. Nobody is put in their place.
Each Organisation has a monthly allowance of Automation actions. Each step that changes something counts once. Looking things up, checks and retrying do not count.
Availability
Automations came with Saphion v0.11.4. Read the Automations guide in the docs.


