Migrate transactional emails to Sendery with AI

Create a Sendery project, then follow the setup guide for Claude Code, Codex, or another MCP client. Open your app’s repository in your coding assistant so it can find your existing emails.

Copy this prompt and name the emails you want to move. Start with one or migrate them all. If you’re unsure, ask your assistant to show you the emails your app already sends.

Mention any branding, content, or languages you want to keep.

Set up Sendery for this application. Inspect the framework and existing transactional emails, then recommend the simplest compatible integration. For a new app, prepare the templates we need. For an existing app, follow my requested migration scope; if I have not chosen emails, summarize them and ask which to migrate. You may suggest starting with one for review. Validate and preview the drafts with sample data. Replace the old sending paths for migrated emails without adding on/off flags or fallback senders. Guide me through adding the sending API key to my local environment and deployment secrets without sharing it in chat or committing it. Explain your changes, tests, draft links, and any remaining setup or publishing steps.

Your assistant turns the selected emails into editable Sendery drafts and previews them with sample data. Open AI Setup in your project to review the design, links, and translations.

Ask for any adjustments, and check any differences your assistant highlights before publishing.

Your assistant updates the sending code using the Sendery SDK or integration for your framework. Create a project API key and add it to your app’s local and production environment settings.

Publish the reviewed templates in Sendery and test your app in sandbox mode. Follow Send your first email to complete Sending setup and send a test to your own address.

Review and deploy the code changes, then check delivery status in Sendery.