Resources · Make integration

Omise Make integrationAutomate Omise with Make.

What if every payment event in Omise could start its own follow-up? The Omise Make integration gives you 29 modules, one of them an instant trigger, to handle charges, customers, refunds, disputes and transfers. This guide walks you from the secret key to a working scenario.

Try the Omise integration on MakeSee the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Omise Make integration automate?

The Omise Make integration links your Omise account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. Omise brings 29 of those modules, so payments, customers, refunds, disputes and transfers can move between Omise and your other apps without a developer.

Payment follow-up without copy and paste. Watch Events tells Make the moment something happens in your Omise account. Add Get a Charge behind it and the full charge lands in your spreadsheet, your CRM or a message to the finance channel.

Cleaner customer records. When someone signs up in your shop, Create a Customer opens their Omise profile, and Update a Customer keeps that profile aligned with the rest of your stack. Search Customers checks first so you do not create the same person twice.

A dispute desk that stays organized. Search Open Disputes pulls every case still waiting, Get a Dispute fetches the details of one, and Accept a Dispute or Update a Dispute records your decision. Refunds and transfers follow the same pattern with their own modules.

Two limits deserve attention. Close a Dispute only works in test mode, so it is a tool for trying your flow, not for live cases. The official Make page for Omise is itself generated with AI and warns it may contain mistakes, so check anything critical against Omise directly. If you are weighing tools, the n8n vs Make comparison helps, and the Make pricing guide explains how operations are counted. To learn the editor properly, see the Make training.

Connect

How do you connect Omise to Make?

  1. 01

    Copy your secret key in Omise

    Open your Omise dashboard, go to the Keys menu on the left, pick the Test dashboard or the Live dashboard, and copy the Secret key shown on screen. You need an active Omise account with API keys for this.

  2. 02

    Add an Omise module and open the connection

    In your Make scenario, add any Omise module and click Create a connection. A connection is your Omise account linked to Make once, then reused by every Omise module. If you start with Watch Events, click Create a webhook first.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name like "Omise test" saves confusion later. Paste the secret key you copied, confirm, and Make can now read and write in your Omise account.

First scenario

Your first scenario: log every Omise event with its charge

GoalWhen an event happens in Omise, Make fetches the related charge so you can pass it to the next tool.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle is where your first module, the trigger, will sit.

  2. 02

    Add Watch Events

    Search for Omise, pick Watch Events, click Create a webhook, then Create a connection and paste your test secret key. The lightning badge means Omise will call Make on its own.

  3. 03

    Chain Get a Charge

    Click the + on the right of Watch Events and add Get a Charge. Map the charge reference carried by the event bundle, the item passed from one module to the next. This assumes the event concerns a charge; check it in the next step.

  4. 04

    Test with Run once

    Click Run once, then create some activity in your Omise test account, such as a test charge, so an event reaches Make. Open the bubbles above each module to read the bundles they received and check the charge came through.

  5. 05

    Switch it on

    Add the tool that should receive the charge, test again, then switch the scenario on. Because Watch Events is instant, the scenario starts whenever Omise sends an event rather than waiting for the clock.

Triggers

What starts an Omise scenario

1 module starts a scenario when something happens in Omise. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Omise as soon as it happens.

Omise1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a new event has happened.”

Watch Events opens the door for everything else: each new event in your Omise account starts the scenario and hands its details to the next module. It is the only Omise trigger, so most automations begin here.

How it fires
instant. Omise calls Make through a webhook as soon as the event happens, which is why the module shows a lightning badge and asks you to click Create a webhook.
When to use it
any flow that should react to activity in your Omise account without you checking the dashboard.
Watch out
if only some kinds of events matter to you, add a filter right after this module so the rest of the scenario skips the others.
Modules

Every Omise module, and when to reach for it

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

Omise1

Accept a Dispute

Action

In Make“Accepts an existing dispute.”

Accept a Dispute records in Omise that you agree with a customer's claim, closing the discussion on your side without leaving your scenario. Pair it with Get a Dispute to see the case first.

When to use it
for small amounts where your team has decided not to fight, once the rule is approved.
Watch out
treat acceptance as a final decision and keep a human step before this module on anything unclear.
Omise2

Close a Dispute

Action

In Make“Closes an existing dispute. Works only in the test mode.”

With Close a Dispute you can end a dispute from Make and watch how the rest of your flow reacts to a closed case. It is a rehearsal tool rather than a daily one.

When to use it
while building a dispute workflow on the Test dashboard, to simulate the end of a case.
Watch out
it only works in test mode, so a scenario connected with the live key cannot rely on it.
Omise3

Create a Charge

Action

In Make“Creates a new charge.”

Create a Charge asks Omise to take a new payment straight from your scenario, so a sale confirmed elsewhere turns into a real Omise charge. Each run creates one charge per bundle.

When to use it
when an order, booking or invoice validated in another tool should be billed through Omise.
Watch out
run your first tests on the Test dashboard, and check that a repeated bundle cannot bill the same order twice.
Omise4

Create a Customer

Action

In Make“Creates a new customer.”

This module opens a new customer profile in Omise, so the people who buy from you exist there before their first payment. It saves typing every signup by hand.

When to use it
right after a form submission or a new account in your shop, before any charge is attempted.
Watch out
place Search Customers before it, otherwise a returning buyer can end up with two profiles.
Omise5

Create a Dispute

Action

In Make“Creates a new dispute.”

Create a Dispute opens a new dispute record in Omise from your scenario. On a test setup, it is the quickest way to generate a case your dispute workflow can practice on.

When to use it
when you need a dispute to exist so that later modules, like Get a Dispute or Update a Dispute, have something to act on.
Watch out
keep this module on the test connection while you build, so live records stay clean.
Omise6

Create a Refund

Action

In Make“Creates a new refund.”

Create a Refund sends money back on a charge without anyone logging into Omise. A return approved in your helpdesk or shop can trigger the refund on its own.

When to use it
after a return is validated, once the matching charge is known, often found with Search Charges or Get a Charge.
Watch out
a refund goes to a real customer on the live key, so test the whole chain before switching the scenario on.
Omise7

Create a Transfer

Action

In Make“Creates a new transfer.”

Your scenario can move funds out of your Omise balance with Create a Transfer, which turns a payout decision into an actual transfer request. Checking the balance first keeps it sensible.

When to use it
after Get a Balance confirms there is enough available, when a payout has been approved in another tool.
Watch out
money is involved, so build the flow on the Test dashboard and keep an approval step upstream.
Omise8

Delete a Customer

Action

In Make“Deletes an existing customer.”

Delete a Customer removes a customer profile from Omise, which helps when a person asks for their account to be erased everywhere. One bundle, one profile gone.

When to use it
in a cleanup flow triggered by a deletion request coming from your CRM or support tool.
Watch out
consider a deletion permanent; confirm the right customer with Get a Customer before this module runs.
Omise9

Delete a Transfer

Action

In Make“Deletes an existing transfer.”

When a payout should no longer happen, Delete a Transfer removes that transfer from Omise directly in the scenario, instead of someone hunting for it in the dashboard.

When to use it
when an approval is withdrawn after Create a Transfer already ran, and you have the transfer reference at hand.
Watch out
use Get a Transfer just before it to be sure you target the right one, since the change is hard to undo.
Omise10

Get a Balance

Action

In Make“Retrieves your account balance.”

Get a Balance reads your Omise account balance and passes it on, so the rest of your scenario can decide with real figures instead of guesses.

When to use it
just before Create a Transfer, or to post the current balance in a finance report or chat message.
Watch out
the value comes from the connection you picked, so a test key returns the test balance, not the live one.
Omise11

Get a Charge

Action

In Make“Retrieves an existing charge.”

Get a Charge fetches one existing charge in full, which turns a bare reference into the full record Omise keeps for that payment, ready to map into later modules.

When to use it
right after Watch Events, when the event points to a charge and you want its details downstream.
Watch out
it needs one charge reference; if you only know a customer, go through Search Charges instead.
Omise12

Get a Customer

Action

In Make“Retrieves an existing customer.”

You get one full customer record back with Get a Customer, handy for enriching a message or checking who is behind a payment before acting.

When to use it
before Update a Customer or Delete a Customer, to confirm you are touching the right person.
Watch out
it expects a customer reference; if you do not have it yet, start with Search Customers.
Omise13

Get a Dispute

Action

In Make“Retrieves an existing dispute.”

Get a Dispute pulls every detail of a single dispute into the scenario, so whoever handles the case sees it in their own tool rather than in Omise.

When to use it
when an event or a search hands you a dispute reference and you need the full record to decide.
Watch out
it reads one case at a time; for a list of pending cases, Search Open Disputes is the better start.
Omise14

Get a Forex

Action

In Make“Retrieves the current foreign exchange rate.”

Get a Forex returns the current foreign exchange rate from Omise, so a quote or report in another currency uses the same rate your payment provider sees.

When to use it
when you sell in several currencies and want a converted amount in a sheet or an email.
Watch out
the rate is the one at the moment the module runs, so store it with the date if you need to explain a number later.
Omise15

Get a Refund

Action

In Make“Retrieves an existing refund.”

Get a Refund brings back one existing refund so your team can confirm it went through and share the details with the customer or accounting.

When to use it
after Create a Refund, or when an event mentions a refund you want to log elsewhere.
Watch out
each run reads a single refund; use Search Refunds when you need several of them at once.
Omise16

Get a Transfer

Action

In Make“Retrieves an existing transfer.”

Pulling a single transfer with Get a Transfer lets you follow a payout from request to arrival without opening the Omise dashboard.

When to use it
to check a transfer before Update a Transfer or Delete a Transfer, or to send its details to accounting.
Watch out
it works on one known transfer; if you are looking for one by criteria, Search Transfers comes first.
Omise17

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the escape hatch: it lets your scenario call any endpoint of the Omise API with the connection you already set up, so you are not stuck when no listed module fits.

When to use it
when you need something from Omise that none of the other listed modules cover.
Watch out
you write the request yourself, so keep the Omise API documentation open while you fill it.
Omise18

Reverse a Charge

Action

In Make“Reverses an existing charge.”

Reverse a Charge undoes an existing charge from inside your scenario, which is useful when an order is cancelled right after payment. It is a separate step from issuing a refund.

When to use it
when your cancellation process calls for reversing the charge itself; check with Omise which one fits your case.
Watch out
money moves on the live key, so test the flow on the Test dashboard first.
Omise19

Update a Charge

Action

In Make“Updates an existing charge.”

Update a Charge edits an existing charge in Omise, so information added later in your process ends up on the payment record itself.

When to use it
when information your team only has after payment should end up on the charge to ease reconciliation.
Watch out
it changes the charge you point to, so fetch it with Get a Charge or Search Charges first to be sure of the target.
Omise20

Update a Customer

Action

In Make“Updates an existing customer.”

Keep Omise in step with your CRM: Update a Customer rewrites the customer profile whenever the source of truth changes, so nobody edits two places.

When to use it
when a customer's details change in your CRM or shop and Omise should follow.
Watch out
map only the fields you really want to change, and confirm the target with Search Customers when you lack the reference.
Omise21

Update a Dispute

Action

In Make“Updates an existing dispute.”

Update a Dispute writes changes on an existing dispute, so the notes and answers your team prepares in another tool reach Omise without copy and paste.

When to use it
when your support or finance team completes a response to a case and wants it recorded on the dispute.
Watch out
fetch the case with Get a Dispute first so you update the one your team actually worked on.
Omise22

Update a Transfer

Action

In Make“Updates an existing transfer.”

Update a Transfer changes an existing transfer in Omise, which spares you a manual edit when payout details shift after the request.

When to use it
when an approval tool revises a payout that Create a Transfer already sent and the transfer should reflect it.
Watch out
confirm the transfer with Get a Transfer beforehand, and try the flow with the test key before going live.
Omise23

Search Charges

Search

In Make“Searches for charges or lists them all.”

Search Charges finds the charges that match what you are looking for, or lists them all, and hands each one to the next module as its own bundle.

When to use it
to rebuild a sales list in a spreadsheet or to find the charge behind a return before Create a Refund.
Watch out
a search can return zero, one or many results, and every module after it runs once per result, which uses operations.
Omise24

Search Customers

Search

In Make“Searches for customers or lists them all.”

Before creating anyone, Search Customers tells you whether that person already exists in Omise, which is the simplest guard against duplicate profiles.

When to use it
ahead of Create a Customer, or to export your customer list to a CRM.
Watch out
when nothing matches, the search returns no bundle and the modules after it do not run, so add a route for the not found case.
Omise25

Search Disputes

Search

In Make“Searches for disputes or lists them all.”

Search Disputes gathers the disputes of your Omise account, not only the open ones, so you can build a full history instead of checking cases one by one.

When to use it
for a dispute report in a spreadsheet, or to review past cases once an event signals a new one.
Watch out
each result becomes a separate bundle; add an aggregator if you want a single message rather than one per dispute.
Omise26

Search Open Disputes

Search

In Make“Searches for open disputes or lists them all.”

Only the cases still waiting show up with Search Open Disputes, which makes it the natural start of a to-do list for whoever answers disputes.

When to use it
to push every pending dispute into your task tool, with Get a Dispute behind it for the details.
Watch out
an empty result means no open case, so the rest of the scenario simply does not run on that pass.
Omise27

Search Refunds

Search

In Make“Searches for refunds or lists them all.”

Search Refunds lists refunds from Omise, so accounting can match what was paid back with returns recorded elsewhere.

When to use it
to fill a reconciliation sheet or to check whether a return was already refunded before creating another one.
Watch out
the modules placed after it run once per refund found, so a long list consumes operations quickly.
Omise28

Search Transfers

Search

In Make“Searches for transfers or lists them all.”

Search Transfers pulls up the transfers that match your criteria, or all of them, giving you a clear trail of what left your Omise balance.

When to use it
to log payouts in your accounting tool or to find a transfer before Update a Transfer.
Watch out
expect several bundles per run, and filter them right after the search to keep only the ones you need.
Need help

Need help automating Omise with Make?

A person reads every message.

FAQ

Omise and Make: common questions

01Is the Omise Make integration free?
Yes, on the Make side. Omise is a standard app, 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. Make counts each module execution as an operation, and paid plans add a 1 minute interval and unlimited active scenarios. Omise itself needs an active account; its own pricing is on the Omise site.
02What do you need to connect Omise to Make?
An active Omise account with API keys, and a Make account. In the Omise dashboard, open the Keys menu, choose the Test dashboard or the Live dashboard, and copy the Secret key. In Make, add an Omise module, click Create a connection, give it a name if you want, and paste the key. For the Watch Events trigger, Make asks you to click Create a webhook before creating the connection.
03Does the Omise trigger in Make react in real time?
Yes. Watch Events is an instant trigger: Omise calls Make through a webhook as soon as a new event happens, so the scenario does not wait for the 15 minute default schedule. That is why the module carries a lightning badge in the editor. It is also the only Omise trigger, so if you prefer a scheduled check, start the scenario on the clock and use a search module such as Search Charges instead.
04What if an Omise module is missing in Make?
Use Make an API Call. It calls any endpoint of the Omise API with the connection you already created, which covers what the listed modules do not. Keep in mind that Close a Dispute only works in test mode, and that the official Make documentation for Omise is AI-generated and may contain mistakes, so confirm anything important with Omise directly before relying on it in a live scenario that moves real money.
05Should you use Make or n8n for Omise?
It depends on the tool your team already builds in. On Make, Omise comes with 29 ready-made modules, including an instant Watch Events trigger and a Make an API Call module for everything else, so most payment, customer, dispute and transfer tasks need no custom request. On n8n, check whether an Omise node exists and what it covers before choosing. Neither tool is ranked here: compare the modules available against the tasks you plan to automate.
Same platform

Other docs you might need on this stack.

Browse all integrations