FlowRunner
PricingContact
Theme
Start Free

Referral Factory

Loyalty & Referral

Build and run referral programs with Referral Factory, adding referrers and capturing referred leads. Agents issue rewards off verified referral events.

19 actions API key available
A scheduled sweep runs against a live campaign to find duplicate referrer records
Agent calls Search Referrers to group records that share an email address, a name or a signup window
Agent calls Search Leads on each candidate to see how many referred leads and qualified conversions sit behind it
Agent confirms the records belong to the same person rather than to two people at one company
Agent posts each duplicate pair with its referral link, lead count and share history to the program owner
The owner names the record that survives, and only then does the agent call Delete Referrer on the other

What This Integration Enables

Referral Factory is the referral program a marketing team builds without asking engineering for anything. The campaign page is hosted, the reward rules are configured in a UI, and the referrer's link, social sharing links and QR code are generated for them. That is a real advantage and it creates a specific gap: the moment your product knows something the hosted page does not, the program starts drifting. A signup that happened in your app rather than on the campaign page is unattributed. A customer whose spend decides a commission reward has a spend figure that lives in your billing system. A reward marked due stays due until a person marks it issued.

The API exists to close that gap, and FlowRunner agents are how you close it without writing an integration, using connectors built and verified against the Referral Factory API. An agent enrols customers as referrers and hands back their link and QR code, records referred leads that signed up outside the hosted page, feeds spend back with Update Reward Total Spend so commission rewards calculate on real revenue, and works the due-reward queue. Referral Factory's filter syntax is the quiet strength here: Search Campaigns, Search Referrers and Search Leads all accept field-level operators and ordering, so an agent can ask for everyone who qualified in a date range or every lead attached to one referrer rather than paging through 250 records at a time and filtering in the flow. That is what makes scheduled reconciliation practical rather than theoretical.

Without FlowRunner

Duplicate advocates split their credit The same customer signs up twice and their referrals land against two records
Rewards issued from a spreadsheet What is owed is copied out of the tool, worked by hand, and copied back
Revenue never reaches the reward rule Commission-based rewards calculate on a spend figure nobody feeds back in

With FlowRunner

Duplicates surfaced with the evidence Matching records arrive with their leads, links and share history side by side
Rewards worked from the due list The due queue drives the fulfilment run and each reward is closed in the tool
Revenue fed back automatically Spend from your billing system reaches the reward rule before the reward is calculated

Use Case Scenarios

Turning paying customers into referrers automatically

The best moment to ask someone to refer is right after they have bought. A Stripe payment succeeds, and the agent calls Get Campaign to read which extra fields the campaign collects, then Create Referrer with those fields populated from your CRM and the notify-by-email option set. Referral Factory returns the personal referral link, the social sharing links and the QR code, and the agent puts the link in the receipt email and the QR code in the packing slip. The advocate never fills in a form, because everything the form would have asked for was already known.

Attribution for signups that never touched the campaign page

Someone hears about you from a friend and signs up in your app rather than through the referral link. Without intervention that referral is invisible and the referrer is never rewarded, which is the most common way referral programs quietly die. Instead the agent captures the referrer identifier from a Typeform field or a signup question and calls Create Lead, identifying the referrer by email or referral code. Later, when the lead converts, the agent calls Update Reward Total Spend with the revenue from billing so any commission-based reward calculates on the real number rather than a default.

A fulfilment run that closes its own loop

Rewards do not deliver themselves. A weekly flow calls List Due Rewards, which returns each recipient, the reward value and the qualifying leads behind it. The agent delivers each one through Gmail or your gift card provider, then calls Issue Reward to move it into the issued list so it cannot be sent twice. List Issued Rewards feeds the finance reconciliation. Where a qualifying lead turns out to be a duplicate or the customer refunded, Cancel Reward takes it off the due list instead, which keeps the ledger honest rather than leaving stale obligations to be argued about later.

Human-in-Loop Highlight

Delete Referrer looks like a housekeeping action and behaves like a public one. Removing a referrer permanently removes their referral link, and by that point the link is not yours any more. It is in a WhatsApp thread, a newsletter, a Slack channel at their employer, printed on a QR code someone stuck to a noticeboard. Deleting the record does not recall any of that. It turns every share already in circulation into a dead URL, and anyone who clicks it becomes traffic nobody can attribute. That is why a duplicate-cleanup agent on this connector gathers evidence and then stops. It posts both records to the program owner with what each has actually done: "Two referrer records for [email protected] in the Spring Campaign. Record A was created in March, has 14 leads with 6 qualified, and its link appears in the newsletter that went out on the 12th. Record B was created last week, has 1 lead, 0 qualified. Keep A and delete B, keep both and merge the leads manually, or leave them?" The owner names the survivor. The agent deletes only what it was told to delete. The same gate belongs on Delete Lead, which withdraws referral credit a referrer has already seen in their dashboard.

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

Agent Capabilities

19 actions

Campaigns

3
  • List Campaigns List the referral campaigns on the account, each with its name, code, public URL, status and the form fields collected from referrers and referred people. Used to resolve the campaign ID that creating referrers and leads requires.
  • Get Campaign Retrieve a single campaign by numeric ID or short code with the full configuration, including the fields captured from the person referring and the person invited, plus branding assets. Used to discover which extra fields a campaign expects.
  • Search Campaigns Search campaigns using Referral Factory's filter syntax, matching on any campaign field with operators such as equals, contains or greater than, with ordering. Used when the plain list is too broad.

Referrers

6
  • List Referrers List the people referring others across your campaigns, each with their referral link, sharing links, QR code and signup details. Paginated up to 250 per page. Used to export advocates or resolve a referrer ID.
  • Get Referrer Retrieve a single referrer by ID with their referral link, social sharing links, QR code and any extra campaign fields they submitted. Used to show someone their personal referral assets.
  • Create Referrer Add someone to a campaign as a referrer and return their personal referral link and sharing assets, optionally notifying them by email and supplying the extra fields the campaign collects. Used when a customer opts into the program.
  • Update Referrer Update a referrer's name, email or extra field values, changing only what is supplied. Used to correct signup details without recreating the referrer and losing their link.
  • Delete Referrer Permanently remove a referrer from a campaign along with their referral link. This cannot be undone, and any share of that link already in circulation becomes a dead URL. Belongs behind an approval gate.
  • Search Referrers Search referrers using Referral Factory's filter syntax with field-level operators and ordering. Used to find advocates by email domain, campaign or signup date, and to detect duplicate records.

Leads

5
  • List Leads List the referred leads captured across your campaigns, each showing who referred them and whether they have qualified. Paginated up to 250 per page. Used to audit referral outcomes.
  • Get Lead Retrieve a single referred lead by ID with who referred them, when they signed up and whether they have qualified. The qualified timestamp is what marks a referral as successful.
  • Create Lead Record a referred lead against the person who referred them, identifying the referrer by one of their fields such as email or referral code. Used when someone signs up through a referral outside the hosted campaign page.
  • Delete Lead Permanently remove a referred lead, withdrawing the referral credit it gave the referrer. This cannot be undone. Used to clear duplicates or fraudulent signups.
  • Search Leads Search referred leads using Referral Factory's filter syntax with ordering. Used to find everyone who qualified in a date range or every lead attached to one referrer.

Rewards

5
  • List Due Rewards List rewards that have been earned and are waiting to be issued, across every campaign or one, each showing the recipient, the reward value and the qualifying leads behind it. Used to drive a fulfilment run.
  • List Issued Rewards List rewards already issued, across every campaign or one, with the date each was sent. Used to reconcile what has been paid out to advocates.
  • Issue Reward Issue a due reward to its recipient, marking it sent and moving it into the issued list. Used once you have delivered the gift card, credit or payment behind it, and the call that stops a reward being sent twice.
  • Cancel Reward Cancel a due reward so it is never issued, for example when the qualifying referral turns out to be fraudulent or the customer refunds. Used to keep the rewards ledger honest.
  • Update Reward Total Spend Record how much a referred lead has spent so commission-based rewards calculate the correct amount. Used when your billing system knows the revenue a referral generated.

Frequently Asked Questions

What can FlowRunner do with Referral Factory?

FlowRunner agents can run List Campaigns, Get Campaign, and Search Campaigns in Referral Factory, plus 16 more actions.

Does connecting Referral Factory to FlowRunner require OAuth?

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

Can Referral Factory trigger a FlowRunner workflow automatically?

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

Start building with Referral Factory

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