---
title: Routing Data to Cloud
description: Learn how to connect Blues Notecard applications to third-party cloud services using Notehub Routes and Cellular, Satellite, LoRa, or WiFi connectivity.
source_url: https://dev.blues.io/guides-and-tutorials/routing-data-to-cloud/qubitro/
canonical_url: https://dev.blues.io/guides-and-tutorials/routing-data-to-cloud/qubitro/
markdown_url: https://dev.blues.io/guides-and-tutorials/routing-data-to-cloud/qubitro.md
---

# Routing Data to Cloud: Qubitro

#### Watch a video of this tutorial

[Video: quickstart-step-4.1280w.20260521.mp4](https://dev.blues.io/_media/quickstart-step-4.1280w.20260521.mp4)

In previous tutorials you've learned about the Blues Notecard, and used it to collect data and send it to Notehub, the Blues cloud service.

One powerful feature of Notehub is routes, which allow you to forward your data from Notehub to a public cloud like AWS, Azure, or Google Cloud, to a data cloud like Snowflake, to dashboarding services like Datacake or Ubidots, or to a custom HTTP or MQTT-based endpoint. The tutorial below guides you through sending data to several popular services, and teaches you how to build visualizations using that data.

*Don't see a cloud or backend that you need? Notehub is able to route data to virtually any provider. If you're having trouble setting up a route, [reach out in our forum](https://discuss.blues.com/) and we will help you out.*

## Introduction

*This tutorial should take approximately 30-40 minutes to complete.*

In this tutorial, you'll learn how to connect your Notecard-powered app to **Qubitro**, and learn how to start creating simple visualizations with sensor data.

This tutorial assumes you've already completed the initial [Sensor Tutorial](https://dev.blues.io/guides-and-tutorials/collecting-sensor-data.md) to capture sensor data, saved it in a [Notefile](https://dev.blues.io/api-reference/glossary.md#notefile) called `sensors.qo`, and sent that data through the Notecard to Notehub (or that you've already created your own app with sensor data and are ready to connect your app to external services).

## Create a Route

A Route is an external API, or server location, where Notes can be forwarded upon receipt.

Routes are defined in Notehub for a [Project](https://dev.blues.io/api-reference/glossary.md#project) and can target Notes from one or more [Fleets](https://dev.blues.io/api-reference/glossary.md#fleet) or all [Devices](https://dev.blues.io/api-reference/glossary.md#device). A Project can have multiple routes defined and active at any one time.

Before you create a Route, ensure the data you want to route is available in Notehub by navigating to the **Events** view:

![events view in notehub](https://dev.blues.io/images/guides/route-tutorial/events-view.png?v=e1b03b17)

We'll start with a simple route that will pass Notecard events through to [webhook.site](https://webhook.site), where you can view the full payload sent by Notehub. Using this service is a useful way to debug routes, add a simple health-check endpoint to your app, and familiarize yourself with Notehub's Routing capabilities.

1. Navigate to [webhook.site](https://webhook.site). When the page loads, you'll be presented with a unique URL that you can use as a Route destination. Copy that URL for the next step.

   ![webhook.site service](https://dev.blues.io/images/guides/route-tutorial/webhook-site-url.png?v=5ed567fe)

2. Navigate to the [Notehub.io](https://notehub.io) project for which you want to create a route and click on the Routes menu item in the left nav.

3. Click **Create Route**.

   ![create a route button in notehub](https://dev.blues.io/images/guides/route-tutorial/add-route.png?v=4724c860)

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

   ![general https request route](https://dev.blues.io/images/guides/route-tutorial/general-route.png?v=b3b8e6a5)

5. Give the route a name (for example, "Health").

   ![name notehub route](https://dev.blues.io/images/guides/route-tutorial/route-name.png?v=9aa60fa8)

6. For the Route **URL**, use the unique URL you obtained from webhook.site.

   ![url for notehub route](https://dev.blues.io/images/guides/route-tutorial/route-url.png?v=449917f5)

7. In the **Filters** section, choose **Selected Notefiles** and check the box(es) next to the Notefile(s) you want to route. For example, we used `sensors.qo` for the sensor tutorial.

   ![choose the notefile to sync](https://dev.blues.io/images/guides/route-tutorial/sensors-qo.png?v=b347af44)

8. Make sure the **Enabled** switch at the top remains selected, and click **Create Route**.

9. Only Notes received *after* the Route is created are routed automatically. If new Notes have been received since you created the Route, proceed to the next step.

   Alternatively, you can **manually route** existing Notes by (1) checking the box next to an event, (2) clicking the **Route** button, and (3) choosing the Route you would like to use:

   ![manually route notes](https://dev.blues.io/images/guides/route-tutorial/manual-route.png?v=904af97c)

10. Return to webhook.site. This page will update automatically with data sent from Notehub. The data from your sensor is contained within the `body` attribute. Notice that Notehub provides you with a lot of information, by default. In the next section, we'll look at using transformations to customize what Notehub sends in a Route.

    ![notehub data in webhook.site](https://dev.blues.io/images/guides/route-tutorial/webhook-site-data.png?v=83ed5ec7)

## Use JSONata to Transform JSON

Before moving on to routing data to an external service, let's briefly explore using JSONata expressions to transform the data Notehub routes.

As mentioned above, Notehub provides a lot of information in each Route request. You may want to trim down what you send to the external service, or you might need to transform the payload to adhere to a format expected by that service. Either way, Notehub supports shaping the data sent to a Route using JSONata.

> **Note:**
>
> To learn more about JSONata later, have a look at the [Blues JSONata Guide](https://dev.blues.io/guides-and-tutorials/notecard-guides/using-jsonata-to-transform-json.md).

### Transform Your Data

Let's try a simple query to the webhook.site Route created in the last section.

1. Navigate to the **Routes** page in Notehub and click on the Route you wish to edit.

   ![view a route](https://dev.blues.io/images/guides/route-tutorial/routes-screen.png?v=0a7ebd91)

2. In the **Transform Data** drop-down, select **JSONata Expression**.

   ![jsonata expression](https://dev.blues.io/images/guides/route-tutorial/jsonata-expression.png?v=98cabc60)

3. In the JSONata Expression text area, add the following query to select the `temp` and `humidity` from the `body`, create a `location` field that concatenates the `tower_location` and `tower_country` fields, and create a `time` field.

   ```json
   {
      "temp": body.temp,
      "humidity": body.humidity,
      "location": tower_location & ', ' & tower_country,
      "time": when
   }
   ```

4. Click **Apply changes**. Then, navigate back to webhook.site. As requests come in, you'll see your custom, JSONata-transformed payload in the Raw Content section.

   ![transformed data routed to webhook.site](https://dev.blues.io/images/guides/route-tutorial/webhook-site-jsonata.png?v=e69aa638)

   > **Note:**
   >
   > The `tower_location` and `tower_country` fields are only populated for events sent over cellular. For Starnote/satellite, LoRa or WiFi devices, those fields will be empty. If you want a single expression that works across connectivity types, use the `best_location` and `best_country` fields instead — Notehub appends those to every event, choosing the most accurate source available (GPS/GNSS, triangulation, or cell tower). See [Data Notehub Appends to Events](https://dev.blues.io/notehub/notehub-walkthrough.md#data-notehub-appends-to-events) to learn more.

JSONata is simple, powerful, and flexible, and will come in handy as you create Routes for your external services. To explore JSONata further, [visit our Blues JSONata Guide](https://dev.blues.io/guides-and-tutorials/notecard-guides/using-jsonata-to-transform-json.md).

## Route to an External Service

Now that you've created your first Route and learned how to use JSONata to shape the data sent by a Route, you can connect Notehub to an external service.

In this section of the tutorial, you'll connect your app to [Qubitro](https://www.qubitro.com/), a no-code/low-code device data platform that enables companies of any size to instantly connect, manage, process, and analyze IoT device data.

### Create a Qubitro Account

If you haven't already, [create your free Qubitro account](https://portal.qubitro.com/signup). The default (free) tier allows you to add two devices (e.g. Notecards).

![create a qubitro account](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-signup.png?v=1ff3765a)

### Create a New Qubitro Project

After logging in, you'll be redirected to your personal dashboard. From here, you'll be able to add and edit projects, manage devices, update settings, and create dynamic data dashboards.

Let's start by creating a new project!

1. Click the **New Project** button.

   ![create a qubitro project](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-new-project.png?v=8ec6ffe8)

2. Provide a **name** for the project, along with at least one identifying **tag**, and a short **description** of the project.

3. After the project is created, click to open it, and click the **New Source** button.

4. Click the **Notehub** tile. On this screen, you'll be provided with unique identifiers for your project which you'll use to configure your Notehub Route. **Leave this tab open for now.**

   ![create a new source in qubitro](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-new-source.png?v=165678c9)

The next step is to create a Route in Notehub to securely transmit new events to this Qubitro project.

### Create a Route in Notehub

1. Back in Notehub, navigate to the **Routes** menu option and click the **Create Route** button.

   ![create a notehub route](https://dev.blues.io/images/guides/route-tutorial/qubitro/create-route.png?v=443878a4)

2. Scroll until you see the **Qubitro** route type and click the **Select** button.

   ![create a qubitro route](https://dev.blues.io/images/guides/route-tutorial/qubitro/create-qubitro-route.png?v=8ead1a14)

3. Provide a **name** for your route. Then, back in your Qubitro project, copy the provided `projectId` and `webhookSigningKey` values. Paste them in the relevant fields provided in your Notehub Route settings.

   ![qubitro projectid and webhooksigningkey](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-proj-webhook.png?v=a504119c)

4. Under the **Filters** section, choose to only sync the `sensors.qo` Notefile, and select **Body Only** from the **Transform Data** dropdown. *You can certainly experiment with other transformations (like JSONata expressions) after completing this tutorial.*

   ![complete notehub route configuration](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-notehub-config.png?v=61e8e3de)

5. When you're done configuring your Notehub Route, click the **Apply Changes** button to save the Route.

### View Sensor Data in Qubitro

1. Back in Qubitro, click the **Go to project** button to return to your project dashboard.

2. Assuming sensor data is still being sent from your Notecard to Notehub in the `sensors.qo` Notefile, you should see your Notecard device appear in Qubitro.

   If no devices appear in the table, add additional Notes to your `sensors.qo` Notefile on your Notecard. Sync the data with Notehub and then click the provided **Refresh** button in the Qubitro device table. Your device should then appear. If you still don't see any devices or data, check the **Logs** tab of your Notehub Route.

   ![view notecard device in qubitro project](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-device.png?v=36906b95)

3. Click on the device and navigate to the **Storage** tab. On this page you'll see all of the raw data previously routed from Notehub to Qubitro.

   ![view data storage in qubitro](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-storage.png?v=e707d8bd)

As new sensor readings are delivered to Notehub, they will be actively routed to your Qubitro project. Your next step is to create a data dashboard using the web-based interface provided by Qubitro.

> **Note:**
>
> Remember, if you don't have any new Notes coming in to Notehub, you can always **manually route** existing Notes by (1) checking the box next to an event, (2) clicking the **Route** button, and (3) choosing the Route you would like to use.

> **Tip:**
>
> To debug a route or inspect the exact request Notehub sends to your third-party service, open an event in Notehub, click **Route as cURL**, and choose the appropriate HTTP-based route. The modal shows a cURL command that reproduces the same request Notehub makes, with secrets (API keys, passwords, etc.) replaced by placeholders.
>
> ![view curl request from route](https://dev.blues.io/images/guides/route-tutorial/event-route-curl.png?v=22e6a261)

## Build Data Visualizations

1. Navigate to the **Dashboard** tab of your Qubitro project and click on the **Go to Dashboards** link.

   ![qubitro go to dashboard](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-go-dashboard.png?v=cf823bbf)

2. From the provided dropdown menu, choose to create a new **Blank dashboard**.

   ![qubitro create blank dashboard](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-blank-dashboard.png?v=8a3c308e)

3. Open the provided blank dashboard, click the toggle to **Edit**, and create your first dashboard widget by clicking the **New Widget** button.

   ![qubitro create new widget](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-new-widget.png?v=598a48b0)

4. Choose a widget type of **Chart**, add a title to your widget (e.g. "Temperature"), and then click the **Add point** button.

   ![qubitro widget settings](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-temp.png?v=a57f7fa7)

5. When the **Connect Data Point** modal opens, select your **project**, **device** (your Notecard), and the **data point** you would like this chart to display (e.g. `temp`).

   ![qubitro add data point](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-data-point.png?v=825e27c5)

6. Click to **Save** the data point and then **Save Widget** to save changes made to your widget.

7. Repeat the above process to add another widget for your `humidity` data.

8. When done adding widgets, be sure to click the **Save Changes** button on your dashboard **BEFORE** toggling back to view your dashboard. (Otherwise you may lose the changes made to your widgets!)

9. After your dashboard is saved, toggle back to the **View** option to see your live data visualizations.

   ![qubitro data dashboard](https://dev.blues.io/images/guides/route-tutorial/qubitro/qubitro-dashboard.png?v=539b9b2b)

Be sure to visit the [Qubitro documentation](https://docs.qubitro.com/) to discover additional capabilities of the Qubitro platform.

## Next Steps

**Congratulations!** You've created your first Route and connected your Notecard app to an external service. If you're following a Cell+WiFi Quickstart, you're done!

Now that you know the basics of how Notecard and Notehub work, you’re ready to apply what you’ve learned towards a real project. We have a few recommendations on what to do next:

- [**Learn Best Practices for Production Projects**](https://dev.blues.io/guides-and-tutorials/best-practices-for-production-ready-projects.md): This skimmable guide has a list of best practices for moving your project from a prototype to a real, production-ready deployment.

- [**Browse Example Apps**](https://dev.blues.io/example-apps.md): Our collection of IoT apps that show how to build common projects with Blues. These example apps include dozens of [official Blues project accelerators](https://dev.blues.io/example-apps/accelerators/) and a collection of [purpose-built sample apps](https://dev.blues.io/example-apps.md).

- [**Follow the Notehub Walkthrough**](https://dev.blues.io/notehub/notehub-walkthrough.md): Learn how to manage projects and device fleets, update Notecard and host firmware, set up alerts, securely route your data, and more.

At any time, if you find yourself stuck, please reach out on the [community forum](https://discuss.blues.com/).