The offer record connects the stack
Use Offers to define the product, price, checkout mode, invoice, and automation context before Kit (ConvertKit) and beehiiv receive events.
Integration pair
Kit (ConvertKit) + beehiiv
Use Kit (ConvertKit) and beehiiv together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.
Common setup
Most teams use Kit (ConvertKit) as their email layer and beehiiv as their email layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.
See Kit (ConvertKit) and beehiiv docs for connection details.
Product surfaces behind this integration
This legacy integration URL now points builders toward the same product reality as the canonical app-pair guide: Offers, payment options, invoices, integrations, Automations, API docs, and webhooks.
Purchase automation carries the details
Automations and webhooks let Kit (ConvertKit) and beehiiv receive buyer, product, payment, invoice, coupon, and deadline context.
Use the richer guide from here
Keep moving from this page into canonical integration docs, platform pages, stack guides, and sequence recipes so every Kit (ConvertKit) or beehiiv mention has a useful next step.
Open canonical app-pair guide Use the richer Kit (ConvertKit) and beehiiv implementation guide. Kit (ConvertKit) platform page Roles, capabilities, and setup notes for Kit (ConvertKit). beehiiv platform page Roles, capabilities, and setup notes for beehiiv. API-first stack SDK checkout, API keys, webhooks, payment processors, and invoices.