Manage incident reporting in PagerDuty and CrateDB
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Data enrichment (°C to °F) | Code node, mode 'Run Once for All Items' |
Rarely used nodes in this template: n8n-nodes-base.amqpTrigger, n8n-nodes-base.crateDb
Nodes used (7)
- If
n8n-nodes-base.if - AMQP Trigger
n8n-nodes-base.amqpTrigger - Edit Fields (Set)
n8n-nodes-base.set - CrateDB
n8n-nodes-base.crateDb - PagerDuty
n8n-nodes-base.pagerDuty - Function
n8n-nodes-base.function - No Operation, do nothing
n8n-nodes-base.noOp
What it does
This workflow automatically monitors the functionality of a factory. The workflow logs machine data coming from factory sensors in a CrateDB database, generates an incident report in PagerDuty, and notifies the responsible staff members when the temperature of a machine crosses the threshold value. This workflow builds on a workflow that generates factory data. Read more about this use case and how to build both workflows with step-by-step instructions in the blog post How to automate your factory's incident reporting. Prerequisites - A PagerDuty account and credentials - AMQP, an ActiveMQ connection, and credentials - A CrateDB instance running locally or on a server, and credentials. Nodes - AMQP Trigger node starts the workflow. - IF node filters sensor values higher than 50°C. - PagerDuty node creates an incident in the account. - Set nodes set the required incident information and sensor data, respectively. - CrateDB nodes ingest the information data and machine sensor data, respectively. - Function node converts degrees from Celsius to Fahrenheit.