Native on one side, webhook on the other
Plandalf talks to Zapier through webhooks only: out with Send Webhook, in with a catch URL, with Stripe as the payment in the middle.
No credit card required. No coding required.
Stripe
ZapierPlandalf publishes no Zapier app. The bridge is Zapier's generic Webhooks: a Send Webhook step posts a paid Stripe checkout to a Zap's Catch Hook URL, and a Zap's webhook action posts to a Plandalf catch URL to start a sequence. Zapier also has its own Stripe app, which needs no Plandalf.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf (paid via Stripe) → Zapier | Zapier or Make | A Send Webhook step posts JSON to a Webhooks by Zapier Catch Hook URL. The Zap can then do anything Zapier connects to, such as add a spreadsheet row or create a record in an app Plandalf lacks. |
| Invoice refunded | Stripe → Zapier | Zapier or Make | A refund that succeeds in Stripe starts Invoice Refunded and a webhook step passes the refund amounts and is_full_refund to the Zap. |
| Subscription cancelled in Stripe | Zapier → Plandalf | Zapier or Make | Plandalf has no cancellation trigger. If Zapier's Stripe app offers a trigger for cancelled subscriptions (check its trigger list), a Zap can post to a Plandalf catch URL and that sequence can remove access. |
| Any trigger in Zapier | Zapier → Plandalf | Zapier or Make | A Zap's Webhooks by Zapier action posts to /hooks/catch/SEQUENCE_ID/TRIGGER_ID. The request body becomes the trigger data for a Webhook Trigger sequence. |
You need a published Plandalf checkout on Stripe and a Zapier plan that includes Webhooks by Zapier.
In Zapier create a Zap, choose Webhooks by Zapier as the trigger app and Catch Hook as the event. Zapier generates a URL on the Test tab. Copy it.
In Plandalf open Automation, then My Sequences, and create a sequence with Plandalf as the app and Checkout Completed as the trigger, limited to your offer. Pick a recent checkout as the sample on the Test tab.
Choose Plandalf, Send Webhook, POST, and paste the Zapier URL. In the JSON payload pass email as {{trigger.customer_email}}, total as {{trigger.total_amount}}, currency as {{trigger.currency}} and invoice as {{trigger.invoice_number}}.
Run the step test. This sends a real request, so Zapier's Test tab shows the fields and you can map them in the next Zap step.
Add your Zap actions, publish the Zap and turn the Plandalf sequence on. Zapier returns a 200 while the Zap is on, and a 404 if the Zap is off or deleted.
To start a Plandalf sequence from a Zap, add the Webhook Trigger in Plandalf, copy its catch URL, and use a Webhooks by Zapier POST or Custom Request step with a JSON body that includes the person's email.
A membership seller adds a Zap on a Stripe subscription-cancelled trigger, if Zapier offers one, that posts the email to a Plandalf catch URL, where a sequence runs the Kit, Circle or Kajabi removal step.
A small shop sends every paid checkout to a Zap that appends a Google Sheets row and posts to a team channel, with no code.
A coach whose booking tool has a Zapier app but no Plandalf support sends each paid order to a Zap that creates the booking record.
/hooks/catch/SEQUENCE_ID/TRIGGER_ID need no dashboard authentication, so treat the URL as a secret, replace the trigger if it leaks and validate important fields before fulfilment./hooks/catch/SEQUENCE_ID/TRIGGER_ID on your Plandalf host. It is generated when you add the Webhook Trigger, and anyone who has it can start the sequence.Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Zapier Help: trigger Zaps from webhooks, Zapier Help: send webhooks in Zaps, Zapier Help: get started with Stripe on Zapier.