Scoped after a free call

IoT alert automation from sensor threshold to the right technician

Sensor alerts that land in a shared inbox or a dashboard nobody watches are how real problems get missed. We build an alert pipeline that reads threshold events from your IoT platform or MQTT broker, filters noise such as brief spikes and low batteries, opens one ticket per real problem with readings attached, texts the on-call technician from your rota and escalates if nobody acknowledges. Because devices, data volumes and platforms vary widely, we scope the price after a free call, often as a pilot on one site.

The problem

Why sensor alerts get missed or ignored

A leak sensor, a freezer probe or a vibration sensor crosses a threshold and sends an alert. It lands in an email folder or flashes on a dashboard, and whether anyone acts depends on who is looking.

Meanwhile false alarms train people to ignore alerts: a door open for a minute, a sensor with a dying battery, a brief network drop that looks like a reading of zero. A good sensor alert system has to filter noise without hiding the one alert that matters, and it has to know who is on call tonight.

What we build

What our IoT alert automation includes

Event intake

Threshold and status events from AWS IoT Core rules, Azure IoT Hub routing, ThingsBoard, Particle webhooks or an MQTT broker.

Noise filtering

Rules for duration, repeat counts, battery and signal checks, so brief spikes and dying sensors are handled differently from real excursions.

One ticket per problem

Related alerts grouped by device and site into one ticket in your help desk or maintenance system, with readings and a chart.

On-call texting

The on-call technician from your rota texted with the site, device and reading, with a link to acknowledge.

Escalation

Unacknowledged alerts escalate to the next person after a time you set.

Alert log and tuning report

Every alert, acknowledgement and outcome logged, with a weekly report of noisy devices and thresholds.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Threshold crossed

    The platform or broker sends a threshold or status event.

  2. 02 Automated

    Filtered and grouped

    Duration and battery rules are applied and related alerts are grouped by device and site.

  3. 03 Automated

    Ticket and text

    A ticket opens with readings and the on-call technician is texted.

  4. 04 Ops team review

    Technician acknowledges

    The technician acknowledges, checks remotely or goes to site and records the outcome.

  5. 05 Engineer or ops lead decides

    Safety and dispatch calls

    Decisions about safety, shutting equipment down or calling emergency services are made by people.

How it behaves

How the sensor alert system behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • Problems handled before they notice, or a clear update if they do
  • A technician who arrives knowing the device and readings
  • Fewer surprise failures

What technicians see

  • One text per real problem with site, device and reading
  • A ticket with readings and history
  • Escalation only when nobody acknowledged

What the automation does

  • Filters noise and groups related alerts
  • Looks up the on-call rota and texts the right person
  • Logs every alert, acknowledgement and outcome

Edge cases and fallbacks

Low battery looks like a bad reading
Routed as a maintenance task, not an emergency.
Whole site goes quiet at once
Treated as a gateway or network issue and passed to offline monitoring.
Nobody on the rota for tonight
Escalates straight to the ops lead and flags the rota gap.
n8n or SMS provider down
The platform's own email alerts stay on as a fallback and the ops lead is told.
Technician acknowledges but does not close
A reminder after a set time, then the ops lead is told.

Architecture

Sensor alerts to tickets and on-call at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Sensors Thresholds, status IoT platform Rules or MQTT n8n workflow Filter and group On-call rota Sheet or calendar Ticket Help desk or CMMS SMS and chat Acknowledge link Technician Acts and records
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Sensors report readings and status to your IoT platform or MQTT broker, where threshold rules fire.
  2. 2 n8n applies duration, repeat and battery rules and groups related alerts by device and site.
  3. 3 One ticket opens with readings attached and the on-call technician is found from the rota.
  4. 4 The technician is texted with an acknowledge link, and unacknowledged alerts escalate.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Sensor alerts to tickets & on-call SMS project plan

Typical time to launch: about 7 weeks, then support

  1. 01

    Discovery

    About 1 week

    Devices, platform, current thresholds, alert volumes, rota and who acts on what.

  2. 02

    Design

    About 1 week

    Filtering rules, grouping, ticket format, escalation chain and message wording.

  3. 03

    Build

    About 2 weeks

    Event intake, filters, ticketing, rota lookup, texting, escalation and logs.

  4. 04

    Pilot

    About 2 weeks

    One site or device type, with alerts compared against what really happened.

  5. 05

    Rollout

    About 1 week

    More sites and device types, run book handover.

  6. 06

    Support

    Ongoing

    Threshold tuning, new device types and the weekly tuning report.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n with MQTT Trigger and HTTP nodes AWS IoT Core rule actions or Azure IoT Hub routing ThingsBoard, Particle or The Things Stack MaintainX, Zendesk or your help desk Twilio SMS Google Sheets or calendar for the on-call rota

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU: users can access device data

The EU Data Act applies from 12 September 2025 and lets users access and share the data their connected products generate, so alert and reading logs are kept in exportable form.

Source: digital-strategy.ec.europa.eu

EU: access by design from September 2026

Connected products placed on the EU market from 12 September 2026 must be designed so users can access their data by default where relevant and technically feasible.

Source: www.matheson.com

EU and UK: readings can be personal data

Sensor data tied to a home, a person or a vehicle can be personal data, so processors such as the automation host are under GDPR Article 28 contracts.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Sensor alerts to tickets & on-call SMS questions, answered.

With rules on duration and repeats, separate handling for low battery and weak signal, and grouping by device and site. A weekly report shows which devices and thresholds are noisy so you can tune them.

Yes. AWS IoT rules can post a message to an HTTPS endpoint, invoke Lambda or publish to SNS, any of which can start the workflow.

That is one of the most common setups: probes report to the platform, excursions that last longer than your limit open a ticket and text the on-call person, and readings are logged.

n8n has MQTT trigger and publish nodes, so it can subscribe to alert topics on your broker. High-volume raw readings stay in the platform or time-series store; n8n handles the events that need action.

Not by default. Remote actions that affect safety or equipment are decided by people. If you want an automated action for a clear case, we design it with your engineers and log it.

Alerts received versus tickets opened, time to acknowledge, escalations, false alarms per device and incidents found by customers first.

Free 20-minute call

Want this for your iot & connected device?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call