Resources · Make integration

HitPay Make integrationAutomate HitPay with Make.

What happens after a HitPay payment lands, without you copying anything by hand? The HitPay Make integration gives you 13 modules: 7 instant triggers and 6 actions. This guide is for merchants and ops teams: connect the account, then build a first scenario.

Try the HitPay integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HitPay Make integration do for you?

The HitPay Make integration links your HitPay account to Make so that payments, invoices, orders and payouts can start a scenario, the automation you build in Make as a chain of modules. HitPay tells Make the moment something happens, and your scenario can also create, check, change or delete payment requests and issue refunds.

A sales log that fills itself. Watch Charges Created fires when a payment is completed. From there, each payment can become a row in your spreadsheet or a message to the team, with no export to run.

Payment requests sent from your other tools. When a quote is accepted in your CRM or a booking form is submitted, Create Payment Request builds the request in HitPay. If the amount changes, Update Payment Request adjusts it; if the deal falls through, Delete Payment Request removes it.

Refunds and paid invoices that update everything else. Watch Updated Charges reacts to full or partial refunds, and Watch Updated Invoices to invoices marked paid or partially paid, so your accounting sheet and support tool stay in line with HitPay.

The HitPay documentation in Make lists no specific limits. Anything the 13 modules do not cover can go through Make an API Call, which reuses the same connection. To size your plan, read Make pricing; if you are still choosing a platform, n8n vs Make sets out the criteria, and Make training helps you learn the editor step by step.

Connect

How do you connect HitPay to Make?

  1. 01

    Copy your API key from HitPay

    You need an active HitPay account. In HitPay, open the dashboard, click API keys and copy the key shown on screen. Make uses it to act on your account, so keep it somewhere private.

  2. 02

    Add a HitPay module and open the connection

    In your Make scenario, add any HitPay module and click Create a connection. A connection is your HitPay account linked to Make once, then reused by every HitPay module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you run several HitPay accounts. Paste the API key you copied, or follow the instructions Make shows on screen, and save.

First scenario

Your first scenario: a HitPay payment request created from another app

GoalWhen a new request comes in from another app, such as an accepted quote, Make creates the matching payment request in HitPay.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the app where the request starts, like your CRM or form tool.

  2. 02

    Add Create Payment Request

    Click the + on the right of that first module, search for HitPay and pick Create Payment Request. Link your account with Create a connection if it is not there yet.

  3. 03

    Map the data

    Fill the fields of Create Payment Request by mapping values from the first module. Each bundle, meaning one item passed along (here one quote or one form entry), becomes one payment request.

  4. 04

    Test with Run once

    Click Run once, trigger a test entry in the first app, then open the bubbles to read the bundles each module received. Check the request in HitPay before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

Which HitPay events can start a scenario?

7 modules start a scenario when something happens in HitPay. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HitPay as soon as it happens.

HitPay1Watch Charges Created

Watch Charges Created

Instant trigger

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

This trigger starts your scenario each time a customer completes a payment in HitPay, so every successful charge can feed a sales log, a thank-you email or a stock update without anyone checking the dashboard.

How it fires
instant. HitPay calls Make through a webhook as soon as the payment goes through.
When to use it
you want one reliable signal that money has actually arrived, rather than an order that might still be pending.
Watch out
refunds on that same payment do not come through here; they belong to Watch Updated Charges.
HitPay2Watch Invoices Created

Watch Invoices Created

Instant trigger

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

Every new invoice created in HitPay reaches your scenario, which lets you log it in a follow-up sheet, alert the account manager or open a task before the client even pays.

How it fires
instant. HitPay calls Make through a webhook as soon as the invoice exists.
When to use it
your team tracks invoices sent, not just cash received, and wants a record the second one is issued.
Watch out
creation says nothing about payment; pair it with Watch Updated Invoices to know when the invoice is settled.
HitPay3Watch Orders Created

Watch Orders Created

Instant trigger

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

With this trigger, each order successfully created in HitPay becomes a bundle Make can pass on, for example to your fulfilment sheet, a packing checklist or a message to the warehouse.

How it fires
instant. HitPay calls Make through a webhook the moment the order is created.
When to use it
you sell through HitPay and want preparation to start from the order itself.
Watch out
later changes to that order, such as a new status, arrive through Watch Updated Orders, so plan a second scenario if you need them.
HitPay4Watch Payouts Created

Watch Payouts Created

Instant trigger

In Make“Triggers when a payout is successfully completed.”

Here the signal is money leaving HitPay for your bank: the scenario starts when a payout is successfully completed, which is handy for reconciliation and for telling finance what to expect.

How it fires
instant. HitPay notifies Make through a webhook as soon as the payout completes.
When to use it
your bookkeeper matches bank lines against payouts and wants each one logged automatically.
Watch out
a payout is not a customer payment; build customer-side flows on Watch Charges Created instead.
HitPay5Watch Updated Charges

Watch Updated Charges

Instant trigger

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

Refunds are what this trigger catches: when a payment is refunded, fully or partially, your scenario runs and can correct revenue figures, update a support ticket or notify the customer team.

How it fires
instant. HitPay tells Make through a webhook as soon as the refund is recorded.
When to use it
refunds happen in the HitPay dashboard and your other tools keep showing the sale as final.
Watch out
partial refunds fire it too, so check the amount in the bundle before marking an order as cancelled.
HitPay6Watch Updated Invoices

Watch Updated Invoices

Instant trigger

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

Knowing an invoice is settled is the point of this trigger, which fires when HitPay marks an invoice as paid or partially paid and lets you close the loop in your accounting or CRM.

How it fires
instant. HitPay calls Make through a webhook as soon as the invoice status changes.
When to use it
you chase unpaid invoices and want paid ones to drop off the list on their own.
Watch out
a partially paid invoice still has a balance; route it with a filter instead of treating it as closed.
HitPay7Watch Updated Orders

Watch Updated Orders

Instant trigger

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

Order status changes in HitPay flow into Make through this trigger, so your delivery tracker, customer messages or internal board reflect where each order stands.

How it fires
instant. HitPay calls Make through a webhook as soon as the status is updated.
When to use it
several people touch orders after checkout and everyone needs the latest status in the tool they use.
Watch out
every status change runs the scenario, so add a filter if only one status matters to you, or you spend operations for nothing.
Modules

What can Make do inside HitPay?

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

HitPay1

Create Payment Request

Action

In Make“Creates a payment request.”

You get a new HitPay payment request built straight from data in another app, so nobody retypes a client name or an amount into the dashboard.

When to use it
a quote is accepted, a booking is confirmed or a form asks for payment, and the request should follow on its own.
Watch out
each bundle creates one request, so a test run with several items creates several requests.
HitPay2

Delete Payment Request

Action

In Make“Deletes a payment request.”

This action removes a payment request from HitPay, which keeps your list clean when the sale it was meant for no longer exists.

When to use it
a deal is lost or a booking cancelled in your CRM, and the open request should disappear with it.
Watch out
test on a dummy request with Run once before switching the scenario on, so a wrong mapping never removes a real one.
HitPay3

Get Payment Request Details

Action

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

Use this action to read where a given payment request stands, and hand that status to the next module for a decision or a report.

When to use it
before sending a reminder, you want to confirm the request is still unpaid instead of guessing.
Watch out
it only reads the request and changes nothing; to adjust the request afterwards, follow it with Update Payment Request.
HitPay4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the listed modules does what you need, this one reaches any endpoint of the HitPay API with the connection you already set up.

When to use it
you need a HitPay feature that has no dedicated module in Make.
Watch out
you build the call yourself, endpoint included, so it suits someone at ease with the HitPay API rather than a first scenario.
HitPay5

Refund Payment

Action

In Make“Refunds a payment in the system.”

A refund can start from outside HitPay with this action: an approved return or a resolved support ticket sends the money back without a trip to the dashboard.

When to use it
your returns or support process already lives in another tool and approvals happen there.
Watch out
money leaves your account, so add a filter or an approval step before this module and test on a small payment first.
HitPay6

Update Payment Request

Action

In Make“Updates a payment request.”

Changes to an existing payment request are applied from your scenario, so the request stays in step with the deal or booking it belongs to.

When to use it
a quote is revised in your CRM after the request was sent, and the client should see the new terms.
Watch out
it edits a request that already exists; for a brand new one, Create Payment Request is the module to add.
Need help

Need help automating HitPay with Make?

A person reads every message.

FAQ

HitPay and Make: common questions

01Is the HitPay Make integration free?
Yes, on the Make side. HitPay is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. You still need an active HitPay account, whose own pricing is separate.
02What do you need to connect HitPay to Make?
An active HitPay account and its API key. In HitPay, open the dashboard, click API keys and copy the key displayed. In Make, add a HitPay module, click Create a connection, give it a name if you like, and paste the key. For the instant triggers, Make asks you to click Create a webhook first, then Create a connection. Once saved, the same connection serves all 13 HitPay modules, so you only set it up once per HitPay account.
03Do HitPay triggers in Make react in real time?
Yes. All 7 HitPay triggers are instant: HitPay calls Make through a webhook as soon as the event happens, whether that is a completed payment, a new invoice, an order, a payout, a refund, a paid invoice or an order status change. There is no polling interval to wait for. In the editor, these modules carry the lightning badge. The schedule you set on the first module matters only when the scenario starts from another app, like the payment request scenario on this page.
04What if the HitPay Make module you need is missing?
Use Make an API Call. It sends a request to any endpoint of the HitPay API with the connection you already created, which covers anything the other 12 modules leave out. You build the call yourself, endpoint included, so it suits someone at ease with the HitPay API more than a first scenario. Make's HitPay documentation lists no specific limits, and it notes that its content is generated from HitPay's official documentation, so double-check important details with HitPay directly when something behaves unexpectedly.
05Should you pick Make or n8n for HitPay?
It depends on your criteria, not on a winner. On Make, HitPay offers 13 modules, including 7 instant triggers, and runs from the Free plan with the visual editor described on this page. The same app often has an n8n node too, so check whether one exists for HitPay before deciding. The n8n vs Make comparison linked earlier on this page lays out the differences between the two platforms without ranking them; start from the tool your team already uses.
Same platform

Other docs you might need on this stack.

Browse all integrations