Ko-fi Make integrationAutomate Ko-fi with Make.
What happens in your other tools when something new lands on Ko-fi? The Ko-fi Make integration gives you 1 instant trigger that starts a scenario on each new event. This guide is for creators and small teams: connect the account, build a first scenario, test it.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Ko-fi Make integration do for you?
The Ko-fi Make integration links your Ko-fi account to Make so that a new Ko-fi event can start an automation on its own. Ko-fi offers a single module in Make, the Watch Event trigger, and it is instant: Ko-fi calls Make as soon as the event happens, and Make passes the data to the next step.
A scenario is the automation you build in Make, a chain of modules. A module is one brick of that chain. With Ko-fi, the first brick is always Watch Event, and everything after it comes from other apps or from Make's own tools.
A supporter log that fills itself. Watch Event hands each new event to a table, for example in Airtable (see the Airtable Make integration), so your list of supporters stays current without copy and paste.
A heads-up for the team. Put a messaging app after Watch Event and the person who handles your community hears about each event in the channel they already read.
A thank-you that goes out on time. Chain an email app after the trigger to send a note once the event reaches Make, instead of relying on memory.
What Make does not give you here: there is no action or search module for Ko-fi, and no generic API call module, so Make can listen to Ko-fi but cannot write back to it. Make also says its Ko-fi documentation is limited because little public information exists about the app. If you are weighing another tool, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains plans.
How do you connect your Ko-fi account to Make?
- 01
Add the Watch Event module
In a new scenario, click the +, search for Ko-fi and pick Watch Event. Then click Create a connection. A connection is your Ko-fi account linked to Make once, and reused by every Ko-fi module after that.
- 02
Name the connection
Give the connection a name you will recognize later, such as the name of your Ko-fi page. This step is optional, but it helps a lot once several accounts or clients share the same Make organization.
- 03
Authorize Make and save
Follow what Make shows next: either you authorize Make on the Ko-fi page that opens, or you paste the key Ko-fi gives you. Finish with Save, and the connection appears in the module.
Your first scenario with Ko-fi and Make
GoalWhen a new event happens on Ko-fi, Make sends its details to the app where you track supporters.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.
- 02
Set up the Ko-fi trigger
Search for Ko-fi, choose Watch Event and select your connection. The lightning badge on the module tells you it is instant: Ko-fi calls Make rather than Make checking Ko-fi.
- 03
Add the destination
Click the + to the right of Watch Event, pick the app that should receive the data, then map the values that came from Ko-fi into its fields.
- 04
Test with Run once
Click Run once, then trigger a real event on Ko-fi. Open the bubble above each module to read the bundle it received, one item passed from module to module.
- 05
Switch the scenario on
When the test looks right, switch the scenario on. From then on, each new Ko-fi event runs it, and each module that runs counts as one operation on your Make plan.
What starts a Ko-fi scenario
1 module starts a scenario when something happens in Ko-fi. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Ko-fi as soon as it happens.
Watch Event
Instant triggerIn Make“Triggers on new events.”
Watch Event gives you the moment something new happens on your Ko-fi page, and turns it into the start of a scenario with the event's data ready to use in the next modules.
Need help automating Ko-fi with Make?
A person reads every message.