Skip to main content

Triggers — Automatic Reactions to Signals

Trigger Rules are if-then automation rules evaluated on every incoming signal. When conditions match, FleetQ triggers a project run automatically — no manual intervention needed.

Scenario: When a signal arrives with a ClearCue intent score above 80, FleetQ automatically triggers the "High-Intent Outreach" project run, passing the signal data as context.

How it works

After every signal is ingested, EvaluateTriggerRulesJob runs asynchronously. It evaluates all active trigger rules for your team against the signal's content. Matching rules fire their actions — in parallel if multiple rules match.

Condition operators

eq
neq
gte
lte
contains
not_contains
exists

Use dot notation to reference nested signal content: content.score, content.company.size.

Available actions

Action What happens
create_project_run Trigger an immediate run of a continuous project, passing the signal as context.

Example trigger rule

Create via API
{
  "name": "High-Intent Auto-Run",
  "status": "active",
  "conditions": [
    {
      "field": "content.score",
      "operator": "gte",
      "value": 80
    },
    {
      "field": "source",
      "operator": "eq",
      "value": "clearcue"
    }
  ],
  "action": "create_project_run",
  "action_config": {
    "project_id": "01jf4a2b-..."
  }
}
Use {{signal.title}}, {{signal.source}}, and {{signal.content.*}} interpolation in action configs to pass signal data to the experiment goal.

Testing rules without live data

From the Triggers page (/triggers), click Test Rule on any active rule and provide a sample signal payload. FleetQ evaluates the conditions and shows which would fire — without actually executing the action.

Rule testing is also available via the MCP tool trigger_rule_test — useful for automated validation pipelines and agent-driven workflows.