Catch Make Scenarios That Fail Silently with the Doyouok App

Make is great at running scenarios every night while you sleep. It is less great at telling you when one of those runs quietly did nothing.

Two things go wrong with scheduled scenarios. Sometimes the scenario doesn't run at all: it was turned off, it ran out of operations, or a module failed and stopped the run. And sometimes it runs perfectly and still gets it wrong: the import imported 0 rows, the API answered with an empty list. Make shows that second kind as a successful run, so nobody notices for days.

The Doyouok app for Make catches both. It is free and takes one module at the end of your scenario.

The app is in review by Make. Once it is approved, search for "Doyouok" when you add a module to any scenario.

Set up in three steps

1. Connect your account. Sign in to Doyouok (the Free plan is enough), open Profile > API tokens, name the token "Make" and press Create token.
2. Add Report a Run at the end of the scenario, after the modules that do the work. Press Create a connection and paste the token into API Token.
3. Run the scenario once. The first run creates the check and takes about 15 seconds longer while the new check is activated. The check then appears on your Doyouok dashboard.

That's it. There is no ping URL to copy and no check to create by hand. With Check set to A check by name (created on the first run), the module creates a check with your Check Name and reports to it on every later run.

Tell it what success looks like

• Expected Interval (minutes): how often the scenario runs, for example 60 for hourly or 1440 for daily. If no report arrives in time, you get an overdue alert.
• Result: Success or Failure. To decide by a condition, turn on Map next to Result and enter an expression that returns success or fail.
• Failure Reason: optional text shown in the alert, such as "0 rows imported".

Say module 2 of a nightly scenario calls your import API and returns { "total": 42 }. Set Check Name to "Nightly import", Expected Interval to 1440 and map Result to if(2.total > 0; success; fail). A night with 42 new rows is reported as healthy. A night that imports 0 rows is reported as failed, and you hear about it the same morning instead of next week.

Three ways to report a failure

• An expression, as above, when one module's output decides the result.
• A Router, with a filter on each route and a Report a Run with a fixed Result on each.
• An error handler: add Report a Run with Result Failure to a module's error handler route, so a scenario error is reported right away instead of waiting for the overdue alert.

Each alert names the check and, for a failure, includes your Failure Reason. Alerts go to email, and to Telegram, Slack or Discord if you connected them in Doyouok.

Only the result leaves your scenario

The app sends the Check Name, the expected interval, whether the run succeeded and, on a failure, your Failure Reason. The rest of your scenario's data stays in Make. You can revoke access at any time under Profile > API tokens.

Free for your first 5 scenarios

The app itself is free. Each monitored scenario uses one check from your Doyouok plan, and the Free plan includes 5 checks with no credit card. Bigger plans are on the pricing page.

Questions about setup, expressions or alerts? The Doyouok for Make help page has a step-by-step guide, an FAQ and an assistant that answers on the spot.