Skip to content

Overview

Integrations send your application's device events (uplinks, joins, acknowledgements, status, logs and more) to your own systems. Each one is configured per application.

  • MQTT

    Subscribe to events and publish downlinks on ChirpCloud's MQTT broker.

    MQTT

  • HTTP

    ChirpStack POSTs every event to your endpoint.

    HTTP

  • Other integrations

    InfluxDB, ThingsBoard, myDevices, Pilot Things, Blynk, IFTTT, AWS SNS, Azure Service Bus and GCP Pub/Sub.

    Other integrations

How integrations work on ChirpCloud

MQTT credentials come from the portal. Every other integration is set up in the native UI under the application's Integrations tab. You manage them yourself; only you can see or change your application's integrations.

  • Endpoints must be on the public internet. Private, local, link-local and ChirpCloud's own internal addresses are unreachable, also through redirects or DNS names that point there. Our own public hostnames are reachable like any other site.
  • The URLs, tokens and keys you enter are stored in ChirpStack. Put credentials in header or key fields rather than in the URL.
  • Each delivery attempt times out after 5 seconds; failed deliveries are not retried.
  • Integrations send your data to the destination you choose, under your responsibility (DPA 3.1 and 6.1).
  • They are kept while your workspace is restricted (devices are disabled, so nothing is sent), deleted with your workspace, and not copied in a dedicated migration.