Internal Funnel Notifications make · scn 4801718
The engine that pings the right teammate in Slack the moment a funnel moves to a new stage on the board.
▸ How each stage hand-off finds its owner and tags them in Slack
What this does
This one sits at the very end of the line. Every time a funnel changes stage on the board, this wakes up, works out who owns that stage, and drops them a tagged message in Slack. Nobody chases. The work just lands in front of the next person, with the due date and a link to the record. It only fires after the funnel already exists and has moved through the pipeline — it's the last link, not the first.
Where it sits
Everything to the left of this builds and files the funnel. This page is what happens after — every time that funnel moves a step forward, this is what keeps the team moving with it.
How it works
One trigger, one job: a funnel moved, so tell the person whose turn it is.
- Someone drags a funnel to a new stage on the Funnels Internal board (your "Funnels: Internal"). An Airtable automation on that board fires and hands three things over: the funnel's record ID, its new stage, and its name.
- The automation hydrates — it fetches the detail it needs before doing anything:
- Pull the full funnel record from its ID.
- Pull the account attached to that funnel — that's how it knows the client and the team behind it (Client Ops Lead, Growth Strategist, Copywriter, and so on).
- It routes on the stage. One branch per stage hand-off — seven in total: write funnel copy, copy QA, build funnel & integrations, tracking, DM funnel QA, live, and monitoring. The funnel's stage decides which single branch runs.
- That branch does three quick things: search the Team table for the person who owns this stage, grab their Slack user ID, and post a tagged message in that stage's Slack channel — "this funnel's ready for you, here's the due date, here's the record." That's it. The next person now knows it's their turn.
The moving parts
What this automation touches, at a glance. 27 steps in total — mostly a router with seven near-identical stage branches.
• It routes purely on the funnel's stage. Each stage carries its own channel and its own owner lookup — they're separate branches, so you can edit one without touching the rest.
• The branch filters are "contains", case-insensitive. Keep them that way when you edit — it's what lets the stage names match cleanly.
• The one soft spot: if a stage has nobody assigned to its role in the Team table, the lookup finds no one, and the ping has no one to tag.
What you can safely change
Green = go ahead. Amber = fine, but move a test funnel through after. Red = leave it, call us.
| Green | The Slack message wording for any stage — it's just text. Reword freely (the purple bit is the person's tag — leave that). |
| Green | Which channel a stage posts to — swap the Slack channel on any branch. |
| Amber | The owner lookup — which role a branch searches for in Team (e.g. swap Growth Strategist for Client Ops Lead). Change it, then test. |
| Amber | Which stage routes where, and adding a brand-new stage branch. Copy an existing branch and keep the filter case-insensitive. |
| Red | The Airtable board automation that triggers this — it lives on the funnel board, not in Make. Break that and nothing fires. |
| Red | The webhook it fires through — re-register or delete it and every ping goes silent. |
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
- A funnel moving stage on the board
The funnel is already there because the intake pipeline built it — New Funnel Brief / Express Funnel and their task builders. This only wakes up once a card gets dragged forward.
Goes out to ▶
- Slack — the responsible teammate for that stage, tagged in that stage's channel.
- Nothing downstream in Make. The chain ends here, with a human getting pinged.
Still to come: this sits alongside other internal and onboarding automations that haven't been filmed or written up yet. They exist and their breakdowns are on the way — this page covers only the funnel-stage notifications, not those.
If something looks wrong
| A funnel moved, but no Slack message went out. Check the board's Airtable automation actually fired, and that the webhook received it. If the board didn't trigger, nothing here runs. |
| A message posted, but it tagged nobody. That stage has no one assigned to its role in the Team table. Fill the role and it resolves. |
| The ping went to the wrong person or the wrong channel. Check that stage's branch — its owner lookup and its Slack channel. |
| The "open in table" link opens the raw record, not the board view. Known and harmless — it's a single field we can point at the interface anytime. |
Call us if: the board automation stops firing, the webhook drops, or a whole stage stops notifying. Those are past the safe-to-touch line.
Jargon buster
- Webhook
- A "listening" address. The board automation posts to it, and that's what starts this automation.
- Router
- The fork with one branch per stage. The funnel's stage decides which branch runs.
- Filter
- The rule on each branch — "only run for this stage." Kept case-insensitive so the names match cleanly.
- Hydration step
- A lookup that fetches more detail — here, the full funnel, then its account — before anything acts on it.
- Slack tag
- The @-mention that pings a specific person. It's built from their Slack user ID.
- Stage / hand-off
- A column on the funnel board. Moving a card to it hands the work to the next owner.