Tapfiliate n8n integrationAutomate Tapfiliate with n8n.
Nobody should be keying new partners into an affiliate dashboard by hand. The Tapfiliate n8n integration ships inside n8n and opens up 12 operations across 3 resources: affiliates, the metadata attached to them, and their standing inside a program. There is no trigger node, so a Schedule or a Webhook starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Tapfiliate n8n integration actually cover?
Tapfiliate keeps your affiliates, their details and the programs they belong to. The n8n node talks to that account through the Tapfiliate API and gives a workflow three handles: the affiliate record itself, the free-form metadata you hang on it, and the link between an affiliate and a program. Twelve operations, three resources, no event listener on the Tapfiliate side.
Start with partner onboarding, because that is where the manual work piles up. A recruitment form drops a name and an email into the workflow, affiliate.create registers the person, then programAffiliate.add places that affiliate in the right program with the Approved flag and a Coupon if the campaign uses one. A message to Slack closes the loop so the partnership manager knows a new name landed.
The second job is keeping context that Tapfiliate alone would lose. Metadata is a plain key and value pair, which is enough to store where a partner came from or which manager owns the relationship. affiliateMetadata.add writes it at signup, affiliateMetadata.update corrects it later, and a scheduled run of affiliate.getAll filtered by Affiliate Group ID rebuilds the same picture inside HubSpot so the sales side sees the partner too.
The third one sits on the commerce side. An order in WooCommerce or a payment in Stripe carries a referral code; affiliate.getAll with the Referral Code filter finds the matching partner, and programAffiliate.get confirms that this affiliate really belongs to the program before the workflow does anything else with the order.
When an endpoint of the Tapfiliate API is not among these 12 operations, the HTTP Request node calls it directly and reuses the very same credential through its predefined authentication, so nothing has to be rebuilt.
Two things shape how you design the workflow. Tapfiliate has no trigger node in n8n, so a run starts from a Schedule Trigger at a fixed interval, from an n8n Webhook called by another service, or from the trigger of another tool. And on the two list operations, Return All pages through the API until every affiliate is back, while leaving it off caps the run at Limit. The n8n review goes deeper on how those runs are billed and hosted.
How do you connect Tapfiliate to n8n?
- 01
Grab the API key from Tapfiliate
The node authenticates with a single API key, and that key lives in your Tapfiliate account rather than in n8n. Open Profile Settings in the Tapfiliate app, then the API Key entry. Tapfiliate also publishes a support article on finding the account ID and the API key if the menu has moved since you last looked. Copy the value somewhere you can paste from in a moment.
- 02
Create the credential in n8n
In n8n, open the Credentials menu and add a new Tapfiliate credential. There is no authentication selector on the node itself, so the form asks for the API Key and nothing else. Paste the value and save. A credential is created once and reused by every workflow in the instance, which means you never paste that key into a node again.
- 03
Pick a resource and an operation
Add the Tapfiliate node to a canvas. It offers the credential you just saved in its dropdown, then asks for a resource, Affiliate, Affiliate Metadata or Program Affiliate, and for the operation inside it. Program fields come as a list read from your account, so you choose the program by name instead of hunting for its identifier. Run the node once with a real value to see the shape of what comes back.
What the Tapfiliate node can do
The Tapfiliate node exposes 12 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
| Resource | Create | Get | Get Many | Update | Delete | Add | Remove | Approve | Disapprove |
|---|---|---|---|---|---|---|---|---|---|
| Affiliate | ✓ | ✓ | ✓ | ✓ | |||||
| Affiliate Metadata | ✓ | ✓ | ✓ | ||||||
| Program Affiliate | ✓ | ✓ | ✓ | ✓ | ✓ |
Affiliate
4 operationsCreate an affiliate
affiliate.createWhat you see in n8n
Notes & use cases
Registers a new affiliate in the Tapfiliate account and hands the created record back to the workflow.
Key parameters
- Email: the affiliate's email, shaped like
name@email.com, usually mapped from the previous node with{{ $json.field }}. - First Name and Last Name: the affiliate's firstname and lastname, both required, so an empty value from the form stops the node.
- Additional Fields: Company Name for the affiliate's company data, and Address, filled through its own sub-form.
Delete an affiliate
affiliate.deleteWhat you see in n8n
Notes & use cases
Removes one affiliate from the account. A single identifier, nothing else, which makes it the last node of an offboarding branch rather than something you call casually.
Key parameters
- Affiliate ID: the ID of the affiliate, required, so the node stops if the branch above passed an empty value.
Get an affiliate
affiliate.getWhat you see in n8n
Notes & use cases
Reads one affiliate by ID and puts that record into the workflow, which is what you need before branching on anything about that partner.
Key parameters
- Affiliate ID: the ID of the affiliate, required. Coming from an earlier node, it is mapped with an expression such as
{{ $json.field }}.
Get many affiliates
affiliate.getAllWhat you see in n8n
Notes & use cases
Lists the affiliates of the account, one item per affiliate, with six filters to narrow the set before the data reaches the next node.
Key parameters
- Return All: on, n8n walks through every page of the API; off, the run stops at Limit.
- Filters: Affiliate Group ID retrieves affiliates for a certain affiliate group, Parent ID retrieves children for a certain parent affiliate, Referral Code matches the value of ref= in a referral link, plus Email, Click ID and Source ID.
Affiliate Metadata
3 operationsAdd metadata to an affiliate
affiliateMetadata.addWhat you see in n8n
Notes & use cases
Attaches metadata to an affiliate that already exists, which is how you keep information Tapfiliate has no field for.
Key parameters
- Affiliate ID: the ID of the affiliate, required.
- Metadata: the meta data to attach, entered in the Add Metadata sub-form.
Remove metadata from an affiliate
affiliateMetadata.removeWhat you see in n8n
Notes & use cases
Drops one metadata entry from an affiliate. The operation works key by key, so the rest of what you stored on that partner stays untouched.
Key parameters
- Affiliate ID: the ID of the affiliate, required.
- Key: name of the metadata key to remove.
Update metadata for an affiliate
affiliateMetadata.updateWhat you see in n8n
Notes & use cases
Sets a new value on a metadata key of an affiliate, for the cases where the information itself changes rather than the partner.
Key parameters
- Affiliate ID: the ID of the affiliate, required.
- Key: name of the metadata key to update.
- Value: value to set for the metadata key.
Program Affiliate
5 operationsAdd a program affiliate
programAffiliate.addWhat you see in n8n
Notes & use cases
Places an existing affiliate inside one of your programs, which is the step that actually puts a partner to work.
Key parameters
- Program Name or ID: required. The ID of the program to add the affiliate to, visible in the URL when you view the program, or picked from the list.
- Affiliate ID: the ID of the affiliate, required.
- Additional Fields: Approved, an optional approval status, and Coupon, an optional coupon for this affiliate.
Approve a program affiliate
programAffiliate.approveWhat you see in n8n
Notes & use cases
Approves an affiliate for a program. Useful once a human has looked at the application, so the decision made in a chat thread lands in Tapfiliate instead of waiting for someone to log in.
Key parameters
- Program Name or ID: choose the program in the list, or pass an ID with an expression. The node does not mark it as required.
- Affiliate ID: the ID of the affiliate, also left optional by the node.
Disapprove a program affiliate
programAffiliate.disapproveWhat you see in n8n
Notes & use cases
The other side of the review: it disapproves an affiliate. Pair it with the approval branch so both outcomes of a decision are handled by the same workflow.
Key parameters
- Program Name or ID: selected from the list or given as an ID through an expression, and not flagged as required.
- Affiliate ID: the ID of the affiliate, equally optional on this operation.
Get a program affiliate
programAffiliate.getWhat you see in n8n
Notes & use cases
Reads one affiliate inside a given program. Both coordinates matter here: the same person can sit in several programs, and this operation answers about one of them.
Key parameters
- Program Name or ID: required, chosen from the list or supplied with an expression.
- Affiliate ID: the ID of the affiliate, required.
Get many program affiliates
programAffiliate.getAllWhat you see in n8n
Notes & use cases
Any roster built program by program starts here, and the affiliates attached to that one program come back as items, ready for an export or a count.
Key parameters
- Program Name or ID: required, so the operation always answers about a single program.
- Return All: on, every page of results comes back; off, Limit caps the number of affiliates returned.
- Filters: Affiliate Group ID, Email, Parent ID for children of a parent affiliate, and Source ID.
Need help automating Tapfiliate with n8n?
A person reads every message.
