Digitorn
Digitorn
All terms
Runtime

Triggers

Declarative entry points that launch an agent on an event: cron, webhook, file watch, or message.

also known as: agent triggers
In depth

Triggers turn an agent into a worker that fires on something. Cron triggers run on a schedule. Webhook triggers expose an HTTP endpoint other systems can call. File watch triggers fire when a file appears or changes. Message triggers fire when an inbound message lands on a channel (Slack, email). The agent's YAML declares its triggers next to the agent itself, no separate scheduler service.

What it looks like in practice

YAML
1triggers:2  - id: weekly-digest3    kind: cron4    schedule: "0 9 * * MON"5    target: { agent: reporter, message: "Run the digest." }
Related concepts
Newsletter

Get the next post in your inbox.

Engineering notes from the Digitorn team. No marketing, no launch announcements, no "10 prompts that will change your life". Just the things we write that we'd want to read.

One-click unsubscribe. We never share your address. Powered by our own infrastructure, not a tracker.

More in Runtime

Behaviour rules/glossary/behavior-rulesCron trigger/glossary/cron-triggerFilesystem module/glossary/filesystem-moduleHooks/glossary/hooksHot reload/glossary/hot-reloadModule/glossary/module