Team chat
Set up Webex (spaces)
Bring Webex spaces in as chat-log documents — each group space becomes monthly documents of who said what, when, thread replies under their parent. Direct messages are never read. Read-only.
Bot token, or Service App — mind the difference
A bot token is the two-minute path, but Webex only shows a bot the group-space messages that @mention it, so history syncs THIN that way. For full space history create a Service App — an app your own org owns and your Webex admin authorises; no vendor app is involved either way.
- Quick path: developer.webex.com → My Webex Apps → Create a Bot; copy its token and add the bot to each space worth searching (by its @…@webex.bot address).
- Full-history path: My Webex Apps → Create a Service App with the spark:messages_read, rooms_read, memberships_read and people_read scopes; have a Control Hub admin authorise it, then generate the token pair on the app's page.
- Documents → Webex (spaces): paste the bot token, OR the Service App's client ID, secret and refresh token — not both. Optionally list space names to sync only those.
- Choose access groups, Test, then Sync.
Months already synced stay searchable when history scrolls out of the sync window. The Service App's access tokens renew themselves from the refresh token on every sync; if the source ever says the credentials were refused, generate a fresh pair on the app's page and paste the refresh token again.
Last updated 29 Aug 2026