Airtable base backups to S3
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 17 nodes and runs on a schedule (every week at 12:00) (plus 1 other trigger). Along the way it connects Airtable, AWS S3 and Slack.
How it runs
Trigger: On a schedule (every week at 12:00) (plus 1 other trigger).
- Set Week (Edit Fields (Set)): sets 1 field: currentWeek
- Set Timestamps (Edit Fields (Set)): sets 1 field: cutoffDate
- Create Folder (AWS S3): work with folder
- List Folders (AWS S3): get many (folder)
- Airtable: get schema (base)
- If: checks a condition and branches into true / false
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- Delete File (AWS S3): delete (folder)
- Aggregate: combines items into one
- Create Table Metadata (Edit Fields (Set)): sets 3 fields: fileName, tableName, tableID
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Airtable
n8n-nodes-base.airtable - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Edit Fields (Set)
n8n-nodes-base.set - Convert to File
n8n-nodes-base.convertToFile - AWS S3
n8n-nodes-base.awsS3 - Schedule Trigger
n8n-nodes-base.scheduleTrigger - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - No Operation, do nothing
n8n-nodes-base.noOp - Aggregate
n8n-nodes-base.aggregate
From the author
This workflow exports every table in a base as its own CSV, saves the files in a time-stamped folder in Amazon S3, pings you on Slack, and optionally prunes older copies. You get an automated weekly backup that is easy to inspect or re-import as needed. You…