Thankster

Create and post handwritten-style greeting cards with Thankster, in one call or step by step with a proof stage. Agents draft the card and hold it for a person to approve before it is mailed.

16 actions API key available

Thankster website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

A client's customer completes a personalised card order in the storefront

Find Or Create User resolves the buyer, and Create Card Project opens a project for the named recipient

Apply Messages writes the buyer's words onto the inside pages, Apply Images places their photo, and Set Handwriting Style picks the font, size and line angle

Render Project Proof produces an image of each side and stores it in FlowRunner file storage

Agent sends the proof to the approver and files the order reference with Set Partner Order ID

The approver reads the proof and calls Approve For Printing, the step Thankster designed as the point of no return

What This Integration Enables

Thankster posts handwritten-style greeting cards, and it ships two paths to do it. Send Card creates and orders in a single call. The other path is deliberately longer: Find Or Create User, Create Card Project, Apply Messages and Apply Images, Set Handwriting Style, Render Project Proof, Order Project, Set Partner Order ID, and finally Approve For Printing. Most vendors would call that friction. It is the reason this connector is interesting.

Almost every send action in this catalogue needs FlowRunner to invent a stopping point. Thankster already has one, and it went further: Order Project alone does not release anything to the printers, and Approve For Printing will not run until Set Partner Order ID has attached your own reference to the order. Two keys, in order, before ink. A flow that calls Send Card walks straight past all of it, which is the right choice for a low-value internal thank-you and the wrong choice for anything a client's name is printed on. FlowRunner agents build the card, render the proof, and then stop, because the vendor built somewhere sensible to stop.

Without FlowRunner

Approval by screenshot A proof is pasted into a thread and approved by whoever replies first

No reference to trace by An order in the vendor's system has no reliable link back to yours

Charged before anyone looked The commitment is made at the same moment the card is built

With FlowRunner

Proof stored with the order Each rendered side is saved as a file and attached to the record it belongs to

Reference set before release Your own order ID is attached to the Thankster order and echoed on the mailing notification

Release is a separate act Building the card and releasing it to the printers are two different decisions made by two different steps

Use Case Scenarios

Customer-personalised cards from a storefront

A buyer configures a card in a Shopify storefront, choosing a design from live catalogue data, writing a message and uploading a photo. The agent calls Find Or Create User with the buyer's email, opens a project, and applies the message across the two inside pages, each of which holds up to 400 characters. Apply Images places the photo into the template's frames, which map in order to the coloured placeholders. Set Handwriting Style picks the font from List Fonts and tilts the line angle slightly off level so the writing does not read as machine-set. Render Project Proof comes back as base64, which the connector decodes and saves into FlowRunner file storage, so the proof can be emailed to the buyer as a real link.

Agency sends on behalf of a client brand

An agency runs card campaigns for several client brands. It imports each client's audience with Import Address Book, builds a project per recipient, and renders proofs. The approval does not go to the agency, it goes to the client's brand owner, because the card carries the client's name and handwriting. Set Partner Order ID attaches the agency's own job reference to the Thankster order, which is also the reference echoed back on the mailing notification, so a card that turns up in a client's post can be traced to the campaign, the approver and the day it was released.

A quick internal thank-you that does not need the ceremony

Not everything deserves a proof cycle. When a support agent resolves a difficult case, the flow calls Send Card once with a test key during build and a live key in production, picking a design from List Cards narrowed by List Card Categories. It creates and orders in one call and spends a card from the subscription allowance. The judgement here was made once, at design time: this category of card is low value and low risk, so it ships without a gate. The agent still records what it sent and to whom, so the decision to skip review is visible rather than accidental.

Human-in-Loop Highlight

The gate is Approve For Printing, and it is worth naming plainly that FlowRunner did not invent it. Thankster did, and then made it hard to reach by accident: it is the billable step, it releases the card to the printers, and it refuses to run until Set Partner Order ID has attached your own reference to the order. An agent can walk the entire build, apply the message, place the images, choose the font, render the proof and place the order, and none of that puts a pen on paper. So the flow stops one call short and asks the person whose name is on the card: "Proof attached, both inside pages and the cover. Card for Dana Whitfield, message 187 characters, handwriting style Marlowe at size 62. Partner reference AGY-4471 is set. Approve for printing?" On yes, the agent calls Approve For Printing and the card is released. On no, the project is still a project: Select Card swaps the design without losing the message, Apply Messages rewrites the text, and the proof is rendered again for nothing. One note worth keeping in the flow: Thankster cannot return uploaded images afterwards, so the agent keeps its own copy of anything it applied.

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

16 actions

One-Call Sending

Send Card Creates and immediately orders a card in a single call, taking sender and recipient details, message text and optional images. This is the shortest path, and it spends a card from the subscription allowance and posts real mail with no review step in between.

Step-by-Step Ordering

Find Or Create User Looks up a Thankster user by email address and creates one if they do not exist, returning the user ID that the step-by-step path needs. This is the first call when the flow intends to review a proof before committing.
Create Card Project Creates a card project for one recipient without ordering it, returning project and recipient IDs that can then be customised with messages, images, fonts and colours.
Apply Messages Writes the message text onto a project's inside pages. Each inside page holds up to 400 characters and a card has two inside pages.
Apply Images Places images into a project's image frames from publicly reachable URLs. Frames map in order to the coloured placeholders in the template. Thankster cannot return uploaded images afterwards, so a flow keeps its own copies.
Select Card Changes which design a project uses without recreating the project or losing its message and images. Used to swap artwork after an approver or a customer picks something different.
Set Handwriting Style Sets the handwriting font, size, colour and line angle used to write the card. Size runs from 1 to 100 and line angle from 1 to 100 where 50 is level, so a slight tilt reads more naturally than a perfectly straight line.
Render Project Proof Renders proof images of the chosen sides so the finished piece can be reviewed before anything is printed. Thankster returns the images inline as base64, so this action decodes each page, stores it in FlowRunner file storage, and returns a usable URL per side.
Order Project Places an order for a completed project and returns the Thankster order ID. Ordering on its own does not release the card to the printers.
Set Partner Order ID Attaches your own order reference to a Thankster order. This is a hard prerequisite for Approve For Printing and is the reference echoed back on the mailing notification.
Approve For Printing Releases an order to the printers to be written and posted. This is the billable step and the point of no return, which is why it is the natural place for a person to stand.

Address Book and Catalogue

Import Address Book Imports a batch of contacts into a user's address book in one call, so an audience can be prepared before any cards are created.
List Templates Retrieves the templates available to the account with their type, size, orientation and thumbnail. Template IDs from here are what the send and project actions expect.
List Cards Retrieves the card designs available, optionally narrowed to one category, with real paper dimensions in inches, orientation and cover thumbnail. Used to present a design picker to a customer.
List Card Categories Retrieves the categories available to the account, such as Thank You Cards and General Thank You Cards. Used to narrow List Cards.
List Fonts Retrieves the handwriting fonts Thankster can write in, each with a preview image. Font IDs from here are what Set Handwriting Style expects.

Frequently Asked Questions

What can FlowRunner do with Thankster?

FlowRunner agents can run Send Card, Find Or Create User, and Create Card Project in Thankster, plus 13 more actions.

Does connecting Thankster to FlowRunner require OAuth?

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

Can Thankster trigger a FlowRunner workflow automatically?

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

Start building with Thankster

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

Start Building Free Talk to us