Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.heybreez.ai/llms.txt

Use this file to discover all available pages before exploring further.

Project-level credentials allow you to store authentication details securely and use them inside workflows within this specific project. These credentials may be created directly at the project level or inherited from the organization.

​
Overview

The credentials page lists every credential available to the project. This includes:
  • Project-specific credentials created in this project
  • Organization-level credentials that have been granted access to this project
For each credential, you can see:
  • Its name
  • The authentication method it uses
  • Whether it is project-specific or inherited from the organization
Inherited credentials behave just like local ones when referenced inside workflows, but they must be edited or deleted at the organization level.

​
Creating a Credential

Selecting Create Credential opens a dialog where you choose:
  • Credential type: You can select from the same authentication methods available at the organization level (e.g., Basic Auth, Bearer Token, Header Auth, Query Auth, Custom Auth, BYOC/SIP providers, etc.).
  • Name: A label used to reference the credential inside your workflows.
Project-level credentials are always scoped to this project only. They cannot be shared with other projects. Once created, the credential is immediately available for use in workflow nodes that require authentication.

​
Editing Credentials

Clicking Edit opens the same interface used during creation, with your existing values prefilled. Notes:
  • Only project-specific credentials can be edited here.
  • Inherited credentials must be edited from the organization’s credential settings.
  • Some fields (such as secrets) may be hidden for security. Leaving them blank preserves the existing stored value.

​
Deleting Credentials

You can delete any project-specific credential using the Delete action. Inherited credentials cannot be deleted from the project. If you need to remove one:
  • Either update its access scope at the organization level to not include the project you want to exclude
  • Or delete the credential entirely from the organization

​
How Credentials Are Used in Workflows

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.