The workspace name is included in the Zapier new meeting payload when a meeting is booked via a router, but is absent when a meeting is booked directly via a Meeting Type link. This inconsistency means teams building automations on top of Zapier or webhooks cannot reliably use workspace as a grouping or routing condition in their flows, since the field only exists for a subset of bookings.

Chili Piper should include the workspace name in the meeting payload for all booking methods, including Meeting Type links, personal scheduling links, and any other entry point, not only router-booked meetings.

Workspace is a fundamental organizational attribute of every meeting in Chili Piper. Omitting it from non-router payloads forces automation builders to handle inconsistent data structures and prevents workspace-based logic from working reliably across all booking flows.