Documentation FAQ and Reference

FlowKeyOps frequently asked questions

Quick answers about workflows, n8n, Git, secrets, environments, drift, billing, and support.

What is FlowKeyOps?

FlowKeyOps is a control plane for managing workflow automation as reviewed, versioned desired state across connected environments. It helps teams compare, promote, audit, and reconcile workflow changes.

Does FlowKeyOps replace n8n?

No. n8n runs your automations. FlowKeyOps adds operational controls around workflow versions, environments, deployments, credential references, drift, and audit history.

Which automation platforms are supported?

n8n is the initial platform focus. Check the current product and plan information for the supported integrations available to your workspace. Future integration availability is not guaranteed until it is published as supported.

Do I need Git?

FlowKeyOps uses a connected repository to support versioned desired state. Repository providers and connection methods depend on the current service configuration. Team members do not necessarily need to use Git commands for routine control-panel work.

What is an environment?

An environment is a connected automation destination, commonly Development, Staging, or Production. It provides the context for versions, deployments, credential references, and drift.

How many environments can I connect?

Your current subscription entitlement controls environment capacity. Review the plan summary in the control panel and the subscription in My account.

Can people edit workflows directly in the runtime?

They can when the runtime permits it, but a direct edit can create drift from the approved desired state. Review and reconcile the difference through your change process.

What is configuration drift?

Drift is a difference between the desired workflow version and the state currently observed in an environment. It needs investigation and a decision about which state should become authoritative.

Does FlowKeyOps reveal my secret values?

Normal control-panel workflows are designed to use safe credential metadata and references rather than reveal protected values. Never place secret values in workflow descriptions, screenshots, tickets, or chat.

Can the same credential be used in every environment?

It may be technically possible for some services, but separate least-privilege credentials reduce risk and simplify rotation. Use your organization’s security policy.

Where do I manage billing?

Sign in to flowkeyops.com and open My account. Orders, subscriptions, payment methods, and account details are managed there. Available actions depend on the subscription state and current terms.

What should I send to support?

Send the expected and actual result, safe workspace and operation identifiers, timestamps with time zone, reproduction steps, recent changes, and business impact. Never send passwords, tokens, private keys, card details, or complete credential payloads.