Resources · Zapier integration

Onepay Zapier integrationAutomate Onepay with Zapier.

The Onepay Zapier integration has 0 triggers, 1 action and 0 searches. It works in one direction only: another app starts the Zap, and Onepay receives a payment built from what that app sent, with the amount and the customer's details mapped in.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Onepay Zapier integration does for you

Zapier is a service that makes your apps work together, without code. With Onepay, the payment platform, it plays a single role: when something happens in another tool, such as a new order or a signed booking, it creates the matching payment in Onepay for you, so nobody types the same customer details twice.

Three results people usually aim for, all built on the one action, Make Payment. A payment raised in Onepay for every order logged in a spreadsheet. A payment prepared the moment a booking or registration is confirmed in your scheduling or form tool, if that tool's trigger is instant. And a payment created from a deal marked won in your CRM, so sales does not hand over by email.

Now the limits, because they are strict. Onepay has no trigger on Zapier: nothing that happens inside Onepay, a payment received or a link paid, can start a Zap. It has no search step either, so a Zap cannot check whether a payment already exists before creating one. And the action asks for five mandatory pieces of information: the amount and the customer's first name, last name, phone number and email. If the app that starts the Zap does not hold all five, the action cannot run.

That narrow scope makes the tool choice worth a look. Two pages to keep at hand: Zapier review and Make vs Zapier.

Vocabulary

Zapier words, in plain English

Eight terms come back throughout the page. One sentence each.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts a Zap. Onepay has none, so the trigger always comes from another app, such as a sheet or a form.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, here a payment in Onepay.
Task
The unit Zapier bills: one action completed successfully. The allowance on your plan is a monthly count of those.
Polling vs instant
Polling: Zapier checks an app on a timer. Instant: the app tells Zapier itself. With Onepay, it depends on the trigger app.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up something already stored in an app. Onepay offers none, so a lookup has to happen elsewhere.
Connection
Your Onepay account linked to Zapier once, then reused by every Zap step that creates a payment.
Cost

What it really costs

Zapier bills tasks, and only actions that work are counted. Each payment Make Payment creates successfully is one task; the trigger in the other app costs nothing.

  • Trigger in the other app0 tasks
  • Make Payment, successful1 task
  • Make Payment, failedNot counted
  • Free plan100 tasks a month, two-step Zaps
  • Onepay on freeYes

The free plan gives you 100 tasks a month, unlimited Zaps and a polling check every 15 minutes on the trigger app, if that trigger polls. Onepay is not reserved for paid plans, so it runs on Free. The limit to watch is the step count: free Zaps stop at one trigger and one action. A filter, a second action or a search step makes the Zap multi-step, and that needs a paid plan. A payment action that fails is not counted against your plan.

Connect

Connect your Onepay account

  1. 01

    Open Apps and start a connection

    In your Zapier account, go to the Apps page and click + Add connection. A dialog opens with a search box: type Onepay and pick it from the list of results.

  2. 02

    Sign in to Onepay

    Click Add connection. A new tab opens on the Onepay sign-in. Log in with the business account that should receive the payments, since every Zap built on this connection writes into it.

  3. 03

    Grant access

    Allow Zapier to access the account. The connection is saved and reused by every Make Payment step. If the Onepay account belongs to someone else in the company, make sure you have write access to it before building.

First Zap

Your first Zap: from order sheet to Onepay payment

GoalEach new order row that meets your condition becomes a payment in Onepay, with the customer details already filled in.

  1. 01

    Pick the trigger in your sheet

    Build a new Zap. Choose your spreadsheet app as the app that starts it and its new row event, then point it to the sheet where orders are logged.

  2. 02

    Test on a real row

    Run the trigger test. Zapier brings back the three most recent rows. Pick one with every customer detail filled in, so the mapping rests on a complete example.

  3. 03

    Add the filter

    Click the plus icon, choose Filter and fill the three boxes: the field to look at, the rule, the value to compare with. Use a number rule on amounts and a text rule on text.

  4. 04

    Add Make Payment

    Add the action step: Onepay, event Make Payment. Map the amount, then the customer's first name, last name, phone number and email from the row. All five are mandatory.

  5. 05

    Test, then publish

    Test each step and read what came back before going further. Then click Publish to switch the Zap on. With the filter it is a multi-step Zap, so it runs on a paid plan.

Actions

Onepay actions

Onepay gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Make Payment

Action

In Zapier“Make a payment in the system”

Creates a payment in Onepay for a given customer and amount, using the details the trigger app passed along, so billing starts without a manual entry.

When to use it
a client signs up for a course through your form and the matching payment should be ready in Onepay.
Watch out
Amount, Customer First Name, Customer Last Name, Customer Phone Number and Customer Email are all mandatory; one missing value and the step fails.
When it breaks

When it breaks

Zapier attaches no help article to Onepay, and no limit specific to the app is documented. What can go wrong comes from how Zapier works and from the mandatory fields of the action.

  • A missing customer detail

    Make Payment refuses to run without its five mandatory values. A row or form entry with no phone number or email stops the Zap at this step.

  • Earlier orders are not billed

    A Zap only reacts to what happens after you switch it on. Orders already logged before that are not sent to Onepay; handling that backlog is a separate job.

  • A sudden flood gets held back

    After a bulk import or a migration, the trigger app can return a huge batch at once, and Zapier's flood protection may hold it back.

  • A polled item never runs twice

    On a polling trigger, Zapier remembers what it has already seen, so the same row or entry does not start the Zap a second time.
Need help

Need help automating Onepay with Zapier?

A person reads every message.

FAQ

Onepay and Zapier: common questions

01Is the Onepay Zapier integration free?
Yes. Onepay is not one of the apps Zapier keeps for paid plans, so it works on the free plan. That plan gives you 100 tasks a month and as many Zaps as you like. The real limit is the shape of the Zap: one trigger and one action, nothing more. A filter, a second action or a search step makes it multi-step, which needs a paid plan. Since Onepay has no trigger, the free version is always a trigger from another app followed by Make Payment. Plan figures change often, so check them on Zapier.
02How many tasks does a Onepay Zap use?
One task for each payment Make Payment creates successfully, and nothing for the trigger. The app that starts the Zap can be checked as often as your plan allows without costing a task. If the payment step fails, for instance because a mandatory field was empty, it is not counted. In a Zap with several actions, every action that succeeds counts on its own, so adding a confirmation email after the payment doubles the tasks per run. A few apps and actions take more than one task, so read each step in the editor.
03Can a Onepay Zap run in real time?
It depends on the app that starts it, because Onepay has no trigger of its own. If that app's trigger is instant, it tells Zapier itself and the payment is created right away, on any plan. If the trigger polls, Zapier checks on a timer: every 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. The editor shows a lightning bolt on Zaps that start on an instant trigger. So to go faster, pick a trigger app that reports events itself rather than upgrading by reflex.
04What do you need to connect a Onepay account?
A Onepay account, plus write access if the account is not yours and the Zap should create payments in it. Then three moves. Open the Apps page of your Zapier account and click + Add connection. Search for Onepay and pick it. Click Add connection, sign in to Onepay in the tab that opens, and grant Zapier access. The connection is saved once and every Zap that uses Make Payment reuses it, so you do not repeat the sign-in for each new Zap.
05Why does Make Payment fail on some runs?
Check its five mandatory fields first: a run stops when one arrives empty. The action needs the Amount, the Customer First Name, the Customer Last Name, the Customer Phone Number and the Customer Email. If the trigger app sometimes lacks one of them, a form where the phone is optional for example, those runs stop at the payment step. Make the field required at the source, or add a filter that lets the Zap continue only when every value is present, keeping in mind that a filter needs a paid plan.
06What if the Onepay operation you want is not listed?
Then Zapier does not offer it for this app. The editor shows a single operation for Onepay, the Make Payment action. There is no trigger, so a payment received in Onepay cannot start a Zap, and there is no search step to check an existing payment. The usual workaround is to keep Onepay at the end of the Zap and let other apps handle what comes before and after. If reacting to Onepay events is central to the project, compare automation tools before building.
07Zapier, Make or n8n for Onepay?
Decide on criteria rather than reputation. First, coverage: on Zapier, Onepay offers one action and nothing else, so check what each tool lists for the operations your scenario needs, a payment-received trigger in particular. Second, speed: on Zapier the delay is set by the trigger app, instant or polling, not by Onepay. Third, the shape of your workflow: one trigger and Make Payment stay on the free plan, while a filter or extra steps call for a paid one. Weigh those points against your budget and skills.
Same platform

Other docs you might need on this stack.

Browse all integrations