Agent / workflow
The agent name, automation name, or workflow that produced the activity.
Template
AI Agent Activity Log Template
Use this structure when product, engineering, support, and operations need to review agent work after the run ends.Checklist
Capture the context humans need later
- Record the agent, workflow, owner, and run time.
- List every tool or system the agent touched.
- Describe the action in language a teammate can review.
- Link affected issues, pull requests, tickets, accounts, or records.
- Mark the outcome, follow-up owner, and review status.
- Make the entry searchable by source, customer, feature, and event type.
Fields
The minimum useful record
Action summary
One plain-language sentence explaining what happened and why it matters.
Systems touched
Tools, APIs, databases, tickets, issues, repositories, accounts, or records affected by the run.
Outcome
What changed, what completed, what failed, or what needs human review next.
Related context
Links to GitHub, Linear, Zendesk, Stripe, Granola notes, internal records, or follow-up work.
Reviewer
The human owner who checked the result or still needs to review it.
Live version
Move from template to timeline
A spreadsheet can define the fields. Grondeo can collect agent activity through APIs and webhooks, then place it beside product events.