Resources · Make integration

Tapfiliate Make integrationAutomate Tapfiliate with Make.

How much of your affiliate program still runs on copy and paste? The Tapfiliate Make integration gives you 30 modules, including 8 instant triggers, to move affiliates, conversions and customers around without code. This guide connects your account and builds a first scenario with you.

Try the Tapfiliate integration on MakeSee the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tapfiliate Make integration do for your program?

The Tapfiliate Make integration links your Tapfiliate account to Make, a no-code tool where you build a scenario: a chain of steps that runs on its own. Each step is a module. Tapfiliate brings 30 of them: 8 instant triggers that react to events in your program, 19 actions that create or change records, and 3 searches that pull lists.

Commission review without the inbox. For a SaaS company paying partners on subscriptions, Watch Conversions can push each new conversion to your finance team the moment Tapfiliate records it. Once someone checks it, Update Commission Approval Status approves or disapproves the commission from the same scenario.

Partner tiers that sort themselves. When Watch Approved Affiliates in Program fires, Set Affiliate Group drops the person into the right tier, and Set Metadata can tag them with the channel they came from. Nobody has to open the dashboard for routine onboarding.

Sales from your own checkout. A scenario can start from another app, such as your billing or shop tool, and call Create a Conversion or Create a Customer so Tapfiliate credits the right partner.

Some things stay outside the listed modules. You can watch payments, but no module creates or edits one, and there is no search for prospects. For those gaps, Make an API Call reaches the rest of the Tapfiliate API with the same connection. If your team already works in n8n, the Tapfiliate n8n integration page covers the node there, and n8n vs Make lays out the differences. New to the editor? The Make training starts from zero.

Connect

How do you connect Tapfiliate to Make?

  1. 01

    Open Tapfiliate first

    Log in to your Tapfiliate account in the same browser. Then, in Make, add any Tapfiliate module to a scenario. Make will ask for a connection, which is your Tapfiliate account linked once and reused by every Tapfiliate module.

  2. 02

    Name the connection

    Click Add next to the Connection field. Type something recognizable in Connection name, like the program or brand it belongs to, and click Save.

  3. 03

    Enter your domain and allow access

    Make asks for your Tapfiliate domain. Enter it and click Continue. Tapfiliate then shows an approval screen: click Allow and you land back in Make with the connection ready.

First scenario

Your first scenario: file every new affiliate in the right group

GoalWhen a new affiliate account is created in Tapfiliate, Make puts it in the affiliate group you chose.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. That empty circle is where your first module, the trigger, goes.

  2. 02

    Add Watch New Affiliates

    Search for Tapfiliate, pick Watch New Affiliates and choose your connection (or Create a connection if you skipped the section above). Make sets up the webhook in Tapfiliate for you.

  3. 03

    Add Set Affiliate Group

    Click the + on the right of the trigger and pick Set Affiliate Group. Map the affiliate from the trigger's output, then fill in the group you want new partners to land in.

  4. 04

    Test with Run once

    Click Run once, then create a test affiliate in Tapfiliate. Each module shows the bundle it received, meaning the record that passed through, so you can confirm the right affiliate moved.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, Make runs it whenever Tapfiliate calls the webhook. Each module run counts as one operation on your Make plan.

Triggers

What can start a Tapfiliate scenario?

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

Tapfiliate1Watch Affiliate Prospects

Watch Affiliate Prospects

Instant trigger

In Make“Triggers when a new affiliate prospect is created.”

A new affiliate prospect is created in Tapfiliate and this trigger hands their record straight to your scenario. It fits programs that screen people before letting them promote anything, since you see each applicant while they are still a prospect.

How it fires
instant. Tapfiliate calls Make through a webhook as soon as the prospect exists, and Make adds that webhook for you.
When to use it
you want each applicant logged in a review sheet or posted to your partnerships channel.
Watch out
a prospect is not a full affiliate yet; for the promoted account, pick Watch Promoted Affiliate Prospects.
Tapfiliate2Watch Approved Affiliates in Program

Watch Approved Affiliates in Program

Instant trigger

In Make“Triggers when an affiliate is approved for one of your programs.”

Approval is the moment a partner can actually start earning, and this trigger catches it for any of your programs. Your scenario receives the affiliate right after the yes, which makes it the natural start for welcome steps.

How it fires
instant. Tapfiliate warns Make through a webhook as soon as the approval happens.
When to use it
sending a welcome kit, adding the partner to your newsletter tool, or placing them in a group with Set Affiliate Group.
Watch out
it reacts to approvals, not sign-ups; for brand new accounts use Watch New Affiliates.
Tapfiliate3Watch Conversions

Watch Conversions

Instant trigger

In Make“Triggers when a new conversion is created.”

Each new conversion in Tapfiliate, the sale or signup credited to a partner, lands in your scenario through this trigger. It is the one most programs start with, because conversions are where commissions and questions come from.

How it fires
instant. Tapfiliate calls Make by webhook the moment the conversion is created.
When to use it
alerting finance, copying the conversion into a revenue sheet, or preparing an approval step with Update Commission Approval Status.
Watch out
if a scenario also runs Create a Conversion, test with Run once so the two do not feed each other.
Tapfiliate4Watch Customers

Watch Customers

Instant trigger

In Make“Triggers when a new customer is created.”

Tapfiliate tracks customers referred by partners, and this trigger fires when a new one is created. Your scenario then knows which person arrived through the program, as soon as they exist in Tapfiliate.

How it fires
instant. Tapfiliate notifies Make through a webhook as soon as the customer record appears.
When to use it
tagging referred customers in your CRM so sales knows a partner sent them.
Watch out
a customer created by your own Create a Customer module will fire it too, so keep those two in separate scenarios with a clear purpose.
Tapfiliate5Watch New Affiliates

Watch New Affiliates

Instant trigger

In Make“Triggers when a new affiliate account is created.”

This one watches the affiliate accounts themselves: every time a new account is created in Tapfiliate, the scenario gets it. It is broader than the program triggers, since it does not wait for someone to join a specific program.

How it fires
instant. Tapfiliate pings Make through a webhook as soon as the account exists.
When to use it
building a partner directory in Airtable or a sheet, or starting onboarding before any program choice.
Watch out
an account created through Create an Affiliate also counts, so keep the loop in mind when you combine both.
Tapfiliate6Watch New Affiliates in Program

Watch New Affiliates in Program

Instant trigger

In Make“Triggers when an affiliate is added to a program.”

When an affiliate is added to one of your programs, this trigger passes them along. If you run several programs, say one for creators and one for agencies, that is the signal that tells you which door they came through.

How it fires
instant. Tapfiliate calls Make through a webhook as soon as the affiliate joins the program.
When to use it
sending program-specific resources or notifying the manager of that program.
Watch out
being added is not the same as being approved; if approval matters, choose Watch Approved Affiliates in Program instead.
Tapfiliate7Watch Payments

Watch Payments

Instant trigger

In Make“Triggers when a new affiliate payment is created.”

Payouts to partners are the part accountants care about most, and this trigger reports each new affiliate payment Tapfiliate creates. Your scenario receives it, ready to be filed or announced.

How it fires
instant. Tapfiliate sends the event to Make through a webhook as soon as the payment is created.
When to use it
logging payouts in your bookkeeping sheet or emailing the partner a thank-you.
Watch out
the integration only watches payments; no listed module creates or edits one, so that part stays in Tapfiliate or goes through Make an API Call.
Tapfiliate8Watch Promoted Affiliate Prospects

Watch Promoted Affiliate Prospects

Instant trigger

In Make“Triggers when a new affiliate prospect is promoted to affiliate.”

Promotion turns a prospect into a real affiliate, and this trigger fires at that exact step. The scenario gets someone you already screened, now allowed to share links.

How it fires
instant. Tapfiliate calls Make by webhook as soon as the prospect is promoted.
When to use it
closing the loop on an application flow started with Watch Affiliate Prospects, for example by updating the applicant's row from pending to accepted.
Watch out
pair it with the prospect trigger in two separate scenarios rather than guessing which event came in.
Modules

What can Make do in Tapfiliate?

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

Tapfiliate1

Create a Conversion

Action

In Make“Creates a conversion.”

Records a conversion in Tapfiliate from outside, so a sale that happened in another tool still earns the partner their credit. The scenario usually starts with the other app's trigger.

When to use it
your checkout or billing app sees the sale first and Tapfiliate would otherwise miss it.
Watch out
avoid running it in a scenario that starts with Watch Conversions, or each new conversion would create another.
Tapfiliate2

Create a Customer

Action

In Make“Creates a customer.”

Adds a customer to Tapfiliate, straight from another tool. Handy when the signup happens in a tool Tapfiliate does not see directly, like a trial form.

When to use it
a referred visitor starts a free trial in your product and you want Tapfiliate to know about them.
Watch out
Watch Customers will fire on these too, which is fine as long as the two scenarios do different jobs.
Tapfiliate3

Create an Affiliate

Action

In Make“Creates an affiliate.”

Opens an affiliate account in Tapfiliate from data your scenario already holds. Partners recruited elsewhere, through a form or a signed agreement, get their account without anyone typing it again.

When to use it
your partner application lives in a form tool and approved rows should become accounts directly.
Watch out
if you only want to screen people first, Create an Affiliate Prospect is the gentler choice.
Tapfiliate4

Create an Affiliate Prospect

Action

In Make“Creates an affiliate prospect.”

Puts someone in Tapfiliate as a prospect, a candidate who is not yet allowed to promote. You keep the review step while skipping the manual entry.

When to use it
leads from a webinar or an event registration list should enter your screening queue in Tapfiliate.
Watch out
the prospect still needs promoting before earning anything; Watch Promoted Affiliate Prospects tells you when that happens.
Tapfiliate5

Delete a Conversion

Action

In Make“Deletes a conversion.”

Removes a conversion from Tapfiliate. It is the cleanup tool for test orders, duplicates or refunds that should never have counted toward a partner.

When to use it
your billing tool flags a refund and the linked conversion should disappear from the program.
Watch out
a deletion is hard to undo, so try it on a test record with Run once and consider Update Commission Approval Status when you only want to refuse the commission.
Tapfiliate6

Delete a Customer

Action

In Make“Deletes a customer.”

Erases a customer record in Tapfiliate. Useful when a data request or a test run leaves a customer that should not stay tied to your program.

When to use it
someone asks for their data to be removed and your privacy scenario cleans every tool at once.
Watch out
if you only want to cancel the customer without erasing the record, Update Customer Status is safer.
Tapfiliate7

Delete an Affiliate

Action

In Make“Deletes an affiliate.”

Removes an affiliate account from Tapfiliate. It closes the loop when a partnership ends or when a duplicate account slipped in through a form.

When to use it
a contract is terminated in your CRM and the partner should leave the program too.
Watch out
treat this as permanent; run Get an Affiliate first to check you hold the right person before the delete step runs.
Tapfiliate8

Get a Conversion

Action

In Make“Gets information about a conversion.”

Fetches the details of one conversion you already know about. Other modules often hand you only a reference, and this step fills in the rest before you act.

When to use it
a support ticket mentions a conversion and you want its full record pasted into the reply draft.
Watch out
it reads a single conversion; to browse several, List Conversions is the right module.
Tapfiliate9

Get a Customer

Action

In Make“Gets information about a customer.”

Reads one customer's record from Tapfiliate. It gives your scenario the full picture of a referred buyer so the next module can decide what to do with them.

When to use it
before changing a customer's status, you want to check their record and share it in your team chat.
Watch out
you need to know which customer to ask for; without that, start from List Customers.
Tapfiliate10

Get an Affiliate

Action

In Make“Gets information about an affiliate.”

Pulls the full profile of a single affiliate. A trigger or a form often carries only an identifier, and this module turns it into something your team can read.

When to use it
a partner writes to support and the scenario enriches the ticket with their Tapfiliate profile.
Watch out
pair it with a delete or an update to confirm the target first, and keep in mind each call costs one operation.
Tapfiliate11

Get Metadata

Action

In Make“Gets the metadata of the selected object.”

Reads the metadata stored on the object you select in Tapfiliate. Metadata is your own extra information, such as a source channel or an internal code, kept alongside the record.

When to use it
routing depends on a tag you set earlier with Set Metadata, like the team that owns a partner.
Watch out
it only returns what someone stored, so an empty result usually means the tag was never written.
Tapfiliate12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Tapfiliate API using the connection you already made. It is the escape hatch when the listed modules do not cover a task.

When to use it
you need something outside the 30 modules, such as working on payments or searching prospects, which no listed module does.
Watch out
you write the request yourself, so keep the Tapfiliate API documentation open and test with Run once before going live.
Tapfiliate13

Set Affiliate Group

Action

In Make“Sets the affiliate group of an affiliate.”

Assigns an affiliate to a group in Tapfiliate. Groups are how many programs separate tiers, regions or partner types without building separate programs.

When to use it
a partner is approved and should start in your entry tier, or hits a milestone tracked in another tool and moves up.
Watch out
create the groups in Tapfiliate first; the module places people, it does not invent the tier.
Tapfiliate14

Set Metadata

Action

In Make“Sets the metadata of the selected object.”

Writes metadata on the object you choose, so Tapfiliate keeps extra context from your other tools. Think of it as a sticky note that later scenarios can read back.

When to use it
you want to remember which campaign or account manager brought an affiliate in.
Watch out
agree on the key names with your team, because Get Metadata only finds what was written under the exact same key.
Tapfiliate15

Set Parent Affiliate

Action

In Make“Sets the parent affiliate for an affiliate (MLM).”

Links an affiliate to a parent affiliate, the structure Tapfiliate uses for multi-level (MLM) programs. Tapfiliate then knows who recruited whom.

When to use it
a new partner signs up through an existing one's invitation and you know the referrer from your form.
Watch out
it only makes sense if your program uses multi-level commissions; otherwise leave it out.
Tapfiliate16

Update a Conversion

Action

In Make“Updates information about a conversion.”

Changes an existing conversion's information. Orders get edited after the fact, and this keeps the partner's record aligned with what the customer finally paid.

When to use it
an upgrade or a partial refund in your billing tool should adjust the matching conversion.
Watch out
approving or refusing the commission is a separate job; Update Commission Approval Status handles it.
Tapfiliate17

Update a Customer

Action

In Make“Updates a customer's information.”

Edits a customer's details in Tapfiliate. When your CRM or product holds the fresher version of a customer, this module carries it over.

When to use it
a customer changes plan or contact details in your app and Tapfiliate should reflect it.
Watch out
cancelling is not an edit here; to cancel or reactivate, use Update Customer Status instead.
Tapfiliate18

Update Commission Approval Status

Action

In Make“Approves or disapproves a commission.”

Approves or disapproves a commission. It lets the decision happen wherever your team already reviews things, and Tapfiliate follows.

When to use it
a refund window closes in your billing tool, or a reviewer ticks a box in a sheet, and the commission should be settled.
Watch out
run it only after a real check, because the scenario decides for you; test it first on a test commission with Run once.
Tapfiliate19

Update Customer Status

Action

In Make“Cancels or uncancels a customer.”

Cancels or uncancels a customer in Tapfiliate. Subscription businesses use it to keep Tapfiliate in step when a customer leaves or comes back.

When to use it
your billing tool reports a cancelled or reactivated subscription for a referred customer.
Watch out
this changes status only; details like the email stay under Update a Customer.
Tapfiliate20

List Affiliates

Search

In Make“Retrieves a list of affiliates.”

Returns a list of affiliates from Tapfiliate, each one as its own bundle that flows to the next module. It is the starting point for bulk jobs across your partner base.

When to use it
you want a full partner export in a sheet or need to tag everyone with Set Metadata.
Watch out
every affiliate in the list runs the following modules once, so a large base consumes many operations.
Tapfiliate21

List Conversions

Search

In Make“Retrieves a list of conversions.”

Retrieves a list of conversions, one bundle per conversion, which is how you look back at history rather than react to new events.

When to use it
preparing a payout review or rebuilding a revenue sheet after changing its structure.
Watch out
the search may return zero, one or many results; add an Aggregator from Make's tools if you want one summary instead of many rows.
Tapfiliate22

List Customers

Search

In Make“Retrieves a list of customers.”

Pulls a list of customers from Tapfiliate, each passed on as its own bundle. It helps when you need to act on customers you did not catch with the trigger.

When to use it
syncing all referred customers into a new CRM before Watch Customers takes over for new ones.
Watch out
the result can be empty, which is normal for a young program, so test with Run once and read the output.
Need help

Need help automating Tapfiliate with Make?

A person reads every message.

FAQ

Tapfiliate and Make: common questions

01Is the Tapfiliate Make integration free?
Yes, on the Make side. Tapfiliate is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Its minimum gap between scheduled runs is 15 minutes, although Tapfiliate triggers are instant and do not depend on that clock. Paid plans (Core, Pro, Teams, Enterprise) lift the scenario cap, allow 40 minutes per run and count usage in credits, meaning operations per month. Your Tapfiliate subscription is a separate matter.
02What does connecting Tapfiliate to Make require?
A Tapfiliate account you can log in to and your Tapfiliate domain. The Make documentation lists no other prerequisite. You add a Tapfiliate module, click Add next to the Connection field, name the connection and save it. Make then asks for the domain, you click Continue, and Tapfiliate shows an approval screen where you click Allow. The connection is shared by every Tapfiliate module in your Make account, so you only do this once per Tapfiliate account.
03Do Tapfiliate triggers in Make fire in real time?
Yes. All 8 Tapfiliate triggers are instant: Tapfiliate calls Make through a webhook as soon as the event happens, whether it is a new conversion, a payment or an approved affiliate. Make creates that webhook in Tapfiliate automatically when you add the trigger, so there is nothing to configure on the Tapfiliate side. Instant triggers show a lightning badge in the editor. The default 15-minute schedule of a new scenario applies to scheduled triggers, which this app does not have.
04What if a Tapfiliate module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Tapfiliate API through the connection you already have. That covers the gaps in the list, for example payments, which the integration can watch but not create or edit, or prospects, which have no search module. You write the request yourself from the Tapfiliate API docs, so test it with Run once. For errors in the scenario itself, the troubleshooting guides are a good next stop.
05Make or n8n for Tapfiliate?
It depends on where your team already builds automations. Tapfiliate exists in both tools, so the choice is less about the app and more about the platform. On Make you get 30 ready modules, 8 of them instant triggers, and a visual editor where Make sets up the webhooks for you. If your other workflows already live in n8n, staying there keeps everything in one place. The n8n vs Make comparison linked above goes through the criteria one by one.
Same platform

Other docs you might need on this stack.

Browse all integrations