Our verdict
Make handles the core Kit jobs: tag a person, add them to a sequence or form, and react when a tag is added or removed. [1] It does not have modules for purchases or custom fields, so record what someone bought as a tag. [1] [2]
Check your plan before you build. Make says the Kit app needs a paid Kit account, and Kit's pricing puts sequences on Creator and Pro only. [1] [4]
Modules in Make's Kit app
Names below are from Make's Kit page, with typos on that page corrected. [1]
| Type | Modules |
|---|---|
| Triggers | Watch Subscriber Activated; Watch Form Subscriptions; Watch Tag Added; Watch Tag Removed |
| Subscribers | Add a Subscriber to Form; List Form Subscribers; List Subscribers; Get a Subscriber; Update a Subscriber; Unsubscribe a Subscriber |
| Sequences | Add a Subscriber to a Sequence; List Sequence Subscribers |
| Tags | Add a Tag to a Subscriber; Remove a Tag by ID; Remove a Tag by Email; List Subscribers by Tag; Get Subscriber's Tags |
| Other | Make an API Call |
API Secret, API keys and OAuth
Make's Kit connection asks for one value, the API Secret from your Kit account. [1] It links to Kit's V4 documentation but does not say which API version its modules call. [1]
Kit's developer docs describe two V4 methods. API keys, sent in the X-Kit-Api-Key header, are for automating your own account; Kit says it offers no official support for public apps built on API keys. OAuth is for apps in the Kit App Store and full V4 support. [2] Kit's V3 reference says V3 is no longer in active development. [3]
| API key (your own account) | OAuth (apps) | |
|---|---|---|
| Intended for | Simple tools and integrations for your own account [2] | Apps for all creators in the Kit App Store [2] |
| Rate limit | 120 requests per rolling 60 seconds [2] | 600 requests [2] |
| Bulk endpoints and purchase creation | Not available; they require OAuth [2] | Available [2] |
Kit plan requirements
Kit's free plan covers up to 10,000 subscribers and includes API access, but not email sequences or visual automations. [4] [5] Prices are for the lowest subscriber tier on Kit's pricing page and change with list size. [4]
| Kit plan | Price at lowest tier | Sequences | Works for this scenario |
|---|---|---|---|
| Free | $0, up to 10,000 subscribers | No | No; Make requires a paid account [1] |
| Creator | $390 billed yearly (shown as $33 a month) | Yes | Yes |
| Pro | $593 billed for the first year (shown as $50 a month, 25% off the first year), then the standard rate | Yes | Yes |
Worked scenario: Stripe purchase to Kit tag and sequence
Goal: when someone buys a course through Stripe Checkout, tag them in Kit and start an onboarding sequence.
Trigger: Stripe Watch Events, an instant trigger. Make creates the Stripe webhook automatically when you save the module. [6] Select checkout.session.completed, which occurs when a Checkout Session completes successfully. [7] If you sell with delayed payment methods, also select checkout.session.async_payment_succeeded. [7]
Filter: continue only if the session's payment status is not unpaid, and only if the product matches this course. Filters use no credits in Make. [8]
Action 1: Kit Add a Tag to a Subscriber with the buyer's email and a tag such as bought-course-a. Action 2: Kit Add a Subscriber to a Sequence for the onboarding sequence. [1] Tag first so the tag exists even if the sequence step fails.
| Step | Module | Credits per sale |
|---|---|---|
| 1 | Stripe Watch Events (checkout.session.completed) | 1 |
| 2 | Filter: paid and correct product | 0 [8] |
| 3 | Kit Add a Tag to a Subscriber | 1 |
| 4 | Kit Add a Subscriber to a Sequence | 1 |
| Total | About 3, or 300 credits for 100 sales |
Before you switch it on
A short checklist for the purchase flow.
- Create the tag and the sequence in Kit before mapping them.
- Use a Stripe restricted key with only the permissions Make needs, or the Stripe OAuth connection. [6]
- Add a second scenario on charge.refunded that uses Remove a Tag by Email, so refunded buyers stop counting as customers. Stripe sends charge.refunded for partial refunds too, so decide how to treat those. [1] [7]
- Run one test-mode purchase and confirm the tag and the sequence in Kit.
- Keep bulk syncs small; an API key allows 120 requests a minute. [2]
Watch demos / Official walkthroughs
See how the tools work.
Videos load from YouTube only when you press play. These are provider videos, not our own product tests.
Make / Official video
Make—Building Your First Automated Workflow from Scratch
What to look for: Follow how modules connect and how data moves through the first workflow.
Watch on YouTubeQuestions before you decide
Does Make's Kit app work on Kit's free plan?
Make's Kit page says a paid Kit account is required. Kit's free plan includes API access, but email sequences and visual automations need a paid plan, so a tag-and-sequence scenario needs Creator or Pro.
Which Kit API version does the Make app use?
Make's page does not say. It asks for an API Secret and links to Kit's V4 documentation. Kit says V3 is no longer in active development and V4 uses API keys or OAuth.
Can Make record a purchase in Kit?
Make's Kit module list has no purchase module. Kit's API docs say purchase creation requires OAuth, and Make's connection uses an API Secret instead. Record the purchase as a tag, such as bought-course-a.
Are there rate limits on Kit API keys?
Kit says an API key is limited to 120 requests over a rolling 60 seconds, while OAuth apps get 600. A normal sales flow is far below that, but a bulk import scenario can hit it.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make Apps: Kit Accessed 30 Oct 2026
- Kit API: Authentication Accessed 30 Oct 2026
- Kit API V3 reference Accessed 30 Oct 2026
- Kit pricing Accessed 30 Oct 2026
- Kit Help: The Kit free plan Accessed 30 Oct 2026
- Make Apps: Stripe Accessed 30 Oct 2026
- Stripe Docs: Types of events Accessed 30 Oct 2026
- Make Help: How features use credits Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.