Connect Ubidots to PostgreSQL
Send Ubidots devices, events, dashboards and 3 more data types to PostgreSQL on a schedule. Refresh as often as every 15 minutes.
ubidots
deviceseventsdashboardsvariablesdevice_groups- 1 more data type
How to connect Ubidots and PostgreSQL
4 steps. You can preview the Ubidots data in Coupler.io before anything reaches PostgreSQL.
Step 1 of 4
Connect Ubidots
Enter your Ubidots API token. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the Ubidots data you want in PostgreSQL.
Step 3 of 4
Connect PostgreSQL
Enter your PostgreSQL connection details, then the schema and table for the Ubidots data.
Show 3 more fields Show fewer fields
Step 4 of 4
Choose a write mode and schedule
Every run either replaces or appends the data in PostgreSQL. Run it as often as every 15 minutes.
Each run deletes the existing rows in devices and loads fresh Ubidots data.
Coupler.io made it easy to create dashboards and reports from different data sources. The sync is reliable and the user experience is amazing.
Take your data analytics to the next level
Sign Up with Google
Sign Up with MICROSOFT
SIGN UP WITH EMAIL
By signing up to Coupler.io, you agree to our Privacy Policy and Terms of Use.
Build your Ubidots integrations with these destinations
Get the most of Ubidots to PostgreSQL integration
Gather data
Understand data
Automate data
Act on data
6 data types, including Devices, Events, Dashboards, Variables and Device groups.
With your Ubidots API token, entered once when you add the connection.
Yes, if the database user has CREATE privileges. Coupler.io creates the ubidots schema and the devices table on the first run.
Yes. Append adds new rows to devices on each run, while Replace swaps in a fresh copy. With Append, add new Ubidots columns to the table yourself before the next run.
On a schedule you choose, from monthly down to every 15 minutes, depending on your Coupler.io plan.
Yes. Add more sources to the same data flow, for example 100ms or Amazon Seller Central, and join or append them before the data reaches PostgreSQL.