Tapfiliate MCP integration for AI agents.
Connect AI agents to Tapfiliate through 11 structured actions, including get affiliate, create affiliate, and create affiliate group. Review authentication…
- ACTION CONTRACTS
- 11
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Tapfiliate integration exposes
The Tapfiliate Agent App exposes 11 provider-backed actions for marketing and data work. Its current contract lets an authorized agent retrieve a single tapfiliate affiliate by affiliate id, create a tapfiliate affiliate with contact, company, address, and custom field data, and create a tapfiliate affiliate group. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Tapfiliate account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Tapfiliate capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_affiliateREADRetrieve a single Tapfiliate affiliate by affiliate id.
INPUTS: affiliate_id
create_affiliateWRITECreate a Tapfiliate affiliate with contact, company, address, and custom field data.
INPUTS: firstname / lastname / email / password / company
create_affiliate_groupWRITECreate a Tapfiliate affiliate group.
INPUTS: title
create_clickWRITECreate a Tapfiliate REST-only tracking click and return its click id for later conversion creation.
INPUTS: referral_code / source_id / meta_data / referrer / landing_page
create_conversionWRITECreate a Tapfiliate conversion using a documented referral, customer, click, coupon, tracking, or asset-source matcher.
INPUTS: override_max_cookie_time / referral_code / tracking_id / click_id / coupon
list_affiliate_groupsREADList Tapfiliate affiliate groups.
INPUTS: page
list_affiliatesREADList Tapfiliate affiliates with optional id, email, referral, and group filters.
INPUTS: page / click_id / source_id / email / referral_code
list_clicksREADList Tapfiliate Enterprise click records with optional program, affiliate, and date filters.
INPUTS: page / program_id / affiliate_id / date_from / date_to
list_commissionsREADList Tapfiliate commissions with optional affiliate, approval status, and paid filters.
INPUTS: page / affiliate_id / status / paid
list_conversionsREADList Tapfiliate conversions with optional program, external id, affiliate, date, and status filters.
INPUTS: page / program_id / external_id / affiliate_id / pending
list_programsREADList Tapfiliate programs with an optional asset filter.
INPUTS: page / asset_id
INPUT CONTRACTS
Know what the action needs before it runs.
get_affiliate
affiliate_idREQUIRED- The Tapfiliate affiliate id.
create_affiliate
firstnameREQUIRED- The affiliate's first name.
lastnameREQUIRED- The affiliate's last name.
emailREQUIRED- The affiliate's email address.
passwordOPTIONAL- The password for the new affiliate account.
companyOPTIONAL- The affiliate's company data.
create_affiliate_group
titleREQUIRED- The affiliate group title.
create_click
referral_codeREQUIRED- The affiliate referral code obtained from the referral URL.
source_idOPTIONAL- The source id used by the affiliate when present.
meta_dataOPTIONAL- Provider-defined metadata key-value pairs to send to Tapfiliate.
referrerOPTIONAL- The HTTP referrer used in Tapfiliate reporting.
landing_pageOPTIONAL- The current landing page used in Tapfiliate reporting.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Affiliate
Retrieve a single Tapfiliate affiliate by affiliate id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_affiliateControl Create Affiliate
Create a Tapfiliate affiliate with contact, company, address, and custom field data. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_affiliateVerify with List Affiliate Groups
List Tapfiliate affiliate groups. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_affiliate_groupsSAFETY BOUNDARY
Operate Tapfiliate with explicit limits
- Authorize Tapfiliate with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Tapfiliate rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Tapfiliate task completed successfully.
CONNECTION MODEL
API key
Tapfiliate API key sent in the X-Api-Key header. Find and manage it in Tapfiliate account settings: https://support.tapfiliate.com/en/articles/1441950-your-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 4
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Tapfiliate.