Webex is used in a variety of our workflows so we’ve published some Webex atomics:
|Add Member to Room||Adds a user to an existing Teams room|
|Create Room||Creates a new Teams room|
|Post Message to Room||Posts a plain text or markdown message to a Teams room|
|Search for Room||Searches for a Teams room and returns its information, including its ID|
|Search for Team||Searches for a Team and returns its information|
|Send Message to User||Sends a message directly to a user by their email address or ID|
If you’re interacting with Webex from your workflows, we recommend highly that you use a bot. When you create a Webex Bot, you’ll be given an authorization token that doesn’t expire. This makes authenticating to the API much simpler since you can just store this token in a
Many of our workflows have the option of posting messages to Webex. This section explains how to configure these workflows with the information necessary for Webex or, if you don’t want to use Webex, how to disable it.
- Make sure you’ve invited your bot to the room you want to post messages to.
- Add your Webex Bot Token to the
Webex Bot Tokenor
Webex Access Tokenlocal variable (or, if you have a token in a global variable already, set the local variable to the global’s value using the
Fetch Global Variablesgroup at the beginning of the workflow).
- Provide either a
Webex Room Nameor
Webex Room IDin their respective local variable. If only one of these local variables exists, fill in whichever is there. If both exist, you typically only need to provide one or the other. See the workflow’s documentation for details.
- Select each Webex-related activity and check the
Skip Activity Executionbox in its properties.