FlowRunner
PricingContact
Theme
Start Free

Convercus

Loyalty & Referral

Run enterprise loyalty programmes with Convercus, enrolling accounts, managing cards, and posting point transactions. Agents award and redeem points from the systems where the qualifying event actually happened.

17 actions Session available
Convercus website ↗ Platform Documentation ↗ Capability data verified 2026-08-02
A basket is finalized at the till
Agent resolves the member with Get Account from the card code, app code or external code they presented
Agent calls Preview Transaction to calculate what this basket awards, without posting anything
The till shows the customer the points the purchase will earn, before they pay
Agent posts the sale with Create Transaction once payment completes, and points accrue under the program's earn rules
Where the posted award differs from the previewed one beyond tolerance, a program owner reviews before any correcting booking is made

What This Integration Enables

Convercus is built for loyalty programs where points are a liability rather than a marketing gesture. The clue is Preview Transaction: an action whose entire job is to calculate what a basket would award without posting it, so the customer can be shown the number before they pay. A program that ships that action is a program where the quoted figure and the posted figure are expected to match, and where somebody downstream reconciles both. The rest of the surface follows the same logic. Every call carries an interaction ID identifying where the activity happened, stores map to business units, and partners are first-class, because in a coalition program the points a customer earns at your till can be redeemed at somebody else's.

FlowRunner agents connect that model to the systems where the qualifying events actually occur. They enroll members from the channel that signed them up, issue and replace card identifiers, post transactions from the point of sale, read balances and status levels before applying tier-specific pricing, and pull bookings when a member asks why their balance is what it is. What they do not do unattended is create value out of band. Points that post are redeemable, and once a coalition partner has honored them, they are gone in the ordinary accounting sense. That is the line, and human-in-the-loop sits exactly on it.

Without FlowRunner

Points quoted from a rate card Staff estimate what a basket earns, and the number on the receipt sometimes disagrees
Accrual happens overnight The member leaves the store without seeing the points, and asks about them days later
Corrections applied in bulk with no record A goodwill credit across a segment lands as a spreadsheet import nobody can trace back to a decision

With FlowRunner

The quoted number is the posted number The preview and the posting come from the same earn rules, so the till can show the figure honestly
Accrual follows the sale Points post from the system that saw the transaction, at the interaction point where it happened
Adjustments carry an approver Manual bookings are proposed with their reach and value, and applied only after a named person authorizes them

Use Case Scenarios

The till quotes the number it is about to post

A member presents a card at checkout. The agent resolves the account with Get Account using the identifier type the card uses, then calls Preview Transaction with the basket's line items and totals. The till displays what the purchase will earn while the customer is still deciding whether to add the last item. When payment completes in Square, the agent calls Create Transaction with the same payload and the points accrue. The customer was quoted the truth, and Get Transaction gives the store a record to reconcile against the till report at close.

A replacement card, without losing the member

A member reports their card lost. The agent calls Lock Account Identifier so the old card can no longer be used, leaving the account itself and its balance untouched, then Add Account Identifier to issue a replacement in the format the program uses. If the card turns up in a coat pocket, Unlock Account Identifier reverses the lock without a second replacement being issued. List Account Identifiers shows the member which cards they can still present in store. The whole exchange is a flow, not a service desk ticket.

Enrollment from the channel that acquired the member

A customer creates an account during an online checkout in Shopify. The agent calls Create Account to open the loyalty account, adds their identifier, and posts the qualifying purchase with Create Transaction against the online interaction point rather than a store one, so the attribution reflects where the sale happened. It then reads Get Account Level, and where the member has crossed into a higher status tier, hands that to the pricing flow so their next order carries the right benefits.

Human-in-Loop Highlight

The gate on this connector is Create Account Booking applied at scale. A single booking credits or debits points on one account outside a normal purchase, and it exists for exactly the situations that are hardest to automate: goodwill after a bad experience, a correction after a system error, a promotional bonus for a segment. The moment those points post they are spendable, and in a coalition program they can be redeemed at a partner's till within the hour. There is no clean way to unwind that once a partner has honored the value and expects to be settled for it.

So when a flow proposes a bulk correction, the agent assembles the case rather than executing it. It builds the account list, sums the total point value, prices it against the program's redemption rate, and puts one message in front of the program owner: "Correction for the double-scan incident at Store 214 on 29 July. 1,180 accounts affected, credit of 250 points each, 295,000 points total. These are redeemable at any store and at the two active coalition partners as soon as they post. Approve, reduce the per-account amount, or hold for finance?" The owner sees the reach and the liability in the same sentence and decides. Merge Accounts asks for the same treatment for a different reason: consolidating a duplicate enrollment folds two members' balances and histories into one, and there is no unmerge, so the agent gathers the evidence with List Account Identifiers and List Account Bookings for both and lets a person choose which account survives.

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

17 actions

Accounts

7
  • Create Account Create a loyalty account, the container a member's points, memberships and identifiers hang from. Used when enrolling a new member from whichever channel acquired them.
  • Get Account Retrieve a loyalty account by one of its identifiers, such as a card code, app code or your own external code. The identifier type is supplied explicitly so Convercus resolves it correctly.
  • Get Account Balance Retrieve the current point balances on an account, optionally narrowed to a single currency. Used before allowing a member to pay with points or claim a reward.
  • List Account Bookings List the point bookings recorded against an account, showing each earn and burn movement. Used to answer a member asking why their balance is what it is, and to audit program activity.
  • Create Account Booking Post a manual booking to an account, crediting or debiting points outside a normal purchase. This is the goodwill, correction and promotional bonus path, and it creates redeemable value directly, so it belongs behind an approval when applied to more than one account.
  • Get Account Level Retrieve the status level an account currently sits at. Used to apply tier-specific pricing or benefits at the point of decision rather than from a stale copy.
  • Merge Accounts Merge a secondary account into a primary one, consolidating their balances and history. Used when a member has enrolled twice, and irreversible once applied.

Identifiers

4
  • List Account Identifiers List the identifiers attached to an account, such as loyalty cards, app codes and external references, with each one's status. Used to show a member which cards they can still present.
  • Add Account Identifier Attach a new identifier to an account, such as issuing a replacement card or linking an app code. The identifier type and code format follow what the program uses.
  • Lock Account Identifier Lock an identifier so it can no longer be used, for example when a card is reported lost or stolen. The account and its balance stay active.
  • Unlock Account Identifier Unlock a previously locked identifier so it can be used again, reversing a lock without issuing a replacement card.

Transactions

3
  • Create Transaction Post a purchase so the member earns points, or redeem points as payment. Line items and totals follow what the program's earn rules expect. This is the point-of-sale action.
  • Preview Transaction Calculate what a transaction would award without posting it, so the member can be shown their points before they pay. Used at the till, and as the check that the quoted figure matches the posted one.
  • Get Transaction Retrieve one transaction by ID, including its line items and the points it generated. Used to investigate a disputed purchase or reconcile a till report.

Program

3
  • List Interaction Points List the interaction points configured on a program, such as tills, apps and online channels. Every other call carries an interaction ID identifying where the activity happened, so this is where the right value for a given flow comes from.
  • List Stores List the stores registered under a program with their identifying details. Used to map your own location records onto Convercus business units.
  • List Partners List the partners participating in a program, such as affiliates or coalition members, with their type and status. Used to review who can issue and redeem points before a bulk credit is approved.

Frequently Asked Questions

What can FlowRunner do with Convercus?

FlowRunner agents can run Create Account, Get Account, and Get Account Balance in Convercus, plus 14 more actions.

Does connecting Convercus to FlowRunner require OAuth?

No. Convercus connects to FlowRunner with session-based authentication, no OAuth flow required.

Can Convercus trigger a FlowRunner workflow automatically?

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

Start building with Convercus

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