Running Agents With Webhooks

Every Firetiger agent has a manual trigger — a stable ID you can use to invoke the agent over HTTP from any external system. This lets you kick off an agent run from a CI pipeline, an alerting system, a cron job, or any other tool that can make an HTTP request.

Finding the Trigger ID

Open the agent’s detail page in the Firetiger UI and look at the Triggers section. You’ll see a Webhook row showing the trigger ID — something like triggers/abc123xyz. Copy that ID; you’ll use it in the request body below.

Making the Request

Invoking a trigger is a single POST request to the InvokeTrigger endpoint:

POST https://api.ft-jam.firetigerapi.com/firetiger.triggers.v1.TriggersService/InvokeTrigger

The request body takes two fields: the trigger name you copied from the UI, and the message to send to the agent as its opening prompt.

curl -X POST \
  https://api.ft-jam.firetigerapi.com/firetiger.triggers.v1.TriggersService/InvokeTrigger \
  -H "Content-Type: application/json" \
  -H "Authorization: Basic {api-key}" \
  -d '{
    "name": "triggers/abc123xyz",
    "message": "Check for any new errors in the last hour and summarize them."
  }'

Required Headers

Content-Type: application/json

The request body must be JSON.

Authorization: Bearer {api-key}

All API requests require authentication. Pass your API key as a Bearer token.

Response

A successful invocation returns the created session name alongside the trigger resource:

{
  "trigger": {
    "name": "triggers/abc123xyz",
    ...
  },
  "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.

Getting an API Key

See API Keys for instructions on creating a key.