Connecting Apps

This guide walks you through connecting a third-party app to your workflow. Credentials are saved for your organization and reused — you connect once, then configure fields on each node.

For managing all connections in one place, see Connections & Credentials.

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 card.
6. Click Connect and complete authentication:
   • OAuth apps (Google, Zoho, Lark, …) — authorize in the provider popup
   • API key / token apps — enter your key or token in the modal (same flow as Settings → Connections → Add credential)
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.

You do not paste API keys into the action field list when the app uses stored credentials. The Connect card handles that.

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 or save an API credential.
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, rotated API key):

1. Open the Action or Start node that uses the app, and click Update credentials / Connect again, or
2. Go to Settings → Connections, find the connection, and Update / Reconnect or Disconnect then add it again.

Multiple accounts

Connections are scoped to your organization. One connection per app (and auth type) is typically shared across all workflows in that org. Switch organizations in the dashboard to use a different set of credentials.

Testing your connection

1. Set the Start trigger to Manual.
2. Configure your Action node with test values (and ensure the app shows as connected).
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

Next steps

• Connections & Credentials — Add credential from Settings
• OAuth Authentication — for Google, Zoho, Lark, and similar apps
• API Keys — org keys, AI keys, and HTTP fallbacks
• MCP Server — run workflows from Claude Code, Cursor, and other AI clients