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: create a Service App with the spark:messages_read, spark:rooms_read, spark:memberships_read and spark: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 narrow the sync, choose access groups, Test, then Sync.
| History to sync (days) | How far back a sync reads — 90 by default, shorter than the other chat sources here. |
|---|
What comes in
- Every group space in scope becomes one document per calendar month — dated turns, thread replies grouped under the message they answered. A shared file is counted, not named: Webex only reveals a filename on download, so a turn notes “shared N attachment(s)” instead.
- Speaker names come from Webex's own directory; once a sync's name-lookup budget runs out, remaining turns show the name in the speaker's email address rather than going blank.
Access
A Webex space has no site-wide “public” setting the way a Slack or Teams channel can — membership is the whole of its access. Every space's own membership is mirrored here, re-checked on every sync; a space whose membership can't be read falls back to the source's access groups instead. Access stays allow-only either way. Switch How access works to “One list for everything” under Permissions to put everything this source brings in under the chosen access groups instead.
Fill in both a bot token and a Service App and the Service App wins — it reads full history where a bot only sees @mentions. Months already synced stay searchable when they scroll out of the sync window; a refused credential means generating a fresh token pair and pasting the new refresh token.
Last updated 20 Sep 2026