This workflow corresponds to n8n.io template #agency-os-n8n.weekly-health — we link there as the canonical source.
This workflow follows the Postgres → Slack recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"name": "Weekly delivery-health report",
"nodes": [
{
"parameters": {
"rule": {
"interval": [
{
"field": "weeks",
"triggerAtDay": [
1
],
"triggerAtHour": 8
}
]
}
},
"id": "c2b2f002-0000-4000-8000-000000000001",
"name": "Weekly Schedule",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
240,
300
]
},
{
"parameters": {
"operation": "executeQuery",
"query": "SELECT client, status, score FROM delivery_health ORDER BY score DESC",
"options": {}
},
"id": "c2b2f002-0000-4000-8000-000000000002",
"name": "Read Delivery Health",
"type": "n8n-nodes-base.postgres",
"typeVersion": 2.5,
"position": [
520,
300
],
"credentials": {
"postgres": {
"name": "<your credential>"
}
}
},
{
"parameters": {
"select": "channel",
"channelId": {
"__rl": true,
"value": "#delivery",
"mode": "name"
},
"text": "=Weekly delivery health:\n{{ $json.client }} \u2014 {{ $json.status }} ({{ $json.score }})",
"otherOptions": {}
},
"id": "c2b2f002-0000-4000-8000-000000000003",
"name": "Post to Slack",
"type": "n8n-nodes-base.slack",
"typeVersion": 2.2,
"position": [
800,
300
],
"credentials": {
"slackApi": {
"name": "<your credential>"
}
}
}
],
"connections": {
"Weekly Schedule": {
"main": [
[
{
"node": "Read Delivery Health",
"type": "main",
"index": 0
}
]
]
},
"Read Delivery Health": {
"main": [
[
{
"node": "Post to Slack",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {
"executionOrder": "v1"
},
"meta": {
"templateId": "agency-os-n8n.weekly-health"
},
"tags": [
{
"name": "agency-os"
}
]
}
Credentials you'll need
Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.
postgresslackApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
Weekly delivery-health report. Uses postgres, slack. Scheduled trigger; 3 nodes.
Source: https://github.com/enached134-ctrl/agency-os-n8n/blob/main/workflows/weekly-delivery-health.json — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
Heavy IO — HTTP + DB + Slack (well-handled). Uses httpRequest, postgres, slack. Scheduled trigger; 5 nodes.
This workflow automatically monitors PostgreSQL database data quality and detects structural or statistical anomalies before they impact analytics, pipelines, or applications.
Data ETL Pipeline - Daily Sales Report. Uses postgres, awsS3, moveBinaryData, emailSend. Scheduled trigger; 13 nodes.
The template allows to make Dropcontact batch requests up to 250 requests every 10 minutes (1500/hour). Valuable if high volume email enrichment is expected.
System Health Check. Uses httpRequest, postgres, slack. Scheduled trigger; 10 nodes.