ActionTapfiliateUpdated May 2026

How do I attach metadata to a Tapfiliate affiliate?

Short answer: Drop the "Tapfiliate → Add Affiliate Metadata" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 Tapfiliate actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Name name	string	Required	Name

Sample request

{
  "name": "{{trigger.name}}"
}

Returns

{}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Add Affiliate Metadata.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Tapfiliate

2 Google Sheets triggers

HubSpot → Tapfiliate

18 HubSpot triggers

FAQ

Questions about Add Affiliate Metadata.

What does the Add Affiliate Metadata action do in Tapfiliate?

Attaches a custom metadata key/value pair to an affiliate in Tapfiliate. Use it to store internal IDs, tier flags, or marketing-source tags alongside each affiliate.

What inputs does Add Affiliate Metadata require?

Required: Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Tapfiliate returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add Affiliate Metadata support batch operations?

Yes. Run Add Affiliate Metadata inside a Loop node to process arrays. Tiny Command handles Tapfiliate's rate limits automatically so you don't have to throttle manually.

More actions