Admin user setup:
Users
Make sure you have 2 admin users, the one admin will update the roles on the other.
Make sure you are logged in as an Admin user with the following Roles
Hub and Control panel setup:
Click create service app https://developer.webex.com/my-apps/new/service-app
Complete the following fields:
App Name: Laurel Webex
Icon:
An image that is 512 (W) x 512 (H) in jpg or png format is required
Description: Laurel Assistant - API integrations
Scopes:
meeting:schedules_readmeeting:participants_readmeeting:admin_participants_readmeeting:admin_schedules_readidentity:people_readspark:people_readspark:calls_readspark:compliance:webhooks.readspark:compliance:webhooks.writespark-admin:calling_cdr_readspark-admin:telephony_config_readspark-admin:people_read
Make sure to count and verify all 12 boxes are checked before proceeding.
Click the Add Service App button
When you get the congratulations window, save the following information
ClientId: <clientId>
Client Secret: <client secret>
Service App Id: <service app id>
Click the Request admin authorization
Click the Apps tab
Click Service apps
Find the Laurel Webex app, select it and toggle the Authorize button
Login with your 2nd admin
Under Org Authorizations
Select your org that matches your org Name
Complete the client secret
Click generate tokens and save:
Refresh Token: <refresh token> ← this is very important
Access Token: <access token>
In the Laurel Web application:
Customer Settings → Customer Integration
Webex
complete with the settings needed.
Webex Integration with Laurel – Setup Q&A
Q: Do I need to be a Webex admin to create the integration app?
A: Not to create it — any user can create a service app in the Webex Developer Portal. However, an admin must authorize the integration after the app is created.
Q: Why do two admins need to be involved in the setup?
A: Webex requires that one admin assign special roles (e.g., Compliance Officer) to another. Admins cannot assign these roles to themselves, so a second admin must perform this task.
Q: What roles are required to complete authorization?
A: The Compliance Officer role is necessary to authorize the integration and access certain scopes (e.g., compliance webhooks). This role is often buried in settings and can be time-consuming to locate.
Q: What credentials must be saved during the setup?
A:
Client ID
Client Secret
Service App ID
Access Token
Refresh Token
These will be required by Laurel for integration and should be stored securely (e.g., using PWPush, 1Password, or encrypted zip files).
Q: What’s the best way to securely share tokens with the Laurel team?
A: Use a secure one-time sharing tool like PWPush. Send the Client ID and Secret in separate messages, each with an expiration or limited retrieval setting.
Q: How do I know the integration is working?
A: Once tokens are submitted and authorized, Laurel's server-side jobs will begin syncing. You’ll see Webex meetings appear in user timelines after the first scheduled job run (typically at midnight).
Q: Can I manually enable test users to validate the setup?
A: Yes. Send the list of test user emails to Laurel's engineering contact and they can force a sync for those users.
Q: Do I need to enable CDR (Call Detail Record) logging manually?
A: No. Laurel will handle enabling CDR access on their side as part of the setup process.
Q: How quickly do Webex meetings appear in Laurel after a call?
A: Typically within 10 seconds of meeting end, assuming the webhook fires successfully. Webex webhook delivery is generally fast but can be affected by their internal delays.
Q: Where do Webex jobs run?
A: All syncing and provisioning jobs run on Laurel's infrastructure — no need for customer-side automation like Boomi for this integration.
Webex Resources:
Webhooks
List
Create
Details
Update
Delete