FlowRunner
Features Pricing
Theme
Start Free

Lettr

Email

Lettr sends transactional and marketing email for SaaS teams from one account, with templates the whole team edits. Agents send and schedule emails from templates, manage domains, contacts, lists and campaigns, and act on 22 delivery, engagement, unsubscribe and inbound events as they happen.

Verified 22 triggers 45 actions API key available
Lettr website Platform Documentation Capability data verified 2026-11-14
On Email Bounced fires for a receipt or reset email
Recipient, subject and bounce_class read from the event
Soft bounce logged; hard bounce continues
Find Contacts confirms the address in the audience
Update Contact sets the Lettr contact to Unsubscribed
HubSpot contact flagged with the bounce reason
Account owner told in Slack which email bounced
Owner gets a working address from the customer

What This Integration Enables

Lettr is built for SaaS teams that send both the receipt and the newsletter, and want one account for both. Developers wire sending up once, and the rest of the team owns the words in Lettr's template editor. That split decides where an agent fits. The API call rarely changes. The template does, and so does the audience. So the risky moment in Lettr is a template edit or a campaign send, not a password reset going out.

Lettr keeps sent emails and their events for about ten days. Its 22 triggers are how a flow keeps the record longer and acts on it: a bounce, a spam complaint, an unsubscribe or an inbound email lands in a FlowRunner flow as it happens. Agents send and schedule email from templates, cancel reminders that no longer apply, keep contacts, lists and topics in step with your CRM, and draft campaigns. They stop and ask before the changes a customer will see: a new active template version, or a campaign that goes out to the audience. That is human-in-the-loop placed on the two operations in Lettr that cannot be taken back.

Without FlowRunner

Bounces found later Hard bounces and spam complaints sit in the sending log until someone exports them and cleans the lists
Reminders outlive the plan A trial reminder scheduled at sign-up still goes out after the customer has already upgraded
Template edits go straight to customers A copy change to a live template reaches every order email before anyone checks its merge tags

With FlowRunner

Suppression on the event Each hard bounce and complaint unsubscribes the contact and flags the CRM record as it arrives
Reminders cancelled on upgrade The scheduled email is cancelled by its request ID once the subscription shows the upgrade
Template changes held for the owner The agent compares merge tags old and new and waits for the template owner before publishing

Flows you can build with Lettr

    • Lettr
    • Shopify
    • HubSpot
    • Slack

    Bounces and complaints handled while they are fresh

    On Email Bounced fires when an order confirmation from Shopify or a password reset cannot be delivered. The agent reads the recipient, the subject and the bounce_class Lettr sends with the event. A soft bounce is logged and left alone. A hard bounce means the address is gone, so the agent finds the contact with Find Contacts and sets it to Unsubscribed with Update Contact, which stops campaigns going to a dead address. It flags the same person in HubSpot with Update Contact and the bounce reason. On Spam Complaint runs the same path, because a recipient who marks you as spam should not get the next newsletter. A receipt that never arrived is a customer problem, not a list problem, so the account owner hears about it in Slack and gets a working address from the customer.

    • Lettr
    • Stripe

    Trial reminders that cancel themselves on upgrade

    When your app reports a new trial, the agent adds the person with Create or Update Contact, puts them on the Trials list and subscribes them to the product updates topic. It then runs Schedule Email with Template for the trial-ending reminder, which Lettr accepts for any time between 5 minutes and 30 days out, and stores the sch_ request ID on the account. A daily flow reads Get Subscriptions List in Stripe. For every trial that has become a paid subscription, the agent runs Cancel Scheduled Email with the stored ID, then moves the contact from the Trials list to the customer list. A reminder already sending can no longer be cancelled, so the agent checks Get Scheduled Email first and notes any that went out.

    • Lettr
    • Linear

    A monthly update campaign drafted from what shipped

    At the end of the month, the agent pulls the issues completed in Linear with List Issues and writes a plain summary of what shipped. Create Campaign turns it into a draft from the team's campaign template, aimed at the customer list and limited to contacts subscribed to the product updates topic. Get Campaign returns the rendered HTML and the audience, and the agent posts both to the marketing channel. Send Campaign starts sending in the background, and the connector has no action to stop a campaign once it is preparing. So the agent never sends on its own. On approval it runs Schedule Campaign for the next morning, which leaves a window in which Unschedule Campaign puts it back to draft. List Campaign Events then feeds bounces and unsubscribes back into the same suppression flow as Scenario 1.

Human-in-Loop Highlight

The gate sits on Update Template. In Lettr, new HTML saved to a template becomes its active version, and every flow that runs Send Email with Template with that slug uses it from the next send on. The connector has no action that restores an earlier version, and Delete Template removes all of them for good. Lettr also reads the merge tags again from the new HTML, so an edit can add a required tag that the sending flows do not fill yet. When an agent prepares a template change, it reads the active version with Get Template, compares the merge tags in the old and new HTML, and asks the template owner in Slack before saving: "order-shipped, active version 3. The new HTML adds a returns paragraph and a new tag, {{return_window_days}}. The order flow fills first_name and order_id only. Publish as version 4 now, or hold until the order flow passes the new tag?" The owner answers in the thread. On publish, the agent runs Update Template and watches On Email Generation Failed and On Email Generation Rejected for the next sends.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

45 actions

Emails

5
  • Send Email Sends an email with your own HTML or plain text to up to 50 recipients, with optional CC, BCC, attachments, merge tags, metadata and tracking settings. Used when the content is written in the flow, such as an alert built from live data. Returns the request ID of the send.
  • Send Email with Template Sends an email built from one of your Lettr templates and fills its merge tags with the values given. Used for order confirmations, password resets and other emails the team designs in Lettr while the flow supplies the data.
  • List Sent Emails Lists sent emails, one row per recipient, newest first, optionally for one recipient or a date range. Lettr keeps them for about 10 days. Used to answer "did this customer get our email?" during that window.
  • Get Email Details Gets a sent email by its request ID with its delivery state, sender, subject, recipients and every event, such as deliveries, bounces, opens and clicks. Used to show a support agent exactly what happened to one email.
  • List Email Events Lists email events, newest first, filtered by type, recipient, email or date range. Lettr keeps events for about 10 days. Used for a daily digest of bounces and complaints, or to backfill events a flow did not catch live.

Scheduled Emails

5
  • Schedule Email Schedules an email with your own HTML or plain text for a time between 5 minutes and 30 days from now. Returns the scheduled email with its sch_ request ID, which the flow keeps to look it up or cancel it.
  • Schedule Email with Template Schedules a template email for a time between 5 minutes and 30 days from now. Used for trial-ending reminders, renewal notices and appointment reminders that may need to be cancelled later.
  • Get Scheduled Email Gets a scheduled email with its state (scheduled, sending, sent, canceled or failed), delivery time, recipients and, once sent, its events. Used to check a reminder before cancelling it.
  • List Scheduled Emails Lists your team's scheduled emails, newest first, optionally only those in one state. Used to review what is about to go out.
  • Cancel Scheduled Email Cancels a scheduled email that has not been sent yet and returns it marked as canceled. An email already sending or sent can no longer be cancelled. Used when the plan, appointment or order behind a reminder changes.

Templates

6
  • List Templates Lists the email templates of a project, or of the default project when none is chosen, optionally only one folder or module. Used to find the slug a flow should send with.
  • Get Template Gets a template by its slug with the HTML or editor JSON of its active version. Used to read the current version before any change.
  • Create Template Creates an HTML email template and publishes its first version. Lettr reads the merge tags from the HTML. Returns the template with its slug and merge tags.
  • Update Template Renames a template or replaces its HTML. New HTML becomes a new active version, with its merge tags read again. Used for copy changes, and gated so the template owner approves before customers see it.
  • Delete Template Deletes a template and all its versions, for good. Used in cleanup only after confirming no flow still sends with that slug.
  • List Projects Lists the projects of your team. Each project holds its own templates. Used when a team keeps separate projects per product or brand.

Domains

5
  • List Domains Lists your team's sending domains with their status and whether they can send. Used in a health check before a campaign goes out.
  • Get Domain Gets a sending domain with its DNS records, verification states and tracking domain. Used to hand the exact records to whoever manages DNS.
  • Add Domain Registers a sending domain with your team and returns its DKIM record. The DNS records are added next, then Verify Domain is run.
  • Verify Domain Checks a sending domain's DKIM, CNAME, SPF and DMARC records now and returns the result of each. Used to confirm a DNS change worked without waiting.
  • Delete Domain Removes a sending domain. Email can no longer be sent from it. Used only when a brand or product is retired.

Contacts

11
  • Create Contact Adds a contact to your audience, optionally to a list. With double opt-in the contact gets a confirmation email and stays unverified until they confirm. Fails if the address is already a contact.
  • Create or Update Contact Adds a contact, or updates the one with that email address, merging the properties given and adding them to the lists and topics given. Used to sync sign-ups from forms, sheets and your CRM without duplicates.
  • Get Contact Gets a contact with their status, custom properties, lists and topics. Used before a change, to see what the contact has opted into.
  • Find Contacts Lists contacts, optionally searched by email or name and filtered by status, list or segment. Used to find the contact behind a bounce or complaint.
  • Update Contact Changes a contact's email address, subscription status or custom properties. Only the values given change. Used to unsubscribe hard-bounced addresses and to keep properties in step with the CRM.
  • Delete Contact Deletes a contact from your audience, for good. Used for data deletion requests, where removing the record is the point.
  • Add Contact to List Adds a contact to an audience list. Succeeds also when the contact is already in it, so a flow can run it safely more than once.
  • Remove Contact from List Removes a contact from an audience list. Succeeds also when the contact was not in it. Used when a trial becomes a customer or a customer leaves.
  • Subscribe Contact to Topic Subscribes a contact to a topic. Succeeds also when the contact is already subscribed. Used when a person opts into a kind of email, such as product updates.
  • Unsubscribe Contact from Topic Unsubscribes a contact from a topic and leaves their other subscriptions alone. Used to honor a narrow opt-out without removing the contact.
  • List Contact Properties Lists the custom properties contacts can hold, with their types and fallback values. Used to map CRM fields to Lettr properties.

Lists, Topics and Segments

6
  • List Audience Lists Lists the contact lists of your audience with their contact counts. Used to show how many people a campaign would reach.
  • Create List Creates a contact list. The name must be unique in your team.
  • Delete List Deletes a contact list, for good. The contacts stay in your audience. A list that segments are limited to cannot be deleted.
  • List Topics Lists the subscription topics of your audience.
  • Create Topic Creates a subscription topic contacts can subscribe to. Its default subscription cannot be changed later, so the agent confirms it before creating one.
  • List Segments Lists the contact segments of your audience, optionally only those limited to one list. Used to pick the audience for a campaign.

Campaigns

7
  • List Campaigns Lists your campaigns with their engagement stats, optionally only those in one status. Used for a weekly report on what went out and how it did.
  • Get Campaign Gets a campaign with its status, audience, engagement stats and rendered HTML. Used to show a reviewer exactly what will be sent and to whom.
  • Create Campaign Creates a draft campaign from your own HTML or a campaign template, for all subscribed contacts or chosen lists and segments, optionally limited to a topic. Nothing is sent until the campaign is sent or scheduled.
  • Send Campaign Sends a draft campaign now. It needs a subject, a sender and content. Sending runs in the background as the campaign moves to preparing, then sending and sent. Run only after a person approves.
  • Schedule Campaign Schedules a campaign for a future time, or moves an already scheduled campaign to a new one. It is sent automatically then. Used after approval, because it leaves time to change course.
  • Unschedule Campaign Cancels a campaign's scheduled send and returns it to draft. Used when a reviewer spots a problem after approving.
  • List Campaign Events Lists a campaign's engagement events, such as deliveries, bounces, opens, clicks and unsubscribes, filtered by type, recipient or date range. Used to feed campaign bounces into the suppression flow.

Triggers

22 triggers

Event Triggers

22
  • On Email Sent Fires when Lettr accepts an email and queues it for delivery, once per recipient. Used to log every send against the customer record.
  • On Email Delivered Fires when the recipient's mail server accepts an email. The message may still be filtered to spam by the mailbox provider.
  • On Email Bounced Fires when an email cannot be delivered, hard or soft. The bounce_class field tells them apart. Starts the suppression flow for hard bounces.
  • On Email Delayed Fires when the receiving server defers an email. Lettr keeps retrying it. Used to warn support when a time-sensitive email is late.
  • On Out-of-Band Bounce Fires when a receiving server first accepts an email and later reports that it could not be delivered. Handled like a hard bounce.
  • On Spam Complaint Fires when a recipient marks an email as spam. Starts the flow that stops sending to that address.
  • On Email Rejected by Policy Fires when an email is rejected by a policy rule before delivery was attempted. Used to alert whoever owns the sending setup.
  • On Email Opened Fires every time a recipient opens an email. Needs open tracking, and image blocking and prefetching make opens approximate.
  • On Email First Opened Fires the first time a recipient opens an email. Needs open tracking. Used to mark an onboarding step as seen.
  • On Link Clicked Fires when a recipient clicks a tracked link in an email. Needs click tracking. Used to hand a hot lead to sales when they click pricing.
  • On AMP Email Opened Fires every time a recipient opens the AMP version of an email.
  • On AMP Email First Opened Fires the first time a recipient opens the AMP version of an email.
  • On AMP Link Clicked Fires when a recipient clicks a link in the AMP version of an email.
  • On Email Generation Failed Fires when something goes wrong while an email is being prepared for delivery. Watched after a template change goes live.
  • On Email Generation Rejected Fires when an email is blocked while it is being assembled for delivery.
  • On List-Unsubscribe Fires when a recipient unsubscribes with the one-click List-Unsubscribe button of their mail app. Used to mirror the opt-out into the CRM.
  • On Unsubscribe Link Clicked Fires when a recipient unsubscribes through the unsubscribe link in an email.
  • On Inbound Email Received Fires when an email arrives on one of your inbound domains. This is a status event; the message itself goes to the domain's forwarding URL.
  • On Inbound Email Forwarded Fires when an inbound email is delivered to the inbound domain's forwarding URL.
  • On Inbound Email Rejected Fires when an inbound email is rejected.
  • On Inbound Forward Delayed Fires when forwarding an inbound email to your URL fails for now and will be retried.
  • On Inbound Forward Failed Fires when forwarding an inbound email to your URL fails for good, and the message will not be delivered. Used to alert the team that owns the inbound address.

Frequently asked questions

What can FlowRunner do with Lettr?

FlowRunner agents can run Send Email, Send Email with Template, and Schedule Email in Lettr, plus 42 more actions.

Does connecting Lettr to FlowRunner require OAuth?

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

Can Lettr trigger a FlowRunner workflow automatically?

Yes. Lettr supports 22 triggers that can start a FlowRunner workflow automatically.

Start building with Lettr

Free plan, no card required. Connect in minutes.