Automate repeat List work
List automation reduces manual updates for repeatable task processes. Use it when the same trigger and conditions should cause the same action every time.
For List-level automation, focus on how to:
- Decide whether a repeated List action should be automated.
- Plan a safe rule before building it.
- Test the rule with a safe task.
- Troubleshoot rules that do not run or affect too much work.
Related Automation Help
Terms to know
- Trigger is the task event that starts the rule.
- Condition limits when the rule should apply.
- Action is the update, notification, assignment, reminder, or other operation performed.
- Scope controls which List or group of tasks the rule can affect.
- Safe task is a low-risk task used only to test behavior.
Before you start
- You must have access to the List.
- Your role must allow automation access.
- The current plan must include automation access.
- The app must be online.
- Test with safe tasks before relying on the rule for important work.
Decide whether to automate
Use automation when:
- The rule is predictable.
- The same condition should always cause the same action.
- The action is low-risk.
- The result is easy to verify.
Keep the action manual when:
- The decision needs judgment.
- The action could affect many tasks unexpectedly.
- The conditions are not clear.
- The change would be hard to reverse.
Plan a List automation
Write the rule before building it:
When [task trigger] happens, if [condition] is true, then [action].
Examples
- When a task moves to Review, assign the reviewer.
- When a task is marked blocked, notify the team.
- When a follow-up date is set, create a reminder.
Create and test the rule
- Open Automations from the app navigation or a supported List automation entry point.
- Create a new rule.
- Choose the trigger.
- Add conditions.
- Choose the action.
- Confirm the scope includes only the intended List or tasks.
- Save.
- Test with a safe task.
- Review the affected task and confirm only the expected action happened.
Troubleshooting
List automation does not run
- Symptom: A task changes, but the expected automatic action does not happen.
- Cause: The rule may be inactive, the trigger may not match, conditions may not match, access may be missing, or automation may be unavailable.
- Resolution:
- Confirm Automations loads.
- Confirm the rule is active.
- Confirm the task is inside scope.
- Check every condition.
- Test with a safe task that clearly matches.
List automation affects the wrong tasks
- Symptom: More tasks than expected are updated.
- Cause: The scope, trigger, or conditions are too broad.
- Resolution:
- Pause or disable the rule if available.
- Narrow the scope.
- Add stricter conditions.
- Test with one matching and one non-matching task.
FAQ
Should I automate task creation or task updates first?
Start with low-risk updates such as assignment, reminders, or notifications. Avoid broad automatic creation or deletion rules until the trigger is proven.
Can automation replace a clear List process?
No. Define the process first, then automate the repeatable parts.