Skip to main content

History

Every process, workflow, task, integration, agent and form says when it was last changed. Cards and list rows show a quiet age, such as 2h ago. Detail pages show one sentence, such as Last edit 2h ago by Ana López with Barry AI. Hover, focus or select that sentence to see who created the object and who last changed it, with exact local times and, for Barry, a link to the chat. Records changed before activity tracking started show only their date.

Select History next to that sentence to open the timeline. Changes are grouped by day and by operation, one sentence each, with the recorded values folded under Show changes. Choose Load older for earlier activity, or Open full history for a page of its own that you can link to (/activity/<kind>/<public id>).

Workflow history includes node and connection edits. Process history also includes its workflows' graph edits. Agent history includes version changes. Form history includes edits to the authored definition. Tasks keep their existing task history alongside this general activity view.

Each event names the actor and how the change arrived. A person is named, and Barry is the channel they used ("with Barry AI"), never the actor. An MCP client is named by its registered name, an API key by its name, and a removed account reads Deleted user. Other channels are workflows, agents, apps and system jobs. A workflow or agent can also show who initiated it. Context links appear when you may read that context. A private Barry chat remains private to its owner, including when an administrator reads the changed object's timeline.

Access and limits​

You can read an existing object's history when you can read that object today. Owners and administrators can open Organization settings → Activity for organization-wide activity, including deleted objects. API keys do not gain administrative access through history.

Values withheld marks sensitive fields such as credentials, integration configuration and task/form payload data. Workflow logic and authored form definitions have bounded recorded diffs. Large values or events may show a preview or truncation marker; the missing portion cannot be recovered from history. Deleted actors are labelled explicitly; a change with no identifiable actor is attributed to System.

History begins when audit capture was enabled for that type of object. Earlier changes are unavailable. Retention is 365 days once the deployment's retention job is installed. History is a record of changes, not a restore control.

API and assistants​

The additive GraphQL queries entityActivity, entityActivityByPublicId and organizationActivity return bounded pages with nextCursor, hasMore and truncated. The default page size is 50 events and the maximum is 100. Reuse a cursor only for the same organization and entity. Before/after values are JSON-encoded strings; the beforePresent, afterPresent and withheld flags distinguish absence, JSON null and values deliberately withheld.

auditAttribution returns creation and latest-change attribution for up to 100 objects. Its createdActor and updatedActor carry the actor as data: kind (user, api_key, workflow, agent, system, or none for changes before tracking), name, deleted, via and viaName. New kinds may be added; treat an unrecognised kind as system. The older createdBy/updatedBy strings are kept unchanged for existing integrations.

Barry and MCP expose list_entity_activity with the same entity permissions. Agent builtins can read live task history when running in the background; user-bound runs use the reader's current permissions. Background agents cannot read deleted objects or organization-wide activity.