Handwrytten
CommunicationWrite and post real handwritten cards with robots through Handwrytten, covering single sends, bulk baskets, and gift cards. Agents send a physical note when a renewal or a save deserves more than an email.
What This Integration Enables
Handwrytten writes with actual pens held by actual robots, which is why a card from it does not read like a mail merge. FlowRunner agents drive the whole surface: the catalogue of card designs, categories, handwriting styles and signatures; the address book; single sends; and the basket, which is where bulk runs are assembled. An agent can build a personalised run of several hundred cards, each with its own message, wishes and send date, and spend nothing at all until one call releases it.
That split is the reason this connector is worth building a flow around. Most send actions in a catalogue commit the moment they fire. Handwrytten separates assembly from commitment, and FlowRunner uses the gap to put a person in it. Enclosed gift cards make the gap matter more than usual, because a gift card is stored value that leaves your account and lands in a stranger's letterbox if the recipient list is wrong.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Renewal save run with enclosed gift cards
A customer success flow watches renewal risk scores. Each week it collects the accounts that crossed the threshold, resolves the primary contact and mailing address, and calls Add Recipient so Handwrytten validates each address against postal records before anything is queued. It then calls Add Cards To Basket once per account, writing a message that names the account manager and the specific thing the customer told them in the last call, and attaching a gift card denomination pulled from List Gift Cards. Nothing has been charged. The retention lead sees the assembled run, approves it, and the agent calls Send Basket. Rejected addresses come back as exceptions rather than as cards posted into the void.
Single card on a closed deal
When an opportunity closes in HubSpot or Salesforce, the agent calls Send Card once. It reads the rep's saved signature short code from List Signatures and embeds it so the robot writes that signature at the foot of the card, picks the handwriting style by its display label from List Handwriting Styles, and posts a first class stamp option from List Stamp Options. The order ID goes back onto the deal record, and a scheduled step polls Get Order Status until the card is written and away. One closed deal, one card, no queue for anyone to work through.
Event artwork on a custom card cover
Ahead of a conference, a marketing flow calls Upload Custom Image with the event artwork, which Handwrytten checks and hosts, returning an image ID for use as a card cover. Before that cover is used on anything, the agent posts the hosted image URL to the brand owner and waits. Artwork that is written onto a physical card cannot be re-versioned the way a landing page can, so the person who owns the brand looks at it once. On approval the agent builds the follow-up run in the basket against that custom cover.
Human-in-Loop Highlight
The gate sits on Send Basket, because that single call is where a Handwrytten run stops being reversible. Add Cards To Basket costs nothing and can be undone entirely with Clear Basket. Send Basket charges the account and hands the whole run to the writing robots, and Cancel Order only works while an order is still in the paid state, so once the pens are moving there is no recall. The agent therefore assembles the run, calls Get Basket Count, and posts to the retention channel: "The renewal save basket holds 84 cards. 31 of them enclose a 50 dollar gift card, so this run carries 1,550 dollars of stored value. Handwrytten rejected 3 addresses as unmatchable. Send the basket, clear it, or send it without the rejected three?" The retention lead answers, and the agent does exactly that. The human-in-the-loop step is not a rubber stamp on a message body. It is sign-off on money leaving the building in an envelope.
Agent Capabilities
21 actionsSending
5- Send Card Writes and posts a single handwritten card in one call, creating the order, charging the account and submitting it for robotic handwriting. Used for one-off moments such as a closed deal or a support save. This action wants the handwriting style's display name, not its ID, and the Handwriting Style picker supplies the right value.
- Add Cards To Basket Queues one or many cards in the basket without charging anything, so a run can be reviewed before it is committed. Every recipient carries their own message, wishes and send date. This action wants the handwriting style's ID rather than its display name, and its own picker supplies it.
- Send Basket Charges the account and submits everything currently in the basket for handwriting and posting. This is the point at which money is spent and paper is committed, so it belongs behind an approval step.
- Get Basket Count Returns how many items are waiting in the basket. Used as the safety check immediately before Send Basket so a flow never charges for an unexpected number of cards.
- Clear Basket Empties the basket without charging for anything in it and returns the items removed. Used to abandon a run that was assembled against the wrong list.
Order Lifecycle
2- Get Order Status Retrieves an order with its status, price, addresses, card details and any child orders from a bulk run. Handwrytten writes and posts asynchronously, so flows poll this to follow production. Handwrytten does not publish a full list of status values, so status is treated as free text.
- Cancel Order Cancels an order before it enters production. Only orders still in the paid state can be cancelled, so this is a narrow window rather than a general undo.
Card Catalogue
7- List Cards Retrieves the card designs available to the account, optionally filtered to one category, with prices and cover artwork URLs. The card IDs returned here are what the order actions expect.
- Get Card Retrieves a single design with its price, dimensions, orientation and hosted cover and interior artwork. Used to show a customer or an approver exactly what is about to be posted.
- List Card Categories Retrieves the categories available to the account, such as Thank You, Birthday, Congratulations and Real Estate, plus any private custom-card category. Used to narrow List Cards.
- List Handwriting Styles Retrieves the styles Handwrytten can write in, each with its ID, its display label and a sample image. The two identifiers are not interchangeable, which is why the send and basket actions ask for different ones.
- List Gift Cards Retrieves the gift card brands that can be enclosed with a card, each with its permitted denominations and prices. The denomination ID is what the send actions take.
- List Stamp Options Retrieves the postage options available for orders, such as first class. Stamp options apply to United States mail and are ignored for international delivery.
- List Signatures Retrieves the saved signatures on the account, each with a preview image and a short code that can be embedded in a message so the robot writes that signature at the end of the card.
Recipients and Senders
4- Add Recipient Saves a recipient to the account address book so later orders reference them instead of repeating the address. Handwrytten validates the address against postal records and rejects what it cannot match, which makes this a useful pre-flight check on a list.
- List Recipients Retrieves the saved recipients with their addresses and IDs. Used to reconcile your own contact records against what Handwrytten will actually mail to.
- Delete Recipient Removes a saved recipient from the address book. Orders already placed to that address are unaffected.
- List Sender Addresses Retrieves the saved sender addresses used as return addresses on cards. The returned IDs are what Add Cards To Basket expects.
Account and Artwork
3- Get Account Returns the authenticated account with its remaining card credits and profile details. Used as a guard before a bulk run so a flow does not stall partway through for lack of balance.
- Set Test Mode Switches the account between test and live mode. In test mode orders are accepted and processed normally but never fulfilled, credits are checked without being deducted, and payments authorise without capturing. Turned on before any send action runs in a flow that is still being built.
- Upload Custom Image Uploads artwork for use as a custom card cover or as a logo printed inside a card. Handwrytten accepts multipart uploads only, so the action takes a publicly reachable image URL, fetches it, and forwards the bytes. Returns the hosted URL and image ID.
Frequently Asked Questions
What can FlowRunner do with Handwrytten?
FlowRunner agents can run Send Card, Add Cards To Basket, and Send Basket in Handwrytten, plus 18 more actions.
Does connecting Handwrytten to FlowRunner require OAuth?
No. Handwrytten connects to FlowRunner with an API key, no OAuth flow required.
Can Handwrytten trigger a FlowRunner workflow automatically?
Handwrytten doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Handwrytten
$100 in credits. No card required. Connect in minutes.