Resources · Make integration

Kit Make integrationAutomate Kit with Make.

Can Make react the moment someone joins your Kit list? The Kit Make integration gives you 19 modules: 5 instant triggers, 9 actions and 5 searches. This guide is for creators and marketers who run Kit, and it walks you from the connection to a first working scenario.

Try the Kit integration on Make See the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Kit Make integration do for you?

The Kit Make integration links your Kit account to Make, a visual tool where you chain apps together without writing code. Kit tells Make when a subscriber joins a form, enters a sequence or gets a tag, and Make answers by tagging, updating, subscribing or looking people up in Kit, or in any other app you add.

Paid customers land in the right sequence. When a payment app confirms an order, Add a Tag to a Subscriber marks the buyer in Kit, and Add a Subscriber to Sequence starts the onboarding emails. No export, no copy and paste between tools.

Your CRM hears about every new lead. Watch Form Subscriptions fires as soon as someone fills a Kit form, and the next module pushes that person into your CRM or a shared sheet. Sales sees the lead without opening Kit.

Cleanup follows your tags. Watch Tag Removed reacts when a tag disappears from a subscriber, which is the right moment to update another tool or call Unsubscribe a Subscriber.

What the 19 modules do not cover, Make an API Call reaches with the same connection, as long as Kit's API offers it. If you are still choosing a tool, the n8n vs Make comparison sets the two side by side, and the Make pricing page explains how operations are counted. For a guided start, see the Make training.

Connect

How do you connect your Kit account to Make?

01
Add a Kit module
In a new scenario, click the +, type Kit in the search box and pick any Kit module. Then click Create a connection. A connection is your Kit account linked to Make once, so you only do this step one time.
02
Name the connection
Make offers a name field for the connection. It is optional, but a clear label such as the name of your newsletter helps when you run more than one Kit account and need to pick the right one later.
03
Authorize and save
Follow what the window asks: either approve Make on Kit's own page, or paste the key Kit gives you. Then click Save. Back in the module, Make can now read your Kit forms, sequences and tags.

First scenario

Your first scenario: a tag that starts a sequence

GoalWhen a tag is added to a subscriber in Kit, Make adds that person to a sequence.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the big +. A scenario is simply the automation you are building, one module after another.
02
Pick the trigger
Search Kit and choose Watch Tag Added. Select your connection, or create it with Create a connection if this is your first Kit module.
03
Choose the tag
Pick the tag to watch from the list Make shows once the connection works. Only this tag will start the scenario, the others stay quiet.
04
Add the sequence step
Click the + on the right of the trigger and add Add a Subscriber to Sequence. Choose the sequence, then map the subscriber data coming from the trigger.
05
Test with Run once
Click Run once, then add the tag to a test subscriber in Kit. Open the bubble on each module to read the bundle it received, one bundle being one subscriber here.
06
Switch it on
When the test looks right, turn the scenario on. The trigger is instant, so Kit calls Make each time the tag lands on someone, without waiting for a schedule.

Triggers

What can start a Kit scenario?

5 modules start a scenario when something happens in Kit. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Kit as soon as it happens.

Kit1Watch Course/Sequence Subscriptions.

Watch Course/Sequence Subscriptions.

Instant trigger

In Make“Triggers when a user subscribes to particular sequence.”

This trigger starts your scenario the moment a subscriber joins the sequence you picked, so the rest of your tools learn about it without a manual export. Each new subscription arrives as one bundle, ready to map into the next module.

How it fires

instant. Kit calls Make through a webhook as soon as the subscription happens, marked by the lightning badge on the module.

When to use it

a subscriber starts your welcome course and your CRM or community tool should know about it right away.

Watch out

it listens to one particular sequence. To follow several sequences, plan one trigger per sequence.

Kit2Watch Form Subscriptions

Watch Form Subscriptions

Instant trigger

In Make“Triggers when a new user subscribes through the form.”

Here you get every fresh sign-up from a Kit form handed to Make, which makes it the natural entry point for lead handling. The person who just filled the form becomes a bundle that the next module can send to a sheet, a CRM or a chat channel.

How it fires

instant. Kit alerts Make by webhook right after the new subscription, with no polling interval involved.

When to use it

a landing page form feeds your list and sales wants each new lead in their own tool.

Watch out

it reacts to form subscriptions only. Someone added by hand or by another module will not appear here.

Kit3Watch Subscriber Activated

Watch Subscriber Activated

Instant trigger

In Make“Triggers when a new activated.”

With this trigger, Make hears about a subscriber as soon as Kit marks them active, which is a better signal than a raw sign-up when you only care about people who really joined. The activated subscriber reaches your scenario as one bundle.

How it fires

instant. Kit sends a webhook call to Make as the activation happens.

When to use it

you sync your list to another tool and want only activated contacts to travel there.

Watch out

a sign-up that never becomes active never fires this trigger. If you need every sign-up, pair it with Watch Form Subscriptions instead of relying on it alone.

Kit4Watch Tag Added

Watch Tag Added

Instant trigger

In Make“Triggers when a particular tag added to any subscriber.”

Tags are how most Kit users segment, and this trigger turns each new tag on a subscriber into an event Make can act on. You pick the tag, and every subscriber who receives it runs through your scenario as one bundle.

How it fires

instant. As soon as the tag is added, Kit calls Make through a webhook.

When to use it

a tag like buyer or webinar attendee should start something outside Kit, such as a sequence, a CRM update or a message to your team.

Watch out

it follows one particular tag. If a later module in the same scenario adds that tag again, check you are not building a loop.

Kit5Watch Tag Removed

Watch Tag Removed

Instant trigger

In Make“Triggers when a particular tag removed from any subscriber.”

The mirror of the previous trigger: your scenario starts when the chosen tag is taken off a subscriber. That gives you a clean signal for the end of a status, a trial or a campaign, delivered as one bundle per subscriber.

How it fires

instant. Kit notifies Make by webhook as soon as the tag leaves the profile.

When to use it

a customer tag is removed after a refund, and your other tools should drop that person from their customer lists too.

Watch out

it watches a particular tag, not any tag. Removing a different tag from the same subscriber will not start anything.

Modules

What can Make do in Kit?

Kit gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Kit1

Add a Subscriber to Form

Action

In Make“Adds a subscriber to a form.”

Puts a person on your Kit list through a form of your choice, without them filling it in themselves, so they enter your list through the door you chose.

When to use it

leads come from an ad platform, a checkout or a spreadsheet and should enter Kit through the right form.

Watch out

pick the form carefully, since it decides which path the new subscriber follows in Kit.

Kit2

Add a Subscriber to Sequence

Action

In Make“Add a subscriber to a sequence.”

Drops a subscriber into one of your sequences, which starts the series of emails you prepared for them without touching Kit by hand.

When to use it

a purchase, a booking or a tag elsewhere should launch onboarding or nurture emails.

Watch out

run the scenario with Run once on a test address first, so a real contact does not get the sequence twice while you tune it.

Kit3

Add a Tag to a Subscriber

Action

In Make“Adds a tag to a subscriber's profile.”

Writes a tag on a subscriber's profile, so segments and automations inside Kit can treat that person differently from now on.

When to use it

a payment, a download or a form answer in another app says something about the person that Kit should remember.

Watch out

if this scenario also starts on Watch Tag Added for the same tag, it will fire itself again.

Kit4

Get a Subscriber

Action

In Make“Returns subscriber's details by subscriber's ID.”

Fetches the full details of one subscriber when you already hold their Kit ID, so the next modules can map any of that data.

When to use it

a trigger or another module gave you the ID, and you need the rest of the profile before deciding what to do.

Watch out

it works by ID only. With just an email address, start from a list module or map the ID from a previous step.

Kit5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the door to the parts of Kit's API that the other Kit modules leave out, using the Kit connection you already made.

When to use it

you need an operation Kit's API offers but no ready module handles.

Watch out

you describe the request yourself, so keep Kit's API documentation open and test with Run once before switching the scenario on. It is the least beginner friendly module of the list.

Kit6

Remove a Tag By Email

Action

In Make“Removes a tag from the subscriber profile by subscriber's email.”

Takes a tag off a subscriber when all you know is their email address, which is often the case when the data comes from another app.

When to use it

a refund in your shop or a cancelled booking should pull the buyer tag off that address.

Watch out

the email has to match the one in Kit exactly. A typo means the tag stays where it is.

Kit7

Remove a Tag By ID

Action

In Make“Removes a tag from the subscriber profile by subscriber's ID.”

Removes a tag from a subscriber identified by their Kit ID, the safest match when that ID already travels through your scenario.

When to use it

your trigger comes from Kit itself, so the ID is right there to map, and you want no doubt about who gets untagged.

Watch out

when the data comes from outside Kit with only an email, the email version of this module fits better.

Kit8

Unsubscribe a Subscriber

Action

In Make“Unsubscribes a subscriber by email.”

Stops all Kit emails to one person, found by their email address. It is the module for honoring an opt-out that happened somewhere else.

When to use it

someone asks to stop hearing from you through a support tool or a form outside Kit.

Watch out

this acts on a real person. Test it on your own address and double check the filter before switching the scenario on.

Kit9

Update a Subscriber

Action

In Make“Update a subscriber.”

Changes the data stored on an existing subscriber, so Kit keeps the same profile you have in your CRM or your shop.

When to use it

a customer edits their details in another tool and your emails should follow that change.

Watch out

map only the values that really changed, then check the result on a test subscriber with Run once before going live.

Kit10

Get Subscribers Tags

In Make“Returns a list of tags assigned to the subscriber.”

Returns the tags currently sitting on a subscriber, which lets your scenario decide based on where that person stands in Kit.

When to use it

before sending someone to a sequence, you want to check they do not already carry a customer tag.

Watch out

as a search, it can return several tags as separate bundles, and each bundle passing to the next module counts as an operation.

Kit11

List Form Subscribers

In Make“Lists form subscribers.”

Pulls the people who signed up through a given form, handy for looking back at a form's audience rather than waiting for new sign-ups.

When to use it

you just built a scenario around a form and want to process the subscribers it already collected.

Watch out

every subscriber comes out as its own bundle, so a large form means a lot of operations on the modules that follow.

Kit12

List Sequence Subscribers

In Make“Lists sequence subscribers.”

Reads who is enrolled in a sequence, so you can copy that group to another tool or act on each member.

When to use it

a course sequence is running and you want its members added to a community or a spreadsheet.

Watch out

the result can be zero, one or many bundles. Add a filter after it if only some members should go further.

Kit13

List Subscribers

In Make“Lists subscribers.”

Goes through your subscribers without limiting itself to one form, sequence or tag, the widest search of the Kit modules.

When to use it

you set up a new tool and want your existing Kit audience copied there once.

Watch out

on a big list, this is where operations climb fastest, since each subscriber is one bundle for the following modules. Check your plan before running it.

Kit14

List Subscribers by Tag

In Make“Lists tag subscribers.”

Gives you everyone who carries a particular tag, the quickest way to work on a segment you already built in Kit.

When to use it

all subscribers tagged for a webinar should be sent to your video tool or a follow-up sheet.

Watch out

each tagged subscriber becomes a bundle, so a busy tag multiplies the operations of every module placed after it.

Need help

Need help automating Kit with Make?

A person reads every message.

FAQ

Kit and Make: common questions

01Is the Kit Make integration free?

Yes. Kit is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes and files up to 5 MB, with 512 MB of data transfer. Scheduled runs are spaced at least 15 minutes apart on Free, while paid plans go down to 1 minute and remove the cap on active scenarios. Since every Kit trigger is instant, the interval matters less here. Your usage is counted in operations, one per module per bundle, and paid plans count that usage in credits each month. Your Kit subscription itself is a separate matter.

02What do you need to connect Kit to Make?

A Kit account and a Make account are enough, since Make lists no other prerequisite for Kit. You add any Kit module, click Create a connection, optionally name it, then either approve Make on Kit's page or paste the key Kit gives you, and click Save. That single connection is then reused by all 19 Kit modules in every scenario. If you manage several Kit accounts, create one connection per account and give each a clear name, so you never tag or unsubscribe people in the wrong list.

03Do Kit triggers in Make fire in real time?

Yes. All 5 Kit triggers are instant: Kit calls Make through a webhook as soon as the event happens, whether that is a form sign-up, a sequence subscription, an activation, or a tag being added or removed. Your scenario does not wait for the default 15 minute schedule that applies to polling triggers. The lightning badge on the module shows this. Once the scenario is switched on, each event starts one run, and each subscriber moves through the modules as one bundle, so plan your operations around how often these events happen in your account.

04What if a Kit module is missing in Make?

Use Make an API Call. It is one of the 19 Kit modules and lets your scenario call any endpoint of Kit's API with the same connection you already set up. The ready modules cover subscribers, forms, sequences and tags; anything else Kit's API supports goes through this module. You write the request yourself, so read Kit's API documentation and test each call with Run once. Make's documentation lists no specific limits for Kit, so if a request fails, the error in the module bubble is your first clue.

05Should you use Make or n8n for Kit?

It depends on how you like to build. On Make, Kit comes with 19 modules, 5 instant triggers and a Make an API Call module, and you assemble scenarios visually, testing them with Run once. The same app often has a node on n8n as well, so check that side if your team already runs n8n workflows. Compare the modules each tool offers for what you plan to do, the way usage is counted, and where your other automations already live. The n8n vs Make comparison linked above goes through these criteria in detail.

Add a Kit module

Name the connection

Authorize and save

Create the scenario

Pick the trigger

Choose the tag

Add the sequence step

Test with Run once

Switch it on

Need help automating Kit with Make?