Fixed-price packages with a sales owner
A sales team wants every package buyer in HubSpot with an offer property, so the account manager sees who bought before the kickoff email goes out.
Native on one side, webhook on the other
A Stripe-paid Plandalf checkout can create or update the buyer in HubSpot through a webhook, and a HubSpot workflow can start a Plandalf countdown.
No credit card required. No coding required.
HubSpotPlandalf and HubSpot are not natively connected, and Plandalf does not sync Stripe customers or invoices into HubSpot. HubSpot has its own Stripe payment-processor connection for sales it collects itself. For Plandalf sales, a Send Webhook step can write the buyer to HubSpot's contacts API, or post to a workflow you build.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf (paid via Stripe) → HubSpot | Webhook | The Buyers to a CRM by webhook template, or a Send Webhook step you write, posts the buyer's email, name, offer and invoice. Aimed at HubSpot's contacts API it creates or updates the contact. |
| Invoice refunded | Stripe → HubSpot | Webhook | A refund that succeeds in Stripe starts Invoice Refunded. A webhook step can set a contact property so a HubSpot list or workflow reacts to the refund. |
| Workflow Send a webhook | HubSpot → Plandalf | Webhook | A HubSpot workflow action posts a contact's properties to a Plandalf catch URL, which can run Enroll in Promo for that person. |
| HubSpot invoice or payment link | HubSpot → Stripe | By hand | If you connect Stripe to HubSpot as a payment processor, HubSpot's own invoices, quotes and payment links charge through it. That is HubSpot's feature, separate from a Plandalf checkout. |
You need a published Plandalf checkout on Stripe and a HubSpot private app token that can write contacts.
Create a private app in HubSpot with permission to write contacts and copy its access token. Check HubSpot's developer docs for the exact scope names and header format.
In Plandalf open Automation, then Templates, and add Buyers to a CRM by webhook for your checkout. Or create the sequence yourself with Checkout Completed as the trigger.
Set the URL to HubSpot's batch upsert contacts path, the method to POST and an Authorization header holding the bearer token. Batch upsert matches on email, so a returning buyer updates rather than duplicates.
Set idProperty to email and the input's id to {{trigger.customer_email}}, then add properties for first name from {{trigger.customer_first_name}} and last name from {{trigger.customer_last_name}}. HubSpot notes that partial upserts are not supported when email is the identifier, so read its page before trimming fields.
On the Test tab pick a recent checkout as the sample, run the step and open the contact in HubSpot. The step test is real, so use your own email.
Create a second sequence on Invoice Refunded with Full refunds only left on, and send a property update so HubSpot can remove the contact from a customers list.
A sales team wants every package buyer in HubSpot with an offer property, so the account manager sees who bought before the kickoff email goes out.
Paid attendees are written to HubSpot as contacts, and a workflow assigns an owner to anyone who bought the premium seat.
Contacts that reach a lifecycle stage enter a HubSpot workflow that sends a webhook to Plandalf, which starts that contact's countdown.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: HubSpot Knowledge Base: use webhooks with workflows, HubSpot Knowledge Base: connect Stripe as a payment processor, HubSpot Knowledge Base: use Stripe with HubSpot, HubSpot developers: CRM contacts API.