4Pay Zapier integrationAutomate 4Pay with Zapier.
The 4Pay Zapier integration gives you 2 actions, 0 triggers and 0 searches. 4Pay can create a payment widget and check a payment's status when another app asks, but it never starts an automation itself. Here is what each step needs, what it costs and where it trips.
Verified Trustpilot reviews · AI, automation & growth agency
What the 4Pay Zapier integration does for you
The integration lets another app drive 4Pay, the payment platform built around online acquiring, through a Zap: the automation you build on Zapier, where one event starts things and one or more steps follow. 4Pay supplies two of those steps, Create Payment Widget and Check Payment Status. It has nothing that can start a Zap, so 4Pay always comes after another tool.
A payment widget for every invoice you log. A small consulting firm keeps its invoices in a spreadsheet. Each new row runs Create Payment Widget with the amount, the client's name, a description and the invoice number as transaction ID. Nobody opens 4Pay to set up a payment by hand.
A status column that updates itself. The payment ID you get back after creating a widget goes into a tracking table. A Zap started from that table runs Check Payment Status on it, so the finance person reads the answer instead of logging in to look.
Course sales with a clean trail. An online trainer takes sign-ups through a form. Each sign-up creates a widget whose transaction ID is the sign-up reference, which makes reconciling payments against students far less painful.
What Zapier does not do with 4Pay: it cannot react to a payment arriving, because 4Pay exposes no trigger. It cannot look up an existing payment by customer or description either (no search). Refunds, payouts and any other operation are not on the list. If you need 4Pay to speak first, see what other platforms offer in Make vs Zapier and n8n vs Zapier.
Zapier words you will meet, in one minute
Eight terms come back on every Zapier screen. Here they are in plain English, with what they mean for 4Pay.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts a Zap; once the Zap is on, Zapier waits for it. 4Pay has none, so another app always fills this role.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you. Create Payment Widget is one.
- Task
- What Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those, nothing else.
- Polling vs instant
- Zapier checks a polling trigger on a timer, while an instant trigger is pushed by the app the moment it happens. The source app decides.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and halts it otherwise.
- Connection
- Your 4Pay account, linked to Zapier one time and then reused by every 4Pay step in every Zap you build.
- Multi-step Zap
- Any Zap with more than one trigger and one action. A second action, a filter or a search turns it into one, and it then needs a paid plan.
What a 4Pay Zap really costs
4Pay is not a premium app, so it runs on the free plan. Only actions that succeed are billed.
- Trigger check0 tasks
- Successful 4Pay action1 task each
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo
The trigger in your source app never costs a task, however often Zapier checks it. Each Create Payment Widget or Check Payment Status that goes through counts as one task, and one that fails costs nothing. The free plan gives 100 tasks a month, but only two-step Zaps. Chaining both 4Pay actions in one Zap, or adding a filter in front, makes it multi-step and needs a paid plan. The plain sheet-to-widget Zap stays free; the version that also writes the payment ID back does not.
Connect 4Pay to Zapier in three steps
- 01
Start from the Apps page
In your Zapier account, open the Apps page and click + Add connection. A dialog appears with a search box: type 4Pay and select it in the results list.
- 02
Sign in to 4Pay
Click Add connection. A new tab opens on 4Pay: sign in with your 4Pay account and grant Zapier access to it. The connection is stored and every 4Pay step reuses it from then on.
- 03
Confirm access before building
The account you used needs read or write access to anything it does not own but that your Zaps will touch. Settle that in 4Pay first, so the first test of an action does not stall on missing rights.
Your first Zap: a payment widget per invoice
GoalEach invoice added to a Google Sheets ledger produces a 4Pay payment widget, with the invoice number as transaction ID.
- 01
Pick the starting app
Create a new Zap. 4Pay has no trigger, so start from Google Sheets and its new-row event, then choose the invoice ledger and the tab where invoices are added.
- 02
Test on real invoices
Run the test. Zapier brings back the three most recent rows, so you map the next step on a real invoice instead of a blank sample.
- 03
Add Create Payment Widget
Add an action, choose 4Pay and Create Payment Widget, then your connection. Map Amount, Customer, Description and Transaction ID from the matching columns of the row.
- 04
Write the payment ID back
Add a Google Sheets step that writes the payment ID 4Pay returns into the same row. This third step makes the Zap multi-step, so it needs a paid plan.
- 05
Test, then publish
Test each step once and read what came back, especially the amount. Then click Publish: from now on, every new invoice row gets its widget.
The 2 actions of the 4Pay Zapier integration
4Pay gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Payment Widget
ActionIn Zapier“Creates a Payment Widget”
Sets up a new 4Pay payment widget from the data your trigger carries: Amount, Customer, Description and Transaction ID are all required.
Check Payment Status
ActionIn Zapier“Checks Payment Status”
Asks 4Pay where a given payment stands, using one required value: the Payment ID received when its widget was created.
When a 4Pay Zap breaks
Zapier attaches no help article to 4Pay and lists no limit specific to it. What goes wrong comes from general Zapier behavior and from the required fields.
Four cases explain most failures. When a run stops, the Zap history shows which step failed; the Zapier troubleshooting guide explains how to read it.
Old invoices get no widget
A Zap only reacts to what happens after you switch it on. Invoices already in the ledger stay out: handling that backlog is a separate job.An amount in the wrong unit
Amount is expected in the minor currency unit. Feed it a value in whole units and the widget asks for the wrong sum.A status check with no Payment ID
Check Payment Status needs the Payment ID returned at widget creation. If it was never stored, the step has nothing to look up.A loop that drains your tasks
If the Zap writes back into the very place its trigger watches, as a new row rather than an update, it sets itself off again and again.
Need help automating 4Pay with Zapier?
A person reads every message.
