Ashby
Ashby is an all-in-one recruiting platform that helps talent teams manage job openings, candidates, interview pipelines, and offers in one place. It's built for high-growth companies that need structured hiring workflows and detailed reporting. Connecting Ashby to Coupler.io lets you pull your recruiting data into any destination for analysis, reporting, or automation.
Why connect Ashby to Coupler.io?
Export candidates, applications, jobs, and offers to Google Sheets, Excel, BigQuery, or Looker Studio for custom recruiting dashboards
Combine multiple Ashby entities — for example, join Applications with Candidates or Jobs to get a full picture of your pipeline
Send recruiting data to AI tools like ChatGPT, Claude, or Gemini to generate summaries, spot trends, or draft reports
Keep your data fresh with scheduled syncs so your reports always reflect the latest hiring activity
Prerequisites
Before connecting, make sure you have:
An active Ashby account with admin access (required to generate an API key)
An Ashby API key — you can generate one in your Ashby account under Settings → Integrations → API Keys
Quick start
Start with the Applications entity joined with Candidates and Jobs — this combination gives you the most complete view of your hiring pipeline right away.
How to connect
Create a new data flow in Coupler.io. Log in to Coupler.io, go to the Data Flows section, and click Add data flow. Search for Ashby and select it as your source.
Enter your Ashby API key. In the source settings, paste your API key into the API key field. You can find this in Ashby under Settings → Integrations → API Keys. If you haven't created one yet, click Add API Key, give it a name, and copy the generated key.
Select an entity. Choose which data you want to export — for example, Applications, Candidates, Jobs, or Offers. You can add more sources to the same data flow to pull multiple entities at once.
Choose a destination. Select where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
Run your data flow. Click Run to execute a manual sync and confirm data is loading correctly. Once it completes successfully, you're all set.
Available entities
Applications
Candidate applications for specific jobs, including pipeline stage and status
Archive reasons
Reasons used when rejecting or archiving a candidate or application
Candidate tags
Tags used to categorize candidates by skill, status, or other criteria
Candidates
Individuals in your talent pipeline with contact info and application history
Custom fields
Custom data fields added to candidates, jobs, or other records
Departments
Departments within your organization
Feedback form definitions
Templates used by interviewers to evaluate candidates
Interview schedules
Scheduled interviews including date, time, and participants
Job postings
Public-facing job ads published on your careers page or job boards
Jobs
Internal job openings or requisitions
Locations
Physical offices or locations associated with your company
Offers
Job offers extended to candidates
Sources
Candidate origins such as job boards, referrals, or career fairs
Users
Recruiters and hiring managers using Ashby in your organization
Last updated
Was this helpful?
