Lightr

Automate the full order flow on Lightr, the Dutch direct-mail platform that produces genuinely handwritten cards and posts them. Agents trigger a physical card off a milestone the CRM already recorded.

20 actions API key available

Platform Documentation ↗ Capability data verified 2026-08-01

A scheduled daily sweep of birthday and jubilee dates in the Lightr address book

List Addresses filtered to the campaign tag returns the contacts whose date falls today

Create Order opens a draft with the chosen preset and handwriting font, then Create Receiver adds each contact with their own text variables

Preview Order renders the card with real variable values so the substituted text can be read as it will be written

Agent reconciles every receiver against the CRM suppression list and calls Delete Receiver on anyone flagged

The account owner reads the rendered preview and the receiver list, removes anyone who should not get a card, and approves; the agent calls Finalize Order and credits are deducted

What This Integration Enables

Lightr is a Dutch direct mail platform whose cards are genuinely handwritten, and its API is built around a draft that stays a draft until you say otherwise. A FlowRunner agent creates an order from a preset and a handwriting font, attaches recipients one by one with their own personalisation variables and QR values, renders a preview, and leaves it sitting there. Nothing is produced and no credits move until Finalize Order is called.

That staging model is what makes Lightr worth automating rather than just integrating. Everything reversible happens on the agent's side of the line: presets can be swapped with Update Order, recipients corrected with Update Receiver, wording changed with Update Order Multiline Message, whole orders duplicated with Replicate Order for a recurring mailing. Everything irreversible sits behind one call. The connector also manages the organisation address book, including the birthday and jubilee dates that make date-driven campaigns possible without maintaining a second copy of your contacts.

Without FlowRunner

Dates that pass unnoticed Anniversaries sit in a CRM field that nobody reports on until the week after

Personalisation by copy and paste Per-contact wording is assembled in a spreadsheet and pasted into an order form

No look before it is written The first time anyone sees the finished card is when a recipient mentions it

With FlowRunner

Dates drive the send The address book's birthday and jubilee fields are the trigger, checked every day

Variables filled from the record Each recipient's text variables come from the system that already holds the truth about them

Preview before credits move The rendered card is read by a person while the order is still a draft

Use Case Scenarios

Anniversary and birthday campaigns from the address book

The address book carries optional birthday and jubilee dates and supports tags, which is enough to run a date-driven campaign without a separate scheduling system. A daily flow calls List Addresses filtered to the campaign tag, finds the contacts whose date lands today, and builds a draft order with one receiver per contact, each carrying the text variables the template expects. Preview Order renders the result. The owner reads it, and if a name has been recorded oddly or a company field is empty, the fix happens with Update Receiver before Finalize Order deducts anything.

A card triggered by a closed deal

When a deal closes in Pipedrive or HubSpot, the agent calls Find Template to read the template's declared text variable names, builds the variables map from the deal and contact records, and creates a draft order with a single receiver. Because Find Template returns the exact variable names, the flow never guesses at placeholder keys. The card carries a trackable QR value per recipient, so List Receivers later reports which recipients scanned it and the order-level open rate becomes a real number rather than an assumption.

Repeating a seasonal mailing without rebuilding it

A seasonal mailing runs every year against the same preset, font, quantity and add-ons. Rather than reconstructing the configuration, the agent calls Replicate Order on last year's order to get a fresh draft with identical settings, then attaches this year's audience. Before finalising, it compares the new receiver list against the previous one and surfaces the difference to the campaign owner: who has been added, who has dropped off, and who has moved address since. The owner decides what to do about the movers, because a handwritten card sent to an old address is a wasted card and a slightly awkward one.

Human-in-Loop Highlight

The gate is on Finalize Order, and what it protects is the ink. Lightr writes personalisation text variables onto the card by hand, so a variable that resolved to an empty string, a legal entity name where a first name should be, or a Dutch address that lost its house number addition, is not a rendering bug that can be redeployed. It is a card in someone's hands with their name spelled wrong. Finalize Order also freezes the audience: recipients cannot be added afterwards, and Delete Receiver only works while the order is a draft, so the moment before finalising is the last moment anyone can remove a name. The agent therefore calls Preview Order with the real values, posts the rendered card and the receiver list, and asks: "42 receivers, 3 of them with an empty company variable and 1 flagged as an open complaint in the CRM. Finalise as is, drop the flagged account, or hold?" The person answers, and the agent finalises exactly what was agreed. That is the digital andon cord pulled at the only point on this connector where pulling it still changes anything.

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

20 actions

Orders

Create Order Creates a new draft handwritten card order. The preset determines format and artwork, the font determines the handwriting style, and quantity sets how many cards each recipient receives. Optionally sets a default QR value, a requested shipping date, and paid add-ons such as gift vouchers.
List Orders Returns a paginated list of orders with preset, font, quantity per recipient, total card count, credit cost, status, external number, shipping date and add-ons. Optionally filters to archived orders and requests extra relations such as card images and QR open rates.
Find Order Retrieves a single order by UUID, including its current status and QR open rate percentage. Used to poll an order after finalising until its status becomes processed.
Update Order Updates a draft order's preset, handwriting font, cards per recipient, default QR value, requested shipping date or add-ons. Only supplied fields change. Finalised orders can no longer be modified.
Delete Order Permanently deletes an order and all of its recipients. Only possible while the order is still a draft, so a finalised order that is already in production cannot be removed this way.
Finalize Order Submits a draft for production. Lightr validates the order, deducts the credits, and moves the status from draft to finalized, after which the cards are handwritten and shipped. Every recipient must be attached first, because none can be added afterwards.
Preview Order Renders the card for an order using supplied template variable values, so layout and handwriting can be checked before finalising. Multiline text variables and QR values can be supplied, and empty variables can be allowed for a partial preview.
Replicate Order Duplicates an existing order into a new draft that reuses the same preset, font, quantity and settings. Used to repeat a recurring mailing without rebuilding the configuration.
Update Order Multiline Message Sets the shared multiline handwritten message printed on every card in the order. Used for common body text such as a seasonal greeting, keeping per-recipient wording in the receiver text variables.

Receivers

Create Receiver Adds a recipient to a draft order with delivery address, country and the personalisation text variables that fill the template placeholders. QR variables can be set per recipient and marked trackable to measure scan-based open rates.
List Receivers Returns the recipients attached to an order with their addresses, personalisation variables, QR variables and the timestamp at which the handwriting extractor picked them up. Optionally includes per-recipient QR open rates.
Find Receiver Retrieves a single recipient by UUID, including the extractor timestamp that indicates whether their card has entered production.
Update Receiver Updates a recipient on a draft order. Used to correct a delivery address or adjust personalisation text before the order is finalised.
Delete Receiver Removes a recipient from a draft order so no card is produced or mailed for them. Only possible while the order is unfinalised.

Address Book

List Addresses Returns the paginated organisation address book, each entry holding name, street address, postal code, city, country, optional birthday and jubilee dates, and any tags. Filter by tag to pull a single audience segment.
Create Address Adds an entry to the address book. Birthday and jubilee dates are optional and are what make date-driven campaigns possible.
Update Address Updates an existing entry, for example after a contact moves or changes their name. Only supplied fields change.
Delete Address Permanently removes an entry from the address book. Recipients already attached to an existing order are unaffected.

Templates and Account

Find Template Retrieves a template by UUID, returning its label, type, paper format, rendered file URL, image variables and the list of text variable names. Those names are what the variables map for Create Receiver and Preview Order must match.
Get Account Returns the organisation user that owns the API token, along with the parent organisation, its credit balance, billing settings and enabled feature flags such as QR codes and custom templates. Used to confirm the token is valid and to check credits before finalising.

Frequently Asked Questions

What can FlowRunner do with Lightr?

FlowRunner agents can run Get Account, List Orders, and Create Order in Lightr, plus 17 more actions.

Does connecting Lightr to FlowRunner require OAuth?

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

Can Lightr trigger a FlowRunner workflow automatically?

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

Start building with Lightr

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

Start Building Free Talk to us