Overview
A workspace is the primary organizational unit in WhataBot. It groups all the resources needed to build and run conversational flows: flows, API keys, OAuth clients, AI agents, and sectors. Workspaces belong to an account, and a single account can have many workspaces, enabling multi-tenant separation of concerns.Workspace fields
| Field | Type | Description |
|---|---|---|
id | UUID v7 | Unique identifier, time-sortable |
name | string | Display name for the workspace |
iframe_enabled | boolean | Whether the workspace can be embedded via iframe |
timezone | string | IANA timezone (default: UTC) |
The
timezone field is used by the flow engine when formatting dates and times inside nodes (e.g., the system.hour variable). Make sure it matches your target audience’s timezone.What belongs to a workspace
Flows
Conversational blueprints built in the visual editor. Each flow belongs to exactly one workspace.
API Keys
Keys used to authenticate external systems when creating sessions and sending messages via the API.
OAuth Clients
Client credentials used for iframe embedding. Each client is scoped to a single workspace.
AI Agents
OpenAI agent configurations used by the OpenAI Agent node within flows.
Sectors
Departments or teams that conversations can be transferred to via the Transfer node.
Iframe embedding
Workspaces can enable or disable iframe embedding through theiframe_enabled flag. When enabled, external applications can embed the WhataBot flow editor inside their own UI using an OAuth client scoped to that workspace.
See the Iframe Embedding guide for setup instructions and the Embed Authentication page for the authentication flow.