Create Credentials

Credentials allow your workflows to securely connect to external services and APIs. Properly managing credentials ensures your browser automations can integrate with these platforms while keeping sensitive information safe.

---

Why credentials matter

• They store tokens, usernames, passwords or API keys needed by nodes to access external services.
• They let you reuse the same “login” or connection across multiple workflows.
• They help you separate sensitive data from workflow logic—keeping it secure and maintainable.
• Before publishing or sharing workflows, remove or anonymize credentials so others don’t see your secrets.

---

How to create a credential

From the Credentials section

1. Open the extension and go to the Credentials section.
2. Click Create New Credential (or the “+” icon).
3. Choose the type of credential you want to create (for example: Token, Basic Auth, OAuth2, etc.).
4. Fill in the required fields (username, password, client ID, secret, etc.).
5. Give your credential a descriptive name — for example: “Google Sheets – Marketing Team”.
6. Hit Save. The system may test the connection automatically to ensure it works.

From a node

1. Open the extension and go to the Workflows section.
2. Go to the node you want to use the credential for (In a Workflow).
3. On the Credential field, click Create New.
4. Choose the type of credential you want to create (for example: Token, Basic Auth, OAuth2, etc.).
5. Fill in the required fields (username, password, client ID, secret, etc.).
6. Give your credential a descriptive name — for example: “Google Sheets – Marketing Team”.
7. Hit Save. The system may test the connection automatically to ensure it works.

---

Tips for naming, testing & organizing

• Use names that clearly describe what the credential is for: service + account + purpose.
• After saving a credential, test it manually by using it in a small workflow, then inspect the output.
• Group credentials by team or purpose if you manage many.
• Avoid embedding credentials directly into workflows—always reference them.
• When you share or publish workflows, ensure any credential fields have been swapped out or removed.

---

Using credentials in nodes

When you add or edit a node (for example an HTTP Request, Google Sheets, or Email node), 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

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.