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 Automations in the sidebar.
Every rule has three parts:
- 1A trigger: the event that starts it. A record type plus something that happens to it.
- 2Betingelser: which of those events actually count. Without conditions the rule fires on all of them.
- 3Handlinger (i rækkefølge): what to do, run in sequence.
Conditions are not optional in practice. Ingen betingelser: denne kører for hver eneste hændelse på {{entity}}, ikke kun dem du har i tankerne. 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".
Folders, once there are a lot of them. A workspace that automates seriously ends up with dozens of rules, and search only helps somebody who already knows the name of the one they want. Mapper above the list opens every workflow at once, grouped under the folder it is in, and typing a name next to one is what puts it there. Flyt til mappe… on a rule's own menu does the same thing for a single rule. The list then groups by folder, each folder heading collapsing when you click it, with Ikke i en mappe at the bottom.
A folder is a name on the rule rather than a thing you create first: it appears the moment something is put in it, and disappears when the last rule leaves. Type the same name on two rules and they are in the same folder; clear the name and the rule comes back out. One level, deliberately — nesting would be more to maintain than it is worth for finding the five rules about invoicing.
I dette afsnit
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
A workflow needs attention
What the red warning on an automation means and how to clear it
Fix a reminder that has no recipient
Find missing recipient details and repair them from the workflow notification
How many workflow runs you have used
What the run count above your workflows means, what counts as a run, and what happens at an allowance
Test an automation before you switch it on
What a test run checks for real, what it only warns about, and what it cannot tell you
Almindelige spørgsmål
- How do I create an automation?
- Can I run a rule when an email arrives?
- What actions can a workflow do?
- How do I see workflow runs?
- Why did I get a notification about an automation?
- What happens if a reminder has no email address?
- What happens when we reach our workflow allowance?
- Can I preview a workflow before turning it on?