/email-lifecycle

name: email-lifecycle
description: Plan, build, and run lifecycle email programs through the Hyper MCP — welcome / onboarding, nurture, re-engagement, win-back, and abandoned-cart sequences across whichever provider fits (Klaviyo for ecommerce, Resend for SaaS / dev tools, Beehiiv for newsletters, Gmail for low-volume ops). Use when the user wants to build an email sequence, set up a welcome flow, recover lapsed users, send a broadcast, manage a list / audience / segment, or asks about lifecycle / drip / nurture campaigns.
requires_toolkits:
  - klaviyo
icon: klaviyo
short_description: Welcome, nurture, win-back, and cart sequences across Klaviyo, Resend, Beehiiv, and Gmail.

Email Lifecycle

End-to-end lifecycle email — pick the right provider for the job, build the audience, draft the sequence, launch, and measure. Cross-provider patterns at the top; provider-specific tool calls below.

Out of scope — defer to other skills

| Request | Send them to | | --- | --- | | Cold outbound to people who haven't opted in | `cold-email-outreach` | | Generating images for email creatives | `image-generation` | | Generating ad creatives that run alongside the lifecycle program | `ad-creative-generation` | | SEO research / blog content for the newsletter | `seo-research` |

Requirements

• **Hyper MCP installed and connected.** [https://app.hyperfx.ai/mcp](https://app.hyperfx.ai/mcp)
• **At least one of these providers** connected at [https://app.hyperfx.ai/apps](https://app.hyperfx.ai/apps):
• **Klaviyo** — ecommerce, Shopify-heavy lists, behavioral triggers off purchase / browse data
• **Resend** — product-led / SaaS / dev tools, transactional + lifecycle on the same domain
• **Beehiiv** — newsletters, paid-tier subscriptions, content-driven lists
• **Gmail** — small / personal lists, founder-mode broadcasts, ops emails

If none of those tool prefixes (`klaviyo_*`, `resend_*`, `beehiiv_*`, `gmail_*`) appear in the agent's tool list, stop and tell the user to enable the Hyper MCP and connect the provider they intend to use.

How to run the tools in this skill

Every tool in this skill is named by its canonical tool name. Run it with the call your surface gives you:

| Surface | Find a tool | Run it | | --- | --- | --- | | MCP client (Claude, Cursor, Codex, ChatGPT) | `search("<what you want to do>")`, then `describe("<name>")` | `call("<name>", {...})` | | Hyper CLI | `hyperai search "<what you want to do>"`, then `hyperai describe <name>` | `hyperai call <name> --json '{...}'` |

If a tool is not found, its integration is not connected or not enabled for the workspace: stop and tell the user which integration to connect.

Provider selection

The wrong provider is the most common reason a lifecycle program fails. Pick first.

| You are… | Use | Why | | --- | --- | --- | | An ecommerce / DTC brand on Shopify, BigCommerce, WooCommerce | **Klaviyo** | Native ecom event listeners (Placed Order, Started Checkout, Browsed Product), mature flow editor, tight Shopify sync. | | A SaaS / dev tool / API product sending product + lifecycle on the same domain | **Resend** | Same API for transactional + marketing, audience management, broadcasts, automation runs. Excellent deliverability for product mail. | | Running a content-led newsletter (free + paid tiers) | **Beehiiv** | Built around the newsletter-as-product model — segments, automations, paid tiers, referral program, post stats. | | Running a small ops list (≤500 contacts), founder-mode broadcasts | **Gmail** | Zero new infra, label-based segmentation, easy templating. Don't scale beyond ~500 — see [`cold-email-outreach`](../cold-email-outreach) for sender deliverability if you do. |

You can run more than one. The pattern is: Klaviyo for marketing, Resend for transactional + product onboarding (when the brand also runs ecom). Or Beehiiv for the newsletter and Resend for the product. Decide once per program, not per email.

Tool surface

| Phase | Klaviyo | Resend | Beehiiv | Gmail | | --- | --- | --- | --- | --- | | Audience setup | `klaviyo_lists_create`, `klaviyo_list_members_add`, `klaviyo_segments_create`, `klaviyo_profiles_create`, `klaviyo_profiles_update` | `resend_audiences_create`, `resend_contacts_create`, `resend_contacts_list`, `resend_contacts_update` | `beehiiv_subscriptions_create`, `beehiiv_segments_create`, `beehiiv_tags_add`, `beehiiv_subscriptions_list` | `gmail_labels_create`, `gmail_labels_add`, `gmail_labels_remove` | | Sequence build | `klaviyo_campaigns_create`, `klaviyo_campaign_messages_update` | `resend_automations_create`, `resend_automations_update`, `resend_automations_get` | `beehiiv_posts_create`, `beehiiv_automations_list`, `beehiiv_automations_subscribers_add` | `gmail_drafts_create`, `gmail_drafts_update` | | Send / launch | `klaviyo_campaigns_send`, `klaviyo_campaign_send_jobs_get` | `resend_emails_send`, `resend_broadcasts_send` | `beehiiv_posts_create` (publish), `beehiiv_posts_update` | `gmail_messages_send`, `gmail_drafts_send` | | Measure | `klaviyo_metrics_list`, `klaviyo_metrics_get`, `klaviyo_campaigns_get` | `resend_automation_runs_list`, `resend_automation_runs_get` | `beehiiv_posts_stats_get`, `beehiiv_subscriptions_get` | `gmail_messages_list` |

Full per-provider mechanics, gotchas, and concrete tool-call examples in [`references/provider-mechanics.md`](./references/provider-mechanics.md).

Critical rules

1. **Pick the provider before writing copy.** The mechanics of how a flow gets triggered, how a segment gets defined, and what data you can personalize against differ enough that "we'll figure out the provider later" wastes a day. 2. **Always start with the audience, not the email.** A welcome flow with no opt-in source is unsendable. A win-back with no inactivity definition is unsendable. Define the audience first; the copy is downstream. 3. **One purpose per sequence.** A "welcome + onboarding + product education + first purchase nudge" mega-flow is brittle and impo