Connections

A connection is an authenticated link between Rapidfolio and an external service. Create and manage connections in the Rapidfolio dashboard.

What is a Connection?

A connection stores the credentials Rapidfolio needs to call an external service on your behalf. For OAuth integrations, Rapidfolio holds an access token obtained through a browser authorization flow. For API key integrations, Rapidfolio holds the key you paste in.

Connections are:

Workspace-scoped — all members of your workspace can use a connection in their procedures.
Environment-scoped — a sandbox connection and a live connection are separate. A sandbox Stripe connection will only be invoked during sandbox runs; a live Stripe connection only during live runs.
Reusable — any number of procedures can reference the same connection.

Creating a Connection

Go to Dashboard → Connections.
Click New Connection.
Select the integration you want to connect.
Follow the setup flow for that integration type (OAuth or API key — see below).
Give the connection a name (e.g., Stripe Production or Plaid Sandbox).
Select the environment: Sandbox or Live.
Click Save.

Once created, the connection appears in the connections list and is immediately available for use in procedure Tool Call nodes.

OAuth Integrations

For integrations that support OAuth (Slack, Linear, Jira, Xero, GoCardless), Rapidfolio initiates a browser-based authorization flow:

Click Connect on the integration setup screen.
You are redirected to the provider's authorization page (e.g., Slack's permission screen).
Grant the requested permissions.
You are redirected back to the Rapidfolio dashboard and the connection is saved.

Rapidfolio stores the resulting access token (and refresh token where applicable) securely using AES-256-GCM encryption. Token refresh is handled automatically.

API Key Integrations

For integrations that use API keys (Stripe, Plaid, Wise, Alloy, Onfido, etc.):

Generate an API key in your account at the provider's dashboard.
In Rapidfolio, paste the key into the API Key field on the connection setup screen.
Some integrations require additional fields (e.g., Plaid requires client_id and secret; Jira requires your instance URL).

Credentials are encrypted at rest. Rapidfolio never exposes the raw key after initial entry — the dashboard shows only a masked preview.

Using a Connection in a Procedure

When you add a Tool Call node to your procedure:

Open the node inspector (click the node on the canvas).
Select the Integration (e.g., Stripe).
Select the Action (e.g., create_payment_intent).
Select the Connection to use from the dropdown.

The procedure always uses the connection you selected. If you want to call the same integration with different credentials (e.g., different Stripe accounts for different regions), create two connections and configure two separate Tool Call nodes.

A single connection can be used by any number of procedures. If you update or rotate credentials, you only need to update the connection once — all procedures using it will automatically use the new credentials.

Private Connections

For on-premise or local services that cannot be reached over the internet, Rapidfolio provides a Private Connection type. Instead of storing credentials in the dashboard, you run the Connection SDK in your own infrastructure. The SDK polls Rapidfolio for invocations and executes them locally.

See Private Connection for setup details.

Custom API Connections

The Custom API integration lets you connect any REST API by providing an OpenAPI specification. Rapidfolio auto-generates actions from the spec and handles authentication (API key or Bearer token) through a standard connection.

See Custom API for details.