Stripe + Customer.io integration

Plandalf has no Customer.io steps and does not sync Stripe customers into it. Customer.io documents its own Stripe sync through a Stripe webhook. For Plandalf sales, a Send Webhook step can post JSON to a Customer.io webhook-triggered automation, and a Customer.io campaign can post back to a Plandalf catch URL.

1. Create the webhook automation

   In Customer.io go to Automations, create one and choose Webhook as the trigger. Copy the Webhook URL it generates.

2. Create the Plandalf sequence

   In Plandalf open Automation, then My Sequences, and create a sequence with Plandalf as the app and Checkout Completed as the trigger. Choose your offer and pick a recent checkout as the sample on the Test tab.

3. Add Send Webhook

   Choose Plandalf, Send Webhook, POST, and paste the Customer.io URL. In the JSON payload send email as {{trigger.customer_email}}, offer as {{trigger.line_items_summary}} and total as {{trigger.total_amount}}.

4. Send a sample first

   Run the Plandalf step test so Customer.io receives real sample data, which lets you pick fields in the automation builder.

5. Add Send Event in Customer.io

   Add a Send Event action that identifies the person by the incoming email, names the event, and fills its data from the trigger fields. Build your messaging campaign on that event, because a webhook automation cannot email anyone itself.

6. Rehearse

   Switch on Run on test purchases in the Plandalf sequence, buy with a Stripe test card, then check the Events view and the person in Customer.io. Turn the setting off afterwards.

• A Customer.io webhook-triggered automation has no person attached. It cannot read existing customer attributes or send a message itself, so you must convert the data into an event with Send Event or Create or Update Person.
• The webhook automation page does not describe how its Webhook URL is authenticated. Treat it as private, and check its docs before sending anything sensitive.
• Customer.io's Stripe guide sets a person's ID to the Stripe customer ID. If you also write people by email from Plandalf, match them the same way in both routes to avoid duplicates.
• If you use Customer.io's Track API instead, it takes HTTP basic authorization, and has separate US and EU hosts. Check its event ID rules for deduplication before you use it.
• Plandalf's Send Webhook waits 30 seconds and its docs make no promise of retries. Check the run in the Events view if a sale is missing in Customer.io.

Does Stripe integrate with Customer.io?

Customer.io documents a way to sync Stripe customers using a Stripe webhook and a webhook-triggered automation. Plandalf is separate and reaches Customer.io with its own webhook step.

How do I connect Stripe to Customer.io?

Follow Customer.io's guide to add a Stripe webhook for customer.created, or for Plandalf sales post to a Customer.io webhook automation from a Send Webhook step. The recipe above covers the second.

Can Plandalf send purchases to Customer.io?

Yes, as JSON posted to a webhook-triggered automation. Plandalf has no Customer.io app, so you choose the fields and build the event in Customer.io.

Can a Customer.io campaign start a Plandalf sequence?

Yes. Add an HTTP Request action that posts JSON with the person's email to a Plandalf catch URL, and have the sequence use the Webhook Trigger.

Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Customer.io docs: webhook-triggered automations, Customer.io docs: sync customers from Stripe, Customer.io docs: Track API.