Snappy

Send personalized gifts through the Snappy corporate gifting platform. Agents send gifts under campaigns when milestones hit, track redemption and shipping status, and browse recipients and gift collections to reconcile gifting spend.

7 actions API key available

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

A milestone lands upstream, a deal closes in the CRM or an employee hits a work anniversary in the HR system

List Campaigns finds the campaign whose budget and collection match the occasion

List Recipients searches by email to see whether this person was gifted recently under the same program

The program owner reviews the proposed gift, recipient, campaign, and budget before anything is spent

Send Gift issues the gift under the approved campaign with a personal message

Get Gift polls the redemption status until the recipient opens and redeems

A note posts to the team channel when the gift is redeemed, naming the item the recipient chose

What This Integration Enables

Snappy is built on a discipline most gifting programs lack: every gift is sent under a campaign that fixes the budget, the eligible collection, and the branding, and the recipient picks their own item within those rails. That structure is what makes gifting automatable without making it reckless. FlowRunner agents watch for the moments worth marking, propose the gift under the right campaign, and hand the actual spend decision to a person. After the send, they track redemption and shipping so the program owner knows what worked. - Trigger gifts from real events: closed deals, completed surveys, anniversaries, referrals - Scope every send to a campaign so budget and catalog stay governed - Track each gift from pending to opened to redeemed, including the item chosen - Reconcile spend continuously by listing gifts per campaign into reporting tools - Search saved recipients to avoid double-gifting and to personalize repeat outreach Gifting is also a workflow that touches half the stack: the trigger lives in the CRM or the HR system, the budget lives in finance's spreadsheet, and the thank-you moment lives in a chat channel. That is exactly the kind of cross-system choreography FlowRunner exists for. One flow watches the milestone sources, one [human-in-the-loop](/concepts/human-in-the-loop) gate governs the spend, and the same flow closes the loop by reporting redemption back to the people who care. The gifting program stops depending on one coordinator's memory and becomes a process the whole company can see.

Without FlowRunner

Gifting runs on memory Anniversaries and closed-won moments slip past because someone had to notice them

Spend reconciles quarterly Finance discovers what the gifting program cost long after the budget conversation

Redemption is a mystery Gifts go out and nobody knows which ones were opened, redeemed, or ignored

With FlowRunner

Milestones trigger gifts automatically Upstream events propose the gift the moment they happen, with the right campaign attached

Spend visible as it happens Every gift lands in a live reconciliation sheet with campaign, budget, and status

Redemption tracked to the doorstep Agents follow each gift from sent to opened to redeemed to shipped

Use Case Scenarios

The survey reward that arrives while the goodwill is fresh

A completed NPS submission arrives from [Typeform](/integrations/typeform) with a high score and a thoughtful comment. The agent looks up the respondent with List Recipients, confirms they have not been gifted this quarter, and queues a Send Gift under the customer-appreciation campaign with a message referencing their feedback. The program owner approves the batch each morning. The recipient gets a redemption link the same day their enthusiasm peaked, not three weeks later when someone processed the spreadsheet.

A gifting ledger finance can actually use

Every Friday an agent calls List Gifts for each active campaign and writes recipient, budget, send date, and redemption status to [Google Sheets](/integrations/google-sheets). Get Campaign supplies each campaign's total budget and currency so the sheet shows burn against plan. When a campaign crosses its spend threshold, the agent flags the program owner before the next gift goes out rather than after the quarter closes. Gifting stops being a line item finance argues about and becomes one they can see.

Closing the loop on the gift itself

A rep closes a strategic deal and the agent proposes a thank-you gift to the champion. After approval and Send Gift, the agent polls Get Gift daily. When the status flips to redeemed, it posts to [Slack](/integrations/slack): the champion chose the espresso maker, shipping is in progress. The rep gets a natural reason to follow up, and the team sees the program producing moments instead of disappearing into a budget line. Gifts that sit unopened past two weeks get flagged too, so the rep can resend the link personally.

Human-in-Loop Highlight

Send Gift spends real budget the moment it runs, and it spends it in the recipient's name: a gift email arrives from your brand, under a campaign with your branding, carrying a message the recipient will read as personal. A wrong recipient, a tone-deaf message, or a duplicate gift two weeks after the last one is money gone and a relationship made slightly worse. So the agent does everything up to the send: it matches the event to a campaign, checks the recipient's gifting history, drafts the message, and presents the package: "Dana Reyes closed the Meridian renewal. Proposed: $150 under the Customer Appreciation campaign, message attached. She was last gifted in November." The program owner approves, edits the budget, or declines. The agent handles the watching and the paperwork. The spending decision stays human.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

7 actions

Campaigns

List Campaigns Lists gifting campaigns with pagination. Each campaign defines a budget, an eligible gift collection, and branding. The step agents use to match an occasion to the right program.
Get Campaign Retrieves a single campaign's full details: name, status, budget, currency, collection, and branding. Used to check burn against plan and confirm a campaign is active before proposing a send.

Gifts

Send Gift Sends a gift to a recipient under a specific campaign, with an optional per-gift budget override and personal message. The recipient chooses their item from the campaign's collection. The operation this page's human gate exists for.
List Gifts Lists sent gifts, optionally filtered to one campaign, with recipient, budget, and redemption status. The backbone of spend reconciliation and stalled-gift sweeps.
Get Gift Retrieves a single gift's current status, redemption URL, the item the recipient selected, and shipping status. How agents follow a gift from sent to delivered.

Recipients

List Recipients Lists saved recipients with name, email, and delivery details, with search on name or email. The dedup check that keeps one person from being gifted twice for the same milestone.

Collections

List Collections Lists the gift collections available in the account, each a curated set of items at a price range. Used when reviewing which catalog a campaign offers before routing an occasion to it.

Frequently Asked Questions

What can FlowRunner do with Snappy?

FlowRunner agents can run List Campaigns, Get Campaign, and Send Gift in Snappy, plus 4 more actions.

Does connecting Snappy to FlowRunner require OAuth?

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

Can Snappy trigger a FlowRunner workflow automatically?

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

Start building with Snappy

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

Start Building Free Talk to us