Skip to main content

​
Automate PayRequest with Zapier

The official PayRequest integration for Zapier lets you start workflows from successful payments and subscription events. You can also create PayRequest payment links from other apps.
Zapier uses real-time REST Hooks for the new payment and subscription triggers. Your Zap runs as soon as PayRequest records the event; it does not need to wait for a polling interval.

​
What You Can Automate

Payment succeeded

Run a Zap after a payment is successfully completed in PayRequest.

Subscription created

Run a Zap when a subscription is created, including subscriptions that are still pending activation.

Subscription activated

Run a Zap when a subscription or trial becomes active.

Subscription renewed

Run a Zap after a subsequent recurring subscription payment succeeds. The initial payment is not reported as a renewal.

Subscription cancelled

Run a Zap when a subscription is cancelled in PayRequest.

Create payment link

Create an amount-based PayRequest payment link from another Zapier app.
You can also use Find Subscription to retrieve a subscription by its PayRequest ID.

​
Connect Your Account

1

Open Zapier settings in PayRequest

Sign in to PayRequest and open Settings → Integrations.
2

Create a dedicated token

Select Create Zapier token. PayRequest creates a token with the billing.read and billing.write permissions required by the integration.Copy the token immediately. For security, its value is shown only once.
3

Open PayRequest in Zapier

Select Open Zapier, or open the PayRequest integrations page. Create a Zap and choose PayRequest as the trigger or action app.
4

Connect your PayRequest account

When Zapier asks for your PayRequest API token, paste the token you just created. Zapier tests the connection before continuing.
5

Choose an event and test

Select a payment or subscription event. Zapier loads recent PayRequest data so you can map fields into the next step of your workflow.
Treat the API token like a password. Do not send it by email, place it in a spreadsheet, or paste it into a Zap field other than the PayRequest account connection screen.

​
Payment Data

The Payment succeeded trigger includes fields such as: PayRequest uses its transaction record as the source of truth for the amount and payment timestamp.

​
Subscription Data

Subscription triggers include:
Use Subscription created when you need to prepare work before payment activation. Use Subscription activated when the next step should happen only after access or billing becomes active.

​
Example Zaps

  • Add a customer to your CRM after a successful payment
  • Send a Slack or Microsoft Teams message for a new subscription
  • Grant course or community access after subscription activation
  • Update a customer record after every renewal
  • Start an offboarding workflow after cancellation
  • Create a PayRequest payment link from a form submission

​
Manage Tokens and Connections

The PayRequest Settings → Integrations page shows:
  • How many active Zap subscriptions are registered
  • Which dedicated Zapier tokens exist
  • When each token was created and when it expires
  • A control to revoke tokens that are no longer used
Existing token values cannot be displayed again. If you lose a token, create a new one, reconnect the PayRequest account in Zapier, and then revoke the old token. Revoking a token immediately prevents Zapier from accessing PayRequest with that connection. Zaps using it will stop until you reconnect them with a valid token.

​
Troubleshooting

Open Settings → Integrations, create a new Zapier token, and reconnect the PayRequest account inside Zapier. Make sure you paste only the token value and do not add Bearer before it.
First test the PayRequest account connection in Zapier. If authentication succeeds, make sure the PayRequest account contains at least one subscription that matches the selected trigger. The subscription sample must belong to the same PayRequest business as the token.
Create or update the relevant record in PayRequest, then test the trigger again. For example, Subscription cancelled needs a cancelled subscription to provide a real sample.
Reconnect the PayRequest account in Zapier with a new token, then update the affected Zaps to use that connection.
Each event includes a stable unique ID. Zapier uses this ID for deduplication, while PayRequest delivers each active REST Hook subscription independently.

​
Next Steps

API authentication

Learn how PayRequest API tokens and permissions work.

Webhooks

Build a direct webhook integration when you need custom code.

Subscription lifecycle

Understand subscription statuses and lifecycle events.

Payment links API

Create payment links directly through the API.