Connections

A connection gives QuickFlo permission to act in another system. Create it once, name it clearly, and reuse it wherever a workflow needs the same account.

Open Connections to search by name, filter by type, change the view, or create a connection.

Create a connection

Select New Connection and enter a name. Names can contain letters, numbers, dashes, and underscores.

Choose one of the two setup paths:

• Connections — credentials you enter directly, such as an API key, basic auth, SMTP account, database, or service account.
• OAuth — providers that ask you to authorize QuickFlo in their own sign-in flow.

The selected type determines which fields appear. Complete only the fields the provider requires, then create or authorize the connection.

Tip

Name the account and purpose, not just the provider: salesforce-production, slack-alerts, or billing-api-readonly is more useful than salesforce-2.

Use it in a workflow

Most integration steps include a connection field. Select the connection there; QuickFlo passes the credentials without placing them in your workflow definition.

For a generic HTTP step, reference the connection by name when the field supports templates:

{{ $connections.billing-api-readonly }}

Connection names become part of the workflow’s contract. If you rename one, update the workflows and packages that refer to it.

Choose the right type

Prefer the provider-specific type when one exists. It can handle the provider’s authorization shape and renewal behavior for you.

Use a general type when the provider does not need a dedicated integration:

Need	Connection type
Header or query credential	API Key
Username and password over HTTP	Basic Auth
OAuth provider without a first-class type	Custom OAuth
Outbound email	SMTP
SQL or document database	Database
Cloud workload identity	AWS Credentials or GCP Service Account
Secure file transfer	SFTP

Use Custom only when the workflow genuinely needs a credential shape that the standard types cannot represent.

OAuth connections

OAuth keeps the provider’s sign-in and consent flow outside QuickFlo. After authorization, the connection page shows the account and connection type you can reuse.

Some providers require an application to be created first. For Salesforce, follow Salesforce External Client App Setup.

If an OAuth-backed workflow starts returning authorization errors, open the connection and reconnect it before changing workflow logic.

Separate environments

Use separate connections for accounts that must never be mixed, such as production and sandbox.

Environments can redirect a workflow from one connection to another without changing each step. A workflow can refer to one logical connection while the active environment chooses the real account. See Environments.

Maintain connections

The row menu is the fastest place to edit or remove a connection. Before changing one that is already in use:

1. Identify the workflows that depend on it.
2. Confirm whether the change affects every environment.
3. Test one small request.
4. Check Executions and Platform Logs for authorization failures.

For scheduled credential rotation or inventory workflows, see Managing QuickFlo from a workflow.

Security model

Connections are organization resources. People need the matching permission to create, edit, or use them.

QuickFlo does not show stored secrets in execution output. Even so, give each connection only the provider permissions its workflows need, and avoid sharing one broad administrator account across unrelated automations.