Connecting accounts

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

​

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, along with how to obtain them, 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.

​

What happens when you save

NoClick checks a key you type in before it stores it, so a bad paste is caught at the form rather than at the first run. First it tidies what you entered: surrounding whitespace is dropped, and a field that holds a key or token rejects a web address or leftover placeholder text. Some services read more out of a paste than you typed, so pasting a full browser URL into a server field can fill in the rest of the form for you. Anything it cannot make sense of is reported under the field it belongs to, and clears as you edit. Then it asks the provider, using the same read-only call that proves a connection works elsewhere in NoClick. One of three things follows: The check runs wherever a key is entered: a node’s Credentials tab, Settings → Credentials, the Setup tab, and a link someone sent you to connect an account for their workflow.

​

When a connection drops

Some connections can stop working from the provider’s side. An expired sign-in makes a credential unusable, a WhatsApp connection can be dropped when the phone unlinks the device or the provider logs the session out, and a Discord Bot Install connection stops working once someone removes NoClick’s bot from the server. 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 how to repair that connection: re-scan the QR code for a WhatsApp credential, or add the bot back to the server for a Discord one.
• 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 connection is marked Disconnected only when the provider says it is gone. When NoClick cannot reach the provider to ask, the credential keeps reading as connected instead of being flagged on a guess. 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. The node offers a QR code on its own only when you have no WhatsApp connection to pick, or when the one attached to it has dropped and the scan will reconnect it. When a working connection is already there, the Credentials tab shows a Connect a different WhatsApp number button instead, so nothing invites a scan you did not mean to make. A reconnecting scan keeps the triggers registered on that credential, so incoming messages start arriving again without any change to the workflow.

​

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. The shield on a row opens that connection’s Tool permissions, where you decide which of its actions run freely and which wait for your approval. See Tool permissions. 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