Choose the handoff that matches your destination. A named Emailify option may upload through an API, create a draft or template, or generate a platform-formatted export; open the exact platform guide before entering credentials or delivering the result.
These workflows move generated email assets into another system. Campaign setup, recipients, approvals, testing, scheduling, and sending still happen in that system.
Choose a handoff
| When you need | Start with | Result and boundary |
|---|---|---|
| A named email or marketing platform | Find its platform guide | The guide states the exact Emailify option, required credentials or manual steps, and where the result is created |
| A local package for a platform that accepts custom HTML | Export an HTML ZIP | Compiled HTML, image assets, a preview page, and a plain-text version in a downloadable package |
| Your own API, CI, or internal delivery service | Use a custom webhook | A JSON POST containing generated HTML, with optional MJML and custom headers or data; your endpoint controls the downstream workflow |
| An automation that receives a ZIP | Use Zapier or Make | The exported ZIP is sent to the webhook you configure |
| Editable source for a developer-controlled compiler | Export MJML | An index.mjml file alongside compiled HTML, using the selected MJML version |
| An AMP for Email package | Export AMP Email HTML | An index.html, plain-text version, and image assets; the sender and receiving client must support AMP for Email |
| Control over where email images are hosted | Choose an image-hosting workflow | Local image files, Emailify-hosted URLs, supported object storage, or a custom base URL, depending on your settings |
If your platform is not listed, follow the custom HTML guidance. The destination must accept imported or pasted custom HTML.
Common method differences
| Platform | Documented handoff | What the guide tells you to review |
|---|---|---|
| Klaviyo | Private API key upload to saved templates | Update-in-place applies to the saved template, not copies already used in a campaign or flow; editable content has platform-specific padding considerations |
| MailChimp | API upload to templates or a manual ZIP workflow | Editable images are exported at 1x; MailChimp can modify uploaded HTML before sending |
| Customer.io | API upload to a Design Studio email or reusable template, or a manual ZIP workflow | Choose the correct region and output type; update-in-place and asset hosting have documented conditions |
| beehiiv | API upload to a draft post | The upload does not publish, schedule, or send; beehiiv wraps the imported content and removes <style> and <link> tags |
| Ghost | Admin API upload to an unpublished email-only draft | The upload does not publish, schedule, or send; Ghost may simplify or remove email-specific markup |
| Shopify | Platform-formatted HTML for manual import | Paste the exported HTML into Shopify's code-based email import workflow |
Check these details in the platform guide
- Handoff method: API upload, OAuth connection, ZIP, pasted HTML, webhook, draft, or another platform-specific flow.
- Credentials and permissions: create the narrow credentials and scopes documented for that platform.
- Destination: confirm whether the result becomes a template, email, draft, asset, or downloadable package.
- Editability: some platforms provide editable regions, while others use a code editor or transform imported HTML.
- Image hosting: confirm whether images are uploaded automatically or must be hosted with the exported HTML.
- Repeat uploads: only rely on update-in-place behavior when the platform guide documents it.
A successful Emailify export or API response does not prove that a campaign has been approved, scheduled, sent, or rendered correctly in every email client. Review the result inside the destination platform and test it before sending.
Platform guide directory
A–F
- Acoustic
- ActiveCampaign
- ActiveTrail
- Amazon SES
- Aweber
- Bazaarvoice
- Benchmark Email
- beehiiv
- Bento
- Bloomreach
- BlueShift
- Braze
- Brevo
- Buttondown
- Campaign Monitor
- Cheetah Digital
- Constant Contact
- Contlo
- ConvertKit
- Customer.io
- Dotdigital
- Drip
- EmailOctopus
- Emarsys
G–M
- GetResponse
- Ghost
- HubSpot
- Insider
- Intercom
- Iterable
- Klaviyo
- Loops.so
- MailChimp
- Mailercloud
- MailerLite
- Mailgun
- MailJet
- Mailmodo
- Marketo
- Mautic
- Microsoft Dynamics 365
- Moosend
N–Z
- Omnisend
- OneSignal
- Ongage
- Oracle Eloqua
- Oracle Responsys
- Pardot
- Postmark
- Resend
- Sailthru
- Salesforce Marketing Cloud
- SARE
- Selzy
- SendGrid
- SendPulse
- Sendwithus
- SendX
- Sendy
- Shopify
- Spotler
- Stripo
- SugarCRM (Sugar Market)
- Webex
- Yotpo
- Zeta
- Zoho Campaigns
Before sending
Review the exported result inside your platform, confirm image URLs and platform-specific merge tags, then test the HTML email across clients.