Tokens and keys for integrations
Store the API keys your graphs need per service, and reuse them across graphs.
Settings → Tokens & keys holds the credentials for the remote APIs your graphs call. Add one per service — or several for the same service when you have separate environments — and reference them from nodes rather than pasting values into graphs.
- Integration nodes describe their auth scheme in the inspector's authorization section: API key or custom header, bearer token, OAuth 2.0, or key pair / mutual TLS.
- Name keys after the environment as well as the service, so a staging key is never mistaken for production.
- Rotating a key in one place updates every graph that references it.
- For OAuth services, press Connect on the key's row to authorize instead of pasting a token.
Related
- Connect an integration with OAuthCredentials & modelsAuthorize a service from Tokens & keys so its credential refreshes itself, instead of pasting a token.
- Reference secrets instead of inlining themCredentials & modelsenv: and ${ENV:VAR} references resolve at run time, so no key is ever written into a graph or preset.
- Browse the node catalogNodes & catalogFind a node type by category, subcategory, owner, or date, and read what it needs before you place it.
- Configure a node in the inspectorGraph editorThe inspector holds a selected node's identity, configuration, connection and authorization settings, and its run defaults.
More in Credentials & models · Search all help