Feature Request: Public-facing endpoint to add members via Zoom Groups into Shared Spaces.
Related-problem:
As far as we can tell, there is not a easy/viable way to associate a Zoom group with a Chat Shared Space via API. Our specific use case involves +150-300 Shared Spaces (5+ channels per alongside #General) for org locations across the US, each of these being a communal space they can use to chat with colleagues. Given this, we are designing for as much automation as possible when it comes to provisioning resources in Zoom. This is the biggest pitfall we’ve found so far in doing so.
Described Solution:
Akin to the endpoint - POST /chat/channels/{channelId}/members/groups ; A dedicated public endpoint to call and associate group_id(s) to a specific Shared Space.
Or, an enhancment of the existing endpoint - POST /chat/spaces/{spaceId}/members to accomodate groups/groups_id values alongside the members/identifier values that it accepts today.
Current alternatives:
The only (((duct-tape))) approach we can see at this time is to read lists of users out of the Zoom Groups themselves, then batch-add those users as members into the Shared Space. But even then it feels rather unwieldy and isn’t going to have the same near-realtime updates to membership that adding the group via the UI on the web would. (+ without the cost from running compute that has to continuously eval memberships …)
Additional context:
The action of adding members via Groups can be done if you are clickops-ing in the Zoom UI on the web as of today, just not via API.
Why are we using groups vs just adding members? The benefit we kinda see here comes down to the fact that adding/removing users from a Zoom Group will near-instantaneously update the channels/spaces that they are in, as well as their Group-level permissions. Less for us to manage and worry about.
Would love to hear feedback or suggestions if others encountered the same/similar scenarios and found better routes! Cheers