Qubitro Documentation
SupportLog inSign Up
  • Documentation
  • Guides
  • Developers
  • Welcome
  • Data Sources
    • No-Code Integrations
      • Onomondo
      • Notehub
      • The Things Stack
      • Soracom
      • Loriot
      • 1NCE
      • Golioth
      • AWS IoT Core LoRaWAN
      • Actility ThingPark
      • Chirpstack
      • Particle
    • MQTT
    • HTTP
  • Platform
    • Project
      • Settings
      • Access Management
      • Roles & Permissions
    • Device
      • Settings
    • Storage
      • Time Series Storage
    • Functions
      • Decoder Function
        • LoRaWAN Device Template Decoder
        • LoRaWAN Custom Decoder
        • Hex Payload Decoder
      • Transformation Function
      • Rule Function
        • Send Email
        • Webhooks
        • Slack
        • Twilio
        • Mailgun
        • SendGrid
      • Storage Function
        • AWS Redshift
        • Google BigQuery
        • MQTT Publish
        • MongoDB Time Series
      • Scheduled Function
        • HTTP
      • Function Settings
      • Function Templates
        • Settings
    • Monitoring
      • Dashboards
        • Setup & Configuration
        • Widgets
          • Chart
          • State Timeline
          • Gauge
          • Stat
          • Headline
          • Aggregated Chart
          • Map
          • Battery
          • Image
          • Image Map
          • Table
          • Storage Table
          • Iframe
          • Blob Storage
        • Settings
        • Access Management
        • Roles & Permission
      • Blueprints
        • Setup & Configuration
        • Settings
    • Credentials
      • API Keys
      • External Credentials
        • Slack
        • Mailgun
        • SendGrid
        • Twilio
        • AWS Redshift
        • MQTT
        • MongoDB
        • The Things Stack
      • Webhook Signing Key
  • Add-Ons
    • Storage Views
    • Aggregated View
    • Archived Views
    • Blob Storage
    • Managed Email
    • Audit Log
    • MCP Server
  • Organizations
    • Overview
    • General
    • Groups
    • Members & Roles
      • Read Only
      • Read/Write
      • Admin
    • Custom Roles
    • Add-Ons
    • Billing
    • Invoices
    • White-Label
  • Account Management
    • Personal Accounts
Powered by GitBook
On this page
  • Overview
  • Prerequisites
  • How It Works
  • Configuring the Integration
  • Frequently Asked Questions
Export as PDF
  1. Data Sources
  2. No-Code Integrations

Notehub

The Qubitro and Blues Notehub integration allows you to sync all devices and their data from Notehub.

PreviousOnomondoNextThe Things Stack

Last updated 2 months ago

Overview

The Qubitro and Notehub—Blues cloud service integration allows you to sync all devices and their data from Notehub to Qubitro using —without writing any code.

Once your hardware is configured and sending data to Notehub, a corresponding device is automatically created in Qubitro, representing each device with its unique Notecard ID.

Qubitro decodes incoming data automatically, and transformation functions can be applied if modifications are needed before storage.

This integration does not require manual MQTT or HTTP forwarding from your device. Data flows directly between Notehub and Qubitro with no additional setup required on the device side.

Prerequisites

How It Works

Below is the diagram that shows how the integration works.

If a is enabled, data will be processed before storage. The built-in decoder applies first, and then any defined transformation function modifies the data before it is stored in Qubitro.

Configuring the Integration

1

Step 1: Create an Integration in Qubitro

  1. Log in to the Qubitro Portal.

  2. Select a project from the list.

  3. Click New Source.

  4. Select Notehub from the available sources.

This page will display the Host URL and required headers for Notehub configuration. Keep it open for the next step.

2

Step 2: Set Up a Route in Notehub

  1. Log in to Notehub.

  2. Open your Notehub project.

  3. Click + Create Route.

  4. Select General HTTP/HTTPS Request/Response as the route type.

  5. Paste the Host URL copied from Qubitro into the Route URL field.

  6. Add the headers from Qubitro to the corresponding fields.

3

Step 3: Configure Data Routing

  1. Choose Fleet (optional) – If you have multiple fleets, select the appropriate one.

  2. Choose Notefile – Select the Notefile you want to forward.

  3. Choose Body Only in the Data section.

  4. Click Save to create the route.

4

Step 4: Verify the Integration

  1. Return to Qubitro Portal.

  2. Click Go to Project and then Refresh to check if the devices appear.

  3. Open a device and navigate to the Data tab to verify incoming data.

Frequently Asked Questions

Do I need to set up MQTT or HTTP forwarding in Notehub?

No. The integration works directly between Notehub and Qubitro using Notehub Routes. No additional forwarding setup is needed.

Do I need to send data from my device to Qubitro?

No. Once data is sent to Notehub, it is automatically forwarded to Qubitro via the Notehub Route.

Can I group Notecards under different Qubitro projects?

Yes. You can create multiple integrations to separate Notecards across different projects.

Are there additional fees for this integration?

No. There are no hidden costs such as data transfer (egress) fees for using the Qubitro <> Blues Notehub integration.

Notehub Routes
Transformation Function