Resources · Zapier integration

PayPro Zapier integrationAutomate PayPro with Zapier.

The PayPro Zapier integration gives you 1 trigger, 0 actions and 0 searches: one event, New Sale, that carries each sale out of PayPro into your other tools. It is a polling trigger, so your plan decides how fast it reacts. Here is what that means in practice.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PayPro Zapier integration actually does

It takes the sales recorded in your PayPro account (a payment provider for selling your products, with affiliate marketing built in) and hands each one to your other apps, through Zapier. A sale is made, Zapier picks it up on its next check, and the rest of your tools hear about it without anyone copying a line.

Three results people build with that single trigger. A sales log that fills itself: New Sale adds a row per order to a spreadsheet, ready for you or your accountant. A customer welcomed by your own tools: the same trigger can pass the buyer to your mailing tool, so the onboarding sequence starts from your side. A team that hears about revenue: a message in a chat channel for each sale keeps everyone close to what sells.

Now what Zapier cannot do with PayPro, because the list is long. There is no action: a Zap cannot create a product, issue a refund or change anything in PayPro. There is no search, so it cannot look up an older order. And the only event is a new sale; nothing reports a refund, a cancellation or an affiliate commission on its own. PayPro sends sales out, full stop.

The other thing to know before you build is speed. New Sale is a polling trigger, which ties its delay to your plan; the cost section gives the grid. If you are weighing other tools for this, the Make vs Zapier comparison is a neutral starting point.

Vocabulary

Zapier vocabulary, in plain words

Seven words come back all along this page. Here they are once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts the Zap. Once the Zap is switched on, Zapier waits for it; with PayPro, that is always a new sale.
Action
What the Zap does once it has started: the step that writes or sends something for you. With PayPro, it always happens in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts exactly those.
Polling vs instant
A polling trigger is checked by Zapier on a timer, like New Sale. An instant trigger is reported by the app itself when the event happens.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it there otherwise.
Connection
Your PayPro account linked to Zapier once, then reused by every Zap that starts from PayPro.
Cost

What a PayPro Zap really costs

Zapier bills tasks, and only one thing creates a task: an action that works.

  • PayPro trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • PayPro on the free planYes, not reserved to paid plans
  • New SalePolling, interval set by your plan

PayPro only provides a trigger, so PayPro itself never costs a task. Zapier checking for new sales is free too, however often it checks. You pay for each successful action in the other apps of the Zap: one per run. A failed action is not counted. PayPro is not reserved to paid plans: the free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps. A second action or a filter makes it multi-step, which needs a paid plan. The grid below matters here, because New Sale is polled: on the free plan, a sale can wait up to 15 minutes before the Zap sees it.

Connect

Connect your PayPro account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a PayPro account first, plus access to any sales data you do not own yourself but want the Zap to read.

  2. 02

    Pick PayPro

    Type PayPro in the search box of the dialog that appears, select it in the results, then click Add connection to start the link. A new tab opens on PayPro's side.

  3. 03

    Sign in and grant access

    Log in to PayPro in that tab and allow Zapier to reach your account. The connection now shows on the Apps page, and every Zap that starts from PayPro can reuse it.

First Zap

Your first PayPro Zap, step by step

GoalEvery PayPro sale is logged in a sheet and announced in the team channel.

  1. 01

    Pick the trigger

    Create a Zap, choose PayPro as the app and New Sale as the event, then select the PayPro connection you just made. It is the only event on offer.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent sales of the account, so you map the next steps on a real order rather than a blank.

  3. 03

    Add the sheet

    Add the spreadsheet app as the first action and map the sale details into its columns. With two steps, this Zap runs on the free plan.

  4. 04

    Add the message

    Add the team chat app as a second action. That makes it a multi-step Zap, so this part needs a paid plan; on the free one, keep only the sheet.

  5. 05

    Test, then publish

    Test each action and check the result in both tools. Then click Publish to switch the Zap on. From then on, each check picks up the new sales.

Triggers

The PayPro trigger

1 event starts a Zap when something happens in PayPro. Zapier checks for them at the interval your plan allows.

1

New Sale

Polling trigger

In Zapier“Triggers when a new sale is made.”

Starts a Zap for each new sale made through PayPro. It is the one event the integration offers, so every PayPro automation begins here, whether it feeds a spreadsheet, a mailing list or a team channel.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
you want each order recorded or announced somewhere without exporting reports from PayPro.
Watch out
it only knows new sales; refunds or cancellations will not start the Zap, so a sheet built on it shows gross orders.
When it breaks

When a PayPro Zap breaks

Zapier lists no help article and no rate limit specific to PayPro. What trips people up is the general behaviour of Zaps, and the polling nature of New Sale.

None of this is a bug. Each case is how Zapier works, and each is easy to plan for. When something else goes wrong, the Zapier troubleshooting page is the next stop.

  • Old sales never arrive

    A Zap reacts only to what happens after it is switched on. Sales made before are not picked up, and moving that history is a separate job.

  • The sale shows up late

    New Sale is polled, so it waits for Zapier's next check: up to 15 minutes on the free plan. On a paid plan you can also run a check by hand from the editor.

  • A big batch gets held back

    If a check suddenly returns a huge number of sales, after a bulk import or a migration, Zapier's flood protection can hold those runs back.

  • Duplicates are filtered for you

    Zapier remembers which sales it has already seen on a polling trigger, so the same order does not start the Zap twice.
Need help

Need help automating PayPro with Zapier?

A person reads every message.

FAQ

PayPro and Zapier: questions people ask

01Is the PayPro Zapier integration free?
Yes, on Zapier's free plan. PayPro is not reserved to paid plans, so you can connect it and build Zaps without paying. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. New Sale plus a spreadsheet row fits that limit. A second action or a filter makes the Zap multi-step, which needs a paid plan. On the free plan, Zapier checks New Sale every 15 minutes. Plan prices change often, so check Zapier's plan page before choosing one.
02How many Zapier tasks does a PayPro Zap use?
PayPro itself uses none. The New Sale trigger costs nothing, and Zapier checking PayPro for new sales costs nothing either, however often it looks. Tasks come from the actions in your other apps: each one that succeeds counts once per run, and a failed one does not count. A Zap with New Sale and one action therefore uses one task per sale; with two actions, two. Your task budget follows your sales volume, so a good month can use up the free plan's 100 tasks faster than you expect.
03Does PayPro trigger Zaps instantly?
No. New Sale is a polling trigger: Zapier goes and asks PayPro for new sales at a fixed interval, and that interval depends on your plan. On the free plan it is 15 minutes, on Professional 2 minutes, and on Team and Enterprise 1 minute. The type comes from how PayPro built its integration and cannot be changed from the editor. On paid plans you can adjust how often the trigger checks, and run a check by hand. For a sales log, a short delay rarely matters.
04What does it take to connect PayPro to Zapier?
A PayPro account, plus access to the sales data if it belongs to someone else. The connection is made from the Apps page of your Zapier account: add a connection, search for PayPro, sign in to PayPro in the tab that opens and grant Zapier access. Every Zap that starts from PayPro then reuses that connection. New Sale does not ask for any required setting, so once connected you only pick the event and run a test, which brings back the three most recent sales of the account.
05Why don't older PayPro sales show up in a Zap?
Because a Zap only reacts to what happens after it is switched on. When you publish a Zap built on New Sale, Zapier starts watching from that point; sales made before were never part of its history and are not picked up later. The test step does show the three most recent sales, but only so you can map fields on a real example. If your spreadsheet must include past orders, move them into it once, as a separate job.
06What if the PayPro operation you need is not available?
Then Zapier cannot do it with PayPro, and the gap is wide: one trigger, no action, no search. A Zap cannot create a product, refund an order or look up an existing sale in PayPro, and no event reports refunds, cancellations or affiliate commissions. If your process needs one of those, that step stays manual in PayPro, or you would have to check whether another automation tool offers it. Compare what your process needs with the single trigger on this page before building.
07Zapier, Make or n8n for PayPro?
Decide on coverage and speed, not on reputation. On Zapier, PayPro gives you one polling trigger, New Sale, whose delay depends on your plan, and a two-step Zap runs on the free plan. There is no way to write back into PayPro. If you only need sales sent to other tools, that is enough. If you need more events or actions, check what another tool's PayPro connector offers, how quickly its trigger reacts, and how it bills each run, before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations