SmartPasses
Loyalty & ReferralManage loyalty program members and reward offers with SmartPasses, enrolling customers, awarding points, and publishing offers. Agents keep wallet passes current as balances change.
What This Integration Enables
SmartPasses puts your loyalty programme on the customer's phone. That is the distinguishing fact, and it changes the stakes on one particular action. A points balance in a database is something a customer checks when they think about it. A wallet pass sits in the place people look at fifty times a day, and when you publish an offer, every pass holder in the programme sees it at once. There is no staggered rollout, no test segment.
The connector gives agents the two halves of that programme. On the member side it enrols customers, retrieves them individually or in full, updates their details, awards points incrementally as purchases happen, and removes them when an erasure request comes in. On the reward side it creates offers in draft, edits their wording and points cost, publishes them so members can claim, cancels them when a promotion ends, and deletes drafts that never ran. Agents keep the balances current so the pass in someone's pocket is telling them the truth.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Points credited at the moment of sale
A payment succeeds in Stripe. The agent resolves the buyer to their SmartPasses record, calls Add Points with the value earned on that basket, and the pass updates. Add Points is deliberately the right call here rather than Update Customer, because Update Customer sets the points field to an absolute value and would wipe whatever the customer had accrued. The customer sees their new balance without opening anything, and the distance to their next reward shrinks in front of them.
Seasonal offer staged, reviewed, then launched
A promotion is due to launch on the first of the month. The agent builds the offer with Create Offer, which starts in draft and remains invisible. It then calls List Offers to check nothing conflicting is already live and List Customers to count how many members are already above the points cost, because an offer with auto-claim enabled will grant itself to all of them the instant it publishes. Those numbers go to the loyalty owner with the draft wording. Once approved, Publish Offer makes it visible. When the promotion ends, Cancel Offer deactivates it while keeping its history intact.
Membership reporting without a report builder
The SmartPasses customer list comes back in a single response with no pagination or filtering, which is fine for reading and unhelpful for analysis. The agent calls List Customers on a schedule, filters and buckets the results by points band downstream, and writes the summary into Google Sheets where the marketing team already works. Nobody logs into a second tool to find out how many members are one purchase away from a reward.
Human-in-Loop Highlight
Publish Offer is a broadcast, which is the whole reason a person should be standing in front of it. A draft offer is invisible. The moment it publishes, it appears on every wallet pass in the programme simultaneously, and if auto-claim is enabled it grants itself immediately to every member who already has enough points. Cancel Offer will stop future claims, but it does not reverse claims already made and it does not un-show the offer to the people who saw it. So the agent stages the reward, models the blast radius, and stops. It posts the draft to the loyalty owner with the specific thing a person needs in order to judge it: "Offer ready to publish. Free coffee, 250 points, auto-claim on. 1,840 members are currently at or above 250 points and would be granted this instantly on publish. Publish, turn auto-claim off first, or hold?" One question, one approval, and the agent publishes. This is the same human-in-the-loop shape FlowRunner applies wherever an agent's next step reaches customers directly and cannot be pulled back. Note also that Delete Offer only accepts drafts, so a published offer must be cancelled before it can be removed, and Delete Customer discards a points balance permanently. Neither is a call an agent should make on its own.
Agent Capabilities
12 actionsMembers
5- List Customers Lists every customer enrolled in a loyalty program with their contact details and current points balance. The API returns the full list in one response with no pagination or filtering, so filtering and bucketing happen downstream in the flow.
- Get Customer Retrieves a single loyalty program customer by numeric ID, returning name, email, phone and points balance. The `humanName` field is a server-computed display name that falls back to an anonymous label when no name is stored.
- Create Customer Enrols a new customer into a loyalty program with their name and contact details, returning the generated ID needed to award points later. Used when someone signs up for the programme through your own form or at the counter.
- Update Customer Updates a customer's name, or sets their points balance to an absolute value. The points field here replaces the balance outright rather than adding to it, so use Add Points for anything incremental.
- Delete Customer Permanently removes a customer from a loyalty program and discards their points balance. This cannot be undone. Used to honour a data erasure request or to clear test enrolments.
Points
1- Add Points Awards points to a customer, adding to their existing balance rather than replacing it. Used at the point of sale so a purchase moves the customer closer to claiming an offer, and the pass in their pocket updates with it.
Offers
6- List Offers Lists the reward offers configured on a loyalty program with their points cost. Used to resolve an offer ID before publishing, cancelling or deleting, and as a conflict check before a new promotion goes live.
- Create Offer Creates a new reward offer, setting what customers get and how many points it costs. New offers start in draft and stay invisible until published. Auto-claim grants the reward automatically once a customer has enough points, which is worth deciding deliberately.
- Update Offer Updates an existing offer's name, description, points cost or auto-claim setting, changing only the fields supplied. SmartPasses uses POST rather than PUT for this operation.
- Publish Offer Publishes a draft offer so customers can see and claim it. Used once the wording and points cost are final, and the single action on this connector that reaches every pass holder at once.
- Cancel Offer Deactivates a published offer so customers can no longer claim it, without deleting it. Used to retire a seasonal reward while keeping its history intact.
- Delete Offer Permanently deletes an offer from the loyalty program. SmartPasses only allows draft offers to be deleted, so a published offer must be cancelled first. This cannot be undone.
Frequently Asked Questions
What can FlowRunner do with SmartPasses?
FlowRunner agents can run List Customers, Get Customer, and Create Customer in SmartPasses, plus 9 more actions.
Does connecting SmartPasses to FlowRunner require OAuth?
No. SmartPasses connects to FlowRunner with an API key, no OAuth flow required.
Can SmartPasses trigger a FlowRunner workflow automatically?
SmartPasses doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SmartPasses
$100 in credits. No card required. Connect in minutes.