Credentials

Credentials are encrypted API keys and tokens stored in your account. They let nodes authenticate with external services without hardcoding secrets into workflows.

Why credentials are separate

Reusability - one credential works across all workflows that need it
Security - encrypted at rest, never exposed in workflow exports or marketplace clones
Rotation - update a key once, all workflows pick up the change

Supported platforms

Platform	Auth type	Used by
OpenRouter	API key	AI nodes
Birdeye	API key	Birdeye node
Helius	API key	Helius node
CoinGecko	API key	CoinGecko node
Dune	API key	Dune node
DefiTheOdds	API key	DefiTheOdds node
Telegram	Bot token	Telegram node
Discord	Webhook URL	Discord node
Jupiter	API key + wallet	API key required for all ops except transfer. Wallet needed for swap/transfer.

Phoenix Flight is intentionally absent. Phoenix uses a one-time per-wallet invite activation, not a persistent credential. Activate via the inline panel inside any Phoenix node's config dialog. See the Phoenix node page and Per-Integration Guide for details.

Encryption

All credential values are encrypted server-side before storage. When you view a credential, values are masked (only last 4 characters shown). The decrypted key is only accessed by the execution engine at runtime.

Scope

Credentials are per-account. Any workflow you own can use any credential you've added. Credentials are never included in marketplace clones - buyers must supply their own.

Connections page layout

Connections are grouped by platform category:

AI Models - OpenRouter
Blockchain - Birdeye, Helius, Jupiter, Dune, DefiTheOdds, CoinGecko
Messaging - Telegram, Discord

Expand a platform to add, edit, or delete keys. A connected badge shows when at least one key exists for that platform.

Next steps

Adding Credentials - step-by-step CRUD
Per-Integration Guide - where to get each key