Running Agents With Webhooks

Every Firetiger agent has a manual trigger with a stable webhook URL. Posting to that URL fires the trigger — the HTTP body and headers become the agent’s opening message. This lets you kick off an agent run from a CI pipeline, an alerting system like PagerDuty or incident.io, a cron job, or any other tool that can make an HTTP request.

No API key is required. The opaque token in the URL is the credential; treat it as a secret.

Finding the Webhook URL

Open the agent’s detail page in the Firetiger UI and look at the Triggers section. You’ll see a Webhook URL with a copy button — something like:

https://api.cloud.firetiger.com/webhooks/dGhpc0lzQVRlc3RUb2tlbjEyMzQ1Njc4OTA

Copy that URL; you’ll use it directly in your HTTP request.

Making the Request

Invoking a webhook trigger is a single POST to the webhook URL. The body can be any format — Firetiger passes it through to the agent as-is.

curl -X POST \
  https://api.cloud.firetiger.com/webhooks/dGhpc0lzQVRlc3RUb2tlbjEyMzQ1Njc4OTA \
  -H "Content-Type: application/json" \
  -d '{
    "event": "incident.triggered",
    "incident": {"id": "Q1A2B3C4", "title": "High error rate on checkout"}
  }'

The agent receives a structured message containing the timestamp, request headers, and body. A few headers are omitted (like X-Forwarded-For). The body is included as-is, truncated to 50 kB if larger.

No Content-Type requirement — the body is passed through verbatim. Including Content-Type is recommended so the agent knows how to interpret the payload.

Response

A successful invocation returns the created session name:

{
  "session": "agents/uvxtwa1yoyrx/sessions/sess456"
}

The session field is the name of the agent session that was started. You can use it to poll for results or read the agent’s output via the agent sessions API.

Using Multiple Sources With One Trigger

You can multiplex multiple webhook sources to the same trigger by including a custom header (e.g., X-Alert-Team: platform). The agent receives all headers and can use them for routing or interpretation without requiring a separate trigger per source.