New from emailrHealthCheck Email iconHealthCheck Email
emailr_

Connect emailr_ to Zapier

Use the emailr_ Zapier app to send email from any Zap and start Zaps when an email lands in an emailr_ inbox. No code required, just an API key.

Zapier iconZapierAutomation

The emailr_ app for Zapier has one action and one trigger. Send Email sends a message from your verified domain as a step in any Zap. Email Received starts a Zap whenever a message arrives in an emailr_ inbox.

Together they cover the common no-code jobs: sending notifications from form tools and CRMs, and routing inbound mail into tickets, spreadsheets or chat.

Set up emailr_ with Zapier

  1. 01

    Create an API key

    Create a key under API keys in the dashboard. Keys start with et_live_ and are scoped to one domain workspace. Store it as EMAILR_API_KEY in your secret manager or environment, never in client-side code.

  2. 02

    Add and verify your sending domain

    In the dashboard, open Domains and add the domain you send from. A subdomain such as mail.yourcompany.com keeps transactional reputation separate from your corporate mailbox.

    Emailr generates the DNS records: a DKIM TXT record on the emailr._domainkey selector, an SPF TXT record, and an MX + TXT pair on the send subdomain used as the MAIL FROM / Return-Path. A DMARC record is optional but recommended.

    Emailr's DKIM selector and send subdomain don't collide with other providers' records, so you can add them before cutting over and send from both providers during the migration. A domain can only have one SPF record: if one already exists, merge Emailr's include: into it instead of adding a second record.

  3. 03

    Connect your account

    In the Zap editor, search for Emailr and choose an action or trigger. When asked for an account, paste your API key. Leave the API URL at its default https://api.emailr.dev.

  4. 04

    Action: Send Email

    Fields: From (required, must use a verified domain, e.g. Support <support@yourdomain.com>), To (required), Subject (required), HTML Body and/or Plain Text Body, and optional Reply-To, CC and BCC (comma-separated).

    Map fields from earlier steps, for example the email address from a Typeform response or a deal owner from your CRM.

  5. 05

    Trigger: Email Received

    Pick an inbox, or leave it empty to watch all inboxes. When the Zap is turned on, emailr_ registers a webhook subscription for email.received; turning the Zap off removes it.

    Each trigger provides: Email ID, Message ID, From Email, From Name, To, Subject, Plain Text Body, HTML Body, Has Attachments, Attachment Count, Inbox ID, Thread ID and Received At.

Tips

  • Example Zap: Email Received (support inbox) → create a ticket in your help desk → post the subject to Slack.
  • Example Zap: New form submission → Send Email with a confirmation to the submitter.
  • Use one API key per tool so you can revoke Zapier's access without affecting your app.

Frequently asked questions

What can the emailr_ Zapier app do?

It has a Send Email action and an Email Received trigger. Send Email sends a message from your verified domain; Email Received starts a Zap when an email arrives in an emailr_ inbox.

Do I need to verify a domain to send from Zapier?

Yes. The From address must use a domain verified in your emailr_ account.

Can I trigger a Zap only for one inbox?

Yes. Choose the inbox when setting up the Email Received trigger, or leave it empty to receive events from all inboxes.

Can Zapier send emailr_ templates or broadcasts?

Not through the Zapier app today. It sends individual emails with the subject and body you map. For templates and broadcasts, use the API directly.

Start sending in minutes

Create a free account, verify your domain and send your first email. No credit card required.