Skip to main content
All CollectionsUser Guides
Data Pipelines: User Guide
Data Pipelines: User Guide

Learn how to set up Data Pipelines on your Ubidots account.

Sergio M avatar
Written by Sergio M
Updated yesterday

Ubidots Data Pipelines enables you to efficiently centralize inbound data from your Ubidots account, allowing it to be consolidated in one location and forwarded to other Ubidots modules or external services. This can be utilized for various purposes, including:

Realtime backup

Data Pipelines can be used to quickly set up a backup for your devices. Suppose that you want to backup the data from a particular set of devices on Ubidots, for example, all the devices belonging to a particular device type. In this case, you can:

  1. Create a Data Pipeline, selecting as data source Device type.

  2. In the Destination tab, configure the webhook to send the data to the backup service that you are using.

In this way, whenever a device belonging to the required device type sends data, it will be captured by the pipeline and forwarded to the selected backup service.

Centralized data processing

Imagine you are a Time and Attendance Solutions Provider managing data for three distinct organizations:

  • NexGen Technologies

  • Pinnacle Dynamics

  • BrightFuture Corp

Currently, your service displays each worker's entrance time on separate dashboards for each organization. While this setup works well for viewing data in isolation, you now want to perform a comprehensive analysis that includes data from all three organizations in one centralized location. To achieve this, you need to aggregate data from all organizations into a single source for analysis.

One efficient solution would be to use Ubidots' Data Pipelines to streamline this process.

  1. Create a new Data Pipeline, select "Organization" as the data source, and choose the relevant organizations from the dropdown menu.

  2. In the Destination tab, configure the webhook to send the data to the service that you are using for the analysis.

In this way, whenever a device from any of the three organizations sends data, it will be captured by the pipeline and forwarded to the selected service.

Requirements

1. What Is "Data Pipelines"?

Data Pipelines is an Ubidots module that allows you to specify a data source, and whenever data is received from that source, you can automatically trigger an action using the incoming data.

Available data sources:

  • Device list

  • Organizations

  • Device type

  • Device group

  • Tags

Available actions:

  • Trigger webhook

  • [PLANNED] Trigger UbiFunction

2. How to use Data Pipelines

Go to your Ubidots account and click on Data Pipelines

Click the "+" button to create a new pipeline:

Select the your data source from the "source" dropdown menu and then click on the "next" button:

From the "destinations" tab, click on the "+ add destination" button and then on "trigger webhook":

On the pop-up screen, configure the following settings:

  • HTTP Method: The allowed method of the resource you are requesting.

  • URL: The URL of the resource you are requesting.

  • Headers: The required headers.

After that, click on the "save" button. Upon doing so, the pop-up will collapse, then click on "next".

From the settings tab, name the pipeline and, optionally, add a description. After that, click on the "save" button.

3. How Do Pipelines Work?

Whenever a device from the selected data source receives data, the webhook will be executed.

  • Device list: When a device from the selected list receives data, the action will take place.

  • Organizations: When a device from the selected organization receives data, the action will take place.

  • Device Type: When a device from the selected Device Type receives data, the action will take place.

  • Device Group: When a device from the selected Device Group receives data, the action will take place.

  • Device tag: When a device with a specified tag receives data, the action will take place.

When a device within the selected data source receives data, the webhook is triggered, and the pipeline forwards the data to it. This applies to all available data sources. For example, if you configure a pipeline and send the following payload to a device:

{
"temperature" : 10,
"humidity" : 55,
"metadata" : {
"SNR" 2
}
}

The webhook will receive this exact payload as its input.

Did this answer your question?