Create a credential

A credential is a saved key, token or sign-in that lets a node act in another service: an API key for OpenAI, a Slack bot token, a Google sign-in. You create it once, then pick it in any node. When you share or export a workflow, your credentials stay behind.

Looking for one app? — 

Each service has its own page with the exact steps, the permissions to grant and the common errors: Slack, Notion, Google, OpenAI and more.

All connections →

From the Credentials page

Open Credentials in the sidebar and click Add Credential. Everything else happens in the New Credential form: hover or tap a step to find it on the screen. In the browser side panel (or any narrow window) the form comes in two steps: first a list of apps, where tapping one moves on (or Continue keeps Simple Credential), then the rest of the form.

123456

1. 1 Step 1:Pick the app or service Under Integration App / Service, pick the app the credential is for, for example Slack or Gmail. For an AI provider or any other API, pick Simple Credential.
2. 2 Step 2:Name it Give it a Name you'll recognise in nodes (service, account and purpose, for example Slack – marketing bot) and, if you like, a Description.
3. 3 Step 3:Check the auth type For an app it is set for you. For a simple credential, choose it: see Auth types below.
4. 4 Step 4:Fill its fields The fields follow the auth type: here Username and Password. For OAuth2 (Google, Microsoft 365), click Check connection and sign in.
5. 5 Step 5:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account). Without an account it is saved locally in this browser, as here.
6. 6 Step 6:Click Create Credential Check: the new credential is listed on the Credentials page, ready to pick in nodes.

Numbered areas in the screenshot: 1. Pick the app or service; 2. Name it so you can find it in nodes; 3. Auth type decides which fields you fill; 4. The fields of the chosen auth type (here Username and Password); 5. Where the secret is stored; 6. Create Credential.

From a node

In a node’s Credential (or Authentication) field, open the list and click + Add Credential. The same form opens. When you save, the new credential is in the list, ready to pick.

Auth types

Auth Type	Fields	Use it for
Bearer Token	Bearer Token	Most app tokens and API keys (Slack, Notion, GitHub…). Paste only the token: AWFlow adds Bearer.
Basic Auth	Username, Password	Services that take two values, such as Trello (API key + token) or Pushover.
JWT	JWT	A value sent exactly as typed. Use it for AI provider API keys in workflow nodes.
OAuth2	Client ID, Client Secret (optional)	Google (Gmail, Drive, Sheets, Calendar) and Microsoft 365, with your own OAuth client.

Client Secret — 

Microsoft 365 is a public client: it has no secret, so the field is hidden and any old value is cleared when you save. A Google Web application client needs its secret; a Google Desktop app client has none.

Where credentials are stored

• Local (this browser only): encrypted in this browser. The key sits on the same device, which guards against casual inspection. Turn on the local secret vault to lock local credentials with a passphrase.
• Cloud (synced to your account): stored encrypted on your AWFlow account, so you can use them on your other devices.

If you use AWFlow without an account, credentials are always local. See Privacy & your data.

Tips

• Create one credential per account and purpose, and reuse it across workflows. Updating it updates every workflow that uses it.
• Give a token only the permissions your workflow needs. Each connection page lists them per operation.
• Never paste a secret into a node’s normal fields: those travel with the workflow when you share it.

Next steps

All connectionsStep-by-step pages per service.

Edit a credential