Automate Watchflow With Make: 4 Modules, Zero Code Needed

What you can automate

What can the Watchflow Make integration do for you?

The Watchflow Make integration links your Watchflow account to Make, a no-code tool where you build a scenario, meaning the automation itself, out of modules, meaning one brick each. Watchflow brings four action modules: Heartbeat Start, Heartbeat Ping, Heartbeat Fail and Make an API Call. There is no trigger, so something else starts the run.

Mark the start of a job. Place Heartbeat Start right after the module that kicks off the scenario. Judging by its name, it tells Watchflow that a run has begun. Make's documentation does not describe it further, so read what the module asks for once it is on the canvas.

Report a failure on its own path. Heartbeat Fail reads as the signal for a run that went wrong. Put it on a separate branch you reach only when an earlier module breaks, so a bad run never looks like a good one.

Confirm a finished run. Heartbeat Ping, placed last, is the natural candidate for a simple sign of life after the useful work is done. When none of the three fits, Make an API Call reaches any endpoint of the Watchflow API with the same connection.

Know the ceiling before you start: Make states it cannot publish complete documentation for Watchflow because too little public information exists, so field names and behavior are only visible inside the editor. For Make itself, see the Make review and Make pricing. Weighing the n8n route instead? Read n8n vs Make.

Connect

How do you connect Watchflow to Make?

01
Add a Watchflow module
Open a scenario, click the +, search for Watchflow and pick any of its modules. Then click Create a connection. A connection is your Watchflow account linked to Make once and reused by every Watchflow module.
02
Name the connection
Give the connection a name if you like, such as the Watchflow workspace it belongs to. This step is optional, but a clear name helps later when several accounts sit side by side in the same Make organization.
03
Authorize and save
Either approve Make on the Watchflow page that opens, or paste the key Watchflow gives you, depending on what the window asks for. Then click Save and the module is ready to fill in.

First scenario

Your first scenario with Watchflow

GoalWhen another app starts a scenario and the work succeeds, Make sends Heartbeat Ping to Watchflow.

01
Create the scenario
From the Scenarios page, create a new scenario and click the +. Pick the module of the app that should start the run, since Watchflow has no trigger of its own.
02
Set up the first module
Connect that first app and fill its fields. Make lists what it can read once the connection exists, so you choose from a menu instead of typing paths by hand.
03
Add Heartbeat Ping
Click the + on the right of the first module, search for Watchflow and pick Heartbeat Ping. Create the connection, then fill the fields the module shows, mapping data from the previous module where it helps.
04
Test with Run once
Click Run once. Make executes the scenario one time and shows the bundles, the items passed from module to module. Check in Watchflow that the signal arrived.
05
Schedule and switch on
Open the clock on the first module to choose when the scenario runs; a new scenario runs every 15 minutes by default. Then switch the scenario on.

Modules

What each Watchflow module does in Make

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

Watchflow1

Heartbeat Fail

ActionIn the docs only

This module gives you a way to tell Watchflow that a run did not go as planned; that reading comes from its name, since the documentation stays silent. It keeps failures visible instead of letting them pass as silence.

When to use it

on an error branch placed after the module most likely to break, such as an upload to another app.

Watch out

each call is one operation, so keep it off the success path.

Watchflow2

Heartbeat Ping

ActionIn the docs only

Here you get a plain sign of life sent to Watchflow from inside a scenario. The name points to a check-in signal; confirm what it expects by opening its fields in the editor.

When to use it

as the last module, so the signal only leaves once the real work is done.

Watch out

placed first, it would report success even when later modules fail.

Watchflow3

Heartbeat Start

ActionIn the docs only

With this one, Watchflow can learn that a run has just begun, if the name is a fair guide. Paired with a closing signal, it frames a job with a clear beginning and end.

When to use it

right after the module that starts the scenario, before any long step such as processing a batch of records.

Watch out

without a matching closing module, Watchflow only ever sees half the story.

Watchflow4

Make an API Call

ActionIn the docs only

You can call any endpoint of the Watchflow API from your scenario, reusing the connection you already created. It covers what the three heartbeat modules do not.

When to use it

when you need a Watchflow action that has no dedicated module in the list.

Watch out

Make publishes almost nothing on Watchflow, so you need the Watchflow API reference to know which path and body to send.

Need help

Need help automating Watchflow with Make?

A person reads every message.

FAQ

Watchflow and Make: common questions

01Is the Watchflow Make integration free?

Yes, Watchflow is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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 allow 40 minutes of execution. Make counts usage in operations, one per module run. Any Watchflow subscription you hold is a separate matter, handled on the Watchflow side.

02What do you need to connect Watchflow to Make?

You need a Watchflow account and a Make account. The Make documentation lists no prerequisite and no dedicated steps for this app, so you follow the generic flow: add a Watchflow module, click Create a connection, optionally name it, then either authorize Make on the Watchflow page or paste the key Watchflow provides, and click Save. The same connection then serves every Watchflow module, including Make an API Call, so you only set it up once.

03Does the Watchflow module react in real time?

No, because Watchflow has no trigger in Make: all four modules are actions. A scenario that uses them starts from something else. Either another app's trigger opens the flow, or you set a schedule on the first module, which is every 15 minutes by default for a new scenario and never under 15 minutes on the Free plan. The Watchflow modules then run at the position you gave them, for example Heartbeat Ping at the end.

04What if the Watchflow module you need is missing in Make?

Use Make an API Call. It reaches any endpoint of the Watchflow API with the connection you already have, so you are not limited to Heartbeat Start, Heartbeat Ping and Heartbeat Fail. Keep one limit in mind: Make says it cannot offer complete documentation for Watchflow because public information is scarce. You will need the Watchflow API reference to build the request, and a quick Run once to check the answer.

05Should you use Make or n8n for Watchflow?

It depends on the tool your team already runs. Make offers four Watchflow modules, Make an API Call included, and a guided editor where you test with Run once. The same app often exists as an n8n node too, so check whether it does before you choose. The deciding criteria are where your other scenarios live, who maintains them and which editor your team already knows, rather than the Watchflow side itself.

Add a Watchflow module

Name the connection

Authorize and save

Create the scenario

Set up the first module

Add Heartbeat Ping

Test with Run once

Schedule and switch on

Need help automating Watchflow with Make?