Skip to main content

​
Overview

Settings → General → System log lists every change to your data, newest first, with who made it and how it reached RevyOps: a person in the app, an API key, Claude or another AI agent, a workflow, a connected tool such as HubSpot or Instantly, or an import. Agency admins and Workspace admins open it; Members don’t see it. The log keeps three months.

​
What is logged

  • People and companies: created, deleted, and changes to name, job title, email, phone, LinkedIn URL, company, owner, status, LinkedIn connection status, Do Not Contact, and every custom field.
  • Emails, LinkedIn messages, calls, SMS and WhatsApp messages: created, deleted, and changes to interest, interest labels, status, owner and the person they belong to.
  • Opportunities, tasks, meetings and notes: created, deleted, and changes to name, amount, stage, status, close date, pipeline, lost reason, owner, task and meeting status, and opportunity custom fields, whether they come from HubSpot, Close or RevyOps.
Scores, counters, computed fields and sync bookkeeping are not logged. Neither are the fields of your own activity types.

​
Changes

One row is one operation: a save in the app, an API or Claude call, a bulk edit, an import, a webhook, or one workflow step. A bulk edit of 300 people is one row, “300 people · Status changed · 300”. Click a row to see each record’s value before and after. Changes a deletion caused are not shown next to it: deleting a company doesn’t list every person it unlinked, and deleting a person doesn’t list their emails.

​
Filters

  • Time: a quick range such as Today or Last 7 days.
  • Record: one person or company changed lately.
  • Who: one person, API key, AI agent or connected tool.
  • Change type: a record created or deleted, a kind of activity (Email, Opportunity, Note, your own activity types), or one field of one kind of record, such as Opportunity → Stage, which covers HubSpot, Close and RevyOps opportunities alike.
  • AI run: the changes of one run.
  • Show system events: also show writes no person or tool made, such as maintenance commands.
  • Search: a name, email, phone, LinkedIn URL, domain, email subject, opportunity name, value, or the start of an operation or run ID.

​
AI runs

The AI runs tab lists one run per workflow run with AI steps, and one per task Claude or another AI agent did through MCP. Each shows its task, trigger, duration, how many records it changed, a Result and a status:
  • A workflow run is Completed, or Failed when one of its AI steps failed. Its Result is the step’s error, or how many fields the model could not fill.
  • An agent opens a run with start_run, naming the task. The run is Unfinished until the agent closes it with finish_run as Completed, Failed or Stopped (it gave the task up), with a sentence on the result. A run the agent never closed stays Unfinished.
  • Waiting approval: the agent called wait_for_approval and waits for a person; the Result says what to decide. Its next change marks the run Unfinished again.
  • Writes the agent makes without a run are grouped into an Untitled session until a 30-minute pause.
Open a run to see who ran it, such as “Ben Reed · via Claude” for an agent signed in with RevyOps (the app is the name the agent gave itself when it connected) or the API key’s name, the model and tokens the agent reported, and any of its calls RevyOps refused. View changes in this run opens the Changes tab filtered to that run.

​
From Claude

The MCP list_system_log, get_system_log_operation and list_ai_runs tools read the same log. They need Sign in with RevyOps as an Agency admin or this workspace’s admin; an API key alone can’t read it.