Who did what, and when.
Spojit keeps a record of every meaningful action: who did it, what changed and when. That includes every tool call an agent makes, and the ones policy refused. Filter by actor, action, outcome or date, on a database kept separate from your workflows.
ryan@acme.comsystemmara@acme.comryan@acme.comryan@acme.comryan@acme.comA trail you can actually use
Every action is recorded
Workflow and connection changes, runs, approvals, billing and member changes, plus every tool call an agent makes, all logged with the actor and the time.
It is kept apart from your data
Audit events are stored separately from the workflow data they describe, and scoped to your workspace.
Filter it down to the answer
Narrow by actor, action, outcome or date range until you have the specific event, then read what it recorded.
Accountability, built in
A complete trail
Meaningful actions across the workspace are captured, so nothing important happens off the record.
Actor on every event
Each event records who or what did it, a person or an automated process, with their identity.
Filter and search
Slice the trail by actor, action, or time window to answer a question in seconds.
Agent tool calls included
Not just what a person changed. Every tool call an agent makes is recorded too, with the connection it used and how it turned out.
Kept apart from your workflows
The record is stored separately from the workflow data it describes, rather than sitting in among the things it is meant to account for.
Tenant-scoped
The trail is isolated to your workspace, so you see your activity and nobody else sees it.
Where an audit trail matters
Pass a compliance review
Show exactly who changed what and when, without reconstructing the story from memory.
Investigate an incident
Trace the change that caused a problem back to the action and the person behind it.
Track configuration changes
Keep a record of connection and workflow changes, so surprises in production have an explanation.
Answer for an agent
When someone asks what an AI agent did in your systems, the trail has the tool calls, the connection used, and the ones policy refused.
A built-in trail vs piecing it together later
The record is captured as things happen, instead of being reconstructed from memory when someone asks.
Lean on the audit log when
- You need to show who changed what, and when
- You need to account for what an AI agent did in your systems
- A review or incident needs a clear paper trail
Without an audit trail you get
- No reliable answer to "who changed this?"
- Incidents reconstructed from memory and guesswork
- A scramble whenever a reviewer asks for evidence
Cada ejecución, con las mismas garantías
Keep a record you can trust
Start free and get a trail of who did what, and of every tool call your agents make. No card needed.