Notify the team on new events: Google Sheets for standups
Fires the moment a webhook arrives across Google Sheets and Slack, routes each kind of record down its own branch, then writes the result out as a file. Built for standups, around a "Compute HMAC Signature" step, in 23 documented nodes.
Notify the team on new events with Slack with instant alerts. An original, ready-to-import n8n workflow built around the 'Event Notification' pattern for software development & devops. It fires on a webhook and orchestrates 23 nodes across Google Sheets, Slack, HTTP / REST API. Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. The result is a hands-off process that just works.
Key benefits
- ✓Keeps Google Sheets and Slack in step for standups, without anyone re-typing a row
- ✓A failed Google Sheets or Slack call is retried rather than dropped, at any of the 23 nodes in this standups build
- ✓Branches rejoin before Google Sheets, so a standups run reports once rather than 23 times
- ✓Every standups run leaves an audit row behind, alongside Google Sheets
- ✓Pinned sample data ships with it — run all 23 nodes for standups before wiring Google Sheets
Use cases
- →Teams keeping Google Sheets and Slack aligned by hand for standups
- →Pushing standups events into Google Sheets and Slack the moment they land, not on the next poll
- →Standups work where "Compute HMAC Signature" is still a manual step before Google Sheets
- →Standups work that only reaches Google Sheets when a webhook arrives, when someone remembers to start it
Integrations
Workflow preview (23 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (23 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Reacting to an event and notifying the right channel
- •Moving data between Google Sheets and Slack in a single run
- •Splitting one run into branches and merging the results back
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Google Sheets, Slack, HTTP / REST API). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Review requests with Slack
Standups on n8n: runs when a form is submitted across Slack, Airtable, Google Sheets and Twilio, starting at "Normalize Task Payload". 21 documented nodes.
Alert stakeholders on changes: Slack for standups
Standups on n8n: runs when a webhook arrives across Slack and Google Sheets, starting at "Map to Canonical Schema". Routes each kind of record down its own branch. 13 documented nodes.
Alert the team on new events: Google Sheets for standups
Standups on n8n: runs when a webhook arrives across Google Sheets, Slack and Microsoft Teams, starting at "Probe Endpoint A". Branches on the check before anything is written. 24 documented nodes.
Route expenses with Slack & MySQL
Standups on n8n: runs when a form is submitted across Slack, MySQL, Outlook and Google Sheets, starting at "Stamp & Shape Task". 21 documented nodes.