Resources · Zapier integration

Payload Zapier integrationAutomate Payload with Zapier.

The Payload Zapier integration gives you 0 triggers, 2 actions and 0 searches. Payload is not a premium app, so it runs on the free plan, but every Zap has to start in another tool. Here is what both actions do, what they cost and what trips people up.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Payload Zapier integration does, and what it leaves out

The Payload Zapier integration lets Zapier, a tool that chains steps between apps without code, ask Payload to do things for you. Payload never starts anything here: another app reports an event, and Payload carries out one of its two actions, such as emailing a customer a link to pay.

Payment requests that leave without copy and paste. Send Payment Request emails a payment link to a customer, with the amount, their name and their address taken from the step before. A signed quote, a booked session or a row in a billing sheet can all start it.

A payment status that reaches you. Payment Webhook registers an address of your choosing with Payload, so status changes on payments get sent there. It is a one-off setup step rather than something to run on every event.

One place for the amount, one place for the link. Your quote or booking tool keeps the commercial side, and Payload handles the collection, without anyone retyping figures between the two.

What Zapier does not do here: Payload has no trigger and no search in the editor. A Zap cannot start on a new payment in Payload, nor look one up. Refunds and cancellations stay in Payload itself.

For a broader view of the tool, read our Zapier review, or the Make vs Zapier comparison.

Vocabulary

The Zapier vocabulary in one minute

Seven terms in plain words, used afterwards without being explained twice.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event that starts the Zap. Payload has none, so the trigger always comes from another app you use.
Action
What the Zap does once started: the step that writes or sends something for you. Payload offers two of them.
Task
What Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Instant vs polling
An instant trigger is reported by its app with no wait. A polling one is checked by Zapier on a timer whose length depends on your plan.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Payload account linked to Zapier once, then reused by every Payload step in every Zap you build.
Cost

What a Payload Zap costs

Zapier bills tasks, not Zaps. The trigger in the other app never costs one; each Payload action that succeeds does.

  • Free plan100 tasks a month, two-step Zaps only
  • Per payment requestOne task when it succeeds
  • Premium appNo, works on the free plan
  • Payload triggersNone, the Zap starts elsewhere

Every action that goes through counts as one task, so one payment request equals one task. A failed action is not counted. The free plan gives 100 tasks a month, unlimited Zaps and two steps per Zap: one trigger, one action. A filter or a second action makes it multi-step, which needs a paid plan. Payload works on the free plan. How fast the Zap starts depends on the trigger of the other app: if it polls, the grid below applies.

Connect

Connect your Payload account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Payload account, plus access to anything you do not own yourself and want a Zap to change.

  2. 02

    Pick Payload

    Type Payload in the search box of the dialog, select it, then click Add connection. A new tab then opens on the Payload side so you can sign in there.

  3. 03

    Sign in and grant access

    Sign in to Payload in that tab and allow Zapier into the account. The connection is saved, and every Payload step of every Zap reuses it from then on.

First Zap

Your first Payload Zap, step by step

GoalEach new row in a billing sheet that passes a check sends the customer a Payload payment link.

  1. 01

    Pick the trigger

    Create a Zap and choose the app and event that start it, here a new row in the sheet where you prepare billing. Payload has no trigger of its own.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so the mapping is done on a real row rather than an invented one.

  3. 03

    Add a filter

    Add a Filter from the plus icon and set the field, the rule and the value, so only rows ready to bill go further. Use a text rule on text.

  4. 04

    Add Send Payment Request

    Pick Payload and Send Payment Request, then map the amount, the names and both email fields from the row. Type in your Processing ID.

  5. 05

    Test and publish

    Test each step and read what came back, then publish to switch the Zap on. With a filter it is a multi-step Zap, so it needs a paid plan.

Actions

Payload actions in Zapier

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

1

Payment Webhook

Action

In Zapier“Create a Webhook to watch for payment status”

Registers an address with Payload so that payment status changes are sent there. The only required field is that address, labelled Webhook URL.

When to use it
a team that wants another tool told when a payment changes status, and has an address ready to receive it.
Watch out
this sets something up once; running it on every event of a busy trigger would repeat the setup and spend a task each time.
2

Send Payment Request

Action

In Zapier“Sends a payment link to an email”

Emails a customer a link to pay the amount you set. Amount, Email, Processing ID, Name, Customer Name and Customer Email are all required.

When to use it
a freelancer or a clinic that wants every confirmed booking followed by a payment link, without opening Payload.
Watch out
two email fields exist, one for the link and one for the receipt, so map each to the right address.
When it breaks

When a Payload Zap breaks

Zapier links no help article to Payload, and no limit specific to the app is documented. What goes wrong is what goes wrong on any Zap.

  • Older rows are never picked up

    A Zap only reacts to what happens after it is switched on. Customers already in your sheet will not get a payment link unless you send those another way.

  • A Zap that sets itself off

    If a Zap writes back into the very place its trigger watches, it starts itself again and again, and burns through the task count fast.

  • A sudden flood is held back

    After a bulk import, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection instead of sending every request.

  • No double sends on polling

    When the trigger polls, Zapier keeps track of what it has already seen, so the same row does not send the same payment request twice.
Need help

Need help automating Payload with Zapier?

A person reads every message.

FAQ

Payload Zapier integration: frequent questions

01Is the Payload Zapier integration free?
Yes, it works on the free plan, because Payload is not one of the premium apps Zapier keeps for paid plans. The free plan gives 100 tasks a month and unlimited Zaps. The limit is the shape of each Zap: one trigger and one action, nothing more. A Zap that starts in your billing sheet and sends a Payload payment request fits. Add a filter to send only some rows, or a second action, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a Payload Zap use?
One task each time a Payload action succeeds, so one payment request sent equals one task. The trigger, which lives in another app, never costs anything, and neither does Zapier checking that app for new items. An action that fails is not counted. Payment Webhook is a setup step: run once, it costs one task, but placed after a busy trigger it would spend a task on every event for no gain. A few apps and actions take more than one task when they complete.
03Can a Payload Zap run in real time?
It depends entirely on the trigger, because Payload has none. The Zap starts on an event in another app, and that app decides the timing. If its trigger is instant, the app reports the event to Zapier right away and the Zap starts whatever your plan. If it polls, Zapier checks on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. Pick a starting app with an instant trigger when speed matters.
04What does it take to connect Payload to Zapier?
A Payload account, plus access to anything you do not own yourself and want a Zap to change. The connection is made once from the Apps page of Zapier with + Add connection: you sign in to Payload in the tab that opens and grant access. Every Payload step then reuses it. Before building, have your Processing ID at hand, because Send Payment Request will not go through without it: it tells Payload which processing account receives the funds.
05Why are there two email fields in Send Payment Request?
Because they do different jobs, and both are required. Customer Email is where Payload sends the payment link. Email is where the receipt goes. The same goes for names: Name and Customer Name are both required. The trap is mapping the same value into both email fields by reflex, or swapping them, and then wondering why receipts land in the wrong inbox. Check both on the test run before publishing, with an address you control.
06What if the Payload operation you need is missing?
Then Zapier cannot do it with Payload, and no setting will reveal it. The integration offers two actions, Send Payment Request and Payment Webhook, and no trigger or search: a Zap cannot start on a new Payload payment, look one up, refund it or cancel it. Those jobs stay in Payload. What you can do is start from another app and let Payload send the request. If you need a lot more on the Payload side, compare what other automation tools offer first.
07Zapier, Make or n8n for Payload?
Decide on criteria rather than a ranking. On Zapier, Payload offers two actions and no trigger or search, and it works on the free plan with two-step Zaps. So check three things: does the other tool let you start a flow on a Payload event, which Zapier does not; does it cover sending a payment request; and how does it bill a run with several steps? If you only need to send payment links from another app, the Zapier side already covers it.
Same platform

Other docs you might need on this stack.

Browse all integrations