{"product_id":"n8n-incident-response-workflow-postgres-slack-email","title":"n8n Incident Response Workflow: Postgres + Slack + Email","description":"\u003ch3\u003eTurn incident alerts into a coordinated response—automatically\u003c\/h3\u003e\n\u003cp\u003eThis n8n Incident Response Workflow connects \u003cstrong\u003ePostgres\u003c\/strong\u003e, \u003cstrong\u003eSlack\u003c\/strong\u003e, and \u003cstrong\u003eEmail\u003c\/strong\u003e to track incidents, launch a Slack war-room, page responders via email, escalate when nobody acknowledges, send periodic status updates, and close incidents with resolution notifications.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cp\u003eDesigned to streamline incident management, it performs the following:\u003c\/p\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eReceives alerts\u003c\/strong\u003e through the \u003ccode\u003ePOST \/bc-alert\u003c\/code\u003e webhook (including simple JSON and Prometheus Alertmanager-style payloads), normalizing them into service, severity, and status fields.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCreates or deduplicates incidents\u003c\/strong\u003e in \u003cstrong\u003ePostgres\u003c\/strong\u003e—either opening a new incident or attaching the alert to an existing open incident for the same service—then returns a \u003cstrong\u003e202\u003c\/strong\u003e response with the incident ID and deduplication status.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eLaunches the response\u003c\/strong\u003e for new incidents by loading service metadata and team contacts from Postgres, creating a \u003cstrong\u003eSlack war-room channel\u003c\/strong\u003e, posting an incident brief and checklist, and emailing each responder a unique \u003cstrong\u003eacknowledgement link\u003c\/strong\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCaptures acknowledgement\u003c\/strong\u003e via \u003ccode\u003eGET \/bc-ack\u003c\/code\u003e, updates the incident in Postgres, and posts a Slack message naming the \u003cstrong\u003eincident commander\u003c\/strong\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eEscalates and reports status\u003c\/strong\u003e every \u003cstrong\u003e5 minutes\u003c\/strong\u003e: it finds unacknowledged incidents needing escalation and open incidents due for updates, then sends escalation notices via \u003cstrong\u003eSlack and email\u003c\/strong\u003e to stakeholders.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCloses incidents\u003c\/strong\u003e when resolution is submitted via \u003ccode\u003ePOST \/bc-resolve\u003c\/code\u003e, marking the incident resolved in Postgres, posting resolution + duration to Slack, and emailing stakeholders (including executives, as provided in workflow data).\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eOperating a SaaS where Prometheus Alertmanager notifications must trigger consistent, fast on-call response.\u003c\/li\u003e\n  \u003cli\u003eCentralizing incident tracking in Postgres while using Slack channels for war-room coordination.\u003c\/li\u003e\n  \u003cli\u003eReducing alert noise by deduplicating incidents per service until they are acknowledged or escalated.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003en8n webhook endpoints:\u003c\/strong\u003e \u003ccode\u003ePOST \/bc-alert\u003c\/code\u003e, \u003ccode\u003eGET \/bc-ack\u003c\/code\u003e, \u003ccode\u003ePOST \/bc-resolve\u003c\/code\u003e\n\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eIntegrations \/ nodes:\u003c\/strong\u003e \u003ccode\u003ewebhook\u003c\/code\u003e, \u003ccode\u003epostgres\u003c\/code\u003e, \u003ccode\u003eif\u003c\/code\u003e, \u003ccode\u003eset\u003c\/code\u003e, \u003ccode\u003ecode\u003c\/code\u003e, \u003ccode\u003eswitch\u003c\/code\u003e\n\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eChannels:\u003c\/strong\u003e Slack war-room + email paging and stakeholder updates\u003c\/li\u003e\n\u003c\/ul\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":46196308672691,"sku":"N8N-20725","price":24.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/u9g8iLLTZgD7fNhK5QOAs_l5ec5aVH.png?v=1791623094","url":"https:\/\/buyflowscripts.com\/products\/n8n-incident-response-workflow-postgres-slack-email","provider":"N8N Commerce","version":"1.0","type":"link"}