New Funnel Brief » Push to Airtable make · scn 4620714
The automation that turns a submitted funnel brief into a fully set-up funnel record in your Airtable.
▸ The full 17-minute walkthrough — every step explained on screen
What this does
When a client submits the full New Funnel Brief form, this is the automation that files it. It reads the form, finds the matching account, creates the funnel record in Airtable, assigns the team, posts the updates to Slack, then kicks off the task lists and the brief document. Nobody types any of it.
The one thing to remember: this automation only moves what the form already collected. If you want it to capture more, you add the field to the Replit form first — not here.
Where it sits
Step 1 · FormKickoff FormGenerates the URL
url
Step 2 · FormReplit FormsClient fills it in
submits
Step 3 · HerePush to AirtableFiles the funnel
calls
TriggersSub-scenariosBuilds the tasks
+ doc
TriggersDeliveryBrief document
later
DownstreamNotificationsSlack fan-out
You're looking at the full New Funnel Brief track. Its shorter twin, the Express Funnel, is a simpler version of this same automation.
How it works
Every submission lands at the webhook and takes one of three paths, depending on which page was filled in.
- A submission hits the webhook — the live link to the Funnel Brief Portal form. The form sends everything the client typed as one bundle.
- The automation checks which page came in, and whether it's new:
- Page 1, brand-new brief:
- Post the "Page 1 in" update to the Slack thread.
- Search for the account by client / company name (case doesn't matter).
- Found → create the funnel record, assign the account's team (Client Ops Lead, Automation Specialist, Copywriter, Growth Strategist), call the Page 1 task builder, and fire the brief document.
- Not found → create it without an account link, flag it in Slack, then continue the same way.
- A team role is missing → create the record under Samantha Wyatt and warn you in Slack to assign it manually.
- Files attached → upload each one into the funnel's Source Material field.
- Page 1, back-edit (they went forward, then back a page) → find the existing brief and update it, so you don't get a duplicate.
- Page 2, funnel details → find the brief, post the "Page 2 in" update, save the final details, and call the Page 2 task builder.
- Page 1, brand-new brief:
- Whichever path ran, the funnel now exists in Airtable, the team is assigned, the tasks are queued, and the brief doc is on its way.
The moving parts
What this automation touches, at a glance. 31 steps in total.
Starts from
A webhook wired to
funnel-brief-portal.replit.appCreates records in
Funnels: Internal
Reads from
Accounts (Agency) — to match the account & pull the team
Posts updates to
Your funnel-notifications Slack channel
Good to know
• The form sends a funnel-type key and a label; the label is what lands in Airtable's Funnel Type field. (You also have a field called Funnel Shape — same idea, different name, easy to mix up.)
• "Email sequence needed" is probably dead now that everyone gets a sequence, so it may come through blank.
• The only real fragility: if an account is missing a team role, the normal create fails and everything defaults to Samantha Wyatt. Fill the missing role and it's fixed.
• The form sends a funnel-type key and a label; the label is what lands in Airtable's Funnel Type field. (You also have a field called Funnel Shape — same idea, different name, easy to mix up.)
• "Email sequence needed" is probably dead now that everyone gets a sequence, so it may come through blank.
• The only real fragility: if an account is missing a team role, the normal create fails and everything defaults to Samantha Wyatt. Fill the missing role and it's fixed.
What you can safely change
Green = go ahead. Amber = fine, but test a dummy submission after. Red = leave it, call us.
| Green | Slack message wording — reword any of the updates freely. It's just text. |
| Green | Which Slack channel the messages post to. |
| Green | A new field mapping — but only if the Replit form already sends that field. |
| Amber | Account matching & team assignment — editable, but a bad match leaves records unassigned. Test after. |
| Amber | The routing filters (Page 1 vs 2, new vs back-edit) — these steer the whole flow. Change one, re-test both paths. |
| Red | The webhook trigger — it's the live link to the Replit form. Re-register or delete it and submissions vanish silently. |
| Red | The hand-offs (Page 1 / Page 2 tasks and the brief-doc call) — remove these and tasks and the brief stop being created. |
| Red | The "create funnel record" table — repoint it and funnels land in the wrong place. |
What connects to this
Each breakdown is one piece of a chain. Here's what feeds this one and what it feeds.
◀ Comes in from
- Replit Forms — New Funnel Brief
The whole payload is built by that form. To capture more here, add the field there first.
Goes out to ▶
- Page 1 & Page 2 task builders
- Delivery — the brief document
- Internal Notifications — fires later, when this funnel moves on the board.
Not covered in this breakdown: the exact tasks the sub-scenarios create and the brief document template — those live in the Sub-scenarios breakdown.
If something looks wrong
| A brief was submitted, but no Airtable record appeared. Check the webhook received it, and whether a team role was empty (look for the Samantha-Wyatt warning in Slack). |
| Record created, but the wrong people (or nobody) are assigned. Check the team roles on the account record. |
| Funnel created, but no tasks or brief doc. One of the hand-off automations errored — check Page 1 / Page 2 tasks or the brief-doc builder. |
| Uploaded files didn't show up. Check the attachment step and the Source Material field on the funnel. |
You can't permanently break this. A full restore copy of the automation is saved alongside this page. If anything gets misconfigured, we rebuild it exactly as it is today from that file.
Call us if: the webhook stops firing, a hand-off automation errors again and again, or file uploads keep failing. Those are past the safe-to-touch line.
Call us if: the webhook stops firing, a hand-off automation errors again and again, or file uploads keep failing. Those are past the safe-to-touch line.
Jargon buster
- Webhook
- A "listening" address. The form posts to it, and that's what starts this automation.
- Payload
- The bundle of answers the form sends over.
- Step / module
- One box in the automation.
- Filter
- A fork in the road — it decides which path a submission takes.
- Sub-scenario
- A separate automation this one calls, like pressing a button that runs another job.
- Back-edit
- A client moving backwards through the form after already submitting a page.