Triggering Agents from incident.io Workflows
You can configure an incident.io workflow to call a Firetiger agent automatically when an incident is created (or at any other workflow trigger point). The agent receives details about the incident as its opening prompt, so it can immediately start investigating, pulling relevant logs, or running a runbook.
Prerequisites
You’ll need the webhook URL for the agent you want to invoke. Open the agent in Firetiger, look at the Triggers section, and copy the Webhook URL. It’ll look like https://api.cloud.firetiger.com/webhooks/dGhpc0lzQVRlc3RUb2tlbjEyMzQ1Njc4OTA. See Agent Webhooks for more detail on how webhook invocation works.
You’ll also need a Firetiger API key to authenticate the request. See API Keys for instructions on creating one.
Creating the Workflow
In incident.io, go to Workflows and create a new workflow. Set the trigger to Incident created (or whichever lifecycle event you want to fire on).
Add a Send a webhook step and fill it in as follows.
URL
Paste the webhook URL you copied from the Firetiger UI:
https://api.cloud.firetiger.com/webhooks/dGhpc0lzQVRlc3RUb2tlbjEyMzQ1Njc4OTA
Method
POST
Headers
| Key | Value |
|---|---|
Authorization |
Bearer {your-api-key} |
Body
The body is passed through to the agent as-is. Use incident.io’s template syntax ({{variable}}) to include incident details so the agent has context to work with.
{
"event": "incident.created",
"incident_id": "{{incident.id}}",
"incident_name": "{{incident.name}}",
"message": "Investigate this incident. Check for relevant errors, anomalies, or spikes in the data from around the time it was declared."
}
The agent receives the full body alongside the request headers, so include whatever context is useful. The more detail you provide, the better the agent can orient itself.
What Happens Next
When the workflow fires, Firetiger creates a new agent session and returns a session ID. The agent starts working immediately on the webhook payload. You can see the session on the agent’s page in the Firetiger UI, or poll the sessions API to read its output.
Related Documentation
- Agent Webhooks — Full reference for webhook trigger URLs