Reporting on revenue inside Kit
A creator wants Kit's own purchase view to show course sales. The Plandalf tag handles segments, while a Zap records the purchase.

Native on one side, webhook on the other
Kit steps are native in Plandalf. Zapier covers Kit events and purchase records that the native steps leave out.
No credit card required. No coding required.
Kit (ConvertKit)Plandalf has no Zapier app. Kit (ConvertKit) has native Plandalf steps and four triggers, so Zapier is optional. It helps where Plandalf stops: Send Webhook can post a sale to a Zap, and a Zap watching Kit can post to a Plandalf catch URL.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Subscriber created, tag added, joined form, unsubscribed | Kit → Plandalf | Native step | Four built-in Kit triggers; Plandalf adds the Kit webhook when you save the trigger. No Zap required. |
| Checkout completed | Plandalf → Kit | Native step | Tag Subscriber, Add Subscriber to Form, Add Subscriber to Sequence and Update Subscriber Fields cover most onboarding. |
| Purchase record | Plandalf → Kit | Zapier or Make | Plandalf's API-key connection cannot write Kit purchase history. Zapier's Kit app lists a Create or Update Purchase action, so a Send Webhook step into a Zap may fill that gap. Confirm that action fits your account first. |
| Tag removed, new sequence subscriber, new purchase | Kit → Plandalf | Zapier or Make | Zapier's Kit app lists these triggers, none of which Plandalf has natively. A Zap can post each to a Webhook Trigger catch URL. |
| Invoice refunded | Plandalf → Kit | Native step | Remove access on refund uses Remove Tag from Subscriber and skips cleanly if the person has no such tag. |
You need a Kit V4 API key for Plandalf and a Kit login in Zapier, on a Zapier plan with webhooks.
In Automation, Marketplace, connect Kit. Build a sequence on Checkout Completed that runs Tag Subscriber with {{trigger.customer_email}} and a Customer tag.
In Zapier choose Webhooks by Zapier, Catch Hook as the trigger and copy the URL from the Test tab. Add the Kit action you want, such as Create or Update Purchase.
Add Send Webhook after the tag step. Use the Zap URL, POST, and a JSON payload with email, product and total from the trigger variables.
Run the step test so Zapier receives a real request. Map those fields in the Kit action and test it with your own email.
Create a sequence on Webhook Trigger, copy its URL, and in a second Zap use a Kit trigger such as Tag Removed From Subscriber with a Webhooks by Zapier POST to that URL.
Turn the Zap On, switch on Run on test purchases in the sequence, and buy through the test link. Then switch the test setting off.
A creator wants Kit's own purchase view to show course sales. The Plandalf tag handles segments, while a Zap records the purchase.
Plandalf's native Kit triggers include Tag Added but not removal. A Zap passes removals to a catch URL, and a sequence can start a win-back promo.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Zapier help: trigger Zaps from webhooks, Zapier: Webhooks by Zapier triggers and actions, Zapier: Kit triggers and actions.