When you clone a Make scenario, do not assume the cloned scenario should keep using the source webhook. In AWB-EXP-002, one same-team clone used a fresh candidate webhook. The source webhook was not reused, and the source scenario remained immutable.

That is a focused observation from one successful synthetic onboarding run, not a universal rule for every Make scenario. But it gives a practical answer to one question worth resolving after cloning: verify that the candidate has its own webhook arrangement before you test the workflow.

What happened to the webhook in this clone

The clone was created in the same Make team with zero requested and zero verified semantic workflow mutations. That describes the workflow’s logic; it does not mean there was no operational setup. A fresh webhook was created for the candidate, rather than reusing the source webhook.

The candidate started inactive. After explicit approval, it was activated and received exactly one synthetic submission. The source scenario was not changed as part of this work.

For the broader result, including the same-team connection context, read the full EXP-002 clone-portability experiment.

How the fresh webhook was verified

Creating a replacement webhook is not, by itself, evidence that the cloned scenario works. In this run, the test verified the downstream path by API after the one synthetic submission. All seven expected targets were verified:

  • the Make execution;
  • a HubSpot company and contact;
  • four expected HubSpot tasks;
  • a Gmail welcome message and internal handoff message; and
  • a Google Calendar kickoff event.

This is the useful verification pattern: confirm that the candidate’s webhook can carry a controlled submission through the actual workflow, then inspect the expected results. Merely seeing a cloned scenario or a newly created webhook is a weaker check.

Practical takeaway

For this tested same-team clone, the evidence-supported description is: keep the source scenario immutable, create a fresh candidate webhook, and verify the candidate with a controlled end-to-end submission. The experiment involved zero manual Make UI module reconfiguration, but the fresh-webhook step is operational setup and should not be erased by the phrase “zero semantic workflow mutations.”

The evidence does not establish that Make automatically preserves webhook configuration, that every cloned scenario needs the same handling, or that a source webhook is always unsafe to reuse. It also does not establish reliability, idempotency, replay safety, or duplicate safety: there was exactly one successful synthetic submission and no retry.

Evidence scope

This article uses the frozen public-safe AWB-EXP-002 result. It records one successful same-team run only and omits webhook URLs, scenario and hook identifiers, account details, and credentials.