Resources · Zapier integration

Lettr Zapier integrationAutomate Lettr with Zapier.

0 triggers, 2 actions and 0 searches in the Lettr Zapier integration. Lettr cannot start a Zap on its own, so another app kicks things off, then Lettr sends the email: raw HTML written in the Zap, or a template you already saved in Lettr.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Lettr Zapier integration does

The Lettr Zapier integration hands an email job to Lettr whenever something happens elsewhere: a row lands in your spreadsheet, Zapier passes its values along, and Lettr sends the message. The content is either HTML you write inside the Zap or a template already stored in your Lettr account. Two actions, no trigger, no search.

Three results you can build. A templated message: Send Email Template takes a design you saved in Lettr and only needs the sender address, the subject and the recipient from the step before. A one-off message: Send Email takes HTML you compose in the Zap, with values mapped from the trigger, so a new row turns into a formatted email. A bare text note: the same action accepts plain text in its HTML content box, handy when layout does not matter.

What Zapier does not do here. Lettr has no trigger on Zapier, so nothing that happens in Lettr can start a Zap, and the engagement and deliverability tracking Lettr offers stays in Lettr. There is no search step either: a Zap cannot look up a template or a past send, it only sends. Every Lettr Zap therefore begins in another app.

Weighing platforms? The n8n vs Zapier and Make vs Zapier comparisons lay out the criteria. This page sticks to what Zapier exposes for Lettr.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain terms, with what each one means for Lettr.

Zap
An automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event shows up.
Trigger
The event in an app that sets a Zap off. Lettr offers none, so on this page the trigger always sits in another app.
Action
The step that does the work once the Zap is running. Here it is Lettr sending one email, raw or from a template.
Task
What Zapier bills: one action that completes successfully. The monthly allowance on your plan is a count of these.
Polling vs instant
Polling: Zapier checks the app on a timer for anything new. Instant: the app tells Zapier the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and halts it otherwise.
Search step
A step that finds something already stored in an app so later steps can use it. Lettr has none on Zapier.
Connection
Your Lettr account, linked to Zapier once and then reused by every step that sends through Lettr.
Cost

What a Lettr Zap really costs

Lettr is not a premium app, so it runs on the Free plan. You pay in tasks, and only the Lettr side counts.

  • Lettr on the Free planYes, not a premium app
  • Tasks on the Free plan100 per month
  • Zap size on the Free plan2 steps
  • Cost of the trigger0 tasks

The trigger in the other app costs nothing, however often Zapier checks it. Each email Lettr sends successfully is one task; a send that fails is not counted. The Free plan gives 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter, a second action or a search and you get a multi-step Zap, which needs a paid plan. The interval grid only matters when the other app's trigger is a polling one.

Connect

Connect Lettr to Zapier in three steps

  1. 01

    Open your connections

    You need a Lettr account first, 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.

  2. 02

    Pick Lettr

    A dialog opens with a search box. Type Lettr, select it in the results, then confirm with Add connection. Zapier opens a new tab for the Lettr side of the link, so leave the Zapier tab where it is.

  3. 03

    Sign in and grant access

    Sign in to Lettr in that tab and grant Zapier access to the account. The connection then appears on the Apps page, and every Lettr step in your Zaps can reuse it instead of asking you again.

First Zap

Your first Lettr Zap: a new row sends a template

GoalEach new row in your spreadsheet sends a saved Lettr template to the address in that row, but only for rows that pass a filter.

  1. 01

    Build the trigger

    Create a Zap and pick your spreadsheet app as the trigger, with its new-row event. Lettr cannot fill this slot since it has no trigger. Connect the sheet account when Zapier asks.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent rows of the connected account, so you map the next steps on a real row rather than on blanks.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field to look at, the rule and the value. Match the rule to the field type: a text rule on a number never passes.

  4. 04

    Add Send Email Template

    Add Lettr with Send Email Template, choose your connection, then map From, Subject and Recipient from the row. The template itself comes from your Lettr account.

  5. 05

    Test, then publish

    Test the Lettr step and open the email that lands. Then click Publish. With a filter on board this is a multi-step Zap, so it needs a paid plan.

Actions

The 2 Lettr actions on Zapier

Lettr gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Send Email

Action

In Zapier“Sends email to given email address”

Composes and sends one email from inside the Zap: you fill in the sender, the recipient, the subject and the body, and Lettr delivers it. The body takes HTML, or plain text when that is all you have.

When to use it
a message whose wording changes with each run, built from values the earlier step brought in.
Watch out
all four boxes are required, so map each one to a value every trigger item actually carries.
2

Send Email Template

Action

In Zapier“This sends email templated saved in Lettr account”

Fires off a template you already saved in your Lettr account, so the design lives in Lettr and not in Zapier. The Zap only supplies the sender address, the subject and the recipient.

When to use it
a recurring message your team edits in Lettr without anyone touching the Zap.
Watch out
the template has to exist in Lettr before the step can send it, and From, Subject and Recipient are all required.
When it breaks

When a Lettr Zap breaks

Zapier attaches no help article and no rate limit to Lettr, so the traps below are Zapier's own, the ones that hit any Zap ending in an email.

Most of them start on the trigger side, which on this page is always another app. When a Zap misbehaves, keep the Zapier troubleshooting guide at hand.

  • Nothing from before the Zap goes out

    A Zap only reacts to what happens after you switch it on. Rows or records that already existed get no email, and sending to 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, sending email after email and eating 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 sending everything.

  • No double sends on polling

    On a polling trigger Zapier remembers what it has already seen, so the same item does not start the Zap twice or send a second email.
Need help

Need help automating Lettr with Zapier?

A person reads every message.

FAQ

Lettr and Zapier: common questions

01Is the Lettr Zapier integration free?
Yes, as far as Zapier is concerned: Lettr is not a premium app, so it works on the Free plan. That plan gives you 100 tasks a month and Zaps of two steps, one trigger and one action. A single Lettr send after a trigger from another app fits inside it. Add a filter, a second Lettr action or any extra step and the Zap becomes multi-step, which needs a paid plan. What Lettr charges on its own side is not covered by the Zapier app page, so check your Lettr account for that.
02How many tasks does a Lettr Zap use?
One per email that goes through. The trigger in the other app costs nothing, and neither does Zapier checking it for new items, however often that happens. Each Lettr action that completes counts as one task, so a Zap that sends a template and then a plain copy uses two per run. A send that fails is not counted against your plan. Watch out for loops: a Zap that keeps refiring itself spends a task on every lap, and the monthly allowance drains quickly.
03Does Lettr send emails in real time through Zapier?
That depends on the app that starts the Zap, because Lettr has no trigger of its own. If that app offers an instant trigger, it reports the event to Zapier straight away and the Lettr step runs without waiting, whatever your plan; the editor marks such a Zap with a lightning bolt. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. Paid plans can also run a check by hand from the editor.
04What does connecting Lettr to Zapier require?
A Lettr account, plus the Zapier account you link it to. From the Apps page in Zapier, you add a connection, search for Lettr, sign in to Lettr in the tab that opens and grant Zapier access. If the Zap should touch anything you do not own yourself, you also need read or write access on it. For Send Email Template, save the template in Lettr first, because the action only sends one that already exists there. After that, every Lettr step reuses the same connection.
05Why does Send Email Template need a saved template first?
Because the action builds nothing: it sends a design that already lives in your Lettr account. Zapier only supplies the sender address, the subject and the recipient, and all three are required. If the design is not there yet, the step has nothing to send, so create and save it in Lettr before you build the Zap. When the message changes too much from one run to the next, Send Email is the better fit, with the HTML written straight into the Zap and fed by the trigger values.
06What if the Lettr operation required is not on Zapier?
Then it is not available through Zapier today. Lettr exposes two visible actions there, Send Email and Send Email Template, and nothing else: no trigger and no search. Anything outside those two, such as reading engagement data back, stays inside Lettr. The workable routes are to handle that part in Lettr directly, or to check whether another automation platform offers it for Lettr before building around the gap. The action list in the editor is the reference, and an operation missing from it cannot be added from the Zap.
07Zapier, Make or n8n for Lettr?
Decide on criteria rather than on a ranking. First, which Lettr operations each platform offers: on Zapier that means two send actions and no trigger, so another app always starts the flow. Second, how usage is billed: Zapier counts one task per successful action, and the Free plan stops at two steps. Third, who will maintain the flows and how comfortable that person is with each editor. Put those three side by side for your own volume and the choice usually becomes clear, without any platform winning in general.
Same platform

Other docs you might need on this stack.

Browse all integrations