TagoIO handles IoT data exceptionally well: ingestion, storage, dashboards, and alerting. But there are workflows that go beyond TagoIO’s native Actions: updating a CRM when a shipment sensor exceeds temperature limits, creating a Jira ticket when a machine goes offline, syncing daily energy readings to a spreadsheet, or sending a WhatsApp message when a CO2 alarm fires.
n8n is an open-source workflow automation platform. It connects hundreds of apps and services through a visual, node-based editor. You can run it self-hosted or use n8n Cloud.
Combining TagoIO and n8n gives you two complementary automation layers: TagoIO for IoT data routing and device logic, and n8n for cross-app business process automation triggered by that data.
What you need before you start
- A TagoIO account (free plan available)
- An n8n instance (self-hosted or n8n Cloud)
- A TagoIO Profile Token with API access (generate it in TagoIO under Account → Profile Tokens)
Architecture overview
[IoT sensors] → [TagoIO: ingestion, storage, alerting]
↓ (webhook trigger or API poll)
[n8n workflow] → [Slack, Jira, Google Sheets, CRM, etc.]n8n can both read from TagoIO (to fetch device data for processing) and write to TagoIO (to push computed values back into device buckets).
Pattern 1: TagoIO Action → n8n webhook trigger
The simplest integration: when a TagoIO Action fires (threshold breach, device offline, new data), it calls an n8n webhook to start a workflow.
Step 1: Create a webhook node in n8n
- In n8n, create a new workflow.
- Add a Webhook node as the trigger.
- Set Method to POST and note the Production URL (e.g.,
https://your-n8n.instance/webhook/tagoio-alert). - Activate the node.
Step 2: Configure a TagoIO Action to call the webhook
- In TagoIO, go to Actions → Add Action.
- Choose your trigger (e.g., Variable value condition:
temperature > 35). - Set the action type to HTTP Request.
- Set the URL to your n8n webhook URL.
- Set the method to POST and add a JSON body with the relevant context:
{
"device_id": "$DEVICE_ID$",
"variable": "$VARIABLE$",
"value": "$VALUE$",
"timestamp": "$TIMESTAMP$"
}- Save the Action.
Now every time the condition is met in TagoIO, n8n receives the event and your workflow runs.
Actions docs: docs.tago.io/docs/tagoio/actions
Pattern 2: n8n polls TagoIO API for device data
For batch processing or reporting, use n8n to schedule a periodic API call to TagoIO and process the results.
Fetch the latest data from a TagoIO device
In n8n, add an HTTP Request node:
- Method: GET
- URL:
https://api.tago.io/data?variable=temperature&qty=100 - Headers:
Authorization:YOUR_PROFILE_TOKENContent-Type:application/json
TagoIO API documentation: docs.tago.io/docs/tagoio/api
The response is a JSON array of data points. Pipe the result to downstream n8n nodes: filter, transform, write to Google Sheets, create a Jira ticket, or post to Slack.
Example: Daily energy report to Google Sheets
- Schedule Trigger (runs every day at 6 AM)
- HTTP Request → TagoIO API, fetch last 24 hours of energy readings
- Code node → aggregate kWh totals per device
- Google Sheets → append row with date, device, and total consumption
This replaces a manual reporting task with a fully automated daily digest.
Pattern 3: Write computed data back to TagoIO from n8n
n8n workflows can process data from external sources and push results back into TagoIO device buckets, enriching your IoT data with business context.
POST data to a TagoIO device
Use an HTTP Request node in n8n:
- Method: POST
- URL:
https://api.tago.io/data - Headers:
Device-Token: YOUR_DEVICE_TOKEN - Body (JSON):
[
{"variable": "work_order_open", "value": 1},
{"variable": "maintenance_due", "value": "2026-06-15"}
]This pattern is useful when you want TagoIO dashboards to reflect data from your ERP, CMMS, or ticketing system alongside live sensor readings.
Sending data docs: docs.tago.io/docs/tagoio/devices/sending-data
Pattern 4: Bidirectional sync: TagoIO Analysis + n8n
For advanced scenarios, you can trigger n8n workflows from TagoIO Analysis scripts (serverless JavaScript that runs in the cloud):
// TagoIO Analysis script
const axios = require("axios");
const N8N_WEBHOOK_URL = "https://your-n8n.instance/webhook/analysis-trigger";
await axios.post(N8N_WEBHOOK_URL, {
event: "anomaly_detected",
device: "sensor-plant-floor-A",
details: "Vibration exceeded 4g threshold for 3 consecutive readings"
});Analysis docs: docs.tago.io/docs/tagoio/analysis
This lets complex TagoIO logic (anomaly detection, multi-variable correlations, fleet-wide aggregations) trigger cross-app workflows in n8n.
Real-world workflow examples
Maintenance ticket creation
Trigger: TagoIO Action fires when vibration sensor exceeds threshold. n8n Workflow: Creates a Jira issue with device ID, timestamp, sensor value, and link to the TagoIO dashboard. Result: Maintenance team receives a structured ticket automatically, no manual logging.
Shipment temperature breach notification
Trigger: TagoIO Action fires when temperature exceeds 8°C on a cold chain device. n8n Workflow: Looks up the shipment record in the CRM by device ID → Posts a Slack message to the logistics channel → Sends an email to the customer. Result: Full traceability and customer communication from a single IoT event.
Weekly executive dashboard email
Trigger: n8n Schedule (every Monday 8 AM). n8n Workflow: Polls TagoIO API for last 7 days of production data → Computes week-over-week trends → Generates a formatted HTML email → Sends via Gmail or SendGrid. Result: Executive team gets a weekly IoT summary without logging into TagoIO.
Taking it further with AI
Combine n8n, TagoIO, and Claude via TagoIO’s MCP server. Your TagoIO data is queryable in natural language, and n8n can orchestrate multi-step workflows that blend AI responses with IoT actions.
MCP docs: docs.tago.io/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration
Summary
n8n and TagoIO are complementary layers. TagoIO manages IoT data, devices, and first-level alerting. n8n handles the cross-app business workflows those events need to trigger. Connect them with webhooks (TagoIO → n8n) or scheduled API polling (n8n → TagoIO), and extend your IoT data into every business system your team already uses.
- TagoIO Actions: docs.tago.io/docs/tagoio/actions
- Sending Data: docs.tago.io/docs/tagoio/devices/sending-data
- Analysis Scripts: docs.tago.io/docs/tagoio/analysis
- TagoIO API reference: docs.tago.io/docs/tagoio/api
- MCP: docs.tago.io/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration
