LettrLabs Zapier integrationAutomate LettrLabs with Zapier.
0 triggers, 3 actions and 0 searches in the LettrLabs Zapier integration. LettrLabs never starts a Zap itself: another app does, then LettrLabs adds recipients to a handwritten mail order, mails around an address, or logs a purchase.
Verified Trustpilot reviews · AI, automation & growth agency
What the LettrLabs Zapier integration does
The LettrLabs Zapier integration turns events in your other tools into handwritten direct mail. A new order lands in your shop, Zapier passes the buyer's address to LettrLabs, and LettrLabs queues a personalized letter on an order you prepared in its web app. Three actions, no trigger, no search.
Three results you can build. A steady stream of mail: Add Recipients to Integration Order drops each new address into an order you set up once, and LettrLabs sends from your subscription credits. A drop around one address: Radius Mail Around a Pin Address takes one address as a pin and mails a list of at least 100 recipients around it. A closed loop on revenue: Send Purchase Event reports a sale, with its total in dollars, to LettrLabs' conversion tracking, so a purchase can be tied back to your mail.
What Zapier does not do here. LettrLabs has no trigger on Zapier, so nothing that happens in LettrLabs (a letter going out, a campaign finishing) can start a Zap. There is no search step either, and no action creates an integration order: you build that order in the LettrLabs web app before the Zap can use it. Every LettrLabs Zap therefore begins in another app.
Comparing platforms first? The n8n vs Zapier and Make vs Zapier comparisons cover the criteria. This page stays on what Zapier exposes for LettrLabs.
Zapier vocabulary in one minute
Eight terms from the editor, in plain words, with what each one means for LettrLabs.
- Zap
- An automation built on Zapier: one trigger, then one or more actions that run every time the trigger event shows up.
- Trigger
- The event that sets a Zap off. LettrLabs offers none, so here the trigger always comes from another app, like your shop.
- Action
- The work the Zap does once started. With LettrLabs, it queues mail, runs a radius mailing or reports a purchase.
- Task
- What Zapier bills: one action that completes successfully. Your plan's monthly allowance is counted in tasks.
- Polling vs instant
- Polling: Zapier checks the app on a timer for anything new. Instant: the app alerts Zapier the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and halts it otherwise.
- Search step
- A step that finds something already stored in an app for the next steps. LettrLabs has none on Zapier.
- Connection
- Your LettrLabs account, linked to Zapier once and reused by every LettrLabs step in your Zaps.
What a LettrLabs Zap really costs
Two meters run side by side. On Zapier, LettrLabs is not a premium app, so it works on the Free plan. On LettrLabs, mail added to an integration order is sent from your subscription credits.
- LettrLabs on the Free planYes, not a premium app
- Tasks on the Free plan100 per month
- Zap size on the Free plan2 steps
- Minimum radius list100 recipients
On the Zapier side, the trigger in the other app is free however often Zapier checks it, and each LettrLabs action that succeeds counts as one task. A failed one costs nothing. The Free plan gives 100 tasks a month but only two-step Zaps: add a filter or a second action and the Zap turns multi-step, which needs a paid plan. The interval grid only matters when the other app's trigger works by polling.
Connect LettrLabs to Zapier in three steps
- 01
Open your connections
Start with a LettrLabs account, plus read or write access to anything in it you do not own. In Zapier, open the Apps page of your account, then click + Add connection.
- 02
Pick LettrLabs
A dialog opens with a search box. Type LettrLabs, select it in the results and confirm with Add connection. A new tab opens for the LettrLabs side of the link; keep the Zapier tab open next to it.
- 03
Sign in and grant access
Sign in to LettrLabs in that tab and grant Zapier access to the account. The connection then shows on the Apps page, and every LettrLabs step in your Zaps reuses it without asking again.
Your first LettrLabs Zap: a handwritten letter for every buyer
GoalEach new order in your shop adds the buyer, with their address, to a LettrLabs integration order, so a handwritten letter goes out from your subscription credits.
- 01
Prepare the order
In the LettrLabs web app, create the integration order that will hold the recipients. Without it, the order dropdown in Zapier has nothing to offer.
- 02
Build the trigger
Create a Zap and pick your shop app as the trigger, with its new-order event. Run the test: Zapier brings back the three most recent orders, so you map on a real one.
- 03
Add the recipient
Add LettrLabs with Add Recipients to Integration Order, choose your connection, pick the order in the dropdown and map Address 1 from the buyer's address.
- 04
Test, then publish
Test each step and read what came back before going further. Then click Publish to switch the Zap on. With one trigger and one action it stays a two-step Zap, so it runs on the Free plan at one task per order.
The 3 LettrLabs actions on Zapier
LettrLabs gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Purchase Event
ActionIn Zapier“Send a purchase event to the Conversions API”
Reports a sale to LettrLabs' conversion tracking, carrying its total revenue, so the purchase sits next to your mail activity instead of in a separate tool.
Add Recipients to Integration Order
ActionIn Zapier“Adds recipients to your trickle order, once added, we will use your subscription credits to send out handwritten mail”
Drops one more address into an integration order you created in LettrLabs, and LettrLabs then sends handwritten mail to it using your subscription credits.
Radius Mail Around a Pin Address
ActionIn Zapier“For each pin address, execute a Radius Mail Automation and mail to N recipients around each pin.”
Uses one address as a pin and runs a radius mailing around it, buying a list of recipients around that point and mailing them.
When a LettrLabs Zap breaks
Zapier attaches no help article and no rate limit to LettrLabs, so the traps below are Zapier's own. With physical mail at the end of the chain, each one matters more than usual.
Most of them start on the trigger side, which on this page is always another app. If a Zap misbehaves, the Zapier troubleshooting guide is worth keeping open.
Past orders are not mailed
A Zap only reacts to what happens after you switch it on. Orders or contacts that already existed get no letter, and mailing that backlog is a separate job.A Zap that keeps setting itself off
If the Zap writes back into the place its own trigger watches, it fires again and again, queueing mail after mail and draining your task count fast.A bulk import held back
A trigger that suddenly returns a huge batch, after an import or a migration, can be held back by Zapier's flood protection instead of mailing everyone.No double letters on polling
On a polling trigger Zapier remembers what it has already seen, so the same item does not start the Zap twice or add the same address a second time.
Need help automating LettrLabs with Zapier?
A person reads every message.
