Organization-level credentials allow you store authentication details securely and reuse them across multiple projects and workflows. These credentials are typically used when your workflows need to call external APIs or connect to third-party services.
The credentials page lists every credential created in the organization or in any project under the organization. For each item, you can see:
Its name
The authentication method it uses
Whether it is available to all projects or restricted to specific ones
Organization-level credentials are centrally managed and can be shared across projects, helping you avoid duplicating secrets or maintaining multiple copies of the same integration.
Selecting Create Credential opens a dialog where you choose:
Credential type: You can pick from a variety of authentication methods (e.g., Basic Auth, Bearer Token, Header Auth, Query Auth, Custom Auth, BYOC/SIP providers, etc.).
Name: A label used for identifying the credential inside your workflows.
Access Scope: By default, credentials are available to every project in the organization. You can optionally limit them to a subset of projects.
Once created, the credential becomes available immediately to all workflows under any project that has permission to use it.
Credentials can be removed at any time using the Delete action.A credential can be deleted even if it is actively being used by a workflow. However, this will cause your workflow to become invalid until you re-enter another set of credentials where the deleted one was previously referenced.
Credentials appear as options inside nodes that make external requests (for example, HTTP Request nodes).When referenced in a workflow, the platform automatically injects the credential into the call using the correct authentication format - no manual handling of secrets is required.This keeps your workflows clean, secure, and consistent.
