Icarus Growth — Sub-scenarios & Brief Template

Watch Full walkthrough (7 min) Map Full system breakdown For AI Point Claude here

System

Funnel Intake

Unit

5 of 6

Platform

Make.com

Built by

Icarus Growth

▸ Seven minutes on the three helpers — the tasks they build and how the brief doc gets picked

What this does

These are the workers. Both main automations — New Funnel Brief and Express Funnel — hand off to them once a funnel record exists. Feed them a funnel's record ID and they do two jobs: turn that funnel into a full checklist of build tasks, and generate the right brief document for the strategist. They have no trigger of their own. They only run when a main calls them.

Split three ways on purpose. Page 1 tasks and Page 2 tasks each write half of the 13-step build checklist; Delivery creates the brief Google Doc. Keeping them separate means either main — full brief or express — can call the exact pieces it needs.

Where it sits

Step 1 · FormKickoff FormGenerates the URL

url

Step 2 · FormReplit FormsClient fills it in

submits

Step 3 · MainPush to AirtableFiles the funnel

calls

Step 4 · HereSub-scenariosBuilds the tasks

+ doc

Step 5 · DocDeliveryBrief document

later

DownstreamNotificationsSlack fan-out

Both mains lean on this hub. The full New Funnel Brief calls Page 1 after its first page and Page 2 after its second. The Express Funnel is one page, so it fires both at once.

How it works

Three separate automations, each one started by a main with a single input: the funnel's Airtable record ID. Here's what each builds.

Page 1 tasks scn 4655587 — grab the funnel record, then create the front half of the build checklist in Funnel Calendar:
1. (1) Adjust Team Task List
2. (2) Confirm Tracking Setup — UTMs and tags
3. (3) Write Funnel Copy
4. (6) Install & Adjust ManyChat Template
5. (8) Build Integrations (Make / Zapier)
6. (10) Create Looker Dashboard Page
7. (11) Send Client Launch Instructions
Most due dates count forward from the submission date (up to five days out). "Send Client Launch Instructions" is pinned to the launch date instead.
Page 2 tasks scn 4655591 — same funnel lookup, then the back half of the checklist plus a launch marker:
1. (4) QA All Copy
2. (5) Client Copy & Strategy Review
3. (7) Build DM Funnel in ManyChat
4. (9) QA & Launch ManyChat + Integrations
5. (12) Document Funnel via Screenshots
6. (13) Handoff to Ongoing Monitoring
7. A "{Funnel Name} — Launch Date" record on the calendar
The 13 steps interleave across both subs — the numbers run in dependency order, not the order they're created in.
Delivery — the brief doc scn 662018 — the one HTTP-triggered helper:
1. Grab the funnel record, then grab its linked account.
2. Run the funnel through a router: one branch per funnel shape (free resource, live event, new follower, paid product, and more).
3. Create a Google Doc from that shape's brief template.
4. Write the new doc's link back onto the funnel's Brief GDoc URL field — that's what the strategist opens to start the copy.

The moving parts

Three small automations, no triggers of their own. What each one touches:

Page 1 tasks

scn 4655587 — creates 7 build tasks

Page 2 tasks

scn 4655591 — creates 6 tasks + a launch record

Delivery / brief doc

scn 662018 — builds the brief Google Doc

Reads

The funnel record; Delivery also reads its Account

Writes tasks to

Funnel Calendar: All tblo2VTsX2AwYaeHV

Writes doc URL to

The funnel's Brief GDoc URL field

Called by

New Funnel Brief 4620714 and Express Funnel 4742834 — this hub is shared

Good to know
• The 13-step build checklist is split across the two subs — Page 1 owns 7 tasks, Page 2 owns the other 6 plus the launch marker.
• Delivery picks the template by funnel shape. Add a new funnel type and it needs its own router branch and its own doc template, or the brief won't generate.
• These task subs are the old build system, kept live for a clean handover. When you stop using them, you unlink the call from the mains — no rebuild needed. The Delivery brief-doc sub stays either way.
• Older screens may still say "Campaigns Internal" — that's just the previous name for Funnels Internal. Same table.

What you can safely change

Green = go ahead. Amber = fine, but run a dummy funnel through afterwards. Red = leave it, call us.

Green	Task names and descriptions — rename any of the 13 tasks or reword the notes. It's just text on the created records.
Green	The brief-doc template wording — edit the Google Doc templates themselves. The automation just copies whatever's in them.
Amber	Which page a task lands on — you can move a task between the Page 1 and Page 2 subs. Re-run both after.
Amber	Which template maps to which funnel type — editable in Delivery's router, but a wrong map gives the strategist the wrong brief. Test the shape you touched.
Red	The "get funnel record" step at the top of each sub — repoint it and the whole helper reads the wrong funnel or nothing at all.
Red	The input the mains send in — rename it and the calls from New Funnel Brief and Express Funnel break silently.
Red	Delivery's funnel-type router — delete a branch and that funnel type stops getting a brief.

What connects to this

This one's a shared hub — two automations call it, and it writes out to two places. It never starts itself.

◀ Comes in from

New Funnel Brief
Calls Page 1 after the brief page, Page 2 after the details page, and Delivery for the doc.
Express Funnel
One page, so it fires Page 1, Page 2 and Delivery together.

Goes out to ▶

Build tasks in Funnel Calendar: All
The Brief GDoc URL on the funnel record — the strategist's starting point.

No trigger, no schedule. If nothing calls these, nothing happens — that's by design. The Notifications fan-out is separate; it fires later off board moves, not off these.

If something looks wrong

A funnel was filed, but no build tasks appeared on the calendar.
Either the main never called the sub, or the funnel-record lookup came back empty. Check the call step in New Funnel Brief / Express Funnel, and that the record ID is valid.

Tasks appeared, but only half of them.
One of the two subs ran and the other didn't — check whether both Page 1 and Page 2 were called.

No brief doc, or the wrong brief doc.
The funnel's shape didn't match a Delivery router branch (or matched the wrong one). Check the funnel shape against the router.

Brief doc created, but the link never landed on the funnel.
The final "Add Brief GDoc URL" step errored — check the update-record step on that branch.

You can't permanently break these. A full restore copy of all three automations is saved alongside this page. Misconfigure one and we rebuild it exactly as it stands today.

Call us if: a main keeps calling a sub that errors, briefs stop generating for a funnel type you didn't touch, or the funnel-record lookups start failing. Those are past the safe-to-touch line.

Jargon buster

Sub-scenario: A standalone automation another one calls — like pressing a button that runs a second job and waits for it.
Run-a-scenario node: The purple step inside a main that hands off to a sub. It passes the funnel's record ID across.
HTTP request: The blue globe step. Delivery is started this way — a message posted to its webhook, same idea as the Replit form posting to the mains.
Router: A fan-out with many branches. Delivery uses one to pick the right brief template for the funnel's shape.
Template: A pre-built Google Doc the automation copies. The strategist fills the copy into the copy.
Anchor date: The date a task's due date counts from — either the submission date or the launch date.
Unlink: Detaching a step so it no longer runs. How you retire the task subs when the new build system takes over.

Page 1, Page 2 & Brief Template Sub-scenarios make · scn 4655587 · 4655591 · 662018

What this does

Where it sits

How it works

The moving parts

What you can safely change

What connects to this

◀ Comes in from

Goes out to ▶

If something looks wrong