Skip to main content

​
Before you create a connection

Pick the app you want to use in a workflow first. Good first connection choices are usually apps where you can verify the result quickly, such as:
  • Slack
  • Google Sheets
  • Notion
  • Gmail
These are easier to validate because the outcome of a workflow step is visible right away.

​
Step 1: Open Connections

Go to Connections in Workflow Machine. This is the central place for managing the app accounts your workflows rely on.

​
Step 2: Choose the app

Create a new connection for the app you want to use. Different apps may ask for different authentication details. In practice, this usually means one of:
  • signing in through OAuth
  • entering an API key or token
  • completing an app-specific connection flow
Use the account that matches the workflow you actually intend to run. Choosing the wrong account is one of the easiest ways to create confusion later.

​
Step 3: Complete authentication

Finish the required sign-in or credential entry flow, then save the connection. After saving, confirm that the connection appears in your connections. At that point it should be available for supported workflow steps that use that app.

​
Step 4: Check the connection details

Before you move on, confirm:
  • the connection is for the correct app
  • the account is the one you intended to use
  • any required permissions were granted
If the app supports multiple environments, teams, or workspaces, this check is especially important.

​
Step 5: Use the connection in a workflow

Open a workflow step that uses the connected app and select the connection from the available options. At this stage, you do not need to build a full production workflow. A simple test step is enough to verify that the connection works correctly.

​
Should you make it the default?

If you expect to use the same account often for that app, setting it up as the default connection can make future workflow setup easier. Be more careful if:
  • several people use different accounts for the same app
  • you have both test and production accounts
  • some workflows must stay isolated from others
In those cases, explicit connection selection is usually safer than relying on defaults.

​
Common mistakes when creating a connection

The most common early issues are:
  • authenticating with the wrong account
  • missing a required permission during sign-in
  • assuming the connection is active without testing it in a real step
  • creating duplicate connections when an existing one would have worked
A quick test run after connection setup is the best way to catch these problems early. After you create a connection, use it in one simple workflow and run a test. That confirms not just that the connection exists, but that it works for the action you actually care about.