This page records what changed in FlowKeyOps and when. FlowKeyOps has three components. Only one of them — the environment agent — runs in your own infrastructure and is installed by you. The control plane and the Git service are operated by FlowKeyOps and update without any action on your part.
Which version am I running?
Open Environments in the control panel. Each connected agent reports its own version, together with whether a newer one is available. If an agent shows no version, it is running a build that predates version reporting and should be updated.
The control plane and Git service do not have customer-visible version numbers. Their changes are listed below by date.
Environment agent
The agent runs beside your n8n instance, inside your own network. It makes only outbound connections and opens no inbound port. Because it runs on your infrastructure, FlowKeyOps cannot update it for you — you choose when to upgrade.
0.16.0 — current release
Released 20 August 2026
- Restore an approved workflow. An approved workflow version can now be written back into your n8n from the control panel, so an unwanted change can be undone.
- A restore never switches a workflow on or off. Restoring content leaves the active state exactly as it was. This is deliberate and is protected by a test.
- Failure messages are cleaned of internal detail before they leave your network.
0.15.0
Released 20 August 2026
- Credential values are converted to the exact types n8n expects, so a credential that previously failed to save now succeeds.
- A credential rejected by n8n now reports the reason instead of being retried without effect.
- Fixed a fault where an already-connected agent could refuse to start after a restart.
0.13.0 – 0.14.0
Released 19–20 August 2026
- Credential synchronisation. The agent can write a credential from your vault into your n8n — the first operation that changes anything in your instance.
- Credentials are encrypted so that only your own environment can open them.
- Fixed an ordering fault during first-time connection.
Note on 0.13.3. This build reports its version as dev rather than a number, so the control panel cannot tell whether it needs updating. If Environments shows dev, upgrade to the current release.
0.10.0 – 0.12.0
Released 17 August 2026
- The agent reports which credentials your n8n actually holds, with their real types — names and types only, never values.
- Credential definitions are read in a single request instead of one at a time.
- Credential creation and modification dates are reported.
0.1.0 – 0.6.0 — first releases
Released 15–16 August 2026
- The agent connects your n8n instance to FlowKeyOps.
- Installs as a standalone service or alongside an existing n8n deployment.
- Exports workflows so an approved version can be kept.
- Applies settings managed centrally from the control panel.
Control plane
The control plane is the service behind the control panel. It is operated by FlowKeyOps and updates continuously; no action is required from you.
20–21 August 2026
- Restore and accept. A workflow difference can now be resolved in either direction — restore the approved version into n8n, or accept the running version as the new approved one.
- Editing a credential now loads its non-secret values into the form instead of clearing them.
- Differences are shown side by side, and a resolved difference correctly clears.
19–20 August 2026
- Each installer is provided as a single downloadable file.
- Fixed installers that referenced an agent image that could not be downloaded.
- Activity history no longer fills with routine page views, and shows what actually changed in each update.
- Fixed a fault where the update notice could suggest moving to an older version.
17–18 August 2026
- Credential forms now show exactly the fields n8n itself shows, using n8n’s own labels and hints.
- FlowKeyOps reports credentials a workflow needs but your n8n does not have — a common cause of a failing workflow.
- Credentials that are stored but no longer used by any workflow are reported.
16 August 2026
- Environments. Create and manage multiple named environments, such as Development and Production.
- Ready-to-run installers for Docker, Kubernetes, Docker Compose, and Linux systemd.
- Credentials are stored so that only your own environment can read them, and a credential can never cross between environments.
15 August 2026
- Workflow visibility and drift detection. See the workflows in your n8n from the control panel, keep an approved version of each, and be told where the running workflow no longer matches it.
- Refresh the view on demand, subject to your plan.
11–14 August 2026
- Subscriptions purchased on flowkeyops.com take effect automatically.
- Audit history. A permanent, tamper-evident record of account activity that can be viewed and exported.
- When a subscription ends, a complete encrypted copy of your data is produced and verified before anything is removed, and removal happens only at the end of the period already paid for.
Git service
The Git service keeps the approved version of each workflow in a private repository dedicated to your workspace. It is operated by FlowKeyOps and updates without action from you. The commit recording each change is itself the audit record.
20 August 2026
- An approved workflow version can be retrieved so it can be restored into your n8n.
- Change history records how many files and lines each update touched.
- A workflow with no approved version yet is reported plainly rather than as a failure.
17 August 2026
- Credential detection matches credentials by their true identity, so renaming one no longer looks like a new credential.
- Steps that are not connected to anything are ignored, which removes incorrect reports of missing credentials.
- Reports exactly which steps are disconnected in each workflow.
15–16 August 2026
- Each workspace receives a private store for approved workflow versions.
- Approved versions are saved and can be read back, each identified by a unique reference.
- Credential values are encrypted so that only your own environment can open them.
What FlowKeyOps does not detect
Two limits apply to every release and are properties of how automation platforms work, not settings that can be changed.
- Changes are detected by checking, not by notification. n8n does not notify FlowKeyOps when a workflow is edited, so FlowKeyOps checks on a schedule set by your plan. A change made directly in n8n is detected at the next check, not immediately.
- Differences in credential values cannot be detected. No automation platform allows a stored credential value to be read back. FlowKeyOps can write a credential from your vault into n8n, but it cannot compare the two. Where a credential is synchronised, the value in your vault is written to n8n.