Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
Monitor Postgres Data Freshness and Email Alert If Stale This template monitors a set of tables inside a Postgres database to ensure they're getting updated. If the table hasn't been updated in 3 d...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.aggregate, n8n-nodes-base.postgres, n8n-nodes-base.datetime, n8n-nodes-base.set, n8n-nodes-base.stickynote, n8n-nodes-base.filter
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Kevin.
Original n8n.io sourceThis template monitors a set of tables inside a Postgres database to ensure they're getting updated.
If the table hasn't been updated in 3 days (configurable), an email alert is sent containing the tables that are stale.
You must have a Postgres database containing one or more tables that you'd like to monitor.
Each table to monitor must have a date or timestamp column that tracks when data was pushed.
For example, this might be:
timestamp column if your table holds event/timeseries datalast_updated column if your rows are expected to be modifiedProduce tables + date columns node to produce pairs of [table, date_column] that should be monitored for freshnessRemove fresh tables node for your desired staleness window (default is 3 days, but you can adjust as you please)Send alerts node to call whichever alerting workflow you please (I recommend my alerting workflow for easiest plug-and-play)This template works by:
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Postgres data freshness monitoring with email alerts |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | Engineering |
| Author | Kevin |
| Published | 20 Jul 2025 |
Use the JSON export at /data/workflows/6190/6190.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Monitor Postgres Data Freshness and Email Alert If Stale This template monitors a set of tables inside a Postgres database to ensure they're getting updated. If the table hasn't been updated in 3 d...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering use case.