Short answer: You can create meeting room in Whereby by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Whereby Create Meeting Room action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
End Date endDate | datetime | Required | Room available until this date |
Locked Room isLocked | boolean | Optional | Requires host to let participants in |
Room Name Prefix roomNamePrefix | string | Optional | Room Name Prefix. e.g. "meeting" |
{"endDate": "{{trigger.endDate}}","isLocked": "{{trigger.isLocked}}","roomNamePrefix": "meeting"}
{"endDate": "2026-04-12T10:00:00Z","roomUrl": "https://whereby.com/meeting-abc123","meetingId": "meeting123","startDate": "2026-04-11T10:00:00Z","hostRoomUrl": "https://whereby.com/meeting-abc123?roomKey=host123"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.