Skip to main content

​
What’s Supported

​
Supported Actions

This connector supports:

​
Supported Objects

The Webex connector supports the following objects from the API:

​
Before you get started

To integrate Webex with Ampersand, you will need a Cisco Webex Account. Once your account is created, you’ll need to create an integration in Webex and obtain the following credentials from your integration:
  • Client ID
  • Client Secret
You will then use these credentials to connect your application to Ampersand.

​
Creating a Webex Integration

The Admin API is a superset of user-level APIs. Some objects (such as events, organizations, and reports) require organization-level admin scopes, while others (such as meetings) can be accessed with user-level scopes. Refer to the Webex API documentation to determine which account type and scopes are required for your use case.
Follow the steps below to create a Cisco Webex integration and add the Ampersand redirect URL to the integration:
  1. Log in to your Webex Developer Portal account.
  2. Click My Apps in the top navigation.
  3. Click Create a New App.
  4. Select Integration as the app type.
  5. Enter your App Name.
  6. Enter a Description for your integration.
  7. Enter Ampersand’s Redirect URI: https://api.withampersand.com/callbacks/v1/oauth.
  8. Under Scopes, select the necessary Scopes for your integration.
  9. Click Add Integration.
Alt text On the next screen, you’ll see a Client ID and Client Secret have been generated. You’ll use these credentials while connecting your app to Ampersand.

​
Add Your Webex App Info to Ampersand

  1. Log in to your Ampersand Dashboard.
  2. Select the project where you want to create a Webex integration.
Ampersand Project Selection
  1. Select Provider apps.
  2. Select Webex from the Provider list.
  3. Enter the previously obtained Client ID in the Client ID field and the Client Secret in the Client Secret field.
  4. Click Save changes.

​
Using the connector

To start integrating with Webex:
  • Create a manifest file.
  • Deploy it using the amp CLI.
  • If you’re using Read Actions, create a destination.
  • Embed the InstallIntegration UI component. This UI component will prompt the customer for OAuth authorization.
  • Start using the connector!
    • If your integration has Read Actions, you’ll start getting webhook messages.
    • If your integration has Write Actions, you can start making API calls to our Write API.
    • If your integration has Proxy Actions, you can start making Proxy API calls.