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 →
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
Ban Claim Handler. Uses postgres, httpRequest, whatsApp, telegram. Webhook trigger; 20 nodes.
Source: https://github.com/sonnyagent30-beep/Styxproxy/blob/da8aa60b5a6f12cf57ee6ab38cdbdf56006ea121/.n8n/workflows/ban-claim.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.
Ban Claim Handler. Uses postgres, httpRequest, whatsApp, telegram. Webhook trigger; 20 nodes.
Refund Handler. Uses postgres, minimax, httpRequest, whatsApp. Webhook trigger; 18 nodes.
Settings. Uses httpRequest, postgres, telegram. Webhook trigger; 38 nodes.
Payment Confirmation. Uses postgres, httpRequest, whatsApp. Webhook trigger; 14 nodes.
Flujowhatsapp. Uses @aldinokemal2104/n8n-nodes-gowa, postgres, httpRequest. Webhook trigger; 65 nodes.