External triggers
When the real trigger for a task lives outside TeamMate — a new JIRA ticket, a Trello card move, a custom HTTP call — use EVENT_BASED execution.
How event-based tasks work
- The task is created in
EVENT_BASEDmode and sits Pending until an event arrives. - An external system sends a request to a TeamMate webhook URL.
- The task fires; the webhook payload is available to the agent as input.
- Subsequent runs happen each time the webhook fires.
Setup
- Open the Triggers tab in the agent builder (see Event triggers) or set up the trigger at the task level.
- Pick a trigger source:
- Trello — card moves between lists.
- JIRA — issue created / updated / commented.
- Webhook — generic HTTP endpoint, you POST anything.
- Configure trigger conditions and parameters.
- Save the trigger. A webhook URL is generated.
- Wire the source system to call the URL.
Generic webhook details
- URL — auto-generated, includes auth.
- Method — POST is standard; GET/PUT/DELETE supported.
- Auth — API key (recommended) or none.
- Payload — accessed as
trigger.bodyin the agent prompt or asinput1in workflow nodes.
Common patterns
| Source | Common use |
|---|---|
| Trello | Auto-summarize a card when it’s moved to “Done”. |
| JIRA | Triage an incoming issue: assign priority, suggest assignee, draft reply. |
| Generic webhook | React to anything that can fire an HTTP call: CI events, form submissions, monitoring alerts. |
Related
- Event triggers — the agent-builder side.
- Integrations → Webhooks overview — workspace-level webhook setup.
- Workflows → Webhook trigger — when the trigger fires a workflow instead of a single task.