SaaS email template

Workspace created email — confirm creation and guide the first steps

Fire workspace.created with the workspace name, URL and setup steps. else.events sends a confirmation that drives immediate activation.

Why workspace creation emails are often missed

Workspace creation is separate from user signup

Multi-workspace SaaS products have users who create additional workspaces after initial signup. These need their own confirmation email — not just a login welcome.

No clear next step after workspace creation

A "workspace created" email with no "invite your team" or "connect your first integration" CTA misses the activation moment.

Workspace URL not shown in the email

Users who create workspaces across multiple organisations need the workspace URL in the confirmation to navigate back easily.

Not triggered for programmatic workspace creation

Workspaces created via API (multi-tenant setup) also need notifications — to the workspace owner or the creating user.

Workspace name, URL and setup steps from the payload

Fire workspace.created for every workspace creation

Whether created through the UI or via API, your backend fires workspace.created. else.events sends the confirmation.

Workspace name and URL from the payload

Include workspace_name and workspace_url in the event payload. The template renders the workspace link as the primary CTA.

First-step CTA in the email

Include an invite_url or setup_url in the payload. The template renders "Invite your team" or "Complete your workspace setup" as the primary action.

Managed outside your workspace service

Edit workspace confirmation copy, add setup steps or change the CTA without touching the workspace creation code.

Template variables for the workspace created email

  • {{ user.name }}Creator's name
  • {{ data.workspace_name }}Name of the newly created workspace
  • {{ data.workspace_url }}Direct link to the new workspace
  • {{ data.invite_url }}Link to invite team members to the workspace
  • {{ data.plan }}Plan assigned to the workspace

Frequently asked questions

What subject lines work for workspace creation emails?
"Your [Workspace Name] workspace is ready", "Workspace created — here is how to get started", "[App]: [Workspace Name] has been set up". Include the workspace name.
What CTA should the workspace created email have?
The primary CTA should take the user directly to the new workspace. A secondary CTA to "Invite your team" or "Complete workspace setup" drives the next activation step.
Should I send workspace creation emails for programmatic workspace creation (API)?
Yes — if a workspace owner should know about it. Your backend decides who receives the notification. For API-created workspaces, notify the API key owner or the designated workspace admin.
What if the workspace is created within an existing organisation?
Include the organisation name in the payload so the template can clarify context: "[Workspace Name] has been created in [Organisation Name]." This avoids confusion in multi-workspace setups.

Workspace creation emails that drive immediate activation

Workspace name, direct link and first-step CTA — all from the event payload.

  • Workspace URL from payload as primary CTA
  • Invite team or complete setup as secondary CTA
  • Works for UI and API-created workspaces