Studio Project workflows for Cisco Webex rooms, messages, people, and teams
Cisco Webex is a cloud collaboration platform providing team messaging, meetings, and calling. This folder covers the Webex REST APIs: administrative resources (audit events, room/space memberships) and the core messaging surface (rooms, messages, people, teams).
This project provides OpenAPI specs for automating against the Webex REST API via an Integration Model. See OpenAPIs below for what each spec covers.
| Asset | Description |
|---|---|
| OpenAPIs/ | Cisco Webex REST API OpenAPI specs — curated -latest plus the full dated spec, for both the core and messaging APIs |
| Studio Projects/Cisco Webex | 30 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Cisco Webex | v1 REST API |
| Cisco Webex / Cisco Webex — Messaging Integration Model | Required to build automation against the OpenAPI specs |
Import one of the OpenAPI specs from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at webexapis.com.
Authentication is a bearer token in the Authorization header:
Authorization: Bearer <your-webex-token> Generate a bot token or personal access token at developer.webex.com (under My Webex Apps or the API docs page for a short-lived personal token).
The instance's authentication/server properties should look like this once configured for cisco_webex-latest.json:
{
"authentication": {
"httpBearer": "<your-webex-token>"
},
"server": {
"protocol": "https",
"host": "webexapis.com",
"base_path": "/v1"
}
} cisco_webex_messaging-latest.json uses the same bearer token value, but under a differently-named scheme key — configure it as authentication.bearer-key instead of authentication.httpBearer on an instance of that model.
| Spec | Version | Operations | Description |
|---|---|---|---|
cisco_webex-latest.json | latest (curated) | 8 | Actively-maintained spec — see breakdown below |
cisco_webex_messaging-latest.json | latest (curated) | 33 | Actively-maintained spec — see breakdown below |
cisco_webex-1.0.json | 1.0 | 10 | Full spec for the Cisco Webex core API, version 1.0. |
cisco_webex_messaging-1.0.0.json | 1.0.0 | 63 | Full spec for the Cisco Webex Messaging API, version 1.0.0. |
cisco_webex-latest.jsonActively-maintained spec (x-vendor-api-version: 1.0). Trimmed to 8 of 10 upstream operations.
Resources included, by category:
GET /adminAudit/events) — the Control Hub compliance/security audit trail of admin actions, not server/API telemetryGET /events, GET /events/{eventId}) — the compliance-officer feed of user actions (messages/calls created, deleted, etc.) within the orgGET/POST /memberships, GET/PUT/DELETE /memberships/{membershipId})Dropped as a non-automatable reference lookup: GET /licenses and GET /licenses/{licenseId} — a read-only license-tier catalog (this API surface has no write/assign operation for licenses) rather than something to create/update/delete via automation.
cisco_webex_messaging-latest.jsonActively-maintained spec (x-vendor-api-version: 1.0.0). Trimmed to 33 of 63 upstream operations covering common CRUD for automation.
Resources included, by category:
/people/me)Dropped as long tails not core to messaging automation: card/attachment actions, room linked folders, the audit event feed (already covered by cisco_webex-latest.json), the Hybrid Data Security module (a specialized enterprise deployment feature), room tabs, and webhook management.
cisco_webex-1.0.jsonFull, unmodified vendor spec for the Cisco Webex core API, version 1.0 (10 operations) — the vendor's complete API surface, preserved as-is. See cisco_webex-latest.json above for the curated subset if you just need common CRUD automation.
cisco_webex_messaging-1.0.0.jsonFull, unmodified vendor spec for the Cisco Webex Messaging API, version 1.0.0 (63 operations) — the vendor's complete API surface, preserved as-is. See cisco_webex_messaging-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Cisco Webex — Messaging:latest Integration Model (see cisco_webex_messaging-latest.json above). The project contains 30 workflows organized into 6 folders, one atomic workflow per API operation, covering the full CRUD surface of the curated messaging spec.
| Folder | Workflows | Scope |
|---|---|---|
| Memberships | List, Create, Get, Update, Delete Membership | Space membership CRUD |
| Messages | List, Create, Get, Update, Delete Message | Message CRUD |
| People | List, Create, Get, Update, Delete Person | Person CRUD |
| Rooms | List, Create, Get, Update, Delete Room | Room/space CRUD |
| Teams | List, Create, Get, Update, Delete Team | Team CRUD |
| Team Memberships | List, Create, Get, Update, Delete Team Membership | Team membership CRUD |
| Dependency | Notes |
|---|---|
Cisco Webex — Messaging:latest Integration Model | Import from cisco_webex_messaging-latest.json before importing the project |
Cisco Webex — Messaging integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Cisco Webex — Messaging — update the adapter_id value in each workflow task if yours is named differently |