Trigger a Team routine

POST /v1/team/routine-hooks/:triggerId

Accept an external JSON event and enqueue the configured instruction as a user message in its Team. The normal Team Coordinator executes the queued turn. The service must be running and reachable locally; no cloud relay is provided.

Request body

{ "event": "changed", "evidence": { "source": "https://example.com/item" } }

Response body

{ "automation_run_id": "run_123", "duplicate": false }

Notes

Requires a trigger-specific secret even though gateway-wide authentication is bypassed. The JSON object must be at most 64 KiB. An active routine accepts up to 100 queued turns. Same key and equivalent JSON return the original run ID with duplicate=true and HTTP 202; changed JSON with that key returns 409. Without a key each call is independent. HTTP 202 means the message and turn were persisted, not that the Team has completed its work. Raw JSON stays in server-side turn context, available to all Agents; public message/history responses do not include it. Pausing rejects new triggers but accepted turns continue. Rotating a secret immediately invalidates the old secret.