Resources · Zapier integration

HitPay Zapier integrationAutomate HitPay with Zapier.

The HitPay Zapier integration gives you 6 triggers and 5 actions, with no search. All six triggers are instant, so a completed payment, a refund or a new order reaches your other tools right away, even on the free plan of Zapier.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the HitPay Zapier integration does for a small business

HitPay handles payments and online sales for small businesses. Zapier is the layer that reacts to what happens there and acts on it. The automation you build on Zapier is a Zap: one event that starts it, then one or more steps that run each time that event comes back.

The HitPay integration splits neatly in two. Six triggers listen to payments, invoices and orders; five actions manage payment requests and refunds. That gives you three concrete outcomes.

Payment links that build themselves. Create Payment Request issues a request with an amount, a currency and the payment methods you accept. A made-to-order furniture shop can send the balance link the moment an order lands.

A paper trail for money coming back. Charge Updated fires when a payment is refunded in full or in part, so the bookkeeper hears about it without logging into HitPay.

Requests that stay tidy. Update Payment Request fixes an amount, Delete Payment Request removes a link nobody should pay anymore, and Get Payment Request Details tells you its status.

What Zapier does not do for HitPay: there is no search step, so a Zap cannot look up an existing request by itself; you need its Request ID from an earlier step. There is also no action to create an invoice or an order, only triggers on them. If you work with Make too, we have a HitPay Make integration page for the same app.

Vocabulary

Zapier vocabulary in one minute

Seven words are enough to follow this page. Here they are in plain English.

Zap
The automation you build on Zapier: one event that starts it, then the steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval and keeps only the ones it has not seen.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. Every HitPay trigger works this way.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set. Otherwise the run stops right there.
Cost

What a HitPay Zap costs you

Zapier bills tasks, not triggers. Listening to HitPay is free; only completed actions count.

  • Free plan tasks100 per month
  • Steps per Zap on Free2 (one trigger, one action)
  • HitPay triggers6, all instant
  • Premium appNo

The trigger never costs a task, however many payments come in. Each action that succeeds counts once: a Zap with three actions uses three times more than a Zap with one, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. HitPay is not a premium app, so it works from the free plan. The polling grid below does not slow it down: all six triggers are instant.

Connect

Connect your HitPay account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your HitPay account linked to Zapier once, then reused by every step that touches HitPay.

  2. 02

    Pick HitPay

    Search for HitPay in the dialog, select it and click Add connection. You need an existing HitPay account for this step; Zapier does not open one for you.

  3. 03

    Sign in and grant access

    Sign in to HitPay in the tab that opens and allow Zapier to use the account. Whatever the Zap should read or change has to be reachable by that account.

First Zap

Your first Zap: a balance link for selected orders

GoalWhen a new HitPay order matches your condition, create a payment request for it.

  1. 01

    Build: pick the trigger

    Start a new Zap, choose HitPay and the Order Created event, then pick your connection. The lightning bolt shows the trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent orders of the account, so pick a real one to build the next steps on.

  3. 03

    Add the filter

    Click the plus icon, choose Filter and, in Configure & test, set the field, the rule and the value. A number rule only works on numbers, so match the rule to the field.

  4. 04

    Add Create Payment Request

    Add an action, pick HitPay and Create Payment Request. Fill Amount, Currency and Payment Methods, then decide whether HitPay should send an email or an SMS receipt.

  5. 05

    Test, then Publish

    Test each step and read what came back. Once the request looks right, click Publish. With the filter, this Zap needs a paid plan.

Triggers

The 6 HitPay triggers

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

1

Charge Created

Instant trigger

In Zapier“Triggers when a payment is successfully completed.”

A customer has just paid and the payment went through: this trigger passes that successful charge to your Zap.

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 yoga studio wants each class pass paid online to show up in its booking sheet without anyone copying it by hand.
Watch out
it only covers payments completed successfully, so a failed attempt never starts the Zap.
2

Charge Updated

Instant trigger

In Zapier“Triggers when a payment is refunded/partially refunded.”

Money going back out is the signal here. It fires when a payment is refunded, whether fully or only in part.

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 accountant keeps a refunds log for the month and every refund should land there the minute it is issued.
Watch out
two partial refunds on one payment mean two runs, so make the action update a line rather than add a new one each time.
3

Invoice Created

Instant trigger

In Zapier“Triggers when a new invoice is created.”

Each new HitPay invoice becomes the starting point of a Zap, the moment it exists.

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 freelance photographer issues invoices from HitPay and wants each one recorded with the client project straight away.
Watch out
it reacts to creation, not to payment; to hear about money received on the invoice, use Invoice Updated.
4

Invoice Updated

Instant trigger

In Zapier“Triggers when an invoice is marked as paid or partially paid.”

This is the one that tells you money arrived on an invoice. It fires when the invoice is marked as paid or partially paid.

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 consultant chases late invoices and wants a paid one to drop off the follow-up list without checking manually.
Watch out
an invoice paid in two goes fires twice, so add a filter if only the final payment matters.
5

Order Created

Instant trigger

In Zapier“Triggers when an order is created successfully.”

New sales start here: an order created successfully in HitPay is handed to the Zap straight away.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an online bakery prepares tomorrow's baking list from every order placed today, and each order should be added as it comes in.
Watch out
the Zap only sees orders placed after you publish it; earlier sales stay out.
6

Order Updated

Instant trigger

In Zapier“Triggers when an order status is updated.”

Orders move through statuses, and every status change sends the order back to your Zap.

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 small shop with a separate fulfilment team wants that team told whenever an order changes status.
Watch out
an order can change status several times, so never let this trigger create a fresh record on each run; it would pile up duplicates.
Actions

The 5 HitPay actions

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

1

Create Payment Request

Action

In Zapier“Creates a payment request.”

Issues a new payment request from your Zap, with the amount, the currency and the payment methods you choose.

When to use it
a tutor sends a payment link after each booked course instead of writing it up one by one.
Watch out
Allow Repeated Payments, Send Email and Send SMS are off by default, and Generate QR only works with certain methods.
2

Delete Payment Request

Action

In Zapier“Deletes a payment request.”

Removes a payment request so nobody can pay it anymore.

When to use it
a quote is declined and its payment link should disappear before the customer clicks it by mistake.
Watch out
the only field is Request ID, and it is required.
3

Get Payment Request Details

Action

In Zapier“Gets the status of the specified payment request.”

Reads where a payment request stands, then hands that status on to whichever step comes next in the Zap.

When to use it
before chasing a customer, a step checks whether the request was already settled.
Watch out
it needs the Request ID. No search exists, so finding a request by customer name is off the table.
4

Refund Payment

Action

In Zapier“Refunds a Payment in the system.”

Sends money back to the customer for a payment that went through, in full or for part of it.

When to use it
an event organiser refunds tickets for a cancelled date once the cancellation is confirmed elsewhere.
Watch out
Amount and Payment ID are required, and this one moves real money, so test it on a small payment first.
5

Update Payment Request

Action

In Zapier“Updates a payment request.”

Changes an existing request: a new amount, another currency, receipts switched on or off.

When to use it
the price agreed with a client changed after the link went out, and the request should follow.
Watch out
Request ID, Amount and Currency are all required, even if only one of them changes.
When it breaks

When a HitPay Zap breaks

Zapier attaches no help article to HitPay and lists no limit specific to the app. The failures below are the ones every Zap can hit, plus one that comes from HitPay's own fields.

The first three never show up as a clear error: the Zap simply does less, or more, than you planned. When a payment Zap misbehaves, compare what you expected with what the test brought back, step by step. If you are still weighing the tools, our Make vs Zapier comparison is the place to start.

  • Past payments are ignored

    A Zap only reacts to what happens after you publish it. Payments, invoices and orders from before stay out; moving that history is a separate job.

  • The Zap keeps triggering itself

    If a step writes back into the place its own trigger watches, each run sets off another one, and that loop eats your task count fast.

  • A big batch is held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.

  • A payment method is rejected

    Payment Methods only accepts methods supported on your account, and Generate QR is valid only for a few of them. Check both in HitPay before you map the field.
Need help

Need help automating HitPay with Zapier?

A person reads every message.

FAQ

HitPay Zapier integration: common questions

01Is the HitPay Zapier integration free?
Yes, within the free plan's limits. HitPay is not a premium app, so it works on Zapier's free plan, which gives 100 tasks a month and unlimited Zaps. The catch is size: each Zap can only have one trigger and one action. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. A plain Invoice Created to Create Payment Request Zap stays free; the order Zap with a filter does not.
02How many tasks does a HitPay Zap use?
One per action that completes, and none for the trigger. A busy sales day costs you nothing on the Zapier side until an action actually succeeds. In a Zap with three actions, each successful one counts on its own, so one run can cost three tasks. An action that fails is not counted. Watching HitPay for new payments, invoices or orders is free whatever your plan, because only completed actions are billed.
03Does HitPay on Zapier work in real time?
Yes. All six HitPay triggers are instant: HitPay tells Zapier the moment a payment, an invoice or an order is created or updated, and the Zap starts right away. The polling intervals of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, do not apply to them. In the editor these triggers carry a lightning bolt, Zapier's sign for an instant trigger, which matters a lot on the free plan.
04What does it take to connect HitPay to Zapier?
A HitPay account and access to whatever the Zap should touch. You add the connection from the Apps page with + Add connection, search for HitPay, sign in in the tab that opens and grant access. For actions, check the fields first: Create Payment Request needs payment methods that your HitPay account actually supports, and every action on an existing request needs its Request ID. The connection is made once and reused by every HitPay step.
05Why does Invoice Updated fire twice for one invoice?
Because it fires each time the invoice is marked as paid or partially paid. A customer who pays in two instalments produces two runs: one for the partial payment, one for the final one. If your Zap creates something on each run, you get duplicates. Either make the action update an existing record, or add a filter so only the run you care about goes through. The same logic applies to Charge Updated when a payment is refunded in several parts.
06What if the HitPay operation you need is missing?
Start by checking whether it is a trigger or an action you need. Zapier offers six triggers on payments, invoices and orders, and five actions centred on payment requests and refunds. There is no search step and no action to create an invoice or an order. If your process depends on one of those, the Zap alone will not do it, and it is worth looking at how other automation tools cover HitPay before building around the gap.
07Zapier, Make or n8n for HitPay?
Choose on criteria, not on brand. Look at which HitPay events and actions each tool exposes, how each one bills a run that has several steps, and who on your team will maintain the flows. On Zapier, HitPay gives six instant triggers and five actions, and simple two-step Zaps run on the free plan. If your flows need searches, branches or many steps per payment, compare the cost of those runs carefully on each platform before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations