Integrations
An integration is a configured connection to another system. Everything the Center talks to — in either direction — is one.
Direction decides everything
When you create an integration you pick a direction, and it cannot be meaningfully changed afterwards because it determines what the integration is.
Providers and adapters
The provider is the concrete system type: SIGFOX, CHIRPSTACK, TTN,
UNA_SU, HTTP, or GENERIC.
Each provider has an adapter — the part of the Center that knows that system's dialect. For a source, the adapter authenticates incoming payloads and translates them into the Center's internal shape. For a sink, it knows how to authenticate outbound and what a successful delivery looks like.
This is why adding a device network is configuration rather than development: the adapter already exists, and everything past normalisation is provider-agnostic.
GENERIC, which accepts
a plain payload. You lose provider-specific niceties like automatic message-type
handling, but you are not blocked waiting for an adapter.Credentials are separate
An integration does not store an API user and password directly. It references a credential held at tenant level.
That separation is deliberate:
- One Sigfox credential serves every integration that needs it. Rotating the password is one edit, not twenty.
- Secrets are encrypted at rest and never returned once saved.
- Credentials can be scoped — tenant-wide by default, or overridden for a single project.
See Provider credentials.
Transports
Not every source is a webhook. An integration's transport can be:
- HTTP — the network POSTs to your ingest endpoint. The common case.
- MQTT — the Center subscribes to a broker topic.
- TCP / CoAP — the Center listens on a port for incoming frames.
HTTP sources accept JSON, XML or plain text, so a backend that posts XML needs no translation layer in front of it.
Testing a connection
Sinks have a Test button that attempts a real connection with the stored
settings and reports Connection OK or Connection failed.
Use it. Finding a wrong URL or an expired token now is far cheaper than discovering it from a queue of dead-lettered deliveries later.
Global integrations
An integration is normally scoped to a project. A platform-level tenant can also create global integrations, available across tenants as templates. These are excluded from ordinary project fan-out — they exist to be copied, not to receive your traffic.