Advertising disclosure: this page contains one advertising (affiliate) link, to Make, marked next to the link. If you sign up through it we may earn a commission at no extra cost to you. Make has been our affiliate partner since 2026-08-22; the tests and the conclusions on this page predate that and have not been changed since. Every other product link on this page is a plain link.

The client-intake Make blueprint: download, import, and what to change before it runs

type templatetested 2026-08-21evidence client-intake-v2 (based on client-intake-v1)see the run recordstatus approved for publication

Tested 2026-08-16 (v1, two rounds), 2026-08-20 (v2 with error handlers, each case once) and 2026-08-21 (v2.1, richer alert emails, each handler once with the final text). Plans used, checked on the dates shown: Tally Free and HubSpot Free CRM (accounts created 2026-08-05), Brevo Free (2026-08-06), Make Free (license read via API 2026-08-20). This is the exact scenario from our tested workflow guide, exported from Make as a blueprint file. It is not a diagram; it is the thing that ran.

What you get

client-intake-v2.1.blueprint.json (recommended): the v2 scenario below with richer alert emails. A handled failure now emails you the scenario name and id, the failed step, the error type and the full error message from HubSpot, the execution id, a run-log URL in the format of Make's history view, all six form fields, and (for the association failure) the HubSpot contact and deal ids. Tested 2026-08-21, one provoked failure per handler plus one healthy run.
client-intake-v2.blueprint.json: Tally webhook trigger, HubSpot contact search with an exact email filter, a router with a new-lead path (create contact, create deal, link deal to contact through one HubSpot API call, send acknowledgement through Brevo) and an existing- contact path (update contact), plus error-handler routes that email an alert and keep the scenario running when the association call or the contact creation fails.
client-intake-v1.blueprint.json: the same workflow without error handlers and with the older free-text search. Kept for reference. We do not recommend running it: in our tests, both unhandled errors we provoked deactivated it (see what breaks).

The published files are sanitized copies of our exports. Make blueprints contain no API keys; they reference connections by numeric ID plus a readable label, and our originals carried our lab account's name and address in those labels and in the email modules. In the download copies those are replaced with placeholders (Your HubSpot CRM connection, you@example.com, sender@example.com, Your Company). Your Make account will ask you to pick your own connections on import anyway.

Download: client-intake-v2.1.blueprint.json, client-intake-v2.blueprint.json and client-intake-v1.blueprint.json.

Import in Make

You need a Make account for this; the free plan is enough for the volumes in our tests (Make sign-up, advertising link: Make).

Create a new scenario and open the three-dot menu in the scenario editor; choose Import blueprint and select the JSON file (Make Help Center, checked on 2026-08-20). We exported on Make Free on 2026-08-16 without restriction. We have not tested importing on Free; try it before you plan around it.
Make's documentation says you must create your own connections after importing (checked on 2026-08-20). Create or pick your Tally, HubSpot CRM, and Brevo connections when the modules ask. We expect the Tally trigger to ask for a webhook as well; choose your own form there. Not tested by us.
Save the scenario explicitly before doing anything else. Run once does not save; we lost two modules that way on 2026-08-15.

Five values you must change

Each of these carries a placeholder or a value from our form. Left as is, the scenario will either fail to map your data or send mail to a placeholder address.

Tally field mappings (modules 3, 5, 6, 7, 13, 20, 22). On our form, Tally identified the email field as question_7vj5DL, the name as question_6v45ke, and the company as question_brgGke; your form's IDs will differ. After connecting your form, submit one test response, then open each listed module and re-pick whichever of those fields it maps: email in 3, 5, 13, 20, 22; name in 5, 6, 7, 13, 20, 22; company in 5 and 6.
Alert recipient (modules 20 and 22). The error-handler emails go to you@example.com. Put your own address there. In v2.1 the alert body uses Make's system variables (var.scenario.name, var.scenario.id, var.scenario.executionId, var.scenario.url) and the failed module's error bundle (12.error.message and 5.error.message); these need no edits. One thing we learned the hard way: a literal = followed by two hexadecimal digits in the plain-text body was decoded as quoted-printable on its way to the inbox (observed once, 2026-08-21; cause not isolated), so keep = signs out of the alert text.
Sender and reply-to (modules 13, 20, 22). Both the sender and the reply-to fields hold Your Company <sender@example.com>. Replace them with a sender you have verified in Brevo. Sender history from our tests: with an unauthenticated Gmail address, Brevo rewrote the visible sender to its shared brevosend.com domain and the emails still reached a Gmail inbox (2026-08-16 and 2026-08-20). After we authenticated our own domain in Brevo and switched the sender to it, the acknowledgement arrived from our domain with DKIM, SPF and DMARC reported as passing at the receiver, and no rewrite (one healthy run, 2026-08-22). Authentication changed the visible sender and the authentication headers in that one run; whether inbox placement improves was not tested. Other providers untested.
Acknowledgement text (module 13). It says "Your Company". Make it yours.
Deal name, stage, pipeline (module 7). Stage appointmentscheduled and pipeline default are internal names of HubSpot's starter pipeline; they worked in our portal, created on 2026-08-05. If you renamed or rebuilt your pipeline, pick your own stage.

Two things to know

HubSpot region. Our portal runs on HubSpot's EU data center. The association call uses a relative path through Make's HubSpot connection, so we expect it to follow your connection's region without edits; we have not tested an import into another region.
Operation budget. A new lead costs 6 Make credits, a duplicate 3, a handled failure up to 7 (measured). Make Free gives 1,000 credits a month (checked on 2026-08-20). Size it with our cost calculator before pointing real traffic at it.

Verify before trusting it

Submit a new test lead. Check HubSpot: one contact, one deal, and the deal's Contacts panel shows the contact. Check the lead inbox: one acknowledgement.
Wait at least a minute (so HubSpot's search index catches up; within seconds a duplicate can slip past the search, as we observed at 29 milliseconds), then submit the same lead again. Check Make's run history: the run should show the existing-contact path (module 6), and the lead inbox should hold no second acknowledgement.
Open module 12, add a letter to deal_to_contact in the URL, and save. Submit a third, new test lead. Expected, based on our v2 run: the run ends without error, the lead still gets the acknowledgement, your alert address receives an email naming the failed step, and the scenario stays active (check its on/off toggle). The deal is created but not linked.
Restore the URL, save, and submit one more new lead to confirm the healthy path again.

Known limits of this template

v2 error handling was observed once per case; the v2.1 alert text once per handler. Re-test in your own account.
The run-log link in the alert follows the URL pattern Make uses in its History view. We read it in the delivered email; we did not click it from a signed-in browser in the test.
A handled association failure leaves the deal unlinked; the alert reports the failed step and points you to the run history. Linking the deal is a manual step.
A handled duplicate that slips past the search is dropped, not merged into the existing contact.
Full name lands in HubSpot's first-name field; no first/last split.
Free-plan execution logs are retained 7 days (make.com/en/pricing, checked on 2026-08-20).

Who this is for: a solo consultant or small agency who wants this exact workflow and is willing to verify it with the four submissions above. Who should skip it: if a simple form-to-contact capture is enough, HubSpot's free form builder does that with no Make at all (checked on 2026-08-18), and it is the non-affiliate alternative we would point you to first.

Evidence packs client-intake-v1 and client-intake-v2 (including the v2.1 extension of 2026-08-21). Module numbers refer to the blueprint's internal IDs. Material statements map to this page's claim ledger; inferences and untested expectations are labeled as such.