InteliG
Sign Up

API Reference / agent-controller

Trigger an agent run now

post https://api.intelig.ai/api/v1/intelig/agents/{name}/trigger

Auth: Authorization: ApiKey <key> (an API key sent as Bearer is rejected) or Authorization: Bearer <jwt> for a dashboard session. operationId: trigger

Runs the named agent immediately for this organization instead of waiting for its schedule, and returns the run result. Names come from GET /agents. The one external automation usually wants is `execution-catch-up`: it backfills commit attribution, which is what makes a newly added ownership pattern apply to commits that already exist.

Example request

curl -X POST "https://api.intelig.ai/api/v1/intelig/agents/string/trigger" \
  -H "Authorization: ApiKey $INTELIG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "send": false,
      "cadence": "WEEKLY"
    }
  }'

Path parameters

NameTypeRequiredDescription
name string yes —

Request body

application/json

FieldTypeRequiredDescription
input object no Per-run input. For the CTO briefing, `send: false` renders a preview without emailing anyone. Example: {"send":false,"cadence":"WEEKLY"}

Response 200

application/json · ApiResponseAgentRunResult

FieldTypeDescription
success boolean —
message string —
data AgentRunResult —

Status codes

  • 200 — OK
  • 401 — —
  • 404 — Not Found
  • 429 — —

Every response is wrapped in { success, message, data }. A 4xx means the request is wrong — do not retry it unchanged. A 429 carries Retry-After in seconds.