Connect HoorayHR to PostgreSQL
Send HoorayHR users, sick leaves, time offs and 1 more data type to PostgreSQL on a schedule. Refresh as often as every 15 minutes.
hoorayhr
userssick_leavestime_offsleave_types
How to connect HoorayHR and PostgreSQL
4 steps. You can preview the HoorayHR data in Coupler.io before anything reaches PostgreSQL.
Step 1 of 4
Connect HoorayHR
Enter your HoorayHR username and password. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the HoorayHR data you want in PostgreSQL.
Step 3 of 4
Connect PostgreSQL
Enter your PostgreSQL connection details, then the schema and table for the HoorayHR 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 users and loads fresh HoorayHR 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 HoorayHR integrations with these destinations
Get the most of HoorayHR to PostgreSQL integration
Gather data
Understand data
Automate data
Act on data
4 data types, including Users, Sick leaves, Time offs and Leave types.
With your HoorayHR username and password, entered once when you add the connection.
Yes, if the database user has CREATE privileges. Coupler.io creates the hoorayhr schema and the users table on the first run.
Yes. Append adds new rows to users on each run, while Replace swaps in a fresh copy. With Append, add new HoorayHR 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 Clockify or Harvest, and join or append them before the data reaches PostgreSQL.