Triggers And Webhooks
The dashboard ships route surfaces for Triggers and Webhooks under Integrations.
These pages matter because they show that Agirunner is not only a dashboard for manual launches. The product is structured to react to upstream systems and to emit events back out to them.
Triggers
Section titled “Triggers”The Triggers page is the operator surface for turning upstream events into platform work. It is where event-to-work mapping belongs as the integrations story expands.
Webhooks
Section titled “Webhooks”The Webhooks page is the operator surface for outbound platform event delivery. It is the natural place to manage subscribers, delivery contracts, and integration posture outside the browser.
Why It Matters
Section titled “Why It Matters”Together, these surfaces make it easier to picture Agirunner as part of a larger system instead of as a self-contained UI.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”Triggers and webhooks connect outside events to internal workflow state:
- triggers are a path into Workflows and the platform API when upstream systems should create or wake work
- webhooks are a path back out when workflow, task, or approval events should notify another system
- Integrations groups these surfaces with MCP and other external connections so the product reads as part of a larger stack rather than a closed console