Connecting Apps

Step-by-step guide to connecting apps in Action and Start nodes.

This guide walks you through connecting a third-party app to your workflow.

In an Action node

  1. Add an Action node to your workflow canvas.
  2. Click the node to open its configuration panel.
  3. Click Select App and search for the service you need.
  4. Choose an Action from the list (e.g. Slack → "Send Message").
  5. If you haven't connected this app before, you'll see a Connect button.
  6. Click Connect and follow the authentication flow (OAuth popup or API key entry).
  7. Once connected, fill in the action's fields:
    • Required fields are marked with a red asterisk
    • Use {{template}} syntax or the Variables button for dynamic values
  8. Save the workflow.

In a Start node (app trigger)

  1. Click the Start node.
  2. Set Trigger Type to App.
  3. Select the app and event (e.g. Gmail → "Email Received").
  4. Click Connect to authorize your account.
  5. Configure any trigger-specific options.
  6. Connect downstream nodes to process the event data.

During workflow execution

If a workflow runs and credentials are missing or expired, you'll see an Authentication Required dialog:

  1. The dialog names the app that needs access.
  2. Click Connect [App Name].
  3. Complete the OAuth flow or enter your API key.
  4. The workflow can then be re-run.

Reconnecting an app

If an integration stops working (expired token, revoked access):

  1. Open the Action or Start node that uses the app.
  2. Click Connect again to re-authorize.
  3. Alternatively, go to Settings and manage connected accounts.

Multiple accounts

Some apps (especially Google services) use a single OAuth connection per organization. The connected account is used for all workflows in that organization.

Testing your connection

  1. Set the Start trigger to Manual.
  2. Configure your Action node with test values.
  3. Click Run.
  4. Check the Execution Data tab on the Action node:
    • Success: you'll see the API response
    • Failure: the error message explains what went wrong (missing field, auth error, etc.)

Common issues

IssueSolution
"Authentication Required"Click Connect and complete OAuth
"Insufficient permissions"Re-authorize and grant all requested scopes
Action fields emptyCheck that upstream nodes produced the expected data shape
App not in the listThe app may not yet be available — use an HTTP Request node as a fallback

Next steps