Automation Rules (Tasks)
Automation rules handle recurring housekeeping in a project automatically: when a specific event happens (e.g. a task is completed), SELLERLOGIC Commerce Services automatically runs one or more actions — such as assigning a person or sending a notification.
What can I do here?
- Select a project and manage its automation rules
- Create a new rule with a trigger and one or more actions
- Activate, deactivate, or delete rules
- See how many times a rule has fired and when it last ran
Step by step
- Open Automation Rules and select the project whose rules you want to manage at the top.
- Click Add Rule, give it a name, and choose a trigger (e.g. "Task added to project" or "Due date approaching").
- Use Add Action to attach one or more actions that should run when the rule triggers.
- If needed, reorder multiple actions with Move Up/Down — they run in that order.
- Save the rule. It's active immediately as long as the Active toggle is on.
Illustration
Automation Rules
| Name | Trigger | Actions | Status |
|---|---|---|---|
| Auto-assign new tasks | Task added to project | 2 | ✓Active |
| Remind before the due date | Due date approaching | 1 | ✓Active |
| Remove the tag after completion | Task completed | 1 | •Inactive |
/tasks/rulesIllustration
Edit rule
Project
Sample delivery project
Name
Auto-assign new tasks
Trigger
Task added to project⌄
Active
onSet assignee
A. Example
1
Add tag
Intake
2
/tasks/rulesFields explained
| Field | Meaning | Notes/Effect |
|---|---|---|
| Project | The project the rule applies to | Rules are always scoped to one project |
| Name | Name of the rule | — |
| Active | Whether the rule is applied | Inactive rules are skipped entirely |
| Trigger | The event that starts the rule | See value list below |
| Days before | For "Due date approaching": how many days before the due date it fires | Only relevant for this trigger |
| From/To status | For "Status changed": which status transition the rule reacts to | Can also be set to "any" status |
| Action | What happens automatically when triggered | See value list below |
| Audience (for notifications) | Who receives the notification | A specific person, a specific role, or all admins |
| Run count | How many times the rule has fired already | Informational only |
Values & Status
Trigger
| Label | Meaning |
|---|---|
| Task added to project | A task is newly assigned to this project |
| Task completed | A task is marked as done |
| Status changed | A task's status value changes |
| Due date approaching | A task reaches the configured number of days before its due date |
| Task assigned | A task gets a responsible person assigned |
Actions
| Label | Meaning |
|---|---|
| Set assignee | Automatically assigns the task to a specific person |
| Move to section | Automatically moves the task to a different column |
| Add tag | Automatically adds a tag to the task |
| Remove tag | Automatically removes a tag from the task |
| Set due date (relative) | Automatically sets a new due date, relative to the trigger time |
| Add comment | Automatically adds a predefined comment |
| Set custom field value | Automatically sets the value of a custom field |
| Create subtask | Automatically creates a subtask |
| Send notification | Automatically sends a notification to a person, role, or all admins |
Frequently asked questions
Do automation rules apply across projects?
No, each rule is bound to exactly one project. For another project, you need to create a separate rule.
What happens if multiple rules match at once?
All matching active rules run; within a single rule, multiple actions run in the order you set.
Can I see whether a rule has ever fired?
Yes, the run count and the timestamp of the last run are shown for each rule.