Use cases
Review the work your AI agent records.
See agent actions and follow-up changes beside the rest of your account activity in the Timeline.
Connected activity
4 events from 1 sourceAgent
- AgentAgent recorded a customer issue reviewRecorded
Event from this source
- AgentAgent linked an outcome to a Zendesk ticketRecorded
Event from this source
- AgentAgent marked a follow-up resolvedRecorded
Event from this source
- AgentAgent recorded a blocked taskRecorded
Event from this source
Recorded agent activity
1 source connectedThe situation
An agent can act across several systems. People need a clear history of what it recorded and which follow-up changed.
See agent actions and follow-up changes beside the rest of your account activity in the Timeline.
The workflow
Review a recorded agent action
- 01
Create a named agent on Starter or Pro and choose separate permissions for reading activity, recording actions, and working with follow-ups.
- 02
Connect the named agent through MCP or REST. After it searches related history, have it record its action and outcome and update a follow-up when appropriate. Review those entries in the Timeline.
- 03
Review the action and outcome the agent recorded.
What you see
Examples of recorded activity
The Timeline shows work an agent records. The Agents tab separately shows key access, without tool inputs or conversations.
- 10m agoAgent
Agent recorded a customer issue review
- 2h agoAgent
Agent linked an outcome to a Zendesk ticket
- 4h agoAgent
Agent marked a follow-up resolved
- YesterdayAgent
Agent recorded a blocked task
- 2d agoAgent
Agent added a related source link
The outcome
Review the action and outcome the agent recorded.
Inspect related source links when supplied.
See follow-up state changes alongside other activity.
Questions
Before you get started
Does Grondeo capture every agent action automatically?
No. Your agent sends the actions and outcomes it should record. The Agents tab logs access by assigned key, not tool inputs or conversation content.
Which plan do I need?
Creating named agents and using their MCP or REST access requires Starter or Pro. Pro is required only for the separate custom JSON API and incoming webhook integration path.
Get started