Resources · Make integration

Ozy Approvals Make integrationAutomate Ozy Approvals with Make.

Can Make pick up where an approval ends? The Ozy Approvals Make integration gives you 7 modules: 2 scheduled triggers, 3 actions and 2 searches. This guide is for ops teams that route approvals through Ozy, and it walks you from the access token to a first scenario that runs.

Try the Ozy Approvals integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Ozy Approvals Make integration let you automate?

The Ozy Approvals Make integration links your Ozy organization account to Make, so approval tickets and requests can move into your other tools without anyone copying them by hand. You build a scenario, the automation itself, out of modules: small bricks that each watch, create or look up one thing in Ozy Approvals.

Escalate late tickets. Watch Breached Ticket SLA hands your scenario the tickets that went past their SLA, so a manager hears about them in the tool the team already reads instead of someone spotting them by chance in the queue.

Open approvals from outside Ozy. When a purchase form lands in another app, Register a Request can log it in Ozy Approvals, and Create a Ticket covers the cases your team tracks as tickets. Search Approval Request can look up what already exists.

Close the loop after a decision. Watch Actioned Tickets picks up tickets once someone has acted on them, and Search Ticket fetches a specific one when a later step needs its details.

Know the limits before you start. The official doc gives no description for any of these modules and flags its own content as AI-generated, so check each module's fields in the editor. Make an API Call reaches the parts of the Ozy API the listed modules skip. Ozy Approvals may also have an n8n node; the n8n vs Make comparison lays out how the two tools differ. For the bigger picture, read our Make review or see what the Make training covers.

Connect

How do you connect Ozy Approvals to Make?

  1. 01

    Generate an access token in Ozy

    You need an active Ozy Approvals organization account. Open the organization account settings, go to the Access Tokens section, click Generate and copy the API token Ozy shows on screen.

  2. 02

    Add an Ozy Approvals module

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

  3. 03

    Paste the token and save

    Give the connection a clear label in the optional Connection name field, handy if you manage more than one organization. Paste the token you copied, or follow the instructions Make displays, then confirm.

First scenario

Your first scenario with Ozy Approvals

GoalWhen a purchase form is submitted in another app, Make registers the matching request in Ozy Approvals.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. This first module is the form app where your team files purchase requests.

  2. 02

    Set the form trigger

    Search your form app by name, pick its module for new submissions and link its account. Each submission then reaches Make as a bundle, one item passed from module to module.

  3. 03

    Add Register a Request

    Click the + on the right of the form module, search Ozy Approvals and pick Register a Request. Choose your connection, then map the answers of the form into the fields Make shows.

  4. 04

    Test with Run once

    Submit a test form, then click Run once. Make executes the scenario one time and shows the bundles each module received, so you can check that the request appeared in Ozy.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run counts as an operation on your Make plan.

Triggers

What can start an Ozy Approvals scenario?

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

Ozy Approvals1Watch Actioned Tickets

Watch Actioned Tickets

triggerIn the docs only

This trigger feeds your scenario the tickets someone has acted on in Ozy Approvals, so the steps that follow a decision no longer wait for a person to relay it. Each ticket arrives as its own bundle, ready to map into the next module.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule rather than being called by Ozy.
When to use it
a decision in Ozy should update a record, notify the requester or open a task somewhere else.
Watch out
the doc describes neither the fields nor what counts as actioned, so run the scenario once and read the bundle before you map anything.
Ozy Approvals2Watch Breached Ticket SLA

Watch Breached Ticket SLA

triggerIn the docs only

Here your scenario receives the tickets whose SLA has been breached, which turns a late approval into an alert rather than a surprise. The breached ticket travels as one bundle to whatever module you place next.

How it fires
scheduled; Make polls Ozy Approvals on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
a manager or a shared channel should hear about an overdue approval the moment Make spots it.
Watch out
on the Free plan the shortest gap between two scheduled runs is 15 minutes, so a breach can sit that long before your alert goes out.
Modules

What can Make do in Ozy Approvals?

Ozy Approvals gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Ozy Approvals1

Register a Request

ActionIn the docs only

Register a Request logs a new approval request in Ozy Approvals from data another app already holds, so nobody retypes it.

When to use it
a form, an email or a CRM record starts a purchase or leave request that must go through Ozy.
Watch out
if the same source can fire twice, you get two requests. The doc does not say what Search Approval Request looks up by, so test it before relying on it to catch a duplicate.
Ozy Approvals2

Create a Ticket

ActionIn the docs only

With Create a Ticket, your scenario opens a ticket in Ozy Approvals, the item your team works through its queue.

When to use it
your process tracks the item as a ticket rather than as a request, for example an issue raised by a customer in your helpdesk.
Watch out
the doc lists no fields for it, so open the module once to see what Ozy asks for.
Ozy Approvals3

Make an API Call

ActionIn the docs only

Make an API Call is your fallback for anything the six other modules do not cover, since it can reach any endpoint of the Ozy Approvals API.

When to use it
you need an operation on tickets or requests that no listed module offers.
Watch out
it reuses your existing connection, but you write the request yourself. Keep the Ozy API documentation open beside the editor while you do.
Ozy Approvals4

Search Approval Request

SearchIn the docs only

Search Approval Request looks up approval requests already in Ozy. That way your scenario knows what is there before it creates or changes anything.

When to use it
a later step needs the details of a request, or you want to see what already exists before registering a new one.
Watch out
a search can return zero, one or several bundles. Every module after it runs once per bundle, so a broad search adds operations fast.
Ozy Approvals5

Search Ticket

SearchIn the docs only

Search Ticket finds tickets already in Ozy Approvals, so your scenario can read one before updating another tool or deciding what to do next.

When to use it
an email or a chat message mentions a ticket and you want its current details in the same flow.
Watch out
when nothing matches, the modules after it receive no bundle and simply do not run, so test that case with Run once.
Need help

Need help automating Ozy Approvals with Make?

A person reads every message.

FAQ

Ozy Approvals and Make: common questions

01Is the Ozy Approvals Make integration free?
Yes, on the Make side. Ozy Approvals is a standard app, so it works 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 and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in operations per month. Your Ozy Approvals subscription is separate: check the Ozy pricing page for it.
02What does it take to connect Ozy Approvals to Make?
You need an active Ozy Approvals organization account and an access token. In Ozy, open the organization account settings, go to the Access Tokens section, click Generate and copy the token shown on screen. Then, in Make, add any Ozy Approvals module, click Create a connection, optionally name it and paste the token. The same connection then serves all seven modules, so you only go through this once per organization account.
03Do Ozy Approvals triggers in Make react in real time?
No. Both triggers, Watch Actioned Tickets and Watch Breached Ticket SLA, are scheduled. Make checks Ozy Approvals on the scenario's schedule, every 15 minutes by default on a new scenario, and never less than 15 minutes apart on the Free plan. Paid plans can go down to 1 minute. A ticket actioned right after a check therefore reaches your scenario at the next one, which is worth keeping in mind for SLA alerts.
04What if an Ozy Approvals module is missing in Make?
Use Make an API Call. It calls any endpoint of the Ozy Approvals API with the connection you already set up, so you are not limited to the six other modules. Build the request from the Ozy API documentation, then test it with Run once. Also note that the official Make doc for this app is flagged as AI-generated and lists no field details, so verify important information with Ozy Approvals directly.
05Is Make or n8n better for Ozy Approvals?
It depends on the tool your team already works in. On Make, Ozy Approvals comes with seven modules: two scheduled triggers, three actions including Make an API Call, and two searches, all usable from the Free plan. Ozy Approvals may also have an n8n node, so check what that node offers before you decide. Pick the tool where the rest of your approval flow already runs, since a scenario that stays in one place is easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations