Connections
Connections are managed OAuth authorizations for third-party providers. Instead of copying API keys into every node, you connect an account once — Sign in with Google, Add to Slack, Allow Notion access — and every workflow in your workspace can use that connection.
Connections are team-scoped, like environment variables. Any member of your workspace can select a connected account from a node's settings.
| Provider | Covers | Plugins |
|---|---|---|
| Drive, Sheets, and other Google APIs | Google Drive, Google Drive Trigger, Google Sheets, Google Sheets Trigger | |
| Notion | Pages, databases, and blocks | Notion |
| Slack | Send messages and receive Events API triggers | Slack Send Message, Slack Trigger |
- Go to app.tensorify.io/connections (or open a node's settings and click Manage next to the account picker)
- Click Add Connection
- Pick a provider — Google, Notion, or Slack
- Choose the connection mode (see below) and click Connect
- Complete the provider's consent screen in the popup that opens
The connection appears in the list with its status. Click Test to verify the stored token is still valid, or the trash icon to remove it.
Tensorify's own OAuth app handles the flow — no setup required on your side. Click Connect, approve the consent screen, and you're done. Refresh tokens are stored and rotated by Tensorify automatically.
Managed mode uses Tensorify's registered OAuth applications. If your organization requires third-party apps to be reviewed or allowlisted before use, ask your workspace admin — or bring your own OAuth client with custom mode.
Use your own OAuth client credentials instead of Tensorify's:
- Google — create OAuth client credentials in the Google Cloud Console. Paste the provided redirect URL into the authorized redirect URI list and the authorized domain into the OAuth consent screen.
- Notion — create a public integration with OAuth enabled.
- Slack — create an app and add the redirect URL to its OAuth settings.
Custom mode shows the exact redirect URL to register; tokens are exchanged through your client but stored and refreshed by Tensorify the same way.
Plugins that support connections show an account picker in their settings (for example, Google Account on Google Drive nodes). Pick a connection — or click Manage to add one — and the node runs under that account.
The binding is stored on the node as an OAuth reference (_oauth_bindings), never as a raw token. If a connection is deleted, nodes that referenced it stop authenticating until you pick another one.
Removing a connection revokes nothing at the provider — it only deletes the stored token. To fully disconnect, also remove the app from the provider's settings (Google Account → Security → Third-party apps, Slack workspace apps, Notion connections).
| | Connections | Environment Variables |
|---|---|---|
| Best for | OAuth providers with refresh flows (Google, Slack, Notion) | Static API keys and tokens (STRIPE_SECRET_KEY, RESEND_API_KEY) |
| Setup | One-click consent screen | Paste a key |
| Refresh | Automatic | Manual rotation |
| Node UI | Account picker | Secret binding picker |
Some plugins support both paths — for example, Notion works with a managed/custom connection or a plain NOTION_TOKEN environment variable. Use a connection when the provider offers OAuth; use an env var when it only issues static keys.
- Environment Variables — static secrets for API-key-based services
- Google Sheets and Google Drive — the most common connection users
- Slack Trigger — Events API setup for connected Slack workspaces