Integrations Overview

Connect external systems to Autoconnecto — first-class Integrations in the sidebar (not Tenant Settings).

Where to go

Open Integrations (/integrations).

Supported sources:

• ChirpStack (HTTP webhook)
• The Things Stack / TTN (HTTP webhook)
• MQTT broker bridge (platform subscribes to your broker)
• Generic HTTP

Typical flow

1. Create / match devices (lorawan.dev_eui or auto-create).
2. New integration → choose source → device matching → connect.
3. Start the integration and confirm Recent events.

Recipes

• ChirpStack
• The Things Stack / TTN
• MQTT broker bridge
• Generic HTTP

Runnable examples

In the app: Integrations shows Examples & recipes (sample JSON + links).

In the device SDK repo (autoconnecto-sdk):

Example	Path
Generic webhook (curl / PowerShell / Python)	examples/integrations/generic-webhook.*
ChirpStack uplink dry-run	examples/integrations/chirpstack-webhook.sh
TTN uplink dry-run	examples/integrations/ttn-webhook.sh
Gateway relay (childDeviceId)	examples/integrations/gateway-relay-webhook.sh + examples/GatewayRelay_http
Modbus / OPC-UA / MQTT bridge (Linux)	examples/integrations/modbus-gateway, opcua-gateway, mqtt-bridge

Copy examples/integrations/env.example, then run a script against your tenant secret and device token.

Gateways (Solutions)

Inbound Integrations are for ChirpStack / TTN / HTTP / MQTT bridges. Industrial Modbus + cellular DTU stacks are under Solutions:

• Connectivity profiles (P1–P6, including gateway MQTT_SERIAL and hub relay P5)
• EnergyFleet / ClimateFleet — bench-tested P1 gateway paths

Transforms

Prefer a Rule Engine on the device profile for rename / filter / notify / webhook / downlink logic after the integration has matched a device.

Legacy per-integration pipeline/script transforms may still appear in older configs; new work should use Rule Engines.

Downlink

ChirpStack / TTN: configure API credentials on the integration, or use Rule Engine node integration_downlink to queue downlinks from telemetry / attribute flows.