Move from Klaviyo
Bring your Klaviyo flows and email templates into VYG with Claude, check the report, and approve the templates.
Claude can copy your Klaviyo email templates into VYG as drafts and report how each Klaviyo flow maps to VYG campaign steps. You then review the drafts and approve the ones you want to use. It uses two tools:
| Tool | What it does |
|---|---|
klaviyo_import | Reads your Klaviyo flows and templates, reports how they map, and saves the templates as drafts. |
email_templates | Lists, creates, previews, edits and test-sends your email templates, and approves a draft. |
Who can use these tools
Both tools need the beta:email-channel feature on your brand (see Beta features). You
must be signed in with your own VYG login, not an API key. The brand is always the one you signed in to. If the
tools are missing, contact your VYG account manager.
What the import does not do yet
The import does not create campaigns, and it does not turn anything on. Your flows arrive as a report, and every template arrives as a draft. Creating paused campaigns from imported flows is coming soon. Nothing is sent to your customers by the import.
Connect Klaviyo
In the vyg.ai app, open Settings, Integrations and connect Klaviyo with a private API key that can read flows and
templates. The import uses this saved connection. Never paste a Klaviyo API key into the chat: klaviyo_import does
not accept one, and the key is never shown in its results.
If Klaviyo is not connected, Claude tells you to connect it in Settings, Integrations and run the import again.
Run a dry run
- "Check what would come over from our Klaviyo account."
- "Do a dry run of the Klaviyo import and show me the gaps."
By default klaviyo_import is a dry run. It reads Klaviyo and writes nothing. For each flow it reports:
| Field | Meaning |
|---|---|
name | The Klaviyo flow name and its status in Klaviyo. |
nodes | The VYG steps the flow maps to, in order: wait, email, sms and split. |
nodes_mapped | How many Klaviyo actions mapped to a VYG step. |
gaps | Klaviyo actions with no VYG step yet, each with a severity and what to do about it. |
arrive_paused | Always true. A flow brought over later arrives paused. |
A split keeps its Klaviyo condition, so a post-purchase flow that splits on a "Subscription" tag shows that tag in the
split step. A gap marked out-of-scope (for example push, WhatsApp, webhooks or customer updates) is not imported. A
gap marked manual-review-on-import (for example A/B tests or smart send time) needs you to rebuild that part by hand.
For each template the dry run says whether it would be added or would update a template imported before, and lists:
- Unmapped variables. Klaviyo variables VYG has no match for, such as a custom profile field or a
{% %}tag.{{ person.first_name }}becomes{{ contact.first_name }}, and the other common ones are translated for you. - Quality issues. Problems the email quality checks found, such as a missing unsubscribe link or postal address.
Run the import
- "Looks good. Run the Klaviyo import for real."
Claude runs klaviyo_import with dry_run: false and confirm: true. It asks you first, because this saves
templates. Every template is saved as a draft with source import. Running the import again updates the same drafts
instead of making copies. The result repeats the flow report so you keep the list of gaps.
Review and approve the templates
- "List the drafts the Klaviyo import made."
- "Preview the cart reminder and tell me what needs fixing."
- "Send me a test of the welcome email."
- "Change the cart reminder's subject to 'Still thinking it over?'"
- "Approve the cart reminder."
email_templates takes an action:
action | What it does |
|---|---|
list | Your templates with their status and version. Filter with status: "draft" to see the imports. |
get | One template in full. |
preview | Renders a template with sample data and lists any quality check issues. |
test_send | Sends one copy to your own email address and nobody else. |
create | Saves a new template as a draft. Nothing sends it until you approve it. |
update | Changes the subject, preview text, HTML or plain text. A draft stays a draft. |
approve | Publishes a draft after the same quality checks Settings, Email runs. Needs confirm: true. |
A draft that fails the quality checks stays a draft, and Claude shows you what failed. Every template needs an
unsubscribe link that points to {{unsubscribe}} and should have your postal address ({{brand.address}}) in the footer.
Ask Claude to fix the draft with update, or fix it in Settings, Email in the vyg.ai app, then ask Claude to
approve it again. An update to a live template must pass every check before it is saved. Flows and broadcasts send a
live template, so Claude asks you first and sends confirm_live_change: true only after you agree.
What comes next
Approved templates can be used in the email step of your campaigns. Turning imported flows into paused campaigns is coming. Until then, build each campaign from the flow report with the approved templates. See Draft campaigns.