Coaching offers that hand off to a sales rep
A coach sells a paid assessment through a Plandalf checkout. The buyer joins the Mailchimp newsletter with a tag, and HubSpot gets the contact so the rep sees who has already paid before the first call.

Native on one side, webhook on the other
Mailchimp keeps the newsletter, HubSpot keeps the sales record, and a Plandalf checkout can write the buyer to both.
No credit card required. No coding required.
Mailchimp
HubSpotPlandalf does not sync Mailchimp with HubSpot. A Plandalf sequence can do two things from one purchase: run native Mailchimp steps, and call HubSpot's contacts API with a Send Webhook step. A HubSpot workflow can post to a Plandalf catch URL to start a sequence in return.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf → Mailchimp | Native step | Add or Update Contact with merge fields such as a plan name, then Add Tags to Contact for the product. Merge fields must already exist in the audience. |
| Checkout completed | Plandalf → HubSpot | Webhook | A Send Webhook step calls HubSpot's batch upsert for contacts, passing the email as the record id with idProperty set to email and the name fields inside properties. A HubSpot private app token goes in an Authorization header as a Bearer token. |
| Contact subscribed | Mailchimp → HubSpot | Webhook | The Mailchimp trigger starts the sequence, and the same upsert call creates the person in HubSpot if a sales rep has not met them yet. |
| Workflow webhook | HubSpot → Plandalf | Webhook | A HubSpot workflow action posts to a Plandalf catch URL, either with all contact properties or a body you shape. HubSpot only allows HTTPS addresses, which Plandalf catch URLs are. |
| Invoice refunded | Plandalf → Mailchimp | Native step | The Remove access on refund template removes the Mailchimp tag. HubSpot has no Plandalf step, so a lifecycle change there would be a webhook call you write. |
You need a Mailchimp API key and a HubSpot private app with contact write access.
In Automation, then Marketplace, connect Mailchimp with the full key including its data-centre suffix. Create any merge fields you plan to fill in the audience settings first.
In HubSpot create a private app, give it the scope for writing contacts and copy its access token. HubSpot's authentication guide shows the token is sent as Authorization: Bearer plus the token.
Under My Sequences choose Plandalf, Checkout Completed and the offer, then pick a sample checkout on the Test tab.
Add Add or Update Contact and Add Tags to Contact. Use {{trigger.customer_email}} for the email and {{trigger.customer_first_name}} for the first name.
Add Send Webhook with POST to HubSpot's contacts batch upsert path and the Bearer header. In the payload put one entry in inputs with the email as id, idProperty as email, and properties for firstname and lastname.
Run the tests, then look for the contact in both tools. Turn on Run on test purchases to rehearse the full path with a test card, and switch it off afterwards.
A coach sells a paid assessment through a Plandalf checkout. The buyer joins the Mailchimp newsletter with a tag, and HubSpot gets the contact so the rep sees who has already paid before the first call.
HubSpot workflows run the webinar follow-up. When a workflow posts a registrant to a Plandalf catch URL, a sequence tags them in Mailchimp so the replay email goes to the same group.
email is the identifying property, so send every property you care about in the same call.Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: HubSpot developer docs: contacts API, HubSpot developer docs: private apps, HubSpot knowledge base: webhooks in workflows.