Resources · Make integration

Wachete Make integrationAutomate Wachete with Make.

Want every Wachete alert to land where your team actually works? The Wachete Make integration gives you 3 modules: 2 triggers that pick up notifications and 1 API call module. This page shows you how to connect your account and build a first scenario step by step.

Try the Wachete integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Wachete Make integration?

The Wachete Make integration links your Wachete account to Make, a tool where you build automations called scenarios without writing code. Make reads the new notifications in your Wachete account, then passes each one to the next step of your scenario.

Catch every alert in one place. Watch Notifications picks up each new notification in your account. Each one reaches Make as a bundle (one item that flows from a module to the next), ready to be sent to a chat tool, a sheet or a ticket.

Follow a single page closely. When several pages are watched from one account, a given team usually cares about only one of them. Watch Notifications for Particular Wachet listens to the one wachet you pick, so pricing, legal or product each get their own scenario without noise from the others.

Reach what the listed modules leave out. Make an API Call sends a request to any endpoint of the Wachete API with the connection you already set up. It is the way to go further once you know which endpoint you need.

Know the limits before you start: Make itself says its documentation for Wachete is limited, because little public information exists about this app. Both triggers are scheduled, so Make checks for news on the scenario's schedule, not the second a page changes. Wachete also often has an n8n node; the n8n vs Make comparison helps you pick a tool. To learn the editor properly, see our Make training, and our Make pricing guide explains how operations are counted.

Connect

How do you connect Wachete to Make?

  1. 01

    Add a Wachete module

    In your scenario, add any Wachete module, for example Watch Notifications, then click Create a connection. A connection is your Wachete account linked to Make once and reused by every Wachete module.

  2. 02

    Name the connection

    This step is optional but helpful. Give the connection a clear name, such as the team or the account it belongs to, so you can tell it apart later if you link more than one Wachete account.

  3. 03

    Authorize and save

    Authorize Make on the Wachete page that opens, or paste the key Wachete gives you, depending on what the window asks for. Then click Save. Make can now read your notifications.

First scenario

Build your first scenario with Wachete

GoalWhen Wachete records a new notification, Make picks it up and calls the Wachete API endpoint you chose to act on it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Search for Wachete and pick Watch Notifications.

  2. 02

    Link your account

    Click Create a connection, authorize Make, then save. Every later Wachete module in this scenario reuses the same connection, so this happens once.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API Call from Wachete. Point it at the endpoint you need and map values from the notification bundle.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which is the easiest way to check what a notification contains.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan allows no shorter gap. Pick your schedule and switch the scenario on.

Triggers

Wachete triggers in Make

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

Wachete1Watch Notifications

Watch Notifications

Scheduled trigger

In Make“Triggers when there is a new notification in your account.”

You get every new notification from your whole Wachete account as the starting point of a scenario, one bundle per alert, whichever page it comes from.

How it fires
scheduled, so Make checks the app on the scenario's schedule (every 15 minutes by default) and collects the notifications created since its last check.
When to use it
pick it when you want one feed of all your alerts, for example a shared channel where the whole team sees every change Wachete spots.
Watch out
it does not filter by wachet, so a busy account sends many bundles, and each module run on each bundle costs an operation on your plan.
Wachete2Watch Notifications for Particular Wachet

Watch Notifications for Particular Wachet

Scheduled trigger

In Make“Triggers when there is a notification from Wachet you have chosen.”

This trigger narrows the feed to one wachet, the single monitor you select, so your scenario only wakes up for the page that matters to it.

How it fires
scheduled as well. Make checks the app on the scenario's schedule and passes along only the notifications from the wachet you chose.
When to use it
choose it over Watch Notifications when one team owns one page, such as a competitor's pricing page followed by sales.
Watch out
a new page to follow means a new wachet, and this trigger will not see it until you build or copy a scenario that points to it.
Modules

Other Wachete modules

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

Wachete1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module, you can reach any endpoint of the Wachete API from your scenario, reusing the connection you already created, so nothing new needs to be authorized.

When to use it
use it when neither trigger covers your need and you know which endpoint of the Wachete API does the job.
Watch out
Make's own documentation for Wachete is limited, so you need the endpoint details from Wachete's side before you set this module up.
Need help

Need help automating Wachete with Make?

A person reads every message.

FAQ

Wachete and Make: frequent questions

01Is the Wachete Make integration free?
Yes. Wachete is a standard app in Make, so it is available from the Free plan onward. The Free plan comes with limits: 2 active scenarios, at least 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) lower the gap between runs to 1 minute, allow unlimited active scenarios and count usage in credits, which are operations, per month.
02What do you need to connect Wachete to Make?
A Wachete account and a Make account. Make's documentation lists no specific prerequisite for Wachete. You add a Wachete module, click Create a connection, optionally name it, then authorize Make on the Wachete page or paste the key Wachete gives you, and save. Keep in mind that Make describes its Wachete documentation as limited, so the window you see may be the best guide to what is asked. The connection is then reused by every Wachete module.
03Does the Wachete trigger in Make fire in real time?
No. Both Wachete triggers, Watch Notifications and Watch Notifications for Particular Wachet, are scheduled. Make checks Wachete on the scenario's schedule, which is every 15 minutes by default on a new scenario. The Free plan cannot go below 15 minutes, while paid plans can check as often as every minute. A notification therefore reaches your scenario at the next check, not at the moment Wachete creates it. Plan for that delay if a change needs a fast reaction.
04What if the Wachete module you need is missing in Make?
Use Make an API Call. This module can call any endpoint of the Wachete API through the same connection as the triggers, so it covers what the 2 listed triggers do not. The catch is documentation: Make says it cannot fully document Wachete because public information is scarce, so you will need the endpoint details from Wachete before you configure the call. Test it with Run once and read the bundle it returns before you switch the scenario on.
05Should you use Make or n8n for Wachete?
It depends on the tool you already work in. Wachete often has an n8n node too, so both routes can exist. On Make you get 2 scheduled triggers for notifications and an API call module for everything else, with a visual editor and the Free plan to try it. Compare how each tool handles the steps you need rather than the app alone; our n8n vs Make comparison lays out the differences between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations