MimePost Zapier integrationAutomate MimePost with Zapier.
The MimePost Zapier integration gives you 0 triggers, 1 action and 0 searches. That action, Send Email, sends a message through MimePost from one of your approved domains whenever another app starts the Zap, and it works on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the MimePost Zapier integration actually does
MimePost is an email sending service, used here from Zapier through a single action, Send Email, which sets the sender name, the sender address, the recipient, the subject and the body. Another app starts the Zap, and MimePost sends a message built from that app's data, from a sender address on a domain you have approved in MimePost.
Three results to start with. A confirmation that leaves on its own: each form submission triggers Send Email to the person who filled it in. An internal alert by email: a new deal or a new row elsewhere sends a short message to your team address. A message in HTML from your domain: the body accepts plain text or HTML, so a formatted email can go out from your own sender name.
Now what Zapier does not do here. MimePost has no trigger and no search on Zapier: it cannot start a Zap, and it cannot look anything up for a later step. Every MimePost Zap starts in another app, and Send Email is where it ends. Send Email needs at least one approved domain in your MimePost account, so check that before the first test, along with the sender name your readers will see. Send Email has six required fields, covered in its note further down.
Weighing tools first? See our n8n vs Zapier comparison or read the Zapier review.
Zapier words in one minute
The rest of the page uses these words. Each one is explained once, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. MimePost has none, so a form, a CRM or a sheet plays that part.
- Action
- What the Zap does once it has started. For MimePost, it is Send Email: the step that sends the message for you.
- Task
- The unit Zapier bills: one action that your Zap completes successfully. Each email sent counts as one.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is reported by the app itself. It depends on the other app.
- Filter
- A step that lets the Zap continue only when the incoming item meets a condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
- Connection
- Your MimePost account linked to Zapier once, then reused by every Send Email step of every Zap.
What MimePost costs you in tasks
MimePost is not a premium app, so it works from the free plan. Each email that Send Email sends successfully counts as one task.
- TriggerFree, never counted
- Each email sent1 task
- Failed sendNot counted
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
Every action that succeeds is one task, an action that fails is not counted, and the trigger is free. A form that sends one confirmation per submission spends one task per submission. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A trigger plus Send Email fits; add a filter or a second action and you need a paid plan. The grid below sets how often Zapier checks a polling trigger. MimePost has no trigger: whether the grid applies depends on the app that starts the Zap.
Connect your MimePost account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a MimePost account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick MimePost
Type MimePost in the search box of the dialog, select it, then click Add connection. A new tab opens on the MimePost side for the sign-in that follows.
- 03
Sign in and allow access
Log in to MimePost in that tab and grant Zapier access to the account. Every Send Email step, in every Zap you build, then reuses this connection. Nothing else to set.
Your first Zap: a confirmation for every form submission
GoalWhen someone submits your form, send them a confirmation email through MimePost from your own domain.
- 01
Create the Zap
Start a new Zap. One trigger and one action: this Zap fits on the free plan, with no filter and no second step after the email.
- 02
Set the form trigger
Pick your form app and its new-submission event. Test it: Zapier brings back the three most recent submissions, so you map fields on a real one.
- 03
Add Send Email
Add MimePost and choose Send Email. Fill From Name, then Sender Username, the part of the address before the at sign, and pick your approved Sender Domain.
- 04
Write the message
Map the submitted email address into To, write the Subject, and build the Message Body in plain text or HTML with fields from the form.
- 05
Test and publish
Test the action with your own address in To, read what the test returns, then click Publish. Submissions made before that moment get no email.
MimePost action
MimePost gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Email
ActionIn Zapier“Send Emails Using Mimepost”
Sends one email through MimePost, from a sender on your approved domain, to the address you map, with a subject and a body in plain text or HTML.
When a MimePost Zap breaks
Zapier publishes no help article and no documented limit specific to MimePost. What breaks is what breaks on any Zap, plus the domain your sender depends on.
Four cases worth knowing before you switch the Zap on. If a run fails anyway, see our Zapier troubleshooting guide.
Past events get no email
A Zap only reacts to what happens after it is published. Submissions or records created before that moment never trigger an email; that backlog is a separate job.A Zap that keeps restarting itself
A Zap that writes into the very place its own trigger watches can set itself off again and again and burn through tasks fast, sending an email each time.A sudden flood of events
A trigger that suddenly returns a huge batch, after a bulk import or a migration for example, can be held back by Zapier's flood protection.No approved domain, no email
Send Email needs at least one approved domain to send. If the step does not go through for that reason, it is not counted against your plan.
Need help automating MimePost with Zapier?
A person reads every message.
