Resources · Zapier integration

Payhere Zapier integrationAutomate Payhere with Zapier.

The Payhere Zapier integration gives you 2 triggers, 1 action and 0 searches. Payhere tells Zapier straight away when a payment comes in or a subscription ends, and a Zap can create new payment plans in your Payhere storefront.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Payhere Zapier integration actually does

Payhere gives service businesses an online storefront where clients pay, once or on a recurring basis. The integration passes two events to Zapier, a payment received and a subscription cancelled, and lets a Zap add a payment plan to your storefront.

Three results people set up. A revenue log: Payment Received adds every payment to the sheet you use for bookkeeping, with nothing copied by hand. A churn alert: Subscription Cancelled warns the account manager in chat, whether the client cancelled or Stripe ended the subscription after failed payments. A plan factory: a row added to a pricing sheet feeds Create Plan, so new offers reach the storefront without anyone opening Payhere.

Now the limits. Zapier cannot edit or delete a plan, refund a payment or touch a customer in Payhere: the single action creates plans and nothing else. There is no search step, so a Zap cannot look up an existing plan or client. And no Zap sees the past: payments and cancellations from before you publish it never reach it.

If you are comparing automation tools before you start, the n8n vs Zapier comparison is a fair first read before you build anything on either tool.

Vocabulary

Zapier vocabulary in one minute

Seven words come back across this page. Here they are, in plain English.

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 the Zap. Once the Zap is on, Zapier waits for it. Payhere offers two.
Action
What the Zap does once it has started: the step that writes, sends or creates something. Payhere has one, Create Plan.
Task
The unit Zapier bills: one action your Zap completes successfully. The quota on your plan is a count of those.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app reports the event itself. Both Payhere triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise. Paid plans only.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What a Payhere Zap really costs

Short answer: the Payhere trigger is free, and each successful action costs one task.

  • Free plan100 tasks a month, unlimited Zaps
  • Zap size on free2 steps: one trigger, one action
  • Payhere triggers2 instant, grid does not apply
  • Payhere premium?No, available on the free plan

A trigger never uses a task, so Payhere reporting a payment costs nothing by itself. Each action that succeeds after it counts as one task, in Payhere or in another app, and an action that fails is not counted. A Zap that logs a payment and thanks the client spends two tasks per payment. On the free plan, Zaps stop at two steps, one trigger and one action; a filter or a second action needs a paid plan. The interval grid below only concerns polling triggers. Both Payhere triggers are instant, so they start your Zap without delay on every plan, free included.

Connect

Connect Payhere to Zapier in three steps

  1. 01

    Open the connection dialog

    From the Apps page of your Zapier account, click + Add connection. A connection is your Payhere account linked once, then reused by every Zap step that works with Payhere.

  2. 02

    Choose Payhere

    Type Payhere in the search box of the dialog, pick it, then click Add connection. You need an existing Payhere account; the dialog will not create one for you.

  3. 03

    Sign in and grant access

    Sign in to Payhere in the tab that opens and allow Zapier in. If your Zaps will create plans on a storefront you do not own, make sure your account can write plans there.

First Zap

Your first Zap: act on a cancelled subscription

GoalWhen a Payhere subscription is cancelled, warn the team in chat and send the client a short goodbye email.

  1. 01

    Pick the trigger

    Build a new Zap, choose Payhere as the app and Subscription Cancelled as the event, then select the Payhere connection you made earlier.

  2. 02

    Test on a real cancellation

    Run the test. Zapier brings back the three most recent cancellations of your account, so you map the next steps on a real client.

  3. 03

    Add the team alert

    Add the first action in your chat app and drop the details from the trigger into the message. Test the step and check what it posted.

  4. 04

    Add the client email

    Add the second action in your mail app. Two actions make a multi-step Zap, so this version needs a paid plan; on the free plan, keep one of the two.

  5. 05

    Publish

    Publish the Zap to switch it on. The trigger is instant, so the next cancellation starts it right away, on any plan, free included.

Triggers

The 2 Payhere triggers

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

1

Payment Received

Instant trigger

In Zapier“Triggers when a payment is received.”

Starts your Zap each time a client pays through your Payhere storefront. One-off or recurring, every payment received is one run of the Zap, with the payment details attached for the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
record revenue in your bookkeeping sheet, or open a project in your task tool when a client pays for a service.
Watch out
on a busy storefront, each action of this Zap is spent on every single payment, so count your tasks before adding steps.
2

Subscription Cancelled

Instant trigger

In Zapier“Triggers when a user has cancelled their subscription, or Stripe has marked it as cancelled due to payment failures.”

Fires when a subscription ends, either because the client cancelled it or because Stripe marked it as cancelled after failed payments. Both cases arrive through the same trigger.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alert the account manager, close the client's access to your service, or start a win-back email.
Watch out
a client lost to a failed card is not a client who chose to leave; word your message so it fits both, or check the case before you write.
Actions

The Payhere action

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

1

Create Plan

Action

In Zapier“Create a new payment plan”

Adds a new payment plan to Payhere. It needs a payment type (recurring or one-off), a name and a currency; you can also flag the plan as donation based or hide it from your storefront.

When to use it
publish offers drafted in a pricing sheet or a form without rebuilding them by hand in Payhere.
Watch out
the plan shows on your storefront unless you tick the hide option, so test it on a hidden plan first.
When it breaks

When a Payhere Zap breaks

Zapier documents no Payhere-specific error or rate limit. The trouble comes from the required fields of Create Plan and from Zapier's general behavior.

  • The plan is not created

    Create Plan needs a payment type, a name and a currency. If one of them arrives empty from an earlier step, the action fails and no task is counted.

  • The currency format is off

    The currency must be a three-letter code like usd, gbp, eur or cad. Map that code, not a symbol or a full currency name from a sheet.

  • A test plan goes live

    A plan created by a Zap shows on your storefront unless the hide option is set. Testing with a real-looking plan can put it in front of clients.

  • Past events are ignored

    A Zap only reacts to what happens after you publish it. Payments and cancellations from before that never reach it; moving them is a separate job.
Need help

Need help automating Payhere with Zapier?

A person reads every message.

FAQ

Payhere Zapier integration: frequent questions

01Is the Payhere Zapier integration free?
Yes. Payhere is not a premium app on Zapier, so it runs on the free plan, which gives you 100 tasks a month and unlimited Zaps. The limit is Zap size: on the free plan each Zap holds one trigger and one action. Logging each Payhere payment in a sheet fits that. Alerting the team and emailing the client in the same Zap does not, because two actions make a multi-step Zap, and multi-step Zaps need a paid plan. A filter has the same effect.
02How many Zapier tasks does a Payhere Zap use?
The trigger uses none: Payhere reporting a payment or a cancellation is free. Each action that succeeds counts as one task, whether it is Create Plan or a step in another app, and an action that fails is not counted. So a Zap that adds a row for each payment costs one task per payment, and one that also emails the client costs two. On a storefront with many payments, the Payment Received Zaps are the ones that use most of your quota.
03Is Payhere on Zapier real time?
Yes. Both Payhere triggers are instant: Payhere itself tells Zapier when a payment comes in or a subscription is cancelled, and the Zap starts without waiting for a check. The plan interval grid, 15 minutes on Free and down to 1 minute on Team and Enterprise, applies only to polling triggers, so it does not slow these Zaps on any plan. A Zap built on an instant trigger shows a lightning bolt in the editor.
04What does it take to connect Payhere to Zapier?
A Payhere account and a Zapier account. On the Apps page of Zapier, click + Add connection, search for Payhere, pick it and click Add connection, then sign in to Payhere in the new tab and grant access. If you work on a storefront that belongs to someone else and plan to create plans there, you need write access to it. The connection is then reused by every Zap you build on Payhere.
05Why does Create Plan fail in a Payhere Zap?
Most often because a required field is missing or badly formatted. The action needs a payment type, recurring or one-off, a name and a currency. The currency must be a three-letter code such as usd, gbp, eur or cad; map that code, not a symbol or a full name. Check the values coming from your sheet or form, test the step on a hidden plan, and read what came back before you publish the Zap.
06What if the Payhere operation you need is not available?
Then Zapier cannot do it with Payhere today. The integration has two triggers, Payment Received and Subscription Cancelled, and a single action, Create Plan. There is no way to edit or delete a plan, refund a payment or look up a client from a Zap, and there is no search step. You can still react to every payment and cancellation in your other tools. The list can change when Payhere publishes a new version of its Zapier app.
07Zapier, Make or n8n for Payhere?
Decide on criteria rather than on a ranking. First, check that the tool offers the Payhere events and actions you need: on Zapier, two instant triggers and one action that creates plans. Second, look at billing: Zapier counts one task per successful action and nothing for the trigger, which matters on a busy storefront. Third, count steps: anything beyond one trigger and one action needs a paid Zapier plan. Ask the other tools those same three questions.
Same platform

Other docs you might need on this stack.

Browse all integrations