How to connect The Things Network sensors to Infodeck

Forward readings from an existing The Things Network application to Infodeck using a custom webhook in The Things Stack console.

Quick summary: Create the Infodeck connector, add a JSON webhook to your application, register each sensor as an asset and verify a new reading.

Before you begin

You need:

• Permission to view, create and update integrations, register assets and use the relevant locations and Asset Types.
• Access to manage your provider application's webhooks and API keys.
• Your application's cluster address, Application ID and an application API key. Commands require permission to write downlink traffic.
• A sensor already registered and transmitting on the network, with its DevEUI available.
• An IoT Asset Type with the correct decoder and measurement fields for the sensor model.

Start with one sensor. Creating a connector does not automatically copy the provider's device list into Infodeck.

1. Create the Infodeck connector

1. Open Settings → Integrations.
2. Click Add connector, select IoT networks, then choose The Things Network.
3. Enter a Connector name, such as Building sensors, and an optional Description.
4. Click Create and continue.
5. In Cluster address, enter your application's HTTPS cluster base address. Use the address for your actual deployment, not a console page or Infodeck's webhook address.
6. In Access token, paste the provider's application API key. Enter the Application ID and the Webhook ID you will use for the custom webhook below.
7. Click Save changes.

Two directions, separate credentials

Access token is the provider credential used for outbound access, including commands. Authorization under Provider webhook belongs to Infodeck and authenticates incoming readings. The editor requires the provider fields to complete setup, but those fields do not create the remote webhook.

2. Create the provider webhook

1. In Infodeck, open the connector and click Edit connector. Under Provider webhook, use Copy webhook URL and Copy authorization.
2. In The Things Stack console, open your application and choose Integrations → Webhooks → Add Webhook → Custom webhook.
3. Set Webhook ID to the same value entered in Infodeck and choose JSON for Webhook format.
4. Set Base URL to the complete copied Infodeck Webhook URL.
5. Add an additional header named Authorization with the complete copied authorization value. Do not add another prefix or enable basic authentication for this connection.
6. Enable Uplink message and leave its path empty, so messages go directly to the Base URL. Leave other event types disabled for this destination.
7. Leave event-data filtering off, then click Add Webhook.

The provider appends each event path to the Base URL; an empty path uses the Base URL itself. See The Things Stack's webhook setup instructions.

Keep the full uplink message, including the device identity, receive time and raw sensor data. Sending only decoded measurements or filtering out these fields prevents this connector from processing readings.

The provider's Downlink API key webhook field is not where you paste Infodeck's authorization. Infodeck uses the provider key saved in Access token for its supported commands. Keep both credentials confidential.

3. Register the sensor in Infodeck

1. Open Assets and click Register Asset.
2. Select the sensor's IoT Asset Type and enter an Asset Name, such as Store room temperature sensor.
3. Set Integration Service to your The Things Network connector.
4. In Device UUID, enter the sensor's DevEUI: 16 hexadecimal characters, without spaces or separators. Preserve leading zeros.
5. Select its Location, complete any other required fields and click Register Asset.

Use the DevEUI in Device UUID, not the provider's text Device ID, Application ID or JoinEUI. The selected Asset Type must decode the sensor's actual message format.

Field reference

Field	Required	What to enter
Connector name	Yes	A recognizable label, up to 256 characters.
Description	No	Helpful context, up to 1,000 characters.
Cluster address	Yes for connector setup	The provider's HTTPS cluster base address.
Access token	Yes for connector setup	The application API key; downlink commands need the appropriate write permission.
Webhook ID	Yes for connector setup	The ID of the custom webhook in that application.
Application ID	Yes for connector setup	The provider application's ID, not its display name.
Webhook URL	Copy only	Infodeck's receiving address, used as the provider Base URL.
Authorization	Copy only	Infodeck's incoming-request credential for the additional header.
Asset Type	Yes	An IoT type with the appropriate sensor decoder.
Asset Name	Yes	A name that identifies this sensor.
Integration Service	Yes	Your The Things Network connector.
Device UUID	Yes	The sensor's DevEUI.
Location	Yes	Where the sensor is installed.
Active Timeout (minutes)	No	Reporting interval allowance, if used by your installation.

4. Confirm a real reading

1. Wait for the sensor's next transmission or use its normal test function.
2. Confirm the provider application shows the new uplink and check webhook delivery.
3. In Infodeck, open the asset and check IoT Status → Last Uplink.
4. Confirm the time advances, then check Reading history, current values and units.

A successful webhook response does not prove that measurements were stored. Complete this check on one real sensor before registering the rest of the application.

If you also need commands

Receiving readings matches the DevEUI. The current command connection additionally expects the provider's Device ID to use eui- followed by the lowercase DevEUI. If your device uses a different Device ID, contact Support to check command compatibility; do not rename or recreate working devices just to test a command.

Confirm the provider key's downlink permissions and the sensor's supported actions. The provider explains these permissions in its downlink scheduling guide.

Correct a mistake later

Open Settings → Integrations → your connector → Edit connector, update the fields and click Save changes. Leaving an already stored access token's masked field blank preserves it; paste a new token to replace it.

Correct webhook URLs, headers, event paths and event filters in the provider console. Infodeck does not update those remote settings when you save the connector.

Troubleshooting

What you see	What to check
Complete connector setup is still shown	Fill in Cluster address, Access token, Webhook ID and Application ID, then save.
Webhook authorization fails	Copy Infodeck authorization again and put it in the additional header, not Access token or Downlink API key.
Webhook destination is not found	Use the full copied URL as Base URL and leave the Uplink message path empty.
Delivery succeeds but readings are missing	Disable event-data filtering, retain raw sensor data, and match the asset's DevEUI and connector.
Measurements are missing or wrong	Check the sensor model, Asset Type decoder, message format and expected units.
Readings work but commands fail	Check Device ID compatibility, cluster, application, webhook and downlink permissions with Support.

Example: store room temperature

Create Building sensors, add a JSON webhook to the sensor's application and register Store room temperature sensor with its matching IoT Asset Type. Enter the DevEUI in Device UUID and choose the store room location. Check the next temperature reading and timestamp before adding more sensors.

Related guides

• Register an asset
• Asset Types
• Sensor data
• Integrations & Connectors

Need help with a decoder or command compatibility? Contact Infodeck Support.