Retreat or event booking from a venue site
A venue's WordPress page sells places on a retreat. Each booking tags the guest and records a Drip event with the amount, and the workflow sends travel and packing information.

Checkout embed
A Plandalf button on a WordPress page can tag the buyer in Drip and record a purchase event, with revenue, that starts a Drip workflow.
No credit card required. No coding required.
WordPress
DripWordPress hosts the page and Drip holds the subscribers; Plandalf links the sale to Drip. A Plandalf button in a Custom HTML block opens the checkout, and native Drip steps create the subscriber, apply a tag and record an event. Drip's own plugin on WordPress.org is a separate WooCommerce connection.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout opened from a WordPress page | WordPress → Plandalf | The SDK and a data-plandalf-present button sit in a Custom HTML block or the theme footer. Your Stripe or PayPal account is paid, not WordPress. | |
| Checkout completed | Plandalf (paid via Stripe) → Drip | Native step | Apply Tag adds a tag such as Retreat 2027 and creates the subscriber when Drip lacks the email. |
| Checkout completed | Plandalf (paid via Stripe) → Drip | Native step | Record Event writes a custom event whose name a Drip workflow starts on. Setting a value property counts it as revenue in cents, using {{trigger.total}}. |
| Invoice refunded | Stripe → Drip | Native step | Remove Tag takes the tag off after a full refund and is skipped when Drip does not know the email. |
| Subscriber created | Drip → Plandalf | Native step | Plandalf registers a webhook in your Drip account when you save the trigger. A sequence can then run Enroll in Promo for each new subscriber. |
You need a WordPress login that can insert JavaScript, a published Plandalf offer and a Drip login that can open User Settings and Account settings.
Open the page in the Code editor or add a Custom HTML block with the Plandalf script and a data-plandalf-present button. If you want it on many pages, load the script from the theme footer file instead.
Visit the published address signed out and open the checkout. Plandalf's WordPress guide notes that builders, cache plugins and optimisers can move or delay scripts, which the editor preview will not show.
In Drip open Settings, User Settings and copy the API Token from User Info. Then open Settings, Account and copy the numeric Account ID under General Info.
Under Automation, Marketplace click Connect on Drip, paste the token into API Token and the number into Account ID, and wait for Drip connected.
Build a sequence on Plandalf, Checkout Completed. Add Drip, Apply Tag for {{trigger.customer_email}}, then Drip, Record Event named for the product with product and value properties. Start a Drip workflow on that event name.
Switch on Run on test purchases, buy with your own email and check the subscriber and event in Drip. Add Remove access on refund and pick the tag, then switch the test setting off.
A venue's WordPress page sells places on a retreat. Each booking tags the guest and records a Drip event with the amount, and the workflow sends travel and packing information.
An author sells a lesson series through a Plandalf button after a long article. The buyer gets a Course tag, which a Drip workflow uses to send the lessons on a schedule.
value property to Record Event set to {{trigger.total}}, which is already in cents, and Drip counts the event as revenue.Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: WordPress.org plugin directory: Drip - Marketing Automation for WooCommerce.