---
{
  "id": "platform.trigger.overview",
  "topic": "trigger",
  "title": "Event-driven Trigger overview",
  "locale": "en",
  "version": "2026-08-10",
  "summary": "A Trigger watches an accepted Arinova resource event and delivers a task to an owned target Agent.",
  "content": "Trigger is Arinova’s event-driven automation. A matching platform resource event creates a fire event and dispatches the configured `systemMessage` as a task to the target Agent. Use `arinova.trigger.create_trigger`; when `targetAgentId` is omitted, the current Agent is the target.\n\nCreate success means the rule is active. It does not mean an event has matched, a task has been delivered, or an Agent execution has succeeded. Those are separate runtime and fire-event states. Use `list_triggers` to find rules, `get_trigger` for one rule and its lineage/summary, `update_trigger` to create an immutable replacement, `set_enabled` to pause or resume, and `cancel_trigger` to stop future normal fires.\n\n`arinova.trigger.delete_trigger` is deprecated and its registry replacement is `arinova.trigger.cancel_trigger`; normal lifecycle operations should cancel rather than soft-delete. `record_run_result` is runtime bookkeeping, not a general user command. Current action results and persisted status are authoritative over this card.\n\nThe current Agent needs `canCreateTrigger` to create a rule. Reading or changing an existing Trigger also requires that Agent's per-resource read or write grant. The target Agent always keeps a write floor, and an Agent-created Trigger also grants its creator write access in the same transaction. Updates use immutable replacement: grants are copied to the new row, and a newly rebound target Agent is re-floored. User owners manage these grants in Office. Existing rules were grandfathered to their target Agent and the owner's active external Agents; new user-created rules do not fan out to every Agent.\n",
  "aliases": [
    "trigger",
    "event rule",
    "event-driven automation",
    "resource event",
    "when a card changes",
    "Agent task delivery"
  ],
  "tags": [
    "trigger",
    "overview",
    "event-driven"
  ],
  "relatedActions": [
    "arinova.trigger.create_trigger",
    "arinova.trigger.list_triggers",
    "arinova.trigger.get_trigger",
    "arinova.trigger.update_trigger",
    "arinova.trigger.set_enabled",
    "arinova.trigger.cancel_trigger",
    "arinova.trigger.delete_trigger"
  ],
  "relatedActionPrefixes": [],
  "url": "https://docs.arinova.ai/en/kb/trigger/overview/"
}
---

Trigger is Arinova’s event-driven automation. A matching platform resource event creates a fire event and dispatches the configured `systemMessage` as a task to the target Agent. Use `arinova.trigger.create_trigger`; when `targetAgentId` is omitted, the current Agent is the target.

Create success means the rule is active. It does not mean an event has matched, a task has been delivered, or an Agent execution has succeeded. Those are separate runtime and fire-event states. Use `list_triggers` to find rules, `get_trigger` for one rule and its lineage/summary, `update_trigger` to create an immutable replacement, `set_enabled` to pause or resume, and `cancel_trigger` to stop future normal fires.

`arinova.trigger.delete_trigger` is deprecated and its registry replacement is `arinova.trigger.cancel_trigger`; normal lifecycle operations should cancel rather than soft-delete. `record_run_result` is runtime bookkeeping, not a general user command. Current action results and persisted status are authoritative over this card.

The current Agent needs `canCreateTrigger` to create a rule. Reading or changing an existing Trigger also requires that Agent's per-resource read or write grant. The target Agent always keeps a write floor, and an Agent-created Trigger also grants its creator write access in the same transaction. Updates use immutable replacement: grants are copied to the new row, and a newly rebound target Agent is re-floored. User owners manage these grants in Office. Existing rules were grandfathered to their target Agent and the owner's active external Agents; new user-created rules do not fan out to every Agent.