Turn repeating work
into a rule.
You hand repeating work to a rule. When something happens, let the notification go out, the task open, the label go on, the owner be assigned — all without you touching it.
Automation module features
From building a rule to watching it run, from ready recipes to outside connections — all inside Workinno.
Triggers
A task created, a stage change, an owner assigned, a comment added, a due date approaching. It works beyond tasks too: a new customer, a new sale, the form on a site you built with Workinno, a stock or price change, an accepted or rejected quote, a leave request. Automation reaches across the whole workspace.
Conditions
Conditions decide whether the rule runs every time or only in certain cases. You pick a field, a comparison and a value; with more than one condition you say whether all of them or any of them must hold. The rule steps in only in the case you meant.
Actions
Send a notification, open a task or subtask, assign an owner, change the stage, add a label, set a due date, start a timer, log a customer interaction, create a bookkeeping entry, send a bulk email and push data to an outside system. A single rule runs several of these one after another. Every step that follows an event goes through on its own.
Using event data in messages
You use what the trigger brought inside the actions. You drop the task name, the name written into a form or the amount into the notification text. Whoever reads the notification does not have to ask what it is about.
Rule scope
You choose the scope: in one project, across the whole workspace, or only on your own tasks. A personal rule affects only you and gets in nobody's way. You draw a rule's reach yourself.
Personal rules
You build personal rules that touch only your own tasks. No administrator permission is needed; you automate your own way of working without touching anyone else's flow. You set up your own routine without asking anyone.
Ready recipes
The Automation Store offers the rules people build most often. You pick a recipe, answer a few questions in the wizard and add the rule to your list. You do not have to build from scratch.
Stage-linked rules
In a project you attach a rule straight to a stage on the board. What happens when work enters that column is settled in advance; nobody has to remember. Every column on the board carries its own rules.
Scheduled rules
Some work waits for the hour, not for an event. You set a rule to run every morning, every Monday or on the first day of the month; you pick from ready intervals and give your own time zone. A weekly report or a monthly reminder arrives at its own hour.
Automatic replies to messages
You set up the greeting and the after-hours reply for incoming customer messages in the flows of the Communication hub. The first answer does not wait for someone to be free. A customer message does not go unanswered.
Rule states
You can stop a rule without deleting it. You prepare a draft and make it active when it is ready; if something goes wrong you switch it off from the row. Trying a rule is not a step you cannot take back.
Run history
Every time a rule fires it lands in the history: succeeded, failed, running, skipped or rate limited. If the rule did not run, the condition that did not hold is written there with the expected and the incoming value. The reason a rule stayed still is in the record.
Loop protection
By default a rule's actions do not trigger other rules. Even if you deliberately open the chain trigger, an hourly limit and suspension after ten failures in a row run in the background. Two rules cannot put each other in an endless loop.
Rule list
You search the rule list and filter active and suspended rules with ready chips. How many times each rule ran and how many of those failed stays in the list. You read from the list which rule is earning its keep.
Bulk actions
You select several rules and turn them on, off or delete them in one go. As the number of rules grows you do not walk through them one by one. Managing them does not get heavier as they multiply.
Webhook integrations
Run your rule when an event happens in another system with an incoming webhook, and send data to other systems with an outgoing webhook. Each rule gets its own address, so you no longer move data between two systems by hand.
Webhook logs
You watch all incoming and outgoing webhook traffic from one page. If a delivery failed, the reason shows up right there. When a connection breaks, you see where it broke.
Webhook and API keys
Keep external service keys in an encrypted vault and use them in rules by name, and verify with the same key that an incoming webhook request comes from the right place. Create API keys with separate read and write permissions for your own software and revoke them whenever you like.
API documentation
Review API endpoints and sample requests in the up-to-date documentation inside the app. The team writing the integration always works with information that is updated together with the product.
Roles and permissions
Creating a rule, editing one and seeing the run history are separate permissions. Not everyone needs to be able to change automation. Responsibility for it stays with certain people.
Let the chasing leave you and go to a rule
Without Workinno Automation
With Workinno Automation
Frequently asked questions
Do I need to know how to code to build an automation?
No. You build the rule by choosing in a window: pick the trigger, the conditions and the actions from a list.
What does a rule consist of?
A trigger, optional conditions and one or more actions. A single rule can carry several actions.
Where does a rule run?
You choose the scope: in one project, across the whole workspace, or only on your own tasks.
How do I see whether a rule ran?
Every run lands in the history. You see the outcome — succeeded, failed, skipped — and if it was skipped, which condition did not hold.
Can rules put each other in an endless loop?
No. By default a rule's actions cannot trigger other rules. Even if you deliberately turn the chain trigger on, an hourly limit and suspension after ten failures in a row are still at work.
Are there ready-made rules?
Yes. You pick one of the Automation Store recipes and set it up in the wizard; the rule goes straight into your list.
Can it talk to outside systems?
Yes. An incoming webhook brings events in from outside, an outgoing one sends data to another system. You watch the deliveries from a single list.
Can I stop a rule for a while?
Yes. A rule can be active, a draft or suspended. You switch it off from the row; you do not have to delete it.
Build your first rule today.
Pick a ready recipe or build your own rule. From today on, let repeating work happen by itself.
Free forever

