Express Funnel » Push to Airtable make · scn 4742834
The one-page version of the funnel filer. Same job as the New Funnel Brief — done in a single pass.
▸ The 6-minute walkthrough — the express track, start to finish
What this does
The Express form is a single page. So this automation is a single pass — nothing to wait on, nothing to reconcile. A brief comes in, and in one run it files the funnel, matches the account, assigns the team, posts to Slack, and kicks off every downstream job. It's the lean twin of the full New Funnel Brief.
The difference from the full brief: there's no page one and page two here. The Express form gathers everything on one screen, so this fires once and it's finished. Want it to capture more? 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 Express Funnel track. Its fuller sibling, the New Funnel Brief, runs the same job across a two-page form.
How it works
One page in, one run out. No second page to wait on, no back-edits to reconcile. Here's the whole path.
- A submission hits the webhook — the live link to the Express Funnel form. Everything the client typed arrives as one bundle, tagged with a brief ID that starts
EFBso express funnels stay easy to tell apart. - Post the "new express funnel" update to Slack — company, funnel type, launch date.
- Search for the account by client name (case doesn't matter). The name came straight from a dropdown up in the kickoff form, so the match is clean.
- Work out the funnel shape. The form sends a funnel-type key like
new_follower_funnel; a Switcher turns it into the Airtable shape it maps to — Express New Follower Funnel. - Split on whether the account was found:
- Found → create the funnel record, link the account, assign the team, post the "account found" message to Slack.
- Not found → create the record without an account link and flag it in Slack.
- Either way, it calls both task builders at once — Page 1 and Page 2 together — and fires the brief-document automation. That's the run.
The moving parts
What this automation touches, at a glance. 15 steps in total.
Starts from
A webhook wired to
express-funnel.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
• It calls both task subs at the same time. The full track spreads them across page one and page two; the express track fires them together in one shot.
• Express brief IDs start with
• A Switcher translates the form's funnel-type key into the Airtable Funnel Shape — so
• Same fragility as the full track: assignment only lands if the matched account has its team roles filled. Leave a role empty and that slot comes through unassigned.
• It calls both task subs at the same time. The full track spreads them across page one and page two; the express track fires them together in one shot.
• Express brief IDs start with
EFB. The normal funnels use a long UUID — that prefix is how you tell the two apart in Airtable.• A Switcher translates the form's funnel-type key into the Airtable Funnel Shape — so
new_follower_funnel becomes Express New Follower Funnel.• Same fragility as the full track: assignment only lands if the matched account has its team roles filled. Leave a role empty and that slot comes through unassigned.
What you can safely change
Green = go ahead. Amber = fine, but send 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 Express form already sends that field. |
| Amber | Account matching & team assignment — editable, but a bad match leaves records unassigned. Test after. |
| Amber | The Funnel Shape switcher — it maps each funnel-type key to an Airtable shape. Add or change a mapping, then re-test that type. |
| Red | The webhook trigger — it's the live link to the Express form. Re-register or delete it and submissions vanish silently. |
| Red | The two sub-scenario calls & the brief-doc hand-off — remove any of them and tasks or 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 link in a chain. Here's what feeds this one and what it feeds.
◀ Comes in from
- Replit Forms — Express Funnel
The one-page form builds the whole payload. To capture more here, add the field there first.
Goes out to ▶
- Page 1 & Page 2 task builders — both called at once.
- 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, then check the account search and the funnel-shape step didn't stall. |
| Record created, but the wrong people (or nobody) are assigned. Check the team roles on the account record — an empty role comes through unassigned. |
| Funnel created, but no tasks or brief doc. One of the hand-offs errored — check the Page 1 / Page 2 subs or the brief-doc builder. |
| The funnel landed with the wrong shape. Check the Funnel Shape switcher — the funnel-type key coming in may not have a matching mapping. |
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 the funnel-shape mapping needs a new type added. Those are past the safe-to-touch line.
Call us if: the webhook stops firing, a hand-off automation errors again and again, or the funnel-shape mapping needs a new type added. 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.
- Router
- A fork in the road — here it decides the "account found" path versus the "not found" one.
- Switcher
- A translator — it turns the form's funnel-type key into the matching Airtable Funnel Shape.
- Sub-scenario
- A separate automation this one calls, like pressing a button that runs another job.