An audit trail for your n8n workflows.
When a workflow changes in n8n, there's no record of what changed or when. If you run automations for clients or a team, that missing audit trail is a real liability. Keel keeps one automatically.
No record, no accountability
Without a change log you can't answer basic questions: what changed last week, was this edited before it broke, what does this client's workflow look like over time. n8n overwrites state on save, so the history simply doesn't exist unless something captures it.
How Keel builds the audit trail
Every change versioned
Each workflow change is snapshotted and timestamped, producing a continuous, queryable history.
Plain-English diffs
See exactly what changed between versions — not raw JSON, but "2 nodes changed, 1 added."
Per-client separation
Multi-client workspaces keep each client's history isolated and clear.
Backed up to Git
Redacted history is committed to your own repo, so the trail survives even a lost instance.
Find out what changed before your client does.
Keel runs a lightweight agent next to your n8n — snapshots, diffs, alerts, and rollback, with your secrets and API key never leaving your box. Free forever on one instance.
Questions
Does n8n have an audit log?
Not natively — there's no built-in record of workflow changes. Keel adds an external, versioned audit trail with diffs.
Can I see who made a change?
Keel records when each change happened and what changed; combined with your team's access it gives you the accountability n8n lacks.
Is the history secure?
Yes — stored workflow JSON is redacted, and your n8n API key never leaves your server.
See every change before it breaks a client.
Point Keel at your n8n estate this week. Free 14-day trial, no card, your keys never leave your infrastructure.