Skip to main content
Some workflow nodes call protected services — external APIs, tracking platforms, or Fail Fast itself. A credential stores the authentication those calls need. You create a credential once, and every workflow in your workspace can reuse it: update it in one place and all the nodes that use it pick up the change.
Credentials are managed from within workflow nodes. When you configure a node that needs authentication, you choose an existing credential or create a new one right there — there is no separate credentials screen to visit first.

​
Generic credential types

For nodes that call arbitrary services — most commonly the HTTP Request node — you pick the authentication method the target service expects:

​
Predefined service credentials

Nodes for specific services come with their own credential type, shaped to what that service requires. Predefined credentials exist for the Fail Fast, Truora, Monitor, RNDC, and Satrack nodes. When you configure one of these nodes, it asks for its matching credential — see the Node reference for what each node does.

​
Create a credential from a node

1

Open the node's configuration

On the workflow canvas, open the node that needs authentication.
2

Choose or create a credential

In the credential selector, pick an existing credential — or create a new one if none fits.
3

Fill in the authentication details

Enter what the credential type asks for, such as a token, a username and password, or a header value.
4

Save and continue

Save the credential. The node now uses it, and it becomes available to reuse in other workflows.

​
Connect an OAuth2 credential

OAuth2 credentials don’t take a fixed secret — they connect through an authorization flow with the service itself.
1

Create an OAuth2 API credential

From the node’s credential selector, create a new credential and choose the OAuth2 API type.
2

Complete the authorization flow

Follow the connection flow to authorize Fail Fast with the external service, signing in and granting access on the service’s side.
3

Use it in your nodes

Once connected, select the credential in any node that calls that service.
Reuse one credential per service across all your workflows rather than creating duplicates. When the service’s token or password changes, you update a single credential and every workflow keeps working.

​
Credentials vs API keys

Credentials authenticate your workflows to outside services. If instead an outside system needs to authenticate to Fail Fast, that’s handled with API keys.