AutomationFlowsSlack & Telegram › Heavy IO — Http + Db + Slack (well-handled)

Heavy IO — Http + Db + Slack (well-handled)

Heavy IO — HTTP + DB + Slack (well-handled). Uses httpRequest, postgres, slack. Scheduled trigger; 5 nodes.

Cron / scheduled trigger★★☆☆☆ complexity5 nodesHTTP RequestPostgresSlack
Slack & Telegram Trigger: Cron / scheduled Nodes: 5 Complexity: ★★☆☆☆ Added:

This workflow follows the HTTP Request → Postgres 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 →

Download .json
{
  "name": "Heavy IO \u2014 HTTP + DB + Slack (well-handled)",
  "nodes": [
    {
      "id": "t",
      "name": "Schedule",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1,
      "position": [
        200,
        300
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "field": "hours"
            }
          ]
        }
      }
    },
    {
      "id": "http",
      "name": "Fetch Orders",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4,
      "position": [
        440,
        300
      ],
      "parameters": {
        "url": "={{$env.ORDERS_API}}/orders",
        "options": {},
        "retryOnFail": true
      },
      "retryOnFail": true,
      "maxTries": 3,
      "continueOnFail": true
    },
    {
      "id": "db",
      "name": "Upsert Postgres",
      "type": "n8n-nodes-base.postgres",
      "typeVersion": 2,
      "position": [
        680,
        300
      ],
      "parameters": {
        "operation": "upsert",
        "table": "orders"
      },
      "onError": "continueErrorOutput",
      "credentials": {
        "postgres": {
          "name": "<your credential>"
        }
      }
    },
    {
      "id": "slack",
      "name": "Notify Slack",
      "type": "n8n-nodes-base.slack",
      "typeVersion": 2,
      "position": [
        920,
        220
      ],
      "parameters": {
        "resource": "message",
        "operation": "post"
      },
      "continueOnFail": true,
      "credentials": {
        "slackApi": {
          "name": "<your credential>"
        }
      }
    },
    {
      "id": "handle",
      "name": "Handle DB Error",
      "type": "n8n-nodes-base.noOp",
      "typeVersion": 1,
      "position": [
        920,
        400
      ],
      "parameters": {}
    }
  ],
  "connections": {
    "Schedule": {
      "main": [
        [
          {
            "node": "Fetch Orders",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Fetch Orders": {
      "main": [
        [
          {
            "node": "Upsert Postgres",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Upsert Postgres": {
      "main": [
        [
          {
            "node": "Notify Slack",
            "type": "main",
            "index": 0
          }
        ]
      ],
      "error": [
        [
          {
            "node": "Handle DB Error",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "settings": {
    "errorWorkflow": "err-wf-1"
  },
  "active": false
}

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.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

About this workflow

Heavy IO — HTTP + DB + Slack (well-handled). Uses httpRequest, postgres, slack. Scheduled trigger; 5 nodes.

Source: https://github.com/malharlakdawala/flowproof/blob/main/examples/workflows/heavy-io.json — original creator credit. Request a take-down →

More Slack & Telegram workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

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.

Postgres, HTTP Request, Slack
Slack & Telegram

System Health Check. Uses httpRequest, postgres, slack. Scheduled trigger; 10 nodes.

HTTP Request, Postgres, Slack
Slack & Telegram

Crypto Price Tracker. Uses httpRequest, postgres, slack. Scheduled trigger; 9 nodes.

HTTP Request, Postgres, Slack
Slack & Telegram

WF-7: Health Check. Uses httpRequest, slack, postgres. Scheduled trigger; 7 nodes.

HTTP Request, Slack, Postgres
Slack & Telegram

This workflow automatically pulls daily signup stats from your PostgreSQL database and shares them with your team across multiple channels. Every morning, it counts the number of new signups in the la

Postgres, Slack, Microsoft Teams +1