Quickstart
The shortest path from an empty Center to a message landing in your system. Roughly fifteen minutes, and every step has a longer guide behind it if you get stuck.
1. Sign in and pick your tenant
Sign in, then check the active tenant in the sidebar. Everything you create belongs to whichever tenant is active — projects, devices, credentials, all of it. If you can reach more than one, get this right before you start; moving things afterwards is more work than picking correctly now.
2. Create a project
Projects → New project. A project is the box everything else lives in: devices, integrations, routes and rules are all scoped to one.
Use one project per deployment, not per customer. A water utility rolling out meters in two cities is two projects; the same utility's twenty apartment blocks are one.
3. Create a source
Integrations → New integration, direction Source (left), and pick your
provider.
Save it, then copy its webhook URL from the list. That is the address the device network will POST to. Paste it into your network's callback configuration — for Sigfox, on the device type's callbacks.
Nothing arrives yet, and that is expected. See Connect a source for the endpoint variants, shared secrets and required headers.
4. Create a sink
Integrations → New integration, direction Sink (right).
For a plain HTTP destination you need the endpoint URL and whatever it
authenticates with. Hit Test — it reports Connection OK or
Connection failed immediately, which is much easier to debug now than after a
message is in flight.
5. Add your device
Devices → New device, choose your project, then Add technology and fill in the identifiers that network uses:
| Network | What it needs |
|---|---|
| Sigfox | Device ID, PAC, device type ID |
| LoRaWAN | DevEUI, and AppKey if you are provisioning |
The identifier is how an incoming message gets matched to this device, so it has to match the network's records exactly.
6. Send a message
Trigger an uplink — press the device's button, wait for its next scheduled report, or use your network's test/simulate function.
Then open Flow and pick your project. With no routes configured yet, every source delivers to every active sink, so your message should already have gone out. Check your destination.
Received is still zero, the problem is upstream (callback URL, secret, or
the device itself). If it received but did not deliver, look in Dead
letters. When delivery fails covers both.7. Decide what the sink receives
By default your sink gets the full message — envelope, payload and the raw provider frame. That is the right default, but it is rarely the final answer.
Open Flow → Routing, pick your source → sink pair, and choose a shape. The dialog previews it with your own field names and last-seen values. Choose what the sink receives explains all five.
8. Decode the payload
Right now the payload is still raw bytes. To turn 00018d46… into
index: 18.061, create a decoder and attach it to a device profile, then
put your device on that profile.
See Decode the payload.