Agent / workflow
The agent name, automation name, or workflow that produced the activity.
Template
The agent name, automation name, or workflow that produced the activity.
One plain-language sentence explaining the action the workflow recorded.
Tools, APIs, databases, tickets, issues, repositories, accounts, or records affected by the run.
What changed, what completed, what failed, or what needs human review next.
An independent check that confirms the intended result beyond the tool call’s technical success.
Links to GitHub, Linear, Zendesk, Stripe, Granola notes, internal records, or follow-up work.
The human owner who checked the result or still needs to review it.
Keep one entry for every meaningful agent action. Record the business outcome separately from the technical result of a tool call.
Timestamp: Agent / workflow: Human owner: Action summary: Systems touched: Records changed: Outcome: completed | failed | needs review Verification: Related links: Follow-up owner: Review status: pending | approved | rejected Notes:
This event separates what the agent did from what a human still needs to confirm. Replace the identifiers and links before using it.
Timestamp: 2026-09-04 14:30 UTC Agent / workflow: Support triage agent Human owner: Jordan Lee Action summary: Summarized an escalated ticket and created product follow-up Systems touched: Zendesk, Linear Records changed: Ticket 1842, Issue ENG-427 Outcome: needs review Verification: Confirm the issue matches the customer report Related links: Ticket 1842, Issue ENG-427 Follow-up owner: Jordan Lee Review status: pending Notes: Customer impact has not yet been confirmed
This illustrative request body follows the agent action format. Check the REST guide for required fields, related links, follow-ups, and validation before sending it. Creating an agent requires Starter or Pro.
{
"idempotencyKey": "support-review-42",
"verb": "reviewed",
"type": "support_follow_up",
"title": "Reviewed escalated customer issue",
"description": "Compared the ticket with recent product activity.",
"status": "completed",
"outcome": "Recorded the review and identified a follow-up.",
"occurredAt": "2026-09-04T14:30:00Z",
"agentRunId": "support-review-42"
}Use the template to decide what a person will need to review. A named agent on Starter or Pro can record its work through MCP or REST; Pro custom sources remain available for other event ingestion workflows.