Get Pinged When It Happens

Why this matters

A row appearing in a spreadsheet nobody is watching is a filing system, not a business improvement. The moment your flow also pings a human — a Slack message or an email the second a lead arrives — it starts changing behavior: sales teams that respond to leads within minutes convert dramatically better than teams that respond the next day, which is why 'instant lead alert' is one of the most commonly sold small automations. Technically this lesson crosses a real threshold too: your flow goes from one action to two, and multi-action flows are where automation earns its keep — one trigger fanning out into a row, an alert, a CRM entry, an autoresponder. The craft skill here is message composition from mapped fields: writing one template that reads like a human wrote it, no matter whose data flows through.

Demo

Extend the flow with a fourth step after the Sheets row: the Slack app, event 'Send Channel Message' (connect Slack via its OAuth screen, just like Google). Pick a channel — make a fresh one called #leads so alerts do not drown in chatter. Now compose the message by mixing typed text with mapped fields. Here is the actual template to type, with curly braces standing in for the fields you insert from earlier steps: 'New lead: {First Name} {Last Name} ({Email}). Company guess: {Company Guess}. They wrote: "{Message}". Logged to the Leads sheet.' When Marco's submission runs through, Slack posts: 'New lead: Marco Rossi (marco@rossicatering.it). Company guess: rossicatering.it. They wrote: "need help with invoices". Logged to the Leads sheet.' Two composition habits worth copying: put the person's name first so the alert is scannable on a phone lock screen, and quote the free-text message verbatim so the reader gets context without opening the sheet.

No Slack workspace? Use email instead — Gmail's 'Send Email' action with your own address as the recipient and subject 'New lead: {First Name} {Last Name}' behaves identically for this exercise. One ordering decision matters and will come up in client work: put the notification after the Sheets row, not before. If the row-write fails, you will not have announced a lead that was never recorded; the sheet is your system of record and the ping is just its messenger. Run one live submission end to end and enjoy the small dopamine hit of your phone buzzing because a form was filled.

Try it yourself

1. Create a #leads channel in Slack (or pick your inbox for the Gmail variant) and add the notification step with its own app connection.
2. Type the message template using at least four mapped fields — first name, last name, email, and the verbatim message — plus enough fixed text that it reads as a sentence, then send a test.
3. Read the test alert on your phone and check: can you tell who the lead is without unlocking? If not, reorder the template so the name leads.
4. Submit one live form entry and time the gap between clicking Submit and the ping arriving — write the number down; it goes in your demo script two lessons from now.
5. Swap the order so the alert fires before the sheet row, note what could now go wrong if Sheets errored, then swap it back — ordering by system-of-record-first is a habit worth building on a flow this small.

References

• Slack Help Center
• Zapier — Slack integrations
• Make Help Center