Integrations
Manage your organization's Slack workspaces and bots, Microsoft Teams bots, Discord, HubSpot and Zendesk installs, and connected knowledge sources and tools.
On this page
Settings → Integrations is the organization-wide view of everything Runbear is connected to. An agent's Chatbots tab deploys that agent to one place; this page manages the installs underneath those deployments, such as a Slack workspace or a branded Teams bot, which every agent in the organization shares.
Use it to add a Slack workspace or a custom bot before anyone deploys to it, to build a branded Microsoft Teams bot, or to remove an install from every agent at once.
The Integrations page#
Open Settings and select Integrations. The page has two parts:
- Connected lists the channels, knowledge sources and tools your organization has connected. Select a channel to open its page, described below. Some knowledge sources have a Manage button, and selecting a tool opens a dialog with its details and Disconnect.
- Available to connect lists what you can add, grouped into Channels, Knowledge and tool categories, with a search box. A channel your plan includes shows Connect; one it doesn't shows Upgrade. See channels by plan.
Slack#
The Slack page (Slack Workspaces) lists each connected workspace and the bots installed in it: the shared Runbear bot and any custom bots, with the agents each one serves.
Adding a workspace or a custom bot#
Click Add workspace. The Add a Slack workspace dialog offers two ways in:
- Add @Runbear installs the shared bot, which every agent in your organization can use.
- Create Custom Bot creates a bot with its own name and avatar. It needs a Slack configuration token. The form asks for a Bot Name, a Short Description, a Full Description, the Configuration Token and the Agent it serves.
If no workspace is connected yet, the page shows a Set up Slack card with the same two choices, the second labeled Create Slack Bot.
You can also create a custom bot from an agent's Chatbots tab; see Slack.
Managing a bot#
Open the menu at the end of a bot's row:
- Detail (custom bots) shows the bot's configuration.
- Reconnect reinstalls the bot in Slack, for example to grant permissions that a newer trigger needs.
- Disconnect (the shared Runbear bot) removes it from the workspace.
- Delete Bot (custom bots) deletes the Slack app.
Both Disconnect and Delete Bot ask you to confirm, and both permanently delete every connection attached to that bot, for all agents.
Microsoft Teams#
The Microsoft Teams page lists your organization's Teams bots under Microsoft Teams Bots: the shared Runbear bot's installs, each shown with its Workspace, and any branded bots with their Pre-connected Assistant(s).
Building a branded bot#
By default the bot appears as "Runbear" in Teams. A branded bot works the same way but carries your own name, icon and description. Start the wizard from either place:
- Click Create Bot on this page.
- In an agent's Chatbots tab, click the Microsoft Teams tile and choose the Create option named after your agent (Create Custom Bot).
The wizard has three steps.
- Step 1: Basic Information. Fill in the bot name, icons, and description. In Pre-Connected Assistants, select the agents the bot connects to, so people can use them immediately after installing it. A live preview shows your customizations. Click Continue.
- Step 2: Connect Microsoft. Sign in with a Microsoft account that can create apps in your Microsoft tenant and has at least the Contributor role on the Azure subscription that will host the bot.
- Step 3: Create your bot. Choose an existing Azure subscription, then
click Create bot. Runbear creates an app in your tenant, a resource group
named
runbear, and a free-tier Azure Bot connected to Microsoft Teams. This takes about 30 seconds.
When the bot is ready, click Download zip to download the installation file.
Installing a branded bot#
Unzip the downloaded file. Inside are the bot installation file and a detailed installation guide. Follow the guide to install the bot in your Teams organization.
Removing a Teams bot or install#
- To delete a branded bot, click its trash icon (Delete Bot). Runbear asks you to sign in with Microsoft, because it needs your permission to remove the app registration from your tenant and the Azure Bot from your subscription, then confirm with Delete permanently. The bot is removed from every Teams organization it was installed in, and all Runbear connections linked to it are deleted.
- To remove the shared Runbear bot from one Teams workspace, click Disconnect Workspace on its row and confirm. Every connection attached to it is deleted.
Discord, HubSpot and Zendesk#
Each of these channels has a Channel Configuration page showing its Channel Type and Status.
- Zendesk can be removed from here: click Disconnect and confirm. This permanently removes the channel and every connection attached to it. If the status reads Reconnect required, Reauthorize with Zendesk appears here for organizations in the Zendesk OAuth rollout.
- Discord and HubSpot can't be disconnected from Runbear's side. Delete each agent's connection from its Chatbots tab, then remove Runbear in the other product: kick the bot from your Discord server, or uninstall Runbear under Settings > Integrations > Connected Apps in HubSpot.
Removing one agent's deployment only#
Everything above affects every agent. To stop one agent from answering in one place, delete that connection from the agent's Chatbots tab instead; see Deleting a connection.