Connect Kit (ConvertKit) to Stripe in two minutes.
Real-time triggers from Kit (ConvertKit), ready-made actions in Stripe. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Kit (ConvertKit).
- Form SubscribedWebhook
- Subscriber ActivatedWebhook
- Tag AddedWebhook
Workflows do something in Stripe, instantly.
- Cancel SubscriptionAPI
- Create ChargeAPI
- Create Checkout SessionAPI
- Create CouponAPI
- Create CustomerAPI
- Create Payment IntentAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Kit (ConvertKit), do it in Stripe.
3 Kit (ConvertKit) triggers wired to 31 Stripe actions. Most-used pairing: Form Subscribed → Cancel Subscription.
Or fire it the other way around.
10 Stripe triggers wired to 4 Kit (ConvertKit) actions downstream.
See Stripe → Kit (ConvertKit) →Common Kit (ConvertKit) → Stripe workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.
Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.
Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.
Fires when a new subscriber confirms opt-in via a specific Kit form (after double-opt-in completes if enabled). Payload includes the subscriber with custom fields and the form they subscribed via. Scope to a single form ID at trigger setup.
Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.
Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.
Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.
Fires when a subscriber clicks the double-opt-in confirmation link. The granular hook for "they confirmed, now they're a real subscriber" downstream automation.
Fires when a tag is added to a subscriber — by Kit automation, by manual edit, or by API. Tags are how Kit represents engagement state and interest, so this is the high-signal hook for behavioural workflows.
Connect Kit (ConvertKit) and Stripe in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Kit (ConvertKit) and Stripe
Open TinyCommand, authorize Kit (ConvertKit) and Stripe once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Kit (ConvertKit) trigger
Drop the Kit (ConvertKit) → Form Subscribed trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/convertkit.trigger-form-subscribed - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the Kit (ConvertKit) payload into the Stripe inputs.
stripe.cancel-subscription - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
