Export to Klaviyo

Push any finished EmailFlow AI email into your Klaviyo template library as an HTML template — the exact final markup the AI Design Studio produced, ready to use in any Klaviyo campaign or flow.

Connecting Klaviyo

Klaviyo authenticates with a private API key rather than OAuth. Create one in Klaviyo under Settings → API keys → Create Private API Key and grant it the Templates scope with Read/Write access — that is the only scope we need, so a key restricted to exactly that is the right choice.

Then open Integrations in the sidebar, click Connect on the Klaviyo card, and paste the key:

The Klaviyo connect page: a private API key field with instructions on which Klaviyo scope the key needs, and a Connect button — Paste a private API key with the Templates read/write scope.

The key is verified against Klaviyo before anything is saved — a bad or under-scoped key is rejected on the spot with Klaviyo's own error message. Once accepted, the key is stored encrypted at rest and the card in the directory flips to Connected.

Pushing an email

From Email Templates, open the more_vert menu on any template card and choose Push to ESP — or use the Push to ESP button in the AI Design Studio's top bar. Pick Klaviyo and the export is queued; the dialog polls the result and links you straight to your Klaviyo template library when it lands.

The email arrives in Klaviyo → Content → Templates as an HTML template under the same name it has here. Klaviyo distinguishes drag-and-drop templates from HTML ones; pushed designs are HTML templates, which Klaviyo's editor opens in its code view.

code

What Klaviyo receives is the same final HTML as Download HTML — inlined, email-client-safe markup from one shared export pipeline. Nothing is rewritten on the way out.

The export log

Every push is recorded on the connection's Manage page (Integrations → Klaviyo → Manage) with its status, timestamp, a link to the artifact, and — for failures — Klaviyo's error message verbatim.

Troubleshooting

My key was rejected at connect time. The message shown is Klaviyo's own. Most commonly the key is missing the Templates Read/Write scope, or a public key was pasted instead of a private one (private keys start with pk_).
The connection shows an error badge. Klaviyo stopped accepting the key — usually it was deleted or its scopes changed in Klaviyo. You also get an in-app notification. Reconnect with a fresh key from the Manage page; history is kept.
Push to ESP asks me to upgrade. Template export follows the same plan flag as Download HTML; it is available on paid plans.

Disconnecting from the Manage page deletes the stored key immediately, while your export history stays visible.