Connect an app

A connection is one of your accounts in another app: a Slack workspace, a Notion workspace, a Shopify store. You connect it once, on the Integrations page under Build in the left menu. Workflows can then use its actions as App action blocks, and agents can call them as tools. 18 apps connect with a token, a key or a webhook URL; six apps that sign in with OAuth are listed as Needs setup and can't be connected yet.

Before you start

• An account in the app, and the right to create a token, a key or a webhook URL in it. Each field on the form says where to find it and which permissions to give it.
• Nothing for Web page reader: it's built in. Choose Connect on it once so workflows can use it (an account has one). Agents' Read web pages tool doesn't need it.

Steps

1. 1

   Open Integrations

   Click Integrations under Build in the left menu. Search with Search apps and actions, or pick a category such as Messaging, Productivity or CRM and support.

2. 2

   Pick the app

   Choose Connect on its card. The app's page has a Connect form and lists the Actions it offers.

3. 3

   Name the connection

   Name is how the connection is listed in workflows and agents, for example "Slack for support". It starts as the app's name; up to 80 characters, different for each connection of the same app.

4. 4

   Paste the credentials

   Fill in the app's fields: a bot token, an API key, a webhook URL or a service account key. The help under each field says where to create it and which scopes it needs. Slack's bot token, for example, needs chat:write, chat:write.public and channels:read.

5. 5

   Save & test

   Choose Save & test. SentientOne checks the details with the app's cheapest read-only call (nothing is posted) and names the account it reached: "Connected to …". If the app refuses them, the connection is still saved, with the app's answer, so you can fix it.

6. 6

   Try an action (optional)

   Under Actions, choose Try it, fill in the action's fields and choose Run action. It really runs: whatever it sends, the app gets. The answer shows Worked or Didn't work with the output.

Manage a connection

• Test checks it again. The Integrations page shows when each connection was last checked.
• Rename changes its name. Update credentials replaces only the fields you fill in; a blank field keeps its saved value. Choose Test afterwards: the connection shows Not tested until you do.
• Delete removes it after you confirm. Agents lose its actions, and workflow blocks that use it stop working until you choose another connection. Your account in the app isn't changed.
• One app can have several connections, for example two Slack workspaces: use Connect another account on the app's page. An account can have up to 100 connections.
• A connection's status is Connected, Not working (the app refused it at the last test or call) or Not tested.

What happens to your credentials

• They're encrypted with AES-256-GCM before they're stored, like your LLM keys, and never shown again.
• They're opened only for the call that needs them, and never logged, cached or written to a trace.
• Calls go only to public internet addresses. Private and local addresses are refused, and redirects aren't followed (Web page reader follows up to 3, checking each one).
• Each request to an app has 15 seconds, and an answer is cut to 16,000 characters of JSON: long lists lose items and long text is shortened, marked truncated.

Apps listed as Needs setup

Gmail, Outlook, Google Calendar, Google Drive, OneDrive and SharePoint, and Salesforce sign in with OAuth. Their cards say Needs setup and open Details instead of a connect form: they can't be connected yet, and they offer no actions. Until they can, a workflow can reach an app that issues API tokens with an HTTP request block. See Workflow blocks.

If something goes wrong