Archive key records: PostgreSQL
Runs on a schedule across PostgreSQL, Outlook and Google Sheets, runs the custom logic in a Code node. Built for migration, around a "Fetch Changes (Google Drive)" step, in 14 documented nodes.
Archive key records with PostgreSQL and Google Drive hands-free. An original, ready-to-import n8n workflow built around the 'Backup & Archive' pattern for data & analytics. It runs on a schedule and orchestrates 14 nodes across PostgreSQL, Outlook, Google Sheets. 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 PostgreSQL and Outlook in step for migration, without anyone re-typing a row
- ✓A failed PostgreSQL or Outlook call is retried rather than dropped, at any of the 14 nodes in this migration build
- ✓Every migration run leaves an audit row behind, alongside PostgreSQL
- ✓Fans the same result out to Google Sheets in the same run, for migration
- ✓Pinned sample data ships with it — run all 14 nodes for migration before wiring PostgreSQL
Use cases
- →Teams keeping PostgreSQL and Outlook aligned by hand for migration
- →Migration work where "Fetch Changes (Google Drive)" is still a manual step before PostgreSQL
- →Migration work that only reaches PostgreSQL on a schedule, when someone remembers to start it
Integrations
Workflow preview (14 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (14 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
Core levelA compact production shape: validation and error handling without extra machinery.
- •Moving data between PostgreSQL, Google Drive and Google Sheets in a single run
- •Adding retries and an explicit error path to external calls
- •Testing against pinned sample data before connecting anything real
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 (PostgreSQL, Outlook, Google Sheets, Google Drive). 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
Archive the database with Slack
Migration on n8n: runs on a schedule across Slack, Google Sheets, Google Drive, Notion, PostgreSQL and Discord, starting at "Export All Rows (Google Sheets)". 31 documented nodes.
Mirror contacts across systems for migration
Migration on n8n: runs on a schedule across Google Sheets, Slack, HubSpot, Google Drive and Outlook, starting at "Fetch Changes Since Watermark". 23 documented nodes.
Snapshot the database: Slack
Backups on n8n: runs on a schedule across Slack, PostgreSQL, Google Sheets and Google Drive, starting at "Fetch Changes (Google Drive)". Runs the custom logic in a Code node. 14 documented nodes.
Snapshot key records on a schedule
Backups on n8n: runs on a schedule across Google Sheets, Google Drive, Slack and Outlook, starting at "Download from Google Drive". Parses the incoming file into rows. 21 documented nodes.