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.
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
What it does
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 can easily swap the S3 node for the storage provider of your choice. ++How it works++ Weekly Backup - Schedule trigger fires weekly - Sets and formats the week ex. 2025-W12 - Create a folder in S3 bucket with the week - Loops through all tables in Airtable base creating CSVs and uploading to the new path - Slack message is sent on completion Monthly Prune - Schedule trigger fires weekly - Sets a cut-off date 4 weeks in the past - Lists folders in S3 - Deletes all folders > 4 weeks old ++Setup Steps++ 1. Clone workflow 2. Swap credentials for Airtable, AWS, and Slack - Ensure AWS credential has appropriate IAM policy to manage bucket & objects 3. Set workflow to "Active"