Connected accounts
How many mailboxes, calendars and contact books a workspace can connect. Past the limit, new connections are refused with plan_limit_accounts.
workwae is in early access. We set pricing with each early-access team, and we will publish plans before general availability.
Plans are built from a small set of limits. When a request would go past one, the API says which, with a reason code your app can act on.
How many mailboxes, calendars and contact books a workspace can connect. Past the limit, new connections are refused with plan_limit_accounts.
Messages sent through the outbox, counted per day (UTC). A send past the limit fails with plan_limit_sends.
Requests per minute for the whole workspace, and optionally per API key. Requests over the rate get HTTP 429 rate_limited.
How many endpoints can receive events. Adding one past the limit is refused with plan_limit_webhooks.
Whether message bodies can be stored for search and fast reads, and how many bytes. Over it: plan_limit_storage.
AI drafting and reply classification are metered per workspace and day, and shown on the Usage tab.
Credentials and stored content are encrypted, every workspace gets roles and an audit log. Details on the Security page.
Real-time events for mail, calendar and contacts, signed and retried, plus a webhook tester in the console.
A hosted page that takes your users through Google, Microsoft or IMAP sign-in and back to your app.
Email support from the people building workwae. See Support.
We have not published prices yet. During early access, pricing is agreed with each team based on what it needs, and we will publish plans before general availability.
Each plan sets the limits above and the modules it includes (calendar, contacts, tracking, AI, meetings and shared mailboxes). A plan can include an amount of accounts, sends, AI calls and storage in its base fee, with usage beyond that, up to the limits, billed as overage.
Through Stripe. Workspace owners buy a plan and manage billing from the Billing tab in the console.
The workspace keeps sending and connecting accounts for a 7-day grace period while the payment is retried. After that, new sends and connections are refused until the invoice is paid; existing data stays where it is.
The request that would go past it is refused with a stable reason code (plan_limit_accounts, plan_limit_sends, plan_limit_webhooks, plan_limit_storage, or plan_module_unavailable for a module outside the plan), so your app can handle it. Nothing already connected or sent is affected.
Yes. The Usage tab in the console shows your metered usage, including sends and AI calls, beside your plan limits.
Yes. Export your data or erase the workspace from the console or API at any time. Exports stay downloadable for 7 days; retention is described in the Privacy Policy.
We are onboarding a small number of teams and setting pricing with each one.