Partnero
Loyalty & ReferralRun affiliate and referral programs with Partnero, onboarding partners, attributing referred customers, and recording commissions. Agents credit partners off verified conversions rather than a claim.
What This Integration Enables
Partnero treats partners as ongoing business relationships rather than one-off advocates, and the data model shows it. Between the partner and the money sits a customer object: you attribute a referred customer to a partner first, and only then do transactions against that customer generate rewards. Partners can be invited rather than created, archived rather than deleted, tagged, given custom fields, and attributed to the partner who recruited them for multi-level programs. This is the shape of a partner program you intend to run for years, not a referral widget you bolted onto a signup page.
FlowRunner agents work that model end to end. An agent onboards a partner from your own application flow and hands back their referral link, searches by email when your CRM knows them but Partnero's ID is not to hand, attributes referred customers at signup, records transactions when revenue lands, and reads customer credit balances for refer-a-friend schemes where the referred side accrues store credit too. One connection detail shapes every flow: each Partnero API key is scoped to exactly one program, so Get Program takes no ID and a multi-program business connects once per program. That is worth knowing before you design the flow, not after. Everything routine here runs unattended, and the small number of moments that are genuinely automation exceptions, chiefly reversals, go to a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Partner onboarding that returns something usable
A prospective partner fills in your application in Typeform. The agent calls Search Partners on their email first, because a partner who applied twice under two addresses is a reconciliation problem later. Finding nothing, it calls Create Partner with your own ID and referral key, attaches the tags that decide their commission treatment, and, for a multi-level program, attributes them to the partner who recruited them. Partnero returns the referral link and the agent sends it back in the confirmation email. The partner has a working link before they close the tab. For partners you would rather recruit than create outright, the agent calls Invite Partner and lets them set up their own account.
Attribution before revenue, reward after
A referred visitor signs up. The agent calls Create Customer, identifying the referring partner by their key, ID or email, and the attribution is now recorded whether or not that person ever pays. When they do pay, a Stripe event drives Create Transaction against that customer, supplying either the sale amount or an explicit reward value, and the partner earns. Splitting attribution from revenue this way means a partner can see their pipeline in the portal rather than only their paid conversions, which is the difference between a partner who stays engaged and one who assumes the program is broken.
Real-time program notifications
On Program Event fires for Partner Created and the agent posts the new partner into the growth channel in Slack with their tags and referral link. The same trigger, configured for Partner Approved, drives the welcome sequence. Configured for Transaction Created, it drives a running revenue feed the partner manager watches during a launch. The trigger covers the eleven events Partnero documents in its API reference, so the flow reacts to program state rather than polling List Partners on a schedule and diffing the results.
Human-in-Loop Highlight
Delete Transaction is where this connector needs a person, and the reason is social rather than technical. Deleting a transaction reverses the reward it generated, and by the time a refund reaches you the partner has usually already seen that reward in their portal. Taking it back is a clawback against someone you want to keep selling for you, and an agent that runs clawbacks automatically will eventually reverse a reward on a partial refund, a duplicate billing record, or a customer who churned and came back, and you will find out about it from the partner. So the agent does the reconciliation and stops short of the reversal. It messages the partner manager: "Refund cleared on invoice 8812 for customer jane@example.com, referred by Northwind Consulting. The matching Partnero transaction generated a reward of the recorded value, and the partner's balance shows it as earned. Reverse the transaction, leave it standing as a goodwill call, or hold for the quarterly review?" The manager decides. The agent applies the decision and logs who made it. Recording transactions stays fully automatic, because adding money is not the risky direction.
Agent Capabilities
15 actionsProgram
1- Get Program Retrieve the program the API key belongs to, including its type, settings, portal configuration and aggregate statistics. Each key is scoped to one program, so no ID is required. Used to confirm which program a connection is wired to.
Partners
7- List Partners List the partners in the program with contact details, approval status, referral links, tags and referral count. Paginated. Used for roster syncs.
- Get Partner Retrieve a single partner by their Partnero ID with their profile, approval status, custom fields, tags and referral links. Used to inspect a partner before updating them or crediting a transaction.
- Search Partners Find a partner by email address, Partnero ID or referral key without paging the full list. Used when your own system knows the partner by email.
- Create Partner Create a partner and return their referral link, optionally setting your own ID and referral key, attaching tags, and attributing them to the partner who recruited them for multi-level programs. Used to onboard from your own signup flow.
- Update Partner Update a partner's name, surname, email or tags. Only the fields supplied are changed. Used to keep partner records in step with your CRM.
- Invite Partner Send a partner invitation email so someone can join the program and set up their own account. Available on affiliate programs. Used to recruit without creating the account outright.
- Archive Partner Archive a partner, removing them from active reporting while preserving their history, with the option to restore later. Used to retire dormant affiliates without destroying the record.
Customers
4- List Customers List the customers referred in the program, optionally narrowed to one partner, with each customer's key, email, status and referring partner. Used to audit referred signups.
- Get Customer Retrieve a referred customer by key with their contact details, status, tags and referring partner. Used to confirm attribution before recording a transaction.
- Create Customer Create a referred customer and attribute them to a partner, which is the prerequisite for recording commissionable transactions. The referring partner is identified by key, ID or email. Used when a referred visitor signs up.
- Get Customer Balance Retrieve a customer's current credit balance, for refer-a-friend schemes where referred customers accrue store credit. Used before applying credit at checkout.
Transactions
3- List Transactions List the transactions recorded in the program, each with its amount, the customer and partner it belongs to, and the rewards it generated. Used to reconcile commissionable revenue.
- Create Transaction Record a transaction against a referred customer so the referring partner earns their reward, supplying either the sale amount or an explicit reward value. Used whenever a referred customer purchases or renews.
- Delete Transaction Delete a recorded transaction, reversing any reward it generated for the partner. Used after a refund or when a sale was recorded in error, and the operation that should always carry an approval gate.
Triggers
1 triggersEvent Triggers
1- On Program Event Fires when a chosen event happens in your Partnero program, such as a partner being created, approved, rejected or archived, a customer being referred, or a transaction being recorded or deleted. Partnero registers a webhook on the program and the flow runs when the event arrives. Used to drive welcome sequences, growth-channel notifications and downstream CRM updates from real program state.
Frequently Asked Questions
What can FlowRunner do with Partnero?
FlowRunner agents can run Get Program, List Partners, and Get Partner in Partnero, plus 12 more actions.
Does connecting Partnero to FlowRunner require OAuth?
No. Partnero connects to FlowRunner with an API key, no OAuth flow required.
Can Partnero trigger a FlowRunner workflow automatically?
Yes. Partnero supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Partnero
$100 in credits. No card required. Connect in minutes.