Connect Ashby to PostgreSQL
Send Ashby users, applications, archive reasons and 11 more data types to PostgreSQL on a schedule. Filter by date. Refresh as often as every 15 minutes.
ashby
usersapplicationsarchive_reasonscandidate_tagscandidates- 9 more data types
How to connect Ashby and PostgreSQL
4 steps. You can preview the Ashby data in Coupler.io before anything reaches PostgreSQL.
Step 1 of 4
Connect Ashby
Enter your Ashby API key. You only do this once per account.
Step 2 of 4
Choose what to export
Pick the Ashby data you want in PostgreSQL.
Show 6 more data types Show fewer data types
Step 3 of 4
Connect PostgreSQL
Enter your PostgreSQL connection details, then the schema and table for the Ashby 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 Ashby 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 Ashby integrations with these destinations
Get the most of Ashby to PostgreSQL integration
Gather data
Understand data
Automate data
Act on data
14 data types, including Users, Applications, Archive reasons, Candidate tags and Candidates.
With your Ashby 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 ashby 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 Ashby 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.