Resources · Make integration

Hexowatch Make integrationAutomate Hexowatch with Make.

What should happen the moment Hexowatch records something new? The Hexowatch Make integration gives you 2 modules: one instant trigger and one open API call. This guide walks an ops or marketing builder through the connection, a first scenario and the questions that come next.

Try the Hexowatch integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Hexowatch Make integration do for you?

The Hexowatch Make integration links your Hexowatch account to Make so that a new event starts a scenario, the automation you build in Make as a chain of modules. From there, Make can pass that event to the other tools you already use, with no code and no server to run.

Alert the right person. Put Watch Events first, then add a module from your chat or email app. Each new Hexowatch event travels as a bundle, one item handed from a module to the next, and lands where your team actually reads it.

Keep a shared log. The same trigger can feed a spreadsheet or a database app, so every event ends up in one place that a manager can filter later without opening Hexowatch.

Reach what the list does not cover. Make an API Call sends a request to any endpoint of the Hexowatch API with the connection you already set up. It asks you to read the Hexowatch API documentation first, which is why the other two ideas are the better starting point.

Be clear about the scope: the catalog holds only these 2 modules, with no ready-made search or update module. The same app often exists as an n8n node too; the n8n vs Make page lays out the criteria. To learn the editor step by step, see Make training, and check Make pricing before you count operations.

Connect

How do you connect Hexowatch to Make?

  1. 01

    Copy your Hexowatch API key

    Log in to Hexowatch, open the Settings section, then the Webhook section inside it. The API key is shown on screen: copy it. You need an active Hexowatch account for this key to exist.

  2. 02

    Create the connection in Make

    In your scenario, add a Hexowatch module and click Create a connection. A connection is your Hexowatch account linked to Make once, then reused by both modules. The Connection name field is optional, so a clear label is enough.

  3. 03

    Paste the key and confirm

    Enter the API key you copied, or follow the instructions Make shows on screen, and save. The connection now appears in the module, and any other Hexowatch module you add later can pick it from the list.

First scenario

Your first scenario with Hexowatch

GoalWhen a new event is created in Hexowatch, Make receives it and calls the Hexowatch API with the same connection.

  1. 01

    Start a new scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That is where the first module goes.

  2. 02

    Add Watch Events

    Search for Hexowatch, pick Watch Events, click Create a webhook, then create or pick your connection with the API key from Hexowatch.

  3. 03

    Chain Make an API Call

    Click the + on the right of the trigger and add Make an API Call. Fill in the request from the Hexowatch API documentation and map data coming from the event.

  4. 04

    Test with Run once

    Click Run once, then produce a new event in Hexowatch. Make runs the scenario one time, and each module shows the bundles it received so you can check the data.

  5. 05

    Switch the scenario on

    When the test looks right, switch the scenario on. Because the trigger is instant, Hexowatch calls Make as soon as an event exists; there is no polling interval to set.

Triggers

What starts a Hexowatch scenario

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

Hexowatch1Watch Events

Watch Events

Instant trigger

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

Watch Events hands you every new Hexowatch event the moment it is created, so the rest of your scenario works on fresh data instead of waiting for a check. Each event arrives as one bundle that the next modules can read and map.

How it fires
instant: the app calls Make through a webhook as soon as it happens, which is why the module carries the lightning badge.
When to use it
any time a new event should reach a person or another tool without someone opening Hexowatch to look.
Watch out
click Create a webhook before Create a connection, or the trigger has no address to receive events on.
Modules

What else the Hexowatch app can do

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

Hexowatch1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives you access to any endpoint of the Hexowatch API from inside the scenario, reusing the connection you already created. It is the only action in the catalog, so it covers everything the trigger alone cannot do.

When to use it
when you need a Hexowatch operation that has no dedicated module.
Watch out
you write the request yourself, so keep the Hexowatch API documentation open and test with Run once.
Need help

Need help automating Hexowatch with Make?

A person reads every message.

FAQ

Questions about the Hexowatch Make integration

01Is the Hexowatch Make integration free?
Yes, on the Make side. Hexowatch is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer, and a minimum of 15 minutes between scheduled runs. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits, meaning operations, each month. You still need an active Hexowatch account with its own subscription, which is set by Hexowatch.
02What do you need to connect Hexowatch to Make?
An active Hexowatch account and its API key. In Hexowatch, open Settings, then the Webhook section, and copy the key displayed there. In Make, add a Hexowatch module, click Create a connection, give it a name if you like, and paste the key. When the module is instant, such as Watch Events, click Create a webhook first and then create the connection. After that, both Hexowatch modules share the same connection.
03Does the Hexowatch trigger in Make fire in real time?
Yes. Watch Events is an instant trigger: Hexowatch calls Make through a webhook as soon as a new event is created, and the scenario starts right away. You do not wait for a polling interval, so the 15 minute default schedule of new scenarios does not slow it down. The one condition is that the webhook exists, which is why the module asks you to click Create a webhook before the connection, and that the scenario is switched on.
04What if the Hexowatch module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Hexowatch API with the connection you already have, so you do not need a second login. The catch is that you build the request yourself from the Hexowatch API documentation. Also note that the Make documentation for this app is marked as AI-generated from Hexowatch sources and may contain mistakes, so verify important details with Hexowatch directly.
05Should you use Make or n8n for Hexowatch?
It depends on the tool your team already runs. Hexowatch often exists as an n8n node too, so the choice rarely comes down to this app alone. On Make, the offer is clear: one instant Watch Events trigger and an open API call module, set up in a visual editor with a Free plan to start. Compare the modules each side offers for your exact case, then choose the platform where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations