Prerequisite: Third-party connectors are available only on the Sana Enterprise tier, with one exception: the Workday connector is included for both Sana Core and Sana Enterprise.

Introduction

Connect Cisco Webex to Sana to send messages, create rooms, and read conversations. Stay on top of your team communication directly from Sana.

In summary, the connector has the following key characteristics:

Category: Communication
Connector type: Real-time
Auth type: OAuth
Hosting type: Managed

Capabilities

This connector is able to do the following:

Capability

List rooms

List messages

Send messages

Create rooms

Tools

While the capabilities above describe what the connector can do at a high level, the underlying tools show exactly which operations the agent can use when you ask Sana about Webex. In practice, the agent may call one or more tools to achieve a single capability.

Tool

Create message

Create room

List messages

Note: This article lists the connector's full set of tools. Your workspace owner can disable individual tools for your workspace, so some of those listed here may not be available to your agents. If a tool you expected is missing, reach out to your workspace owner.

Triggers

While tools are the actions an agent takes on your behalf, triggers are the events that can start an agent automatically. When you build an agent, you can choose one of the triggers below as its starting point. For example, having the agent run every time something new happens in Webex.

Trigger

New Message (Instant)

Scope and permissions

This connector uses OAuth. When you connect your account, you will need to sign into your account and grant the required permissions:

Scope	Purpose
spark:all	Full access to your Webex account resources
spark-admin:people_read	Read organisation users and their basic details
spark-admin:people_write	Update organisation user details and settings
spark:devices_read	Read information about Webex devices in your organisation
spark:devices_write	Manage and update Webex device settings

Set up instructions

Prerequisites:

You are a Sana Enterprise user – all third-party connectors except the Workday connector are available only for users on the Sana Enterprise tier.
Your Sana workspace owner has enabled this connector – if the workspace owner has disabled the connector it won't appear in the list of available connectors.

Step 1: Go to the connectors page in Sana

In Sana, click on your profile icon and name in the bottom left corner and select Connectors.

Step 2: Find Webex in the list of available connectors

Scroll to the Available connectors section and locate Webex.

Note: If you can't find a connector in this list, it means one of the following:

You've already connected it — check the ”Active connectors” section at the top of the connectors page, or
Your workspace owner has disabled this connector for your workspace — reach out to them for more information or to request that it be enabled.

Step 3: Hover the connector card and click the connect button

Hover the Webex card and click the Connect button.

Tip: If you click the card itself instead of the Connect button, you'll open a connector detail page with more information about its capabilities.

Step 4: Initialize the Pipedream connection

When clicking Connect in the previous step, a pop-up will appear powered by Pipedream. Click the Continue button in the pop-up to initialize the set up.

Note: Sana uses Pipedream to connect your account. Pipedream is a Workday product, trusted by millions of people to keep their data secure.

Step 5: Sign in to Webex and approve the requested scopes

You'll be redirected to Webex to go through their OAuth flow. Sign in and approve the scopes Sana needs to operate the connector.

Step 6: Complete the set up

You've successfully connected your Webex account. Click Continue to complete the setup and start using the connector.

Known limitations

Sender attribution: Messages sent through the connector appear as "Pipedream" rather than the signed-in user. The signed-in user is referenced in the message metadata, but it won't look like a normal user sent it.