Safe by default, from the first draft.
Every new rule starts as a draft in sandbox with an approval gate on, and only Testing or Active rules run.
Anslation One · Automation
Automation in Anslation One is a rules engine for repeatable checks and reminders. A rule runs on a schedule or when someone presses Run now, and can notify a person, write an audit entry or flag the run for review.
Every new rule starts as a draft in sandbox with an approval gate on, and only Testing or Active rules run.
An editor asks to activate a rule, and the company’s approvers decide before it can run.
Each run shows what started it, whether its conditions matched, what its actions did and why it stopped.
A guided editor in four parts, When, If, Then and Safety, reads each rule back as one plain sentence.
A dry run with sample data shows what the rule would do, and it sends nothing.
Inside a Workboard space, a rule can act each time a task is created or moves to a status.
What each feature of Automation lets you do, and where it lives in the workspace.
| Feature | What you can do | Where it lives |
|---|---|---|
| Guided rule editor | Build a rule in four parts, When, If, Then and Safety, and read it back as a plain sentence. | Rules |
| Schedule or run now | Run a rule on a schedule, from every 5 minutes up to every 30 days, or only when someone presses Run now. | Rules |
| Conditions on run data | Let a rule go ahead only when its conditions match the run’s data, using equals, contains, at least or at most. | Rules |
| Notify, record or flag | Send an in-app notification to a person, write an entry to the audit trail, or flag the run for a person to review. | Rules |
| Ready templates | Start from a template such as a daily reminder, a weekly planning nudge, a monthly access review or flagging large amounts. Each opens as a draft that saves nothing until you save it. | Templates |
| Sandbox and dry run | Test a rule in sandbox or do a dry run that sends nothing, and keep the approval gate on until an approver switches the rule on. | Rules |
| Ask to activate | An editor without approval rights asks to activate a rule, the request goes to the company’s approvers, and approving it moves the rule to Testing. | Rules |
| Run history | See every run with what started it, whether its conditions matched, what its actions did and why it stopped, then run a failed one again. The engine writes each run, so nobody can create or edit one by hand. | Runs |
| Success rate and failures | Follow active rules, rules in sandbox, runs per day, the 14-day success rate and failed runs, with the engine’s rules in plain words. | Automation dashboard |
| Workboard space rules | In a Workboard space, act when a task is created or moves to a status by notifying or assigning people, setting a priority, adding a label or setting a due date. | Workboard |
How it works
A ready template becomes a live rule only after an approver says yes, and every run leaves a record.
Open the Monthly access review template, which arrives as a draft in sandbox with the approval gate on.
The editor asks to activate it, and the request goes to the company’s approvers.
An approver approves the request, and the rule moves to Testing.
The approver sets the rule to Active, and every 30 days it notifies its owner and writes a dated audit entry.
A failed run shows on the Command Center under Where work is stuck, and an approver can run it again from the run history.
Each person sees the tools their role opens, scoped to the company, a department, a team or their own work.
Still have a question? Contact us
Automation is the rules engine of Anslation One. A rule runs on a schedule or when someone presses Run now, checks its conditions against the run’s data, and then notifies a person in the app, writes an audit-trail entry or flags the run for review.
Inside Workboard, yes: a space rule can act when a task is created or moves to a status. Automation rules themselves run only on a schedule or when someone presses Run now, because triggers on record changes or webhooks are not fired today.
No. A rule notifies people inside Anslation One, writes an audit entry or flags a run for review, and it does not email or text customers, create or change records, or call outside apps. There is no invoice-reminder or onboarding-step action today.
New rules start as drafts in sandbox with an approval gate on, and only Testing or Active rules run. A dry run shows what a rule would do without sending anything, and only approvers can switch a rule on.
Owners, admins, HR and managers whose role allows it can build rules, and approvers switch them on and run them. An editor without approval rights asks to activate, and the company’s approvers decide.
Not yet. AI agents stay closed until an agent run does real work, because today a run would only draft a plan. The rules on this page are what runs today.
Every suite shares the same people, files and records, so work moves between them without copying anything.
Tell us how your company is organised and which tools you need first. We set up Automation with your teams and roles, and the rest of Anslation One when you are ready.
Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838