Resources · Zapier integration

PayRequest Zapier integrationAutomate PayRequest with Zapier.

The PayRequest Zapier integration gives you 8 triggers, 2 actions and 1 search. Five triggers are instant, three are older polling versions you can mostly skip. It runs on the free plan, two steps per Zap. Here is what each operation does.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PayRequest Zapier integration actually does

It links your PayRequest account (the tool you use to send payment links and run a branded payment page) with your other apps, through Zapier. A payment goes through or a subscription changes state, and Zapier carries that event wherever it is useful. It also works the other way: an event elsewhere can create a payment link in PayRequest.

Three results people build first. A payment log that keeps itself: Payment Succeeded adds each successful payment to a spreadsheet or an accounting tool. A churn alert: Subscription Cancelled tells the account owner the moment a customer leaves, while there is still time to call. A payment link on demand: a booking or an order elsewhere starts the Zap, and Create Payment Link produces a link for the right amount, ready to send.

What Zapier does not do for PayRequest: there is no action to refund, cancel or change a subscription, and no way to edit or delete a payment link once created. The only search finds a subscription, and only by its ID, so it cannot look up a customer by name or email.

One more thing before you pick a trigger. Three of them carry (Legacy) in their name and work by polling, so their delay depends on your plan. Each one has a newer instant counterpart that does the same job without waiting; the notes below pair them up. For a broader view of the tool itself, see the Zapier review.

Vocabulary

Zapier vocabulary, in plain words

Eight 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, here a payment or a subscription change in PayRequest.
Action
What the Zap does once it has started: the step that writes, sends or creates something for you, such as a PayRequest payment link.
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. An instant trigger is reported by the app itself, at the moment 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.
Search step
A step that looks up something already in an app, so the steps after it can reuse what it found, like an existing subscription.
Connection
Your PayRequest account linked to Zapier once, then reused by every step of every Zap that touches PayRequest.
Cost

What a PayRequest Zap really costs

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

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • PayRequest on the free planYes, not reserved to paid plans
  • PayRequest triggers5 instant, 3 polling (Legacy)

The trigger costs nothing, and neither does Zapier checking for new data. Each action that succeeds counts once, so a Zap with two actions uses twice what a one-action Zap does. A failed action is not counted. PayRequest is not reserved to paid plans: the free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. A second action, a filter or a search makes it multi-step, which needs a paid plan. The grid below applies only to the three Legacy triggers, which are polled. The five others are instant, so on any plan they start the Zap without waiting.

Connect

Connect your PayRequest account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a PayRequest account first, plus access to anything you do not own yourself but want the Zap to touch.

  2. 02

    Pick PayRequest

    Type PayRequest 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 PayRequest's side.

  3. 03

    Sign in and grant access

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

First Zap

Your first PayRequest Zap, step by step

GoalWhen a subscription is cancelled, PayRequest creates a payment link and the customer gets it by email.

  1. 01

    Pick the trigger

    Create a Zap, choose PayRequest as the app and Subscription Cancelled as the event, then select your PayRequest connection. It is the instant version, so no waiting.

  2. 02

    Test the trigger

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

  3. 03

    Add the payment link

    Add PayRequest with Create Payment Link. Description, Amount and Currency are required: write a clear description and set the amount of your offer.

  4. 04

    Add the email

    Add your email app as a second action and insert the link from the previous step into the message. Two actions make this a multi-step Zap, which needs a paid plan.

  5. 05

    Test, then publish

    Test each action and check the link and the email before going further. Then click Publish to switch the Zap on. Only cancellations from then on count.

Triggers

The 8 PayRequest triggers

8 events start a Zap when something happens in PayRequest, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Cancelled Subscription (Legacy)

Polling trigger

In Zapier“Triggers when a subscription is cancelled.”

Starts a Zap when a subscription is cancelled. It is the older version of this event, kept for Zaps built before the newer one existed.

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
only if an existing Zap already relies on it and works the way you want.
Watch out
for a new Zap, Subscription Cancelled covers the same event and is instant, so it does not depend on your plan.
2

New Payment (Legacy)

Polling trigger

In Zapier“Triggers when a new payment is received.”

Goes off when a new payment reaches your PayRequest account. Like the other Legacy triggers, it predates the instant events and is still offered for older setups.

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 maintain an older Zap built on it and do not want to rebuild it yet.
Watch out
Payment Succeeded reports successful payments instantly; prefer it when you build something new.
3

New Subscription (Legacy)

Polling trigger

In Zapier“Triggers when a subscription is activated.”

Fires when a subscription is activated in PayRequest. Despite its name, it watches activation rather than creation, which matters if you also run trials or pending subscriptions.

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
an existing Zap depends on it and you are not ready to switch.
Watch out
Subscription Activated covers activations instantly, and Subscription Created covers creations; choose the one that matches your intent.
4

Payment Succeeded

Instant trigger

In Zapier“Triggers when a payment succeeds in PayRequest.”

Reacts each time a payment succeeds in PayRequest. This is money actually collected, so it is the right base for anything that records revenue or thanks a customer.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a spreadsheet, an accounting tool or a team channel should get a line for each payment.
Watch out
it only reports payments that succeed, so a failed attempt never starts the Zap and cannot be chased from here.
5

Subscription Activated

Instant trigger

In Zapier“Triggers when a subscription or trial becomes active.”

Kicks in when a subscription or a trial becomes active. That is the moment a customer can actually use what they signed up for, which makes it the cleanest point to start onboarding.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
new members should get access, a welcome email or a spot in your community.
Watch out
trials count too, so a filter may be needed if paying customers get a different welcome.
6

Subscription Cancelled

Instant trigger

In Zapier“Triggers when a subscription is cancelled.”

Cancellations are its whole job, and it is the instant counterpart of the Legacy cancellation trigger, and the one to use for anything new.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the account owner should hear about a departure while a call can still change the outcome.
Watch out
no PayRequest action can reactivate a subscription; the follow-up has to happen by message or through a new payment link.
7

Subscription Created

Instant trigger

In Zapier“Triggers when a subscription is created, including pending subscriptions.”

Responds to every new subscription, including pending ones that are not active yet. It catches sign-ups earlier than Subscription Activated does.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your CRM should log a new subscriber the moment they sign up, paid or not.
Watch out
pending subscriptions are included, so do not grant access from this trigger; Subscription Activated is safer for that.
8

Subscription Renewed

Instant trigger

In Zapier“Triggers when a subsequent subscription payment succeeds.”

Tracks every successful subscription payment after the first one. It tells you a customer stayed for another period, which is a different signal from a brand-new payment.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you track retention in a sheet or want to thank loyal customers on each renewal.
Watch out
on a busy subscription base this fires a lot, and every action it runs costs a task.
Actions

The 2 PayRequest actions

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

2

Create Request (Legacy)

Action

In Zapier“Creates a PayRequest payment request.”

Creates a payment request in PayRequest. It is the older way of asking a customer to pay, still listed for Zaps that already use it.

When to use it
only to keep an existing Zap running as it is.
Watch out
for new Zaps, Create Payment Link is the current action; it asks for a description, an amount and a currency.
Searches

The PayRequest search

1 search step looks for data that already exists in PayRequest, so a later step can use it.

A search step looks for something already in PayRequest and hands it to the next steps. In the editor, it sits at the bottom of the Action event list, under SEARCH. PayRequest offers no find-or-create variant, and adding a search makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the result is not what you expected.

1

Find Subscription

Search

In Zapier“Finds a PayRequest subscription by its ID.”

Retrieves a PayRequest subscription from its ID, the only required field, and passes its details to the following steps.

When to use it
a Zap that starts from a payment needs the full subscription behind it before updating your CRM.
Watch out
without an ID from an earlier step there is nothing to search with; a customer name or email will not work.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Find Subscription does not offer it, so creating anything must be a separate action.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass every match along at once.
When it breaks

When a PayRequest Zap breaks

Zapier lists no help article and no rate limit specific to PayRequest. What breaks is the general behaviour of Zaps, plus the split between Legacy and instant triggers.

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

  • Past payments never arrive

    A Zap reacts only to what happens after it is switched on. Payments and subscriptions from before are ignored, and moving that history is a separate job.

  • A Legacy trigger runs late

    The three Legacy triggers are polled, so they wait for Zapier's next check: up to 15 minutes on the free plan. Their instant counterparts do not wait.

  • A sudden batch gets held back

    If a large number of payments or subscriptions reaches Zapier at once, after an import for instance, its flood protection can hold those runs back.

  • Duplicates on Legacy triggers

    Zapier remembers what it has already seen on a polling trigger, so the same payment does not start a Legacy-based Zap twice.
Need help

Need help automating PayRequest with Zapier?

A person reads every message.

FAQ

PayRequest and Zapier: questions people ask

01Is the PayRequest Zapier integration free?
Yes, on Zapier's free plan. PayRequest 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 every Zap is limited to two steps: one trigger and one action. Payment Succeeded writing a spreadsheet row fits that limit. A second action, a filter or a search turns it into a multi-step Zap, which needs a paid plan. Plan prices move often, so check Zapier's plan page before you choose.
02How many Zapier tasks does a PayRequest Zap use?
One task per action that succeeds, each time the Zap runs. The trigger costs nothing, and Zapier checking PayRequest for new events costs nothing either. So a Zap with Subscription Cancelled and one action uses one task per cancellation; with Create Payment Link and an email, two. A failed action is not counted. Volume is what to watch: Payment Succeeded fires on every successful payment and Subscription Renewed on every renewal, and on the free plan's 100 tasks a month that adds up quickly on a large subscriber base.
03Do PayRequest triggers start a Zap instantly?
Five of the eight do. Payment Succeeded, Subscription Activated, Subscription Cancelled, Subscription Created and Subscription Renewed are instant: PayRequest tells Zapier the moment the event happens, whatever your plan. The three triggers marked Legacy are polling: Zapier checks at a fixed interval that depends on your plan, 15 minutes on the free one. The type cannot be changed from the editor. Each Legacy trigger has an instant counterpart covering the same event, so for a new Zap, pick the instant one.
04What does it take to connect PayRequest to Zapier?
A PayRequest account, plus access to whatever the Zap will touch if it belongs to someone else. The connection is made from the Apps page of your Zapier account: add a connection, search for PayRequest, sign in to PayRequest in the tab that opens and grant Zapier access. Every Zap that uses PayRequest then reuses it. Keep the required fields in mind: Create Payment Link needs a description, an amount and a currency, and Find Subscription needs a subscription ID.
05Legacy or new PayRequest triggers: which one to pick?
For anything new, use the instant ones. The three Legacy triggers (Cancelled Subscription, New Payment, New Subscription) are polled, so on the free plan they can wait up to 15 minutes before the Zap starts. Their counterparts, Subscription Cancelled, Payment Succeeded and Subscription Activated, report the same events instantly. Keep a Legacy trigger only in an existing Zap that already works. The same logic applies to actions: Create Payment Link replaces Create Request (Legacy) for new builds.
06What if the PayRequest operation you need is not available?
Then the Zapier integration cannot do it, and it is better to know before building. There is no action to refund a payment, cancel or pause a subscription, or edit a payment link once created. The single search finds a subscription by ID only, not by customer. If your process needs one of those steps, it stays manual in PayRequest, or you would have to check whether another automation tool offers it. Comparing your process with the full list on this page is the fastest check.
07Zapier, Make or n8n for PayRequest?
Decide on coverage, not on reputation. On Zapier, PayRequest brings five instant triggers whose speed does not depend on your plan, three older polling ones, two actions and a search by subscription ID. A two-step Zap runs on the free plan. The gaps are refunds, subscription changes and searches by customer. Check whether another tool's PayRequest connector covers the operations your process needs, whether its triggers are instant, and how it bills multi-step runs, before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations