Automated Google Sheet to CSV conversion via Slack messages
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 5 nodes and runs on Slack events. Along the way it connects Slack and Google Sheets.
How it runs
Trigger: On Slack events.
- Extract Sheet ID (Function): runs custom JavaScript (legacy Function node)
- Read Google Sheet (Google Sheets): uses Google Sheets
- Convert to CSV (Spreadsheet File): reads or writes a spreadsheet file (legacy node)
- Upload to Slack (Slack): work with file
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Extract Sheet ID: replace with Code node, mode 'Run Once for All Items'.
- Also check Slack Trigger requires a signing secret on the Slack API credential.
- Also check Spreadsheet File: Convert to File / Extract from File.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Extract Sheet ID | Code node, mode 'Run Once for All Items' |
Nodes used (5)
- Slack Trigger
n8n-nodes-base.slackTrigger - Function
n8n-nodes-base.function - Google Sheets
n8n-nodes-base.googleSheets - Spreadsheet File
n8n-nodes-base.spreadsheetFile - Slack
n8n-nodes-base.slack
From the author
Step 1: Slack Trigger The workflow starts whenever your Slack bot is mentioned or receives an event in a channel. The message that triggered it (including text and channel info) is passed into the workflow. Step 2: Extract the Sheet ID The workflow looks…