FlowRunner
PricingContact
Theme
Start Free

Run a Shopify affiliate programme with the GoAffPro Admin API, onboarding and approving affiliates and recording referred orders. Agents pay and police the programme against real order data.

18 actions API key available
GoAffPro website ↗ Platform Documentation ↗ Capability data verified 2026-08-02
An affiliate application lands on your own application form
Agent reads the applicant's name, email, promotion channel and requested coupon code
Agent runs Search Affiliates to see whether this person already holds an account under another address
Agent confirms the requested referral code and coupon are not already claimed
Agent calls Create Affiliate to hold the applicant in an unapproved state
Agent posts the application, the channel they promote on, and the duplicate check result to the growth channel
The program owner approves or rejects, and only then does the agent call Update Affiliate to set the approval status and hand back the referral link

What This Integration Enables

GoAffPro is an affiliate program that sits on top of a Shopify store, which makes it a different proposition from a standalone referral widget. The referee is the store's own order data. Commission is computed against real orders, orders can be recalculated when your commission rules change, and every reward an affiliate accrues traces back to a line in the order list. That is the part worth automating: not the sending of links, but the policing of the money.

FlowRunner agents work the whole program surface through connectors built and verified against the GoAffPro Admin API. An agent can onboard affiliates from your own application form, search the roster before creating a duplicate, record orders that arrived through a channel GoAffPro does not watch, recalculate commission after a rate change, credit manual bonuses, and assemble a payout run from the amounts currently owed and the withdrawal requests sitting in the affiliate portal. What it does not do is decide who joins the program or whose commission clears. Those are the two moments where a person should be looking.

Without FlowRunner

Applications queue up Applications sit in a form inbox while the store keeps taking orders
Approval by gut feel Nobody checks whether the applicant already holds an account or a competing coupon
Payout run assembled by hand Balances owed and withdrawal requests are reconciled into a spreadsheet each cycle

With FlowRunner

Screened on arrival Every application arrives with the duplicate check and coupon availability already run
Approval is a decision, not a chore The owner sees the evidence assembled and makes one call
Payout run built from source data Amounts owed and payment requests are pulled straight from GoAffPro

Use Case Scenarios

Affiliate intake from your own application form

You do not want a public self-signup that anyone can walk into, so applications arrive through a Typeform instead. When one lands, the agent reads the applicant's details, runs Search Affiliates against their email and against the referral code they asked for, and creates the account with Create Affiliate in an unapproved state so nothing can be earned yet. It then posts the whole picture into the growth channel: who applied, where they promote, whether the email matches an existing affiliate, and whether the requested coupon is free. The owner approves. The agent sets the approval status with Update Affiliate and returns the working referral link.

Attributing orders GoAffPro never sees

Not every sale comes through the storefront. Wholesale orders, phone orders, and orders placed on a second platform never reach GoAffPro on their own, so affiliates who drove them go unpaid and eventually go quiet. An agent watches the other channel, matches the order to an affiliate by referral code or affiliate ID, and calls Create Order to attribute the sale. When you change an affiliate's rate or restructure a tier in List Groups, a follow-up flow calls Recalculate Order Commission across the affected orders so the numbers reflect the rules you actually have now rather than the ones you had at checkout.

Assembling the payout run

On payout day the agent calls List Pending Payments to pull what each affiliate is owed and the cut-off date the totals were struck at, then List Payment Requests to pull the withdrawals affiliates have submitted through their portal. It writes both into a Google Sheets tab, one row per affiliate, with a link to that affiliate's commission history from List Affiliate Commissions. Before any commission is approved with Update Order, the agent flags anything that fell inside the refund window and asks the finance owner what to do with it.

Human-in-Loop Highlight

The gate on this connector is affiliate approval, not payout. Update Affiliate flips an application from unapproved to approved, and that single field change is not a one-time payment. From the moment it lands, that person earns commission on every future order carrying their code, indefinitely, without anyone reviewing the next one. An agent that approves applications on a keyword match will hand a permanent revenue share to a coupon-scraping site that would have taken the sale anyway. So the agent stops. It posts the application into the growth channel with the duplicate check already run and asks: "Approve this affiliate? Email matches an existing account created in March. They promote on a coupon aggregator, and the code they requested overlaps an active site-wide discount." The owner answers. The agent applies the answer with Update Affiliate. Nobody starts earning a share of your revenue because a workflow was in a hurry.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

18 actions

Affiliates

6
  • List Affiliates List the affiliates in the store, filtered by approval status, email, referral code or coupon, or by created and updated date ranges. Used to sync the roster into your own systems or to resolve an affiliate ID.
  • Search Affiliates Search affiliates by keyword across chosen fields, with control over whether the keyword must be contained in, start, or end the value. Used as the duplicate check before an application is accepted.
  • Create Affiliate Create an affiliate account, optionally setting their referral code, a personal coupon and its discount, their approval status, and the affiliate who recruited them. Used to onboard from your own application form rather than a public signup page.
  • Update Affiliate Update an existing affiliate's details or approval status. Only the fields supplied are changed, so the agent can flip approval or correct one contact field without resending the record.
  • Delete Affiliate Permanently delete an affiliate account. This cannot be undone. Used to honour an erasure request or clear a test account.
  • List Affiliate Commissions List the commissions a single affiliate has earned. Used to show someone their earnings history or reconcile what they are owed before a payout run.

Orders and Commission

4
  • List Orders List referred orders with their total, attributed affiliate and calculated commission, filtered by affiliate, approval status, customer email or creation date. Used to audit attributed sales.
  • Create Order Record a referred order against an affiliate so commission is calculated, attributing by affiliate ID or by the referral code the customer used. Used to feed sales from a channel GoAffPro does not integrate with directly.
  • Update Order Update an order's commission approval status, commission amount or customer details. Used to approve commission once the refund window closes, or to reject it when an order is cancelled.
  • Recalculate Order Commission Recalculate the commission on an order against your current commission rules. Used after changing an affiliate's rate or restructuring the program.

Rewards and Payouts

4
  • List Rewards List rewards credited to affiliates, including signup bonuses, sale commissions, recruitment bonuses and target bonuses, filtered by type, status, affiliate or order. Used to see everything an affiliate has earned beyond straight order commission.
  • Create Reward Credit a reward to an affiliate, such as a manual bonus or an adjustment outside normal order commission, with the amount, type and starting status. Used for negotiated one-off payments.
  • List Pending Payments List the amounts currently owed to each affiliate with the cut-off date the totals were calculated to. Used to prepare a payout run.
  • List Payment Requests List withdrawal requests affiliates have submitted through their portal, showing which are in progress, paid or rejected. Used to work the withdrawal queue as requests arrive.

Program Structure

1
  • List Groups List the affiliate groups configured in the store, which hold the tiered commission rules affiliates inherit. Used to review commission tiers or resolve a group before assigning members.

Webhooks

3
  • List Webhooks List the webhooks registered on the store with each one's topic and delivery URL. Used to review which external systems are subscribed to store events.
  • Create Webhook Register a webhook so GoAffPro posts store events to a URL you control. The topic is free text because GoAffPro does not publish a fixed list of topic values.
  • Delete Webhook Remove a registered webhook so GoAffPro stops posting to that URL. Used when retiring an integration endpoint.

Frequently Asked Questions

What can FlowRunner do with GoAffPro?

FlowRunner agents can run List Affiliates, Search Affiliates, and Create Affiliate in GoAffPro, plus 15 more actions.

Does connecting GoAffPro to FlowRunner require OAuth?

No. GoAffPro connects to FlowRunner with an API key, no OAuth flow required.

Can GoAffPro trigger a FlowRunner workflow automatically?

GoAffPro doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with GoAffPro

$100 in credits. No card required. Connect in minutes.