Skip to content
ExpertEnterpriseRAG / Knowledge BaseWebhook trigger31 nodes

Digest meeting notes: Slack + sub-workflow

Fires the moment a webhook arrives across Slack, Google Sheets and Notion, pulls structured fields out of free text, then branches on the check before anything is written. Built for q&a, around a "Collect Raw Text" step, in 31 documented nodes.

Digest meeting notes with MySQL and Telegram end to end. An original, ready-to-import n8n workflow built around the 'AI Summarize & Route' pattern for AI & automation. It fires on a webhook and orchestrates 31 nodes across Slack, Google Sheets, HTTP / REST API. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. What used to take a morning now runs on its own.

Key benefits

  • Keeps Slack and Google Sheets in step for q&a, without anyone re-typing a row
  • Safe to re-run: records already in Slack or Google Sheets are skipped, across all 31 nodes of this q&a build
  • A failed Slack or Google Sheets call is retried rather than dropped, at any of the 31 nodes in this q&a build
  • Branches rejoin before Slack, so a q&a run reports once rather than 31 times
  • Every q&a run leaves an audit row behind, alongside Slack

Use cases

  • Teams keeping Slack and Google Sheets aligned by hand for q&a
  • Pushing q&a events into Slack and Google Sheets the moment they land, not on the next poll
  • Q&a work where "Collect Raw Text" is still a manual step before Slack
  • Q&a work that only reaches Slack when a webhook arrives, when someone remembers to start it

Integrations

SlackGoogle SheetsHTTP / REST APINotionMySQLTelegramOpenRouter

Workflow preview (31 nodes)

The template's actual node layout and connections. Node parameters and credential slots unlock with the download.

On Telegram EventTelegram TriggerCollect Raw TextSetExtract Structured Fiel…Information ExtractorOpenRouter Chat ModelLm Chat Open RouterAll Required Fields Fou…IfUpsert into NotionNotionQueue for Manual ReviewSlackMerge Review PathsMergeStamp Completion TimeDate TimePersist Run MetadataExecution DataFingerprint for Idempot…CodeDrop Already-Processed …Remove DuplicatesLoad Previous SnapshotGoogle SheetsCompute Drift vs Snapsh…CodeOffload to Post-Process…Execute WorkflowRecord Sub-workflow Res…Execution DataEnrich with Reference D…Http RequestFold In Enrichment Fiel…SetSerialize Run Output (C…Convert To FileArchive Row SnapshotGoogle SheetsStamp Processing TimeDate TimeGuard Non-Empty titleFilterCap Batch VolumeLimitSort Documents Newest F…SortTag Pipeline MetadataSetSummarize Run StatsSetAppend Audit Row (Googl…Google SheetsSend Summary to SlackSlackCapture Failure ContextSetEscalate Failure to Sla…SlackPark in Dead-Letter Que…My Sql

What's inside (31 nodes)

A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.

CodeConvert To FileDate TimeExecute WorkflowExecution DataFilterGoogle SheetsHttp RequestIfInformation ExtractorLimitLm Chat Open RouterMergeMy SqlNotionRemove DuplicatesSetSlackSortTelegram Trigger

From download to running in 3 steps

  1. 1
    Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
  2. 2
    Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
  3. 3
    Activate. Run it once to test, then toggle Active. The automation is live.

What you'll learn

Architect level

The deepest tier - sub-workflow delegation, state snapshots, and full observability.

  • Routing classified output into separate action branches
  • Rejoining parallel branches with Merge so the run reports once
  • Moving data between Telegram, Notion and Slack in a single run

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 (Slack, Google Sheets, HTTP / REST API, Notion, …). 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.

Original n8n workflow template created and owned by WorkflowCrate. After purchase you receive the ready-to-import JSON file and a license to use and adapt it in your own projects.