Cisco Webex Teams Spoke › Integration Hub spokes › Build integrations › Integration Hub › Workflow Data Fabric

Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Set up the Cisco Webex Teams spoke

Integrate the ServiceNow instance and Cisco Webex Teams by creating a custom OAuth application in Cisco Webex Teams or using the custom Cisco Webex Credentials to authenticate ServiceNow requests.

Before you begin

Request an Integration Hub subscription.
Activate the Cisco Webex Teams spoke.
Role required: admin.

You can choose to use either OAuth 2.0 or the custom credentials, Cisco Webex Credentials, for authentication.

Register Cisco Webex Teams as an OAuth provider

Use the information generated during the Cisco Webex Teams application configuration to register Cisco Webex Teams as an OAuth provider and allow the ServiceNow instance to request OAuth 2.0 tokens.

Before you begin

Role required: admin.

Procedure

Navigate to All > System OAuth > Application Registry.
Click New.

The system displays this message: What kind of OAuth application?.
Select Connect to a third party OAuth Provider.
On the form, fill these values.

Right-click the form header, and click Save.

What to do next

Ensure that the OAuth entity profile has these permissions:

Image omitted: cisco-teams-entity-profiles.png
OAuth entity profile scopes.

Create a OAuth credential record for the Cisco Webex Teams Spoke

Create a credential record for the Cisco Webex Teams account. The Cisco Webex Teams Spoke connection and credential alias uses these credentials to authorize actions.

Before you begin

Role required: admin.

Procedure

Navigate to All > IntegrationHub > Connections & Credentials > Credentials.
Click New.

The system displays this message: What type of Credentials would you like to create?
Select OAuth 2.0 Credentials.
On the form, fill these values.

Field	Description
Name	Name to uniquely identify the record. For example, enter: `Cisco Webex Teams OAuth`
Client ID	Client ID created during the Cisco Webex Teams application configuration.
Client Secret	Client Secret created during the Cisco Webex Teams application configuration.
Authorization URL	OAuth authorization code endpoint. Enter: `https://webexapis.com/v1/authorize`
Token URL	OAuth server token endpoint. Enter: `https://webexapis.com/v1/access_token`
Token Revocation URL	OAuth server token revocation endpoint.
Redirect URL	OAuth callback endpoint in this format: `https://.service-now.com/oauth_redirect.do`
OAuth API Script	Script to customize the request and response. Select OauthCiscoWebexTeamsUtils.
Logo URL	URL that contains an image to use as the application logo.
Default Grant Type	Grant type used to establish the token. Select Authorization Code.
Refresh Token Lifespan	Time, in seconds, that the refresh token is valid. The default time is 8,640,0000 seconds.
PKCE required	Option to enable public clients to require PKCE for an authorization.Note: You can use only Authorization Code as the Default Grant type when PKCE is enabled.
Application	Application scope that contains this record.
Accessible from	Application scope that this registry is accessible from.
Active	Option to actively use the application registry.
Use mutual authentication	Option to use mutual authentication for token request and revocation. This option requires a mutual authentication profile to be specified.

Field	Description
Name	Name to uniquely identify the record. For example, Cisco Webex Teams Cred.
Active	Option to actively use the credential record.
OAuth Entity Profile	OAuth profile created during the registration of Cisco Webex Teams as an OAuth provider. For example, Cisco Webex Teams OAuth Profile.
Applies to	Option to specify if the credential applies to all MID Servers in your network, or to one or more Specific MID servers. Specify the MID Servers that should use this credential in the MID servers field.
Order	Order to apply this credential. For example, `100`.
Credential alias	Credential alias associated with the spoke.

Right-click the form header and click Submit.

To generate the OAuth token, click the Get OAuth Token related link.

Create a connection and credential alias record for the Cisco Webex Teams Spoke

Create a credential record for the Cisco Webex Teams account. The Cisco Webex Teams Spoke connection and credential alias uses these credentials to authorize actions.

Before you begin

Role required: admin.

Procedure

Navigate to All > IntegrationHub > Connections & Credentials > Connection & Credential Aliases.
Open the CiscoWebexTeams record.

Image omitted: cisco\_webex\_teams\_conn-credential.png
Cisco Teams Webex connection and credential alias

The **CiscoWebexTeams** Connection &amp; Credential Aliases display.

Click New under Connections tab.

Image omitted: new\_connection\_credential\_cisco\_webex\_teams.png
New connection and credentials for Cisco Webex Teams

On the form, fill these values.

Field	Description
Name	Name for the HTTPS connection record for Cisco Webex Teams spoke
Credentials	Name of the credential created for Cisco Webex Teams spoke Provide the value ceated in “Create a OAuth credential record for the Cisco Webex Teams spoke”.
Connection URL	Option to provide the connection URL. Provide the value as https://webexapis.com

Image omitted: connection\_record\_cisco\_webex\_teams.png
Connection record for Cisco Webex Teams

Right-click the form header and click Submit.

Create a Connection & Credentials alias for Visa Spoke

Create a connection record for your . The Visa spoke connection and credential aliases use these connections to perform actions in .

Procedure

Navigate to All > Connections & Credentials > Connections & Credentials Aliases.
Open the alias record for ****.
From the Connections tab, click New.

On the form, fill these fields.

Field	Description
Name	Name to uniquely identify the record. For example, `<Application-Name> Connection`.
Credential	Credential record created for Visa spoke. For example, `<Application-Name> Cred`.
Connection alias	Alias record associated with this connection.
Host	Fully qualified domain name of the target host where the **** server is installed. For example, `<host>.<domain>.com`.
Connection URL	Base URL to connect to ****. Enter: ``
Active	Option to actively use the connection record.
Domain	Domain that the action runs in.
Override default port	Target port used by the connection. If blank, the system uses the default port.
Use MID server	Option to use a MID Servers for this connection. If the check box is selected, define the fields in the Advanced MID Server Configuration related list.

Click Submit.