Skip to main content
Automation rules are the core building block of fsckmsft Automation. Each rule pairs a trigger (something that happens in your workspace) with one or more actions (what fsckmsft does in response), optionally filtered by conditions that narrow when the rule fires. Once enabled, a rule runs automatically in the background — no manual intervention required.

​
How rules work

A rule follows a simple structure:
When [trigger event occurs] and [conditions are met] → do [action]
For example: When a task’s status changes to “Done” and the task is in the “Engineering” project → send a Slack message to #releases. You can chain multiple actions onto a single trigger, and add as many condition filters as you need to keep rules precise.

​
Creating a rule

1

Open the Automation tab

Navigate to your project or workspace, then click Automation in the left sidebar. The Automation hub opens.
2

Create a new rule

Click New Rule in the top-right corner. A rule editor panel slides in from the right.
3

Choose a trigger

Click Select a trigger and pick the event that should start the rule. See the trigger reference table below for all available options.
4

Add conditions (optional)

Click Add condition to filter when the rule fires. For example, restrict the rule to tasks in a specific project, assigned to a specific person, or with a specific priority. Add as many conditions as needed using AND / OR logic.
5

Add one or more actions

Click Add action and choose what should happen when the trigger fires. You can add multiple actions — they execute in the order you define them.
6

Name and save the rule

Give the rule a descriptive name (e.g., “Notify #releases on task completion”), then click Save. The rule is saved in a disabled state by default.
7

Enable the rule

Toggle the rule to Enabled in the rule list. It is now live and will fire the next time its trigger conditions are met.

​
Trigger and action reference

​
Available triggers

TriggerDescription
Task status changedFires when a task moves from one status to another
Task assignedFires when a task is assigned (or reassigned) to a member
Due date approachingFires a set number of days before a task’s due date
Comment addedFires when a new comment is posted on a task or document
Project createdFires when a new project is created in the workspace

​
Available actions

ActionDescription
Send Slack messagePosts a message to a Slack channel or DM (requires Slack integration)
Assign taskSets or changes the assignee of the triggering task
Update fieldChanges the value of any custom or standard field on a task
Trigger webhookSends an HTTP POST request to any URL with event payload data
Start workflowKicks off another automation workflow or rule chain

​
Adding conditions and filters

Conditions let you restrict a rule so it only fires for the exact subset of events you care about. After selecting a trigger, click Add condition in the rule editor to open the condition builder. You can filter on:
  • Project — limit the rule to one or more specific projects
  • Assignee — only fire for tasks assigned to certain people
  • Priority — trigger only on high-priority (or any specific priority) tasks
  • Custom fields — match any text, number, dropdown, or date field value
  • Label / tag — restrict to tasks with specific labels
Combine conditions with AND (all must match) or OR (any must match) logic using the toggle between condition rows.

​
Enabling and disabling rules

You can toggle any rule on or off from the Automation hub at any time without deleting it. This is useful for temporarily pausing a rule during migrations, bulk updates, or maintenance windows.
  1. In the Automation hub, find the rule in the list.
  2. Click the toggle in the Status column to enable or disable it.
  3. The status indicator updates immediately — no page refresh required.
Disabling a rule does not affect runs already in progress. Any action triggered before you disabled the rule will complete normally.

​
Viewing rule run history

Every rule execution is logged so you can audit what fired and why.
1

Open the rule

In the Automation hub, click the rule name to open its detail view.
2

Switch to the Run history tab

Click the Run history tab in the rule detail panel.
3

Inspect individual runs

Each row shows the timestamp, the trigger event that caused the run, the conditions that were evaluated, and the outcome of each action (success or error). Click any row to expand the full event payload and action logs.
Use run history to debug rules that don’t seem to be firing. Check whether the trigger event is being detected and whether any condition filters are excluding the events you expect.

​
FAQs

fsckmsft includes loop detection to prevent a rule from triggering itself indefinitely. If an action would cause the same trigger to fire again for the same task, the second run is suppressed. You’ll see a note in the run history when loop protection activates.
Rules fire within seconds of the trigger event being detected, typically under 5 seconds under normal load. The Due date approaching trigger is evaluated on a daily schedule, not in real time.
Yes. Open the rule’s detail view, click the ⋯ menu, and choose Duplicate to project. Select the target project and the rule is copied there in a disabled state for you to review and enable.