Prefinery
Loyalty & ReferralRun viral waitlists and referral launches with Prefinery, adding people to a waitlist and returning their share link and position. Agents move people up the list off verified referrals.
What This Integration Enables
Prefinery is a waitlist, and on a waitlist the ordering is the product. Everything else is packaging. People join, get a referral code and a share link, and climb by bringing other people, and the entire psychological contract is that the queue is fair and the position is real. That is a stronger constraint than it sounds, because it means the interesting operations here are not the ones that add people but the ones that change where people sit.
FlowRunner agents run both sides. Routine intake is fully automatic: Create User adds someone with their referrer attributed and returns their code, share link and queue position in the response, so your signup confirmation can quote all three without a second call. Verify User checks an invitation code at redemption time, Check In User marks someone as genuinely active once they start using the product, and Update User walks people through the status transitions from applied to invited as you open access. The suppression list is handled properly too: an unsubscribe captured anywhere in your stack becomes a Create Suppression call, and Prefinery deliberately refuses to delete unsubscribe and spam-complaint suppressions, which is a constraint worth respecting rather than working around. What an agent should not do unsupervised is reach into the ordering, and that single exception is where human-in-the-loop earns its place on a waitlist.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Signup and share link in one response
Someone submits your launch form in Typeform. The agent calls Create User, passing the referring user's ID where the form carried a referral code, and Prefinery returns the new user's referral code, share link and waitlist position in the same call. The agent puts all three into the welcome email. There is no second round trip and no gap where the user has joined but has nothing to share. If the address is on the suppression list, the agent sees it through List Suppressions and skips the email rather than generating a bounce.
Milestone rewards driven by your product, not by referrals alone
Referral count is a blunt measure of enthusiasm. Trigger Reward Event fires a named event for a user and lets Prefinery evaluate and issue whatever rewards you configured against it, so completing onboarding, connecting an integration, or inviting a teammate can each carry their own reward without you reimplementing the rules. The action returns every reward created as a result, and the agent picks those up, delivers them through Gmail, then calls Update Reward Status to mark them delivered so the ledger matches reality.
Opening access in controlled waves
Launch day is a capacity problem, not a marketing problem. A scheduled flow calls List Users, takes the top slice by position, and walks each one from applied to invited with Update User. It records who was invited in your own system, watches for Check In User events as people actually arrive, and stops the next wave if activation lags. When someone abuses the referral mechanic, the same action suspends them rather than deleting them, so their referral history stays available for review instead of vanishing along with the evidence.
Human-in-Loop Highlight
Award Points is the operation that quietly rewrites the queue. It adds to a user's balance and moves them up, which means it also moves everyone between their old and new position down, and none of those people are told. That is the honest cost of a manual bump: it is not a gift to one person, it is a small demotion for a group. There are good reasons to do it, including a pre-order, a press mention, a bug someone reported that cost them their place, but every one of them is a judgment about fairness rather than a rule an agent can apply. So the agent assembles the case and hands it over. It messages the launch owner: "Bump request for [email protected], currently position 1,842 with 3 referrals and 30 points earned. Proposed award is 200 points for a pre-order, which would move her to roughly position 260 and displace about 1,580 people. Approve, award a smaller amount, or decline?" The owner answers, the agent calls Award Points with the reason recorded so the ledger stays explainable, and List Points can later show anyone exactly how that balance was built. Grant Reward, which can bypass the normal referral threshold entirely, sits behind the same gate for the same reason.
Agent Capabilities
18 actionsProjects
2- List Projects List the waitlist and referral projects on the account with counts of imported, applied, invited, active and rejected users plus impression and share statistics. Used to resolve the project ID every other action requires.
- Get Project Retrieve a single project with its name, homepage URL and full participant counts. Used to report on a launch campaign's size and conversion.
Waitlist Users
7- List Users List the users on a project's waitlist, filterable by exact or partial email, name or referral code, returning each person's referral code, share link, waitlist position and referral counts. This endpoint is not paginated, so large projects return everything at once.
- Get User Retrieve a single user by Prefinery ID with their status, referral code, share link, waitlist position and how many people sit ahead of and behind them. Used to show someone their place in the queue.
- Create User Add someone to a project's waitlist and return their referral code, share link and queue position, optionally attributing them to an existing user as referrer so the referral is credited.
- Update User Update a user's status or profile details, for example promoting them from applied to invited or suspending an abusive account. Not every status transition is legal, so the accepted values differ from those available at creation.
- Delete User Remove a user and their referral history, optionally queueing the deletion so large removals process in the background. This cannot be undone.
- Verify User Check a user's invitation code and confirm whether it is valid for that person. Used to gate access to the product when someone redeems an invitation.
- Check In User Record a check-in, marking the user active and logging engagement. Used when someone actually starts using the product after being invited off the waitlist.
Points and Rewards
6- List Points List the points ledger for a project, or for one user when an email is supplied, showing how each balance was earned. Used to audit a leaderboard or explain a user's score.
- Award Points Award bonus points to a user, adding to their balance and moving them up the waitlist, with the reason recorded so the ledger stays explainable. The operation that should always carry an approval gate.
- List Rewards List the rewards earned in a project, optionally filtered by user email or fulfilment status, showing whether each went to the referrer or the referred friend. Used to see what still needs delivering.
- Grant Reward Grant a specific reward to a user by its descriptor, bypassing the normal referral threshold, with the option to skip the remaining-quantity check on limited supply. Used to hand out a reward manually.
- Update Reward Status Mark a reward as delivered or revoked once you have fulfilled or withdrawn it outside Prefinery, so the reward ledger stays accurate.
- Trigger Reward Event Fire a named event for a user so Prefinery evaluates and issues any rewards configured against it, returning every reward created. Used to drive milestone rewards from your own product events.
Suppressions
3- List Suppressions List the email addresses suppressed on a project with the reason for each, whether manual, unsubscribe, hard bounce or spam complaint. Used to audit who is excluded from campaign email.
- Create Suppression Suppress an email address so Prefinery stops sending that person campaign email. Only manual suppressions and unsubscribes can be created through the API. Used to honour an opt-out captured elsewhere.
- Delete Suppression Remove a suppression so the address can receive campaign email again. Prefinery refuses to delete unsubscribe and spam-complaint suppressions, because those must be honoured.
Frequently Asked Questions
What can FlowRunner do with Prefinery?
FlowRunner agents can run List Projects, Get Project, and List Users in Prefinery, plus 15 more actions.
Does connecting Prefinery to FlowRunner require OAuth?
No. Prefinery connects to FlowRunner with an API key, no OAuth flow required.
Can Prefinery trigger a FlowRunner workflow automatically?
Prefinery doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Prefinery
$100 in credits. No card required. Connect in minutes.