--- title: "n8n Integration for Uptime Monitoring — Uptrack" description: "Manage Uptrack monitors and incidents from n8n workflows, and start a workflow when a monitor goes down or recovers. Open source community node." url: https://uptrack.app/integrations/n8n ---

# Uptime monitoring in your n8n workflows.

The Uptrack community node reads and manages your monitors and incidents from n8n, and a trigger starts a workflow the moment a monitor goes down or recovers. It is open source (MIT). [Get the node on npm](https://www.npmjs.com/package/n8n-nodes-uptrack) [Source on GitHub](https://github.com/Uptrack-App/n8n-nodes-uptrack) The node is not verified by n8n yet, so n8n Cloud cannot install it yet. It installs on self-hosted n8n today. ## What the node does Two nodes and two credentials. Operations call the Uptrack API with your API key. Monitor Get many (with search), get, create (HTTP or heartbeat), update, pause, resume, delete Incident Get many (only ongoing, or all), get with its updates, acknowledge, post an update Uptrack Trigger Starts a workflow when a monitor goes down, recovers, or a watched third-party status page cannot be read ## How to set it up 1. 1 ### Install the node On self-hosted n8n, open Settings, then Community Nodes, then Install, and enter n8n-nodes-uptrack. 2. 2 ### Add your API key Create an API key in the Uptrack dashboard. In n8n, create an Uptrack API credential and paste it. Select Test to check it. 3. 3 ### Build the workflow Add the Uptrack node to read or change monitors and incidents, or the Uptrack Trigger node to start from an alert. ## Start a workflow from an alert The Uptrack Trigger node receives the signed webhook that Uptrack sends when a monitor changes state. 1. Add the Uptrack Trigger node to a workflow and copy its webhook URL. 2. In Uptrack, create an alert channel of type Webhook, paste the URL, and add the channel to the monitors you want. 3. Copy the signing secret that Uptrack shows once, and save it in the Uptrack Webhook API credential in n8n. The trigger checks the signature of every request and refuses old or unsigned ones. Webhook alert channels need a paid plan, so the trigger does not work on the free plan. The payload is described in [webhook payloads](https://uptrack.app/guides/webhook-payloads). ## Workflow ideas Built from the node and n8n's own nodes. - Open a Linear or Jira ticket when a monitor goes down, and add a note when it recovers. - Post the incident to a team channel with the monitor name and the failure details from the alert. - Pause the monitors of a service while a deploy runs, then resume them. - Add a row to a spreadsheet for each incident, with its start and end time. ## Limits - This first version creates HTTP and heartbeat monitors. Other monitor types are made in the dashboard and can still be read and updated. - Your plan sets the number of monitors and the shortest check interval. Uptrack answers with an error when you go over, and the node shows the message. - You add the webhook channel in Uptrack by hand. The node does not register it for you. Prefer plain HTTP? Everything the node does uses the public API, which has an [OpenAPI description](https://api.uptrack.app/openapi.json), so the HTTP Request node works too. Using an AI assistant instead? See [AI and MCP](https://uptrack.app/ai). ## Connect your monitors to your workflows Know in seconds when a site is down, then let n8n do the rest. [Start free](https://uptrack.app/signup?plan=free) [See plans](https://uptrack.app/pricing) Free: 5 monitors at 30 s · paid from $3/mo, 30-day money-back guarantee