Workflow automation
A workflow rule does something automatically when something happens: when a deal reaches a stage, create the follow-up task; when a customer goes quiet, tell the account manager. Rules live under Arbetsflödesautomation in the sidebar.
Every rule has three parts:
- 1A trigger — the event that starts it. A record type plus something that happens to it.
- 2⟦Villkor⟧ — which of those events actually count. Without conditions the rule fires on all of them.
- 3⟦Åtgärder (i ordning)⟧ — what to do, run in sequence.
Conditions are not optional in practice. Inga villkor — den här körs för varje händelse på {{entity}}, inte bara de du har i åtanke. This is how a helpful rule becomes an email storm: "notify me when an opportunity changes stage" with no condition notifies you about every stage change on every deal in the company, forever. Add the condition that says which ones you meant.
Rules run on real data and are not undoable. A rule that creates a task on every customer creates thousands of tasks, and there is no single button that takes them back. Test with a narrow condition first, widen once you have seen it behave.
Check that they are working. Rules fail quietly by nature — nobody notices an email that was never sent. The run history shows what fired and what failed, and it is worth looking at after creating a rule rather than assuming. See "A rule is not firing".
I det här avsnittet
Create a workflow rule
Build a rule narrow, watch it fire, then widen it
What can trigger a rule
The events a rule can listen for, and why they differ per record type
What a rule can do
What a rule can actually do once it fires, and the order it does it in
A rule is not firing
Work out why a rule did nothing, starting with the run history