ActionWebexUpdated September 2026
How do I list Webex spaces the user is in?
Short answer: You can list spaces in Webex by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Webex List Spaces action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Type type | options | Optional | Type. Options: All, Direct (1:1), Group |
Max Results max | number | Optional | Max Results |
Sample request
{"type": "{{trigger.type}}","max": "{{trigger.max}}"}
Returns
{"items": [{"id": "room456","type": "group","title": "Project Team","lastActivity": "2026-04-11T10:00:00Z"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Spaces.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Spaces.
What does the List Spaces action do in Webex?
Lists all Webex spaces (rooms) the authenticated user is in, with type (direct/group), title, and last-activity. Used to populate a space picker before posting.
What inputs does List Spaces require?
List Spaces has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Webex returns an error?
The run history shows the failed step with its input and the error message Webex returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Spaces support batch operations?
Run List Spaces inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Webex's rate limits.
More actions