Workflow Automation
4 min read · Part of the Features cluster
Workflow automation in project management software is the rule-based triggering of actions based on events. The pattern is almost always “When [trigger] happens, Then [action] fires” — sometimes with conditions: “When [trigger] happens, If [condition] is true, Then [action] fires.”
A status-change automation: “When a task’s status changes to ‘Ready for review’, assign it to the QA lead and send a Slack notification to the #qa channel.” This replaces a manual process: someone completes work, remembers to change status, remembers to notify QA, hopes QA saw the Slack message.
The difference between a team that “uses PM software” and a team that “runs its operations on PM software” is usually whether workflow automation is wired up for the 5–10 most frequent process steps.
Concrete example
An agency runs a content production workflow: Brief → Research → Writing → Internal review → Client review → Approved → Published.
Without automation, each transition requires the current owner to manually move the task to the next stage and manually notify the next person. In practice, this breaks: someone forgets to update status, someone misses the notification, the account manager has to check Slack to confirm where a brief is.
With automation:
- When status = “Writing complete”, assign to editor, send Slack notification to editor
- When status = “Approved for client”, send automated email to client contact with the draft link
- When status = “Approved”, assign to publisher, move to “Publishing queue” board
- When due date passes and status is not “Published”, send reminder to publisher and escalation Slack to account manager
These four automations replace 20–30 manual actions per piece of content. At 40 pieces per month, that’s 800–1,200 manual actions eliminated. At 30 minutes per missed handoff (status not updated, chase message sent, context recovered), automation saves 10–15 hours per month.
The automation cap — the gotcha in the fine print
The most important number in PM software automation isn’t the feature depth — it’s the monthly limit:
| Tool | Tier | Automation limit |
|---|---|---|
| monday.com | Standard (£10/seat) | 250 actions/month |
| monday.com | Pro (£24/seat) | 25,000 actions/month |
| ClickUp | Business (£10/seat) | 10,000 actions/month |
| Asana | Starter (£10.99/seat) | 25,000 rule runs/month |
| Wrike | Business (£19.95/seat) | Unlimited |
| Smartsheet | Pro (£6.20/seat) | 250 runs/month |
monday.com’s Standard tier is the most commonly misconfigured. Teams build 6–8 automations following the template library, hit the 250/month cap by week three, and don’t notice until the ops manager asks why the archive board hasn’t updated.
A single automation that fires on a status change 50 times/week = 200 actions/month. Two automations like that = 400 actions/month = 60% over the Standard limit. Plan for Pro (£24/seat) from the start if you’re building more than two active automation chains.
What “native” automation means vs Zapier
Native automation: Built into the PM tool’s own rule engine. Fires instantly on internal events. No third-party dependency.
Zapier automation: Connects the PM tool to external services or handles events the native engine doesn’t support. Adds latency (Zapier’s polling interval, typically 5–15 minutes on paid plans). Adds cost (Zapier Professional at £66/month for 2,000 tasks).
For most workflow automation within a single PM tool (status changes, assignment routing, notification sending), native automation is faster, cheaper, and more reliable. Zapier is the answer when you need to connect events in one tool to actions in a completely different tool — “when a Jira ticket is created, add a row to a Google Sheet.”
Tools that do workflow automation well
- Asana Starter (£10.99/seat) — 25,000 rule runs/month, intuitive rule builder, condition branching
- ClickUp Business (£10/seat) — 10,000 actions/month, most flexible trigger/condition/action model
- Wrike Business (£19.95/seat) — unlimited automation, complex conditional branching
- monday.com Pro (£24/seat) — 25,000 actions/month, most approachable builder (but needs Pro for this volume)
Why it matters for your buying decision
Ask before you sign up: “What is the automation limit on the tier I’m evaluating, and how many automation actions does my typical month of operations generate?” If you can’t answer that question, sign up for the trial, build your actual workflows, and monitor the action count for two weeks before committing.
The teams that overpay for PM software typically do so because they evaluated on Standard tier, built their operations on the assumption of unlimited automation, hit the cap in month two, and upgraded to Pro — a tier they would have bought from the start if they’d understood the automation economics.