Connect BlueTally to PostgreSQL
Send BlueTally assets and employees to PostgreSQL on a schedule. Filter by date. Refresh as often as every 15 minutes.
PostgreSQL
schema bluetally
assetsemployees
How to connect BlueTally and PostgreSQL
4 steps. You can preview the BlueTally data in Coupler.io before anything reaches PostgreSQL.
Step 1 of 4
Connect BlueTally
Enter your BlueTally API key. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the BlueTally data you want in PostgreSQL.
Step 3 of 4
Connect PostgreSQL
Enter your PostgreSQL connection details, then the schema and table for the BlueTally 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 assets and loads fresh BlueTally 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 BlueTally integrations with these destinations
Get the most of BlueTally to PostgreSQL integration
Gather data
Understand data
Automate data
Act on data
2 data types, including Assets and Employees.
With your BlueTally API key, entered once when you add the connection.
Yes. Set the start date to cover the period you need.
Yes, if the database user has CREATE privileges. Coupler.io creates the bluetally schema and the assets table on the first run.
Yes. Append adds new rows to assets on each run, while Replace swaps in a fresh copy. With Append, add new BlueTally 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.
