Trigger Agent
Trigger an agent with an arbitrary JSON payload. Tembo passes the request body to the agent as event context, so the agent can use values such as issue URLs, ticket IDs, Slack thread links, Sentry event IDs, priorities, or customer-provided instructions.
If the agent has a post-trigger hook, Tembo also exposes the same request body to that hook as the TRIGGER_PAYLOAD environment variable. To add dynamically fetched context to the agent’s starting thread, have the hook print the final useful context to standard output.
You can identify the agent by either its UUID or its macro (key). The API key can be supplied via the Authorization: Bearer header or the apiKey query parameter.
Path Parameters
The agent's UUID or its macro (key). You can find the UUID in the agent's properties panel.
"a1b2c3d4-5678-9abc-def0-1234567890ab"
Query Parameters
API key for authentication. Alternative to using the Authorization header.
Body
Arbitrary JSON payload passed to the agent as event context and, when configured, to the post-trigger hook as TRIGGER_PAYLOAD.
The body is of type object.
Response
Agent triggered successfully
Unique identifier for the queued job
The type of job that was queued
"RunAgent"
Current status of the job
"pending"
Job priority
5