Email integration
Connect Customer.io to Plandalf
Send every Plandalf purchase to Customer.io as an event, and drive your lifecycle campaigns from it.
We build the Customer.io step in 24 hours. No credit card required.
StripeCustomer.iocheckout.completedinvoice.paidinvoice.voided
Overview
How Customer.io and Plandalf split the work
Plandalf sells and records the purchase. Customer.io gets the buyer and the context, and does the emailing.
- Checkout completedStudio Pro · $199.00
- Buyeralex@studio.co
- SequenceCustomer.io step ran
Built for you in 24 hours
Customer.io runs as a step inside a Plandalf sequence. Tell us what should happen in Customer.io and we build the step for your account within 24 hours. From then on, when a checkout completes, an invoice is paid or a buyer takes an upsell, the Customer.io step can add subscriber, add tag or update subscriber fields, with the buyer's email and name, the products and the price paid already filled in.
Customer.io owns
- Lists, tags and segments
- Campaigns and newsletters
- Deliverability and unsubscribes
Plandalf owns
- The checkout and the payment
- Who bought what, and for how much
- The event that starts the email
Set it up
Connect Customer.io in three steps
We build the Customer.io step for your account in 24 hours. After that it works like every other app.
- 1
Tell us what it should do
Open the chat on this page. Name the event that starts it (checkout completed is the usual one) and what should happen in Customer.io.
- 2
We build the Customer.io step
Within 24 hours the Customer.io step is in Automations for your account. Connect your Customer.io account once, right there in the editor.
- 3
Add it to a sequence
Pick the trigger, add the Customer.io step and choose add subscriber, add tag, update subscriber fields. Run a test checkout to watch it fire, then switch it on.
- Also with Promos: drop the Plandalf countdown image into a Customer.io campaign; enrol Customer.io people via a Campaign webhook. Promos docs →
- Request the Customer.io step →
- Browse Customer.io connections →
Triggers and actions
Start with the sale. Build whatever comes after.
Any checkout event can start an automation with the whole order in hand. Stack the steps, wait between them, branch on what was bought.
Customer.io runs as a native step. See every integration
Checkout completedOrder #4821 · Maya Chen · $249.00FiredAdd or update contactCustomer.ioDoneFinds Maya in HubSpot, or creates her, and tags the purchase.
ContactUpdated just nowIntegrations
Keep your site. Upgrade how it sells.
Plus a fully documented REST API and webhook layer for whatever’s not in the list.
Questions
Common questions about Customer.io and Plandalf
The short answers. The docs have the long ones.
Is there a Customer.io step in Plandalf?
We build it for your account within 24 hours of you asking. Tell us what starts it and what should happen in Customer.io; the step then sits in Automations like any other app: connect the account once, pick the action.
What does Plandalf do in Customer.io?
The Customer.io step can add subscriber, add tag, update subscriber fields. Each carries the buyer's email and name, the products, the price paid, the coupon and the offer they bought from.
Can I run a countdown in a Customer.io email?
Yes. Promos render a per-recipient countdown image; drop the URL into a Customer.io email and each subscriber sees a timer pegged to their own deadline.
Does Plandalf send email itself?
Plandalf sends receipts and transactional email. Newsletters, sequences and campaigns stay in Customer.io, triggered by what happens at checkout.
Can I disconnect Customer.io later?
Yes. Disconnecting revokes access; contacts already created in Customer.io stay there, and the sequence history stays in Plandalf.
The team
Built by a team obsessed with conversion.
15+ years building SaaS businesses together. Every part of Plandalf comes from a real checkout problem we’ve had to solve ourselves.
No credit card required. Nothing to migrate.