Automation rules

Automation rules let Reactor take action automatically when a condition is met. Rules run in the background and can trigger brief creation, scheduling changes, or alerts.

:::note Hidden in the UI The automation page is not part of the current analytics navigation (it redirects to the overview), but rules keep running in the background and remain fully manageable over MCP with list_automation_rules and create_automation_rule. :::

Rule structure

Each rule has:

A trigger type: what condition activates the rule
A threshold: the numeric value at which the trigger fires
An action type: what Reactor does when triggered
An action config: parameters for the action

Trigger types

Trigger	Description
`engagement_threshold`	A post's engagement rate crosses a defined value
`topic_velocity`	A topic is being searched or referenced at an accelerating rate
`posting_gap`	No content has been published for N days on a platform
`conversion_rate`	A conversion rate drops below a threshold

Action types

Action	Description
`create_brief`	Automatically create a brief with the specified topic and platform
`pause_platform`	Stop publishing to a platform until manually re-enabled
`alert`	Send a notification (webhook or in-app)
`reschedule`	Move a scheduled post to a different time

Creating a rule via MCP

{
  "tool": "create_automation_rule",
  "arguments": {
    "name": "Revive top performers",
    "triggerType": "engagement_threshold",
    "triggerConfig": {
      "threshold": 0.05,
      "comparison": "above",
      "platform": "linkedin"
    },
    "actionType": "create_brief",
    "actionConfig": {
      "topic": "Follow-up on high-engagement post",
      "platform": "linkedin",
      "angle": "Expand on the key insight from the top performer"
    }
  }
}

List what exists with:

{
  "tool": "list_automation_rules",
  "arguments": {}
}

Returns all active and inactive rules for the workspace.

Rule evaluation

Rules are evaluated hourly as part of the analytics sync cycle. There is no real-time trigger evaluation; the maximum latency between a condition being met and the action firing is approximately one hour.

Use cases

Never let the cadence stall: a rule that fires a new brief whenever there has been no post on LinkedIn in the last 3 days. (For fixed cadences, recurring schedules are usually the better tool.)

Amplify what works: fire a create-brief action whenever a post exceeds 5% engagement rate on X, and expand the same subject into a longer piece.

Rule structure​

Trigger types​

Action types​

Creating a rule via MCP​

Rule evaluation​

Use cases​