One trigger-action pair is often not enough. MatterFirst lets automations chain — the result of one rule becomes the event that fires the next — so you can build sophisticated processes without code.
Before you start
- Comfortable building a single automation (see 'Building automation rules')
How chaining works
Automation actions don't run in a vacuum — many of them emit their own system events. When an action such as moving the matter's stage, creating a task, or adding a key date runs, the resulting event re-enters the automation engine and can trigger further rules. The engine tracks how deep a chain has gone and stops it at a depth of 10, which protects you from accidental loops (a rule that keeps triggering itself).
Explicit vs implicit chaining
Chaining can be implicit — Automation A moves a matter to another stage, which fires Automation B that listens for 'When a matter moves to another stage'. A stage cannot call an automation by name; the move itself is what the next rule listens for. Either way, you compose small, single-purpose rules into a larger process rather than building one giant rule.
Worked example: settlement
Automation A — WHEN a matter moves to the 'Settlement' stage THEN Create Task (settlement checklist), Send Email (client), and Create Calendar Event. Automation B — WHEN a task is done THEN Notify Users. Completing a settlement task fires B without A knowing anything about it. Each rule stays simple; the behaviour emerges from the chain.
-
1
Compose rules into a sequence
Build several small automations whose triggers line up with earlier rules' actions, and view them together on the Automations list. Here a 'When a matter moves to another stage' rule creates tasks and a calendar event, while a separate 'When a task is done' rule notifies the team — together they form a chain no single rule expresses.
Tips & pitfalls
- Keep each rule single-purpose. Chains are easier to reason about and debug than one rule that tries to do everything.
- The engine halts a chain at depth 10 to stop runaway loops. If a chain stops earlier than expected, check that each downstream trigger actually matches the upstream action's event.
Key takeaways
- Automation actions emit events that can trigger further automations
- Chaining is event-driven: one rule's change is the next rule's trigger
- The engine stops chains at depth 10 to prevent infinite loops
Put the lesson into practice.
Book a guided session and our team will help you configure MatterFirst for your own practice.
We can't find the internet Attempting to reconnect
Something went wrong! Attempting to reconnect