Keys and Identifiers

Flowgear objects have stable keys that are separate from editable display names.

Common examples include Tenant, Account, Site, Environment, Workflow, Connection, API Key, folder, revision, and Workflow-instance keys. Console shows copy controls where an exact identifier is useful.

Use the correct value

Use a display name for people and a key for durable references, API calls, agent Tools, relationships, and audit correlation. Renaming an object does not intentionally change its key.

Discover the intended object in Console or through a supported API or tool. Scope is part of identity: the same-looking name can refer to different objects in different Sites or Environments.

FileHash identifies Workflow source content for revision and optimistic-concurrency purposes. It is not the Workflow key. An instance key identifies one activation and is not reusable as a design identity.

Protect identifiers appropriately

Most keys are identifiers rather than secrets, but they can reveal internal structure and should not be published without need. API-key primary and secondary values are credentials and must never be treated as ordinary IDs.

See Platform Object Model, Revision Management, and API Key.