Configure Credentials for a Workflow

Configure Credentials for a Workflow

Some workflows require API keys or OAuth connections before they can run. This guide shows you how to configure them.

Credential Configuration Flow:

1. Browse → Find a workflow
2. Purchase → Buy the workflow
3. Configure → Add your API keys or connect OAuth
4. Ready → Run the workflow

Configuration options:

• Paste API key manually
• Connect via OAuth (one-click authorization)

Do I Always Need to Configure Credentials?

No. There are three ways credentials can be provided:

Credential Priority:

1. Builder Keys (Tier 1) — Highest priority; used whenever the builder has pre-configured that credential. Shown as locked — you cannot override it
2. Your Keys (Tier 2) — Used for every credential the builder left open, when you connect your own (BYOK)
3. Platform Keys (Tier 3) — Fallback when neither of the above are available

The system checks in order and uses the first available credential source.

Platform-provided keys are not available on every workflow. They are withdrawn onworkflows offering free trials, and on workflows whose Builder includes AI usage in theprice — in both cases nobody is funding that usage, so the workflow runs on its ownkeys or not at all.

If your workflow card shows "needs-config", it's waiting for your credentials.

How to Configure

Reuse a saved credential. An API key you saved for another workflow can be reused by its id. If the id is not one of your saved credentials, the answer is 404 "Saved credential not found in your Secure Vault". List your saved credentials and reuse one by its id.

Where to Find Your API Keys

Are My Credentials Secure?

Yes. Credentials are stored in the Secure Vault and only decrypted at execution time inside the secure sandbox. See: Credentials System Deep Dive.

Related

• What happens to my credentials?
• Credentials System Deep Dive
• Tutorial: Deploy & Run Your First Workflow