Flow Lab

Make.com scenario rescue · demo case

Urgent quote requests now go to the on-call tech, the rest to sales.

A website quote form feeds a Make scenario, which logs the request, looks up the service area, alerts the on-call tech about urgent jobs, and emails sales about the rest. In Make's run history, almost every run looks successful. Every finding from the audit is now fixed.

This demo scenario was built for this case and modeled on a typical home-services lead flow. It is not a client's scenario.

11findings, all fixed: 9 from the automated review, 2 from the manual review
6of them related to lead delivery and alert content
0findings when the same automated checks ran again after the fix

The scenario

What was found and fixed

HIGH PRIORITY · lead delivery

A step now waits and retries, and the scenario stays on

Before the fix, "Allow storing of incomplete executions" was off. A run that stopped at Google Sheets, Slack, or Gmail could not be retried, because the website does not resend the form. With default settings, Make also turns off a webhook-triggered scenario right after its first error.

Fix: storing of incomplete executions is now on, and the Sheets, Slack, and Gmail steps have Break handlers with automatic retry. If one of these steps does not go through, it now waits and retries, and the scenario keeps running.

HIGH PRIORITY · alert content

The "Area" field now always shows the service area or a clear note

Before the fix, the ZIP lookup ran on the legacy HTTP module with "Evaluate all states as errors" off. Make treated a 401 or 500 error response from the API as the service area.

Fix: the ZIP lookup now runs on the current HTTP "Make a request" module with "Return error if HTTP request fails" on, and a Resume handler writes the note "area lookup failed, check ZIP" to the field. The lead reaches sales with this note.

HIGH PRIORITY · security

The API key now lives in a Make keychain

Before the fix, the live key sat in the module URL and traveled with every exported blueprint, for example to a freelancer or into a shared template.

Fix: the key moved into a Make keychain (API key authentication in the HTTP module), so it no longer appears in exports, and the old key was replaced with a new one.

HIGH PRIORITY · alert content

The quote number now appears in both the Slack alert and the sales email

Before the fix, the Slack alert took "Quote #" from the Gmail module on the other route, and the sales email took a field from a deleted module, so both always came out empty.

Fix: both fields now use the Google Sheets row number from the "Log request" step, which every request passes through before the router.

MEDIUM PRIORITY · sales emails

Sales now gets one email per request

Before the fix, an Iterator went through the "services" list and sent each one straight to Gmail: three checked services meant three near-identical emails. The manual review found one more case: with no services checked, the Iterator had nothing to pass on, and no email was sent.

Fix: the Iterator is gone. The email lists the services with the join() function and says "not specified" when the list is empty. One request always means one email.

HIGH PRIORITY · request routing, found in the manual review

Requests marked "Urgent" and "urgent" now take the same route

Before the fix, the router filters matched "urgent" and "standard" exactly, letter case included, and there was no fallback route. A form value of "Urgent", or an empty value, was written to the sheet but matched neither route.

Fix: "urgent" now matches regardless of letter case, and the sales route is now the fallback: every request that is not urgent reaches sales.

LOW PRIORITY · sheet format

Dates and numbers now sort and filter in Sheets

Before the fix, rows went into Sheets as plain text.

Fix: rows are now written with valueInputOption: USER_ENTERED, so Google Sheets recognizes dates and numbers.

Before and after the fix

SituationBeforeAfter
Gmail or Sheets is unavailable for a minuteRun stops, scenario turns offStep is retried, scenario keeps running
ZIP lookup service returns an errorMake takes the error reply as the service areaLead sent with "check ZIP" note
Form sends "Urgent" (capital U)No route matches, no alert sentOn-call tech alerted
Customer picks 3 services / none3 emails / no emailAlways 1 email
Quote number in alertsField always emptySheet row number
Exported blueprint sharedIncludes the API keyNo API key inside

The audit report

The audit starts with an automated review of the exported blueprint. It needs only the file: the scenario does not run, and no access to your accounts is needed. Next comes a manual review of the logic, and Flow Lab confirms every finding in the editor before making any change. Excerpt:

Make scenario review: Quote requests → Sheet → Sales alerts (BEFORE)
7 modules, trigger: instant (webhook).

1. HIGH - Scenario settings: "Allow storing of incomplete executions" is off and the scenario starts with a webhook. If any module returns an error, the run stops and the request is not stored for a retry. With default settings, Make deactivates an instant-trigger scenario immediately after its first error.
2. HIGH - "ZIP → service area" [3]: "Evaluate all states as errors" is off: a 4xx/5xx reply is read as success.
4. HIGH - "Alert on-call tech" [5]: Maps a field from "Email sales" [7], which is not on the path before this module. On this path the field is always empty.
...
AFTER: all automatic checks pass. (Manual review: done.)

The blueprints were written by hand for this demo to show how the fix is built. They were not imported into Make, and the module settings in them are illustrative. On a real project, Flow Lab makes and tests every change in your own account.

How a rescue works

  1. You export the scenario: in the editor, … (More) → Export Blueprint, and send the .json file. The first look needs no access to your account.
  2. Within one business day, you get a plain-English list of what to fix, how it affects your business, and the changes Flow Lab proposes.
  3. You approve the changes. Flow Lab then fixes the scenario in your account, runs test submissions through every route and shows you the results.
  4. Optional monthly support: Flow Lab monitors the scenario and makes fixes as needed.