@loewencreville/n8n-nodes-ttn

Community n8n nodes for The Things Stack (TTS) — also known as The Things Network (TTN) on the public cloud.

Connect your LoRaWAN applications to n8n workflows: receive real-time uplinks via webhooks, read stored messages, send downlinks, and monitor devices and gateways through the TTS API.

Table of contents

• Installation
• Credentials
• Nodes
  • TTN (main node)
  • TTN Trigger (webhook)
• Usage examples
• Compatibility
• Development
• Resources
• Version history
• License

Installation

Follow the n8n community nodes installation guide.

npm package: @loewencreville/n8n-nodes-ttn

# In n8n: Settings → Community Nodes → Install → enter "@loewencreville/n8n-nodes-ttn"

For self-hosted n8n with a custom nodes folder (Docker volume, etc.):

git clone https://github.com/etoilary974-ship-it/n8n-nodes-ttn.git
cd n8n-nodes-ttn
npm install
npm run build
# Copy dist/ + package.json to your n8n custom nodes directory, then restart n8n.
# Or use: npm run deploy

Credentials

The Things Stack API (ttnApi)

Create an API key in the TTS console: User settings → API keys, or per application under API keys. See the official guides:

• API authentication
• API key rights

Required rights by operation:

The credential test calls GET /api/v3/applications to verify connectivity.

Storage vs webhooks: Storage reads historical uplinks from the TTS database. Webhooks push events to n8n in real time. Enable Storage on your application in TTS if you use Get Last Uplink.

Nodes

All TTN nodes share the same icon and appear grouped in the n8n node picker under TTN.

TTN (main node)

Unified action node with three resources.

Data

Get Last Uplink options:

• Storage scope — single device or whole application.
• Last window — same duration format as the TTS console (1h, 24h, 168h, …). See Storage API.
• Uplink output shape — Decoded Payload + Meta, Decoded Payload only, or Full Storage record.

Devices

Downlink parameters match The Things Stack downlink fields:

• FPort (1–223)
• Payload type — Hex (frm_payload, base64-encoded by the node) or JSON (decoded_payload)
• Priority — LOWEST … HIGHEST
• Confirmed downlink — requires device ACK

Gateways

Dynamic dropdowns (applications, devices, gateways) support n8n expressions for dynamic IDs.

API errors from TTS are mapped to readable messages with gRPC codes and suggested actions.

TTN Trigger (webhook)

Pick TTN → Triggers → Webhook · Receive Events in the node picker.

Receives real-time POST webhooks from TTS — the recommended way to react to uplinks and other events. HTTP method is fixed to POST.

TTS console setup

1. Open your application in TTS Console.
2. Go to Integrations → Webhooks.
3. Set Base URL to your n8n webhook URL (test or production).
4. Format: JSON. Method: POST.
5. Under Enabled event types, check the events you need (e.g. Uplink message).

Full guide: TTS Webhooks integration

Node parameters

Credentials are optional on the trigger (only needed for the application/device filter dropdowns).

Usage examples

Real-time sensor data (webhook)

TTN Trigger (Webhook · Receive Events)
  → Event type: Uplink message
  → Output format: Sensor Data
  → [your logic: Slack, database, etc.]

Output shape (Sensor Data):

{
  "device_id": "my-sensor",
  "application_id": "my-app",
  "received_at": "2026-06-07T12:00:00.000Z",
  "f_port": 1,
  "data": { "temperature": 22.5, "humidity": 60 }
}

Send a downlink command

TTN → Devices → Send Downlink
  → Application: my-app
  → Device: my-sensor
  → FPort: 10
  → Payload type: Hex
  → Payload: 0102FF

See Scheduling downlinks in the TTS docs.

Read recent uplinks from Storage

TTN → Data → Get Last Uplink
  → Storage scope: One Device
  → Last window: Last 12 Hours
  → Uplink output shape: Decoded Payload + Meta

Requires Storage integration enabled on the application.

Monitor device connectivity

TTN → Data → Get Device Status
  → Status mode: Summary
  → Offline threshold: 24 hours

Check gateway health

TTN → Gateways → Get Gateway Status
  → Gateway IDs: [your-gateway]
  → Status mode: Detailed

Compatibility

No runtime npm dependencies — only n8n-workflow as a peer dependency.

Development

npm install
npm run dev      # Start n8n with hot reload
npm run lint     # ESLint (n8n node rules)
npm run build    # Compile to dist/
npm run deploy   # Build + copy to custom n8n folder
npm run release  # Lint, build, version bump, tag — triggers publish.yml on push

Requires Node.js 22+. See n8n node development.

Publishing: configure an npm Trusted Publisher on the package (owner etoilary974-ship-it, repo n8n-nodes-ttn, workflow publish.yml), then run npm run release. The GitHub Actions workflow publishes to npm with provenance (required for n8n community verification since May 2026).

Resources

n8n

• Community nodes documentation
• Install community nodes
• Building custom nodes

The Things Stack / TTN

• The Things Stack documentation
• TTS Console (public cloud)
• API authentication
• Webhooks integration
• Storage integration
• Application Server API (devices, downlinks)
• Gateway Server API
• LoRaWAN concepts

This project

• npm package
• GitHub repository
• Changelog
• Report an issue

Version history

See CHANGELOG.md for the full release history.

License

MIT — Copyright Loewen Creville