Tremendous

Send digital rewards through Tremendous: gift cards, prepaid cards, and charitable donations. Agents create and track orders, inspect individual rewards and their redemption status, and reconcile spend across funding sources, products, and campaigns.

7 actions API key available

Tremendous website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A completed research interview is logged in the study tracker

List Funding Sources confirms the study's balance covers the pending payout batch

List Campaigns resolves the branded campaign so each participant chooses their own reward

Each recipient is matched against prior orders by external ID so nobody is paid twice for one session

The program owner reviews the batch, names, denominations, and total against the study budget, and releases it

Create Order sends each reward by email with an External ID making the request idempotent

Get Order verifies execution and per-reward delivery status

Confirmations post to the rewards channel and each payout logs to the reconciliation sheet

What This Integration Enables

An incentive that arrives three weeks late is a smaller incentive. Tremendous turns digital rewards, gift cards, prepaid cards, and charitable donations, into an API call, and FlowRunner turns that call into the last step of the workflows where rewards are actually earned: the survey completed, the referral closed, the milestone hit. Agents handle the matching, the funding checks, and the reconciliation; the release of real money stays a decision with a name on it. - Send rewards the moment a qualifying event fires, by email, link, or SMS - Let recipients choose from a branded catalog via campaigns instead of guessing their preferences - Track every order through execution, delivery, and redemption - Reconcile spend across funding sources, products, and campaigns continuously - Make every send idempotent with external IDs so retries never become duplicate charges

Without FlowRunner

Incentives paid in batches, late Participants wait weeks for someone to run the manual gift card purchase, and the goodwill expires first

Spend reconciled from receipts Who was paid, what they chose, and whether they redeemed is a spreadsheet archaeology project

Duplicates and misses The same respondent gets paid twice while another falls out of the queue entirely

With FlowRunner

Rewards at the moment earned The payout goes out minutes after the qualifying event, and the recipient picks the card they actually want

Spend visible line by line Orders, rewards, redemption status, and funding source live in the ledger as they happen

Idempotent by design External IDs make retries safe, so a flaky network cannot double-charge a funding source

Use Case Scenarios

The survey incentive that arrives before the tab closes

A completed response lands in [Typeform](/integrations/typeform). The flow validates the completion against screening criteria, then calls Create Order with the respondent's email, the study's campaign ID, and the response ID as External ID. The participant gets the reward email while the experience is still fresh, chooses their card, and the research team's completion rates stop paying the tax of "your incentive is coming, we promise."

Referral thanks that scale with the pipeline

When a referred deal closes in [HubSpot](/integrations/hubspot), the flow pulls the referrer's contact, checks List Products for the right denomination in their country and currency, and sends the thank-you through Create Order funded from the referral budget's funding source. [Slack](/integrations/slack) posts the confirmation with recipient, denomination, and order status to the rewards channel, so the program is visible without being anyone's job.

The reward ledger that closes itself

Weekly, the agent walks List Orders for the period, calls Get Reward for each reward's delivery and redemption status, and writes the ledger to [Google Sheets](/integrations/google-sheets): value, recipient, campaign, funding source, redeemed or outstanding. List Funding Sources adds remaining balances so budget owners see runway, not just spend. Finance stops reconstructing the program from card receipts, and unredeemed rewards surface while a friendly nudge can still fix them.

Human-in-Loop Highlight

Create Order spends real money from a funding source, and a delivered reward is not coming back: once the recipient redeems the card, the spend is final in a way few API calls are. A workflow bug here does not create bad data, it creates a bill. So FlowRunner flows draw the line at release. Agents assemble the batch, verify funding with List Funding Sources, dedupe against prior orders, and then stop: "Payout batch for study NPS-Q3: 41 recipients, $25 each, $1,025 total against a $1,400 remaining balance. Release?" The program owner approves, Create Order runs with idempotent External IDs, and Get Order confirms delivery. The [human-in-the-loop](/concepts/human-in-the-loop) gate sits exactly where a retry loop could otherwise become a budget incident.

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

7 actions

Orders and Rewards

List Orders Retrieves orders newest first with pagination and filtering by campaign or external ID. The reconciliation backbone and the dedupe reference before any new send.
Get Order Retrieves one order with its payment breakdown, status, and every reward it contains with delivery status. The verification step after a release.
Create Order Sends a single reward to one recipient from a chosen funding source, by campaign for recipient choice or product ID for a specific card, delivered by email, link, or SMS. External IDs make it idempotent. The operation this page's human gate exists for.
Get Reward Retrieves one reward's value, recipient, delivery method and status, and redemption link where available. The per-reward truth behind redemption tracking.

Catalog and Funding

List Funding Sources Lists the balances and payment methods that can fund orders, with available amounts for balances. The budget check before any batch is proposed.
List Products Lists the sendable reward catalog with categories, supported currencies, and denominations, filterable by country or currency. The reference for sending the right card to the right geography.
List Campaigns Lists the configured campaigns bundling curated products with your branding and messaging. The mechanism that lets recipients choose instead of receiving a guess.

Frequently Asked Questions

What can FlowRunner do with Tremendous?

FlowRunner agents can run List Orders, Get Order, and Create Order in Tremendous, plus 4 more actions.

Does connecting Tremendous to FlowRunner require OAuth?

No. Tremendous connects to FlowRunner with an API key, no OAuth flow required.

Can Tremendous trigger a FlowRunner workflow automatically?

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

Start building with Tremendous

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

Start Building Free Talk to us