Simulation — shows exactly what the scenario does with sample data

Client Onboarding Autopilot — Make.com scenario simulation

This page replays the exact module logic shipped in client-onboarding-autopilot.blueprint.json (plus its daily reminder sweep): signed-proposal webhook → validate → Drive folder tree → CRM upsert → kickoff email + questionnaire → Slack channel & team → task seeding → day-3 questionnaire reminder. Nothing here calls a network — every value below is computed in-page with the same rules the scenario uses on the shipped sample client.

active modulecompleted
INTAKE → DRIVE WORKSPACE CRM → KICKOFF COMMS → TASKS DAY 3 — QUESTIONNAIRE REMINDER PATH isValid = true isValid = false proposal.signed crm ≠ airtable crm = airtable tool ≠ clickup tool = clickup event = questionnaire_reminder ∧ sent_at ≤ now − 3 days POSTs event to the same webhook, daily Webhookonboarding events Parse & Validateclient record router 400Respond 400named errors 200Respond 200instant answer event router Drive: Root Folder{Company} — {YYYY-MM} Iteratorsubfolder template Drive: Subfolders× 6 templated Aggregator6 bundles → 1 CRM router HubSpot: Upsert Contactkeyed on email Airtable branchsearch → update / create Kickoff Email+ questionnaire link Slack: Create Channelcl-{client-slug} Invite TeamPM + producer Post Kickoff Brieflinks + notes task router Asana: Seed 6 Tasksiterator + create ClickUp branchsame 6 tasks Daily Reminder Sweep2nd scenario · CRM search Reminder Emailonly if still pending Slack: Team Nudgein the client channel

Execution log — the real data at every hop

Simulation of the importable blueprints sold with this listing. In the real product the connections (Google Drive, HubSpot / Airtable, email, Slack, Asana / ClickUp) are yours, every template is editable, and invalid payloads never touch your tools.