Confluence Automation Rules
Repeated manual steps drain time: adding the same label, posting the same notification, creating the same weekly page. Automation rules perform those steps for you. A rule watches for an event, checks conditions, and runs actions without anyone clicking a button.
The Three Parts of a Rule
Every rule follows the same shape: trigger, condition, action.
TRIGGER CONDITION ACTION
(what happens) --> (does it qualify?) --> (what Confluence does)
Page published --> Space = "Support" --> Add label "needs-review"
AND title has FAQ and send a message
Trigger
A trigger starts the rule. Examples include a page being created, a page being published, a label being added, a comment being posted, or a scheduled time arriving.
Condition
A condition filters events. The rule continues only when the page meets the requirement, such as a specific space, label, or title pattern.
Action
An action performs the work. Typical actions include adding a label, sending an email, posting a chat message, creating a page, or adding a comment.
Where to Find Automation
Space administrators open space settings and look for automation. Site administrators manage rules that apply across many spaces. Available triggers, actions, and monthly run limits depend on your plan, so check your plan details before you design large workflows.
Building Your First Rule
- Open automation and choose create rule.
- Pick a trigger, such as page published.
- Add a condition, such as space equals Support.
- Add an action, such as send an email to the team lead.
- Name the rule clearly and turn it on.
- Publish a test page and confirm the result.
Smart Values
Smart values are placeholders that fill in live details, such as the page title or the author name. A notification message can read "New FAQ published" followed by the page title value, and each message carries the correct title automatically.
Rule Ideas for Teams
| Team | Rule | Benefit |
|---|---|---|
| Support | When an FAQ page is published, post a message in the team chat | The team learns about new answers quickly |
| HR | When a policy page changes, add the label "updated" | Readers filter recent changes |
| Engineering | Each Monday, create a weekly meeting page | Nobody forgets the agenda |
| Documentation | When a page stays untouched for months, comment and mention the owner | Old content gets reviewed |
Testing and Monitoring
Every rule keeps an audit log. The log shows each run, its result, and any errors. Review the log after you launch a rule, and fix failures quickly. A rule that triggers too often can spam colleagues, so tighten the conditions when the volume feels high.
Design Principles
- Start with one small rule and expand gradually.
- Write conditions narrow enough to avoid false triggers.
- Give every rule a descriptive name and a short note about its purpose.
- Assign one owner who maintains the rule.
- Turn off rules that no longer serve the team.
Common Pitfalls
- Building loops where one rule triggers another endlessly.
- Sending messages to large groups without need.
- Skipping tests before turning a rule on.
- Ignoring run limits on the plan.
A Walkthrough with Real Numbers
A support team publishes about twenty FAQ pages each month. Before automation, a team lead spent ten minutes per page labelling it and alerting the team. After one rule, the labelling and the alert happen the moment someone publishes. The team lead recovers more than three hours every month and no page misses its label.
Key Takeaways
- A rule combines a trigger, conditions, and actions.
- Smart values insert live page details into messages.
- Audit logs show how each rule performs.
- Small, well-named rules deliver the most value.