Create Credentials
Credentials are saved “login details” that some nodes need to access an external service.
Examples:
- An API key for a service
- A token (Bearer token)
- A username/password
- An OAuth connection (sign in with Google, etc.)
Why credentials matter
Section titled “Why credentials matter”- They keep sensitive information out of your workflow steps.
- You can reuse the same credential across multiple workflows.
- If you update a credential later, everything using it can keep working.
- When you share a workflow, you should never share your real secrets.
How to create a credential
Section titled “How to create a credential”From the Credentials section
Section titled “From the Credentials section”- Open the extension and go to the Credentials section.
- Click Create New Credential (or the “+” icon).
- Choose the type of credential (Token, Basic Auth, OAuth2, etc.).
- Fill in the required fields.
- Give your credential a descriptive name — for example: “Google Sheets – Marketing Team”.
- Hit Save. The system may test the connection automatically to ensure it works.
From a node
Section titled “From a node”- Open the extension and go to the Workflows section.
- Go to the node you want to use the credential for (In a Workflow).
- On the Credential field, click Create New.
- Choose the type of credential (Token, Basic Auth, OAuth2, etc.).
- Fill in the required fields.
- Give your credential a descriptive name — for example: “Google Sheets – Marketing Team”.
- Hit Save. The system may test the connection automatically to ensure it works.
Tips for naming, testing & organizing
Section titled “Tips for naming, testing & organizing”- Use names that make sense later: service + account + purpose.
- After saving, test it with a small workflow.
- If you have many credentials, keep them organized by team or by project.
- Don’t paste secrets directly into node fields if the node supports credentials.
Using credentials in nodes
Section titled “Using credentials in nodes”When you add or edit a node (for example: HTTP Request, Google Sheets, Email), you’ll often see a Credential field:
- Open the node’s configuration.
- In the “Credential” dropdown, select an existing credential.
- If the credential isn’t created yet, you can select Create New from within the node configuration.
- Once selected, the node will use the stored credential when the workflow runs.
Common credential types and what to check
Section titled “Common credential types and what to check”| Credential Type | What to configure | Things to check |
|---|---|---|
| Basic Auth (username + password) | Provide login credentials | Ensure password is correct and user has access |
| OAuth2 | Client ID, Client Secret, Redirect URL | Make sure tokens are valid and scopes are granted |
| API Token / Bearer | A single token/key | Confirm token hasn’t expired or been revoked |
| Generic / Custom Auth | Headers, query params, certificates | Ensure fields match the service requirements |
For service-specific details, see documentation such as Google Credentials or HTTP Request Credentials.