Viral Loops
Loyalty & ReferralRun referral and giveaway campaigns with the Viral Loops API, registering participants and returning their referral codes. Agents credit referrals off confirmed conversions.
What This Integration Enables
Viral Loops keeps a ledger of promises. Every reward a participant earns sits in a pending state until somebody says it was delivered, and the platform tracks pending and given rewards as separate, queryable things. That is the design decision that distinguishes it, and it maps almost exactly onto the problem most referral programmes actually have, which is not counting referrals. It is knowing which prizes you owe, which you have paid, and whether the two lists agree.
Two other pieces reinforce the same idea. Track Conversion means a referral does not become real until the referred person completes the action you actually care about, so a wave of signups that never convert does not generate a wave of rewards you owe. Flag Participants gives you somewhere to record a fraud concern inside the platform rather than in a colleague's memory, so a suspect entrant can be excluded from a prize draw by the system that runs the draw.
Around those, the connector covers the everyday work. Agents register participants and return their referral code, update a participant's details and standing with the option to suppress campaign emails while doing it, and read a full participant record with the referral tree and reward state attached. They can pull a leaderboard rank along with a suggestion of how many more referrals would move that person up, and run a free-text search across participants filtered by conversion status and by whether they arrived organically or through a referral. Headline campaign statistics and the full campaign configuration are both readable too.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The referral becomes real at the purchase, not the signup
Someone joins through a referral link and does nothing for two weeks. Then they buy. The agent picks the payment up from Stripe and calls Track Conversion with the conversion value, which is the moment the referral counts. Get Pending Rewards on the referrer then shows what that conversion just unlocked. Nothing was owed while the referred person was only a signup, and now something is, which means the reward ledger and the revenue report tell the same story instead of two different ones.
Fulfilment closed in the right order
Get Pending Rewards returns what a participant has earned but not yet claimed. The agent reads that list, checks Get Given Rewards so the same prize does not go out twice, sends the prize through Gmail or hands it to a fulfilment step, and only then calls Redeem Reward. The order matters. Redeeming first would tell the participant they have received something that is still sitting in a queue, and their pending list would go quiet while they wait for a prize the system already considers delivered.
Fraud review that the prize draw respects
Before a draw, the agent runs Search Participants filtered on conversion status and referral origin, pulls the outliers, and checks each with Get Participant Data to see the referral tree and the timing. Anything that looks like duplicate or manufactured entries goes to a human with the evidence attached. On a decision, the agent calls Flag Participants to record it inside Viral Loops, identifying each person by email or referral code. The exclusion is now recorded in the platform that runs the draw rather than in a message thread somebody has to remember to check.
Human-in-Loop Highlight
Redeem Reward is the gate, and it is a gate about honesty rather than about spend. Redeeming marks a reward as claimed and moves it out of the participant's pending list, and this connector has no un-redeem action. If the agent redeems before the prize is genuinely in the winner's hands, the record now says a promise was kept that was not. The participant sees an empty pending list, has nothing to point at when they ask where their prize went, and the one system that knew you owed them something has forgotten. That is worse than a delay.
So the agent does everything up to delivery and then stops. It tracks the conversion, reads the pending rewards, checks the given rewards for a duplicate, dispatches the prize, and posts a message asking for confirmation: "Dana Reyes earned the 50 dollar credit after Northwind converted on Tuesday. Credit applied to their account manually this morning by the support team. Confirm delivered and close the pending reward, or leave it open?" A person confirms, and only then does Redeem Reward fire. Flag Participants gets the same treatment in the other direction, because flagging someone for review is a step toward excluding a real person from a prize they may have earned fairly. Both are the automation exceptions of a referral programme: rare, consequential, and exactly the moments where a human-in-the-loop step earns its place while the thousands of registrations and rank lookups run untouched.
Agent Capabilities
12 actionsCampaign
2- Get Campaign Stats Retrieves headline statistics for the campaign, returning the total number of participants captured and how many referrals have been made. Used for a quick performance read without pulling the participant list.
- Get Campaign Data Retrieves the full configuration of the campaign, including its type, widgets, styles, email service settings, sharing options and consent text. Used to inspect how a campaign is set up before wiring automations to it.
Participants
7- Register Participant Registers someone in the campaign and returns their unique referral code, optionally attributing them to an existing participant's referral code so the referral is credited. Used when a visitor joins the giveaway or waitlist from your own form.
- Update Participant Updates a participant's name, referral count, conversion count or stored extra data, identified by email or referral code, with the option to suppress campaign emails and downstream integrations while the change is made. Used to correct records or adjust standings without triggering a notification the participant would not understand.
- Get Participant Data Retrieves a participant's full record, including their referral code, rank, points, referred leads, who referred them, and their redeemed and pending rewards. Used to show someone their personal standing, and to assemble the referral tree during a fraud review.
- Get Participant Rank Retrieves a participant's leaderboard position with their total referrals and points, plus a suggestion of how many more referrals would move them up. Used to power a live rank display or a nudge email that tells someone exactly how close they are.
- Search Participants Searches campaign participants by free text, conversion status and whether they arrived organically or through a referral, paged with an offset and limit. Used to segment the audience, export a filtered list, or isolate the outliers ahead of a prize draw.
- Track Conversion Marks a participant as converted, recording that they completed the action the campaign rewards and optionally the value of that conversion. Used when a referred signup makes a purchase or finishes onboarding, and the point at which a referral stops being a signup and becomes an outcome.
- Flag Participants Flags one or more participants for review, marking suspected fraudulent or duplicate entries so they can be excluded from prize draws, identifying each person by email or referral code. Used after a person has reviewed the evidence, not before.
Rewards
3- Get Pending Rewards Retrieves the rewards a participant has earned but not yet claimed. Used to show someone what is waiting for them, and to drive the fulfilment step in a flow.
- Get Given Rewards Retrieves the rewards already delivered to a participant, so a flow can confirm what has been handed out before issuing anything further. Used as the duplicate guard ahead of any dispatch.
- Redeem Reward Redeems a specific pending reward for a participant, marking it as claimed. Used once the prize has actually been delivered, so the pending list stays accurate. There is no reverse of this call, which is why it belongs behind a confirmation.
Frequently Asked Questions
What can FlowRunner do with Viral Loops?
FlowRunner agents can run Get Campaign Stats, Get Campaign Data, and Register Participant in Viral Loops, plus 9 more actions.
Does connecting Viral Loops to FlowRunner require OAuth?
No. Viral Loops connects to FlowRunner with an API key, no OAuth flow required.
Can Viral Loops trigger a FlowRunner workflow automatically?
Viral Loops doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Viral Loops
$100 in credits. No card required. Connect in minutes.