Skip to main content
A credential is a connected account or API key. You connect a service once, then reuse that credential across every workflow and node that needs it.

Connect from a node

1

Open the node's Credentials tab

Click the node, then open the Credentials tab (K) in the config panel.
2

Pick or create a credential

Choose an existing account from Select credential…, or create one in place. The dropdown’s footer offers Connect new for OAuth services and Create new for API-key services.
3

Complete the connection

For OAuth, a provider sign-in window opens; approve access and the window closes. For API keys, paste your key into the form. Either way the new credential is selected on the node automatically.
Node credentials tab with the credential picker open

The Credentials tab on a node: pick an existing account or connect a new one.

OAuth services

Around 25 services (Google, Slack, GitHub, Notion, X, and more) connect with a browser consent flow: click Connect [Service] Account, sign in, approve the requested permissions, done. NoClick stores the resulting tokens and refreshes them automatically, so you don’t need to reconnect when they expire. The permissions NoClick asks for are the ones the service’s operations actually need, and each integration’s page lists the exact set. A connection keeps only what it was granted when you made it, so reconnect it if a step later fails on a permission. See Credential problems. A few providers ask for one extra detail before the sign-in window opens, like your Shopify store name or your Jira site.

API-key services

Other services use a key you paste in. The form lists exactly the fields the service needs, and most include a Get your API key here link that takes you to the provider page where the key is issued. Every field in a credential form carries a badge: Required fields show an amber badge until you fill them, Optional fields stay neutral. This is the same marking node config fields use.
WhatsApp is the exception to both patterns: it connects by scanning a QR code with your phone.

When a connection drops

Some connections can stop working from the provider’s side. An expired sign-in makes a credential unusable, and a live connection like WhatsApp can be dropped when the phone unlinks the device or the provider logs the session out. Either way, messages stop arriving and runs that use the credential fail. NoClick reports this in every place your credentials are read:
  • The credential picker labels the credential Disconnected and sorts it below the healthy ones.
  • The node’s Credentials tab explains what happened and what to do.
  • Asking an AI agent or the AI builder about the workflow reports the credential as attached but disconnected, rather than as working.
  • You get an email, unless you have turned that alert type off. See Email notifications.
A dropped WhatsApp connection also stops costing you the $0.99 monthly connection fee for the hours it is down, since it can neither receive nor send. Billing resumes once you re-scan.
Fix a dropped WhatsApp connection by re-scanning the QR code for the credential you already have, using the reconnect prompt on the node. Do not create a new WhatsApp credential. Each fresh scan adds another linked device on your phone, and WhatsApp can log all of them out at once. Reconnecting also avoids paying the $0.99 monthly connection fee a second time.

Services that run without a key

A few nodes can run on NoClick’s own keys, so connecting an account is optional. Their Credentials tab is headed API Credentials and carries a green Usage-based billing available - credentials optional marker, and while nothing is attached it reads Using NoClick’s usage-based billing (no credentials needed). Runs like that are metered against your NoClick credits. The picker stays available in the same place, so connect your own key whenever you would rather the provider billed you directly. Which nodes and operations this covers is listed under What costs credits.

Manage credentials in Settings

Settings → Credentials lists every credential you can use, grouped into Personal, Shared With Me, and (when you’re in an organization) Organization tabs. From here you can search, create credentials with New credential, share a credential, or delete one.
Credentials settings page with personal and shared tabs

Settings → Credentials: all your connected accounts in one place.

To rename a credential or replace its key, select it on a node and use the Edit credential button next to the picker. Existing secret values are never shown back; you re-enter them when updating. Removing NoClick from the provider’s side does not usually delete the credential here, so delete it yourself when you no longer need it. Pipedrive is the exception: if you uninstall the NoClick app in Pipedrive, the Pipedrive account you signed in with is deleted from your credentials for you, along with any sharing on it. Deleting works the other way around for some services too. When you delete a Klaviyo credential in NoClick, NoClick revokes the access it was granted, so the app stops showing as installed on your Klaviyo account. You do not have to remove it in Klaviyo as well.

Per-plan limits

Each plan caps how many credentials you can hold per service: Hitting the cap shows an upgrade prompt when you try to connect another account of the same type.

Next steps

Bring your own OAuth app

Use your own client ID and secret on supported providers.

Credentials and other people

How collaborators and teammates use your connections.