Resources · Zapier integration

Pepipost Zapier integrationAutomate Pepipost with Zapier.

The Pepipost Zapier integration has 0 triggers, 1 action and 0 searches. Pepipost cannot start a Zap: another app does that, and Pepipost's single action, Send Email, sends a message through your account at the end of the chain.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pepipost Zapier integration is good for

It lets any Zap send an email through your Pepipost account. Pepipost never starts the Zap itself: an event in another app does, a form entry, a new order, a booking, and Send Email turns that event into a message sent from your own sender domain, under your name.

Three results people build with it. A confirmation for every form entry: the form tool starts the Zap, Send Email thanks the person from your domain. An order email from the shop: a new sale in your store triggers a message with the order details in the body. An internal alert: a new row in a shared sheet emails the person in charge, so nobody has to watch the sheet.

What Zapier does not do with Pepipost is just as clear. There is no trigger, so nothing that happens in Pepipost, a bounce, an open, a click, can start a Zap. There is no search step, and no action beyond Send Email: no contact lists, no templates picked from the account, no scheduling. Each run sends one email, built from the six fields you fill in, and each email sent is one task on your plan.

If you are weighing tools before you build, see Make vs Zapier. For the bigger picture of Zapier itself, read the Zapier review.

Vocabulary

Zapier words in one minute

Seven terms, one line each. They come back on every screen of the editor.

Zap
The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. Pepipost has none, so it always comes from another app, such as a form tool.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you. Here, Send Email.
Task
The unit Zapier bills: one action that completes successfully. With Pepipost, one email sent is one task.
Instant vs polling trigger
An instant trigger is reported by its app the moment the event happens; a polling one is checked by Zapier on a timer.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your Pepipost account linked to Zapier once, then reused by every Send Email step of every Zap.
Cost

What a Pepipost Zap really costs

The trigger in the other app costs nothing. Each Send Email that succeeds costs one task, and one that fails is not counted against your plan.

  • Trigger (other app)0 tasks
  • Each email sent1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on Free

Pepipost is not a premium app, so it works on the free plan: 100 tasks a month, which means at most 100 emails sent through Zapier, unlimited Zaps and two steps per Zap. A trigger plus Send Email fits. A filter or a second action makes it multi-step, which needs a paid plan. If the trigger app polls, its check interval follows the grid below; if its trigger is instant, the email goes out without that wait.

Connect

Connect Pepipost to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Pepipost account first, with the sender domain you plan to send from already set up.

  2. 02

    Pick Pepipost

    Type Pepipost in the search box of the dialog, select it, then click Add connection. A new tab opens on the Pepipost side to finish linking the accounts.

  3. 03

    Sign in and grant access

    Log in to Pepipost in that tab and allow Zapier to use the account. The connection is saved once, and every Send Email step of every Zap you build reuses it.

First Zap

Your first Zap: a confirmation email for each form entry

GoalWhen someone fills in your web form, send them a confirmation from your own domain through Pepipost, but only when your condition passes.

  1. 01

    Pick the trigger

    Build: choose your form tool as the app that starts the Zap and its new-entry event, then connect your form account to Zapier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent entries of the form, so you map the email on a real one rather than a blank.

  3. 03

    Add the filter

    Add a Filter from the plus icon and set the field, the rule and the value. A text rule only works on text: pick the wrong type and it never passes.

  4. 04

    Add Send Email

    Pick Pepipost and Send Email, then fill the six required fields: the sender username, domain and name, the recipient from the form, a subject and the content.

  5. 05

    Test and publish

    Send the test to an inbox you own, read what arrives, then click Publish. The filter makes this a paid multi-step Zap; drop it to stay on Free.

Actions

The Pepipost action

Pepipost gives you 1 action. 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“Send emails using your Pepipost account.”

Sends one email through your Pepipost account, from your domain and sender name, to the recipient the earlier steps provide, with plain text or HTML content.

When to use it
a booking tool records an appointment and the client should get a confirmation that looks like it comes from you.
Watch out
From Email Username is only the part before the @ (test for test@yourdomain), and the domain is picked separately in From Sender Address.
When it breaks

When a Pepipost Zap breaks

Zapier attaches no help article to Pepipost, and no sending limit of its own is documented on the Zapier side. What breaks is what breaks on any Zap that sends.

  • Past entries never get an email

    A Zap reacts only to what happens after it is published. People who filled your form last week will not receive anything; that backlog is a separate job.

  • A big import becomes a big send

    Load hundreds of rows into the trigger app at once and the trigger returns a huge batch. Zapier's flood protection can hold it back before the emails go out.

  • The free plan runs dry

    Every email sent is one task. On Free that is 100 a month, shared with your other Zaps, and a busy form can use them up before the month ends.

  • The username holds the full address

    From Email Username wants only the part before the @. Typing the whole address there, or picking no sender domain, leaves the sender wrong or the step incomplete.
Need help

Need help automating Pepipost with Zapier?

A person reads every message.

FAQ

Pepipost and Zapier: common questions

01Is the Pepipost Zapier integration free?
Yes, on Zapier's side. Pepipost is not a premium app, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. Since each email sent is one task, that is up to 100 emails a month through Zapier. The free plan also stops at two-step Zaps: a trigger in another app plus Send Email fits, but a filter or a second action makes the Zap multi-step and needs a paid plan. Your Pepipost account is billed separately.
02How many tasks does a Pepipost Zap use?
One per email that goes out successfully, and nothing for the trigger. A Zap that confirms each form entry uses one task per entry. If the same Zap also adds a row to a sheet, that is two tasks per entry. A Send Email that fails is not counted against your plan. Because Pepipost exists in Zapier only to send, the volume of events in the trigger app is exactly the volume of tasks you will spend.
03Is Pepipost on Zapier real time?
That depends on the other app, because Pepipost has no trigger of its own. If the app that starts the Zap has an instant trigger, it reports the event to Zapier itself and the Zap starts straight away, whatever the plan. If it has a polling trigger, Zapier checks it on a timer: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. The editor shows a lightning bolt on a Zap built on an instant trigger.
04What do you need to connect Pepipost to Zapier?
A Pepipost account with at least one sender domain set up, since Send Email asks you to pick one. The connection takes three moves: open the Apps page of your Zapier account and click + Add connection, search for Pepipost and click Add connection, then sign in to Pepipost in the tab that opens and grant Zapier access. The connection is saved once, and every Send Email step of every Zap reuses it.
05What goes in From Email Username?
Only the part of the sender address before the @. If you send from test@yourdomain, the username is test, and the domain is chosen on its own in From Sender Address. Then come From Name, the name the recipient sees, the Recipient, the Subject and the Email Content, in plain text or HTML. All six fields are required. Map the Recipient from a trigger field that always holds an address, so no run reaches Send Email without one.
06What if the Pepipost operation you need isn't there?
Then Zapier cannot do it for Pepipost today. The app offers a single action, Send Email, and nothing else: no trigger on bounces, opens or clicks, no search, no contact or template management. If the workflow depends on reacting to what happens after the email is sent, Zapier has no step for it here. Check the app page on Zapier before planning around a missing step, and keep that part of the work in Pepipost itself.
07Zapier, Make or n8n for Pepipost?
Choose by criteria rather than by name. On Zapier, Pepipost gives you one action, Send Email, no trigger and no search, and it runs on the free plan, where each email is one of your 100 monthly tasks. So ask each tool three things: can it send through Pepipost with your sender domain, can it react to what happens after sending, and what does a sending volume like yours cost there. The answer depends on that volume and your workflow.
Same platform

Other docs you might need on this stack.

Browse all integrations