Credentials

Credentials store connection information in a secure and centralized way. Instead of placing passwords and tokens directly in nodes, you create a credential and reference it in flows.

Managing Credentials

1. In the side menu, click Credentials
2. The list displays all registered credentials

Image: Credentials screen with a list showing name, type, and creation date

Creating a Credential

1. Click + New Credential
2. Select the credential type
3. Fill in the type-specific fields
4. (Optional) Click Test Connection to verify
5. Click Save

Credential Types

HTTP / API

For connections with REST APIs.

Usage in the HTTP Request node: Select the credential and provide only the path:

Credential: "API Exemplo"
URL: /api/users  (the base URL is added automatically)

Pipeline Override — Enterprise

In QANode Enterprise CI/CD integration, specific credential fields can be overridden only for the current execution.

Example:

npx @qanode/cli run scenario \
  --scenario-id SCENARIO_ID \
  --credential api-main.token=$API_TOKEN \
  --wait

This pattern is useful for:

• ephemeral pipeline tokens
• temporary staging secrets
• transient environment endpoints

The saved credential value remains unchanged after the execution ends.

For details, see Per-execution Overrides.

PostgreSQL

MySQL

MariaDB

Same fields as MySQL.

Oracle

MongoDB

Example URIs:

mongodb://usuario:senha@host:27017/banco?authSource=admin
mongodb+srv://usuario:senha@cluster.mongodb.net/banco

SSH

Email

Credential for connecting to mailboxes via IMAP. Used by the Email Inbox node.

Password Mode:

For Gmail with password mode, you must use an App Password — not your regular account password. Generate App Password

OAuth2 Mode:

After filling in Client ID and Secret, click Connect OAuth (Browser) to authorize. A window will open for provider login and, once completed, Access Token and Refresh Token are filled automatically.

Gmail: register the OAuth Callback URI shown in the field as an "Authorized redirect URI" in the Google Cloud Console → Credentials → OAuth 2.0.

Outlook: register the URI as a "Redirect URI" in the Azure Portal → App registrations → Authentication.

Testing the Connection

Before using a credential, test the connection:

1. On the credential edit screen, click Test Connection
2. QANode will attempt to connect using the provided information
3. The result will be displayed: success or error with a detailed message

Image: Credential with a test connection button and success message

Using Credentials in Flows

In Database Nodes

In the PostgreSQL, MySQL, MariaDB, Oracle, or MongoDB node:

1. In the Credential field, select the credential
2. The connection fields are filled in automatically
3. Configure only the query/operation

In HTTP Request Nodes

1. In the Credential field, select the HTTP credential
2. The base URL and authentication are applied automatically
3. In the URL field, provide only the path

In SSH Nodes

1. In the Credential field, select the SSH credential
2. The connection details are applied automatically
3. Configure only the commands

Security

• Passwords and tokens are encrypted in the database
• Sensitive values are masked in the interface
• Credentials are accessible only to users with the appropriate permission
• The credential owner can edit it; others require admin permission

Tips

• Create credentials per environment — Production, Staging, Dev
• Always test the connection before using it in a flow
• Use descriptive names: "PostgreSQL Production" is better than "pg1"
• Prefer credentials over placing passwords directly in nodes
• When duplicating environments, create new credentials for each one