Account & security / transactional
Access code change
Temporary studio guest code replaced after it was shared accidentally
Open published preview ↗Bring your assistant
Claude Code workflows
Treat an email change like a code change: preserve the contract, inspect the diff, and test the artifact.
Make the next step deliberate.
Define the template contract
List merge variables, required content, and immutable links.
Change narrowly
Request one edit and inspect its exact diff.
Verify the output
Compile where needed, check mobile and images-off behavior, and review before deployment.
A brief with boundaries.
Review this email template locally. Preserve merge variables, recovery paths, identifiers, and accessibility text. Make the requested copy change only, show the diff, and list rendering checks. Do not deploy or send.
Read the complete text
Review this email template locally. Preserve merge variables, recovery paths, identifiers, and accessibility text. Make the requested copy change only, show the diff, and list rendering checks. Do not deploy or send.
Workflow guidance, not a claim of a verified public connector. Confirm connection, workspace, identity, and permissions before using any assistant with an account.
Published designs to start from.
Real entries in the public library. Preview each design, choose its delivery flow, and replace illustrative content with your approved facts.
These are starting points, not a claim of a completed or activated campaign. Studio examples may need structural changes for your use case.
Keep these checks close.
- A local rendered preview is not a real Gmail or Outlook capture.
- Install or connect only through a verified, approved setup.
Keep the work connected.
Template collections ↗Agent playbooks ↗Find your workflow ↗Free email tools ↗Campaign kits ↗Web, mobile & desktop ↗
Talk to Moosewave about your workflow. For technical context, see documentation and security.