Skip to main content
Version: v1.7.5

Data Connectors

Overview​

Data Connectors lets you connect your own account on an external service to Enterprise h2oGPTe. After you connect an account, agents can use it to read data you have access to and act on your behalf. For example, an agent can post to Slack as you instead of through a shared bot. A banner on the page confirms that Enterprise h2oGPTe stores your credentials securely and that you can revoke them at any time.

note

Data Connectors and Connectors work together but aren't the same thing. Connectors define how Enterprise h2oGPTe imports documents into a collection. Data Connectors is where you link your own account, so Enterprise h2oGPTe can act as you. For example, it can import documents you access with the SharePoint or Confluence connector, or let an agent post to Slack as you.

Data Connectors is available only when your administrator has configured it. If no cards appear, the page shows: "No connectors are currently configured. Please contact your administrator to enable data connectors."

The Connectors option itself appears only if your administrator has turned on data connectors and your role has the Link connectors permission. If you don't see it in the account menu, ask your administrator to grant it. See Roles and permissions reference.

Open the Data Connectors page​

To open the page:

  1. In Enterprise h2oGPTe, click Account Circle.
  2. Select Connectors.

Each supported service appears as its own card, reading "No accounts connected" until you connect one. Which cards appear depends on what your administrator has configured. This guide uses Slack as the example throughout.

Connect an account​

To connect an account:

  1. On the card for the service you want to connect, click Connect.
  2. Sign in to the service.
  3. Approve the consent screen.

Enterprise h2oGPTe returns you to the Data Connectors page. The card now shows your connected account with an Active status pill.

The consent screen shows only the permissions your administrator configured for that service.

If a connection stops working, its status pill can change to Expired, and the card shows Reconnect in place of Connect. A connection can also stay Active after its token stops working, for example a Slack connection that includes a workspace bot token, or any connection when your deployment stores credentials in SecureStore. In that case Reconnect doesn't appear. If actions start failing while the pill still reads Active, click Disconnect, then Connect again.

View granted permissions​

If Enterprise h2oGPTe recorded the granted scopes for a connection, its card also shows View Scope. Click it to open the Slack Permissions dialog, which shows the scopes you granted. Bot scopes aren't shown.

Reconnect an account​

Click Reconnect on an expired connection. Reconnecting revokes the expired token first, then starts a new consent flow. If revoking fails, Enterprise h2oGPTe shows Revocation Failed and doesn't start a new consent flow. Try again.

Disconnect an account​

To disconnect an account:

  1. On the account you want to remove, click Disconnect.
  2. In the Confirm Disconnection dialog, click Disconnect to confirm.

Disconnecting deletes the copy Enterprise h2oGPTe stored and, for services that support it, revokes your personal token at the service. Anything that depended on that account stops working: an agent can no longer act as you, and a connector can no longer import documents with your access. You can reconnect at any time.

If you connected Slack, see Slack for what disconnecting does and doesn't revoke.

Slack​

The Slack card reads: "Connect your Slack workspace so the assistant can post as you." Connecting authorizes your own Slack account. If your administrator configured bot scopes, the same authorization also returns a workspace-level bot token that every connected user in the workspace shares. Depending on what your administrator configured, the connection can hold either or both of the following tokens:

BehaviorPersonal tokenWorkspace bot token
The agent acts asYouThe Slack app's bot user
Can reachEvery conversation the granted scopes cover; message search works when your administrator grants search:readOnly channels you invite the bot to; no search

Your administrator can configure user scopes, bot scopes, or both. When a connection holds both, the agent uses your personal token by default: it posts as your Slack account, not as a bot.

important

Disconnecting Slack revokes only your personal token. It doesn't revoke the workspace bot token, because everyone in your workspace who has connected shares that token. Revoking it would break the bot for everyone. The bot token stays valid at Slack until an administrator removes the Slack app from the workspace.

After you connect Slack, add the built-in Slack Integration tool to an agent. See Browsing and adding predefined tools.

Feedback