Coupler.io is a no-code data integration and analytics platform that gives businesses access to data from 400+ sources in one place. It helps Data Analysts and teams across Finance, Marketing, Sales, and Leadership collect, combine, transform, and automatically refresh their business data for reporting and analysis.
Users can load this data into spreadsheets, BI tools, and data warehouses to build automated reports and dashboards, or connect it to AI tools to explore their data using natural language, get answers to business questions, and generate insights without manually preparing or uploading datasets.
With the Greenhouse Recruiting integration, Coupler.io brings recruiting data - including applications, jobs, interviews, offers, scorecards, and other hiring data - into the same analytics workflow. Users can combine Greenhouse data with information from other business systems, transform it, build automatically refreshed reports and dashboards, or make it available for AI-powered analysis.
Configure the Coupler.io integration
Before you begin
- A Coupler.io account. You can sign up for free at https://app.coupler.io/register/sign_up.
- A Greenhouse Recruiting user with Site Admin permissions. Greenhouse's Harvest v3 list endpoints require the authorizing user to be a Site Admin. You can connect with a lower permission level, but some data entities will not be available.
Connect Greenhouse in Coupler.io
Sign in to Coupler.io and start a new data flow.
On the Sources step, select Greenhouse as the source application.
Click Connect.
Optionally, enable Share connection with your team. You can also change this setting later. Click Start.
You are redirected to Greenhouse's secure sign-in page. Sign in with a Greenhouse Site Admin account.
Review the read-only permissions Coupler.io requests to access your recruiting data, then click Authorize to grant access.
You are redirected back to Coupler.io, with your Greenhouse account connected and ready to use.
Data actions: Coupler.io only uses read-only (list) endpoints from the Greenhouse Harvest v3 API. It does not add, edit, delete, or write any fields back to Greenhouse. Custom fields configured in Greenhouse are included as nested data within the relevant entities.
Use the Coupler.io integration
Once Greenhouse is connected, you can configure what data to import and where to send it. A typical data flow is set up in the following steps:
Select the Greenhouse data entity you want to import - for example, Candidates, Applications, or Jobs. Each entity becomes its own data set.
Set a start date to specify how far back Coupler.io should fetch data. The default start date is 60 days ago. The Sources entity ignores the start date and always retrieves all available data.
Optionally, transform the data on the Data set step - filter rows, rename or hide columns, and add formulas such as IF, COUNT, CONCAT, SUM, and others. You can also combine Greenhouse data entities with each other or with data from other connected sources.
For example, to add candidate details such as first and last name to Applications, join the Applications and Candidates data sets by candidate ID:
Choose one or more destinations on the Destinations step - for example, Google Sheets, Google BigQuery, Looker Studio, Power BI, Claude, or ChatGPT.
Each destination has its own settings. For example, for Google Sheets, connect your Google account and select the spreadsheet and sheet where you want to load the data.
Within a single data flow, you can load your data to multiple destinations — for example, share a filtered list of applications with your team via Google Sheets, export raw data to BigQuery, and analyze the data with Claude:
Run the data flow.
Turn on Automatic data refresh to keep the destination up to date on a schedule, with refreshes available as often as every 15 minutes.
Greenhouse data available in Coupler.io
The integration can import the following Greenhouse entities. Each entity is imported as a separate data set.
| Entity | Description |
| Candidates | Candidates |
| Candidate educations | Education history for candidates |
| Candidate employments | Employment history for candidates |
| Applications | Job applications |
| Application stages | Application pipeline stage history |
| Attachments | Resumes and other application files |
| Sources | Candidate sources (full refresh only) |
| Referrers | Referrers |
| Prospect pools | Prospect pools |
| Prospect pool stages | Stages within a prospect pool |
| Prospect details | Prospect links to talent pools and stages |
| Jobs | Open positions |
| Job hiring managers | Hiring managers on a job |
| Job owners | Sourcers, recruiters, and coordinators on a job |
| Job posts | Job postings |
| Job post locations | Locations on a job post |
| Job board custom locations | Custom job-board locations |
| Openings | Headcount openings |
| Close reasons | Job and opening close reasons |
| Offers | Offers |
| Job interview stages | Interview stages on a job |
| Job interviews | Interviews on a job stage |
| Interview kits | Scorecard templates |
| Scorecard questions | Questions on an interview kit |
| Default interviewers | Default interviewers on an interview kit |
| Rejection reasons | Rejection reason catalog |
| Rejection details | Rejection details on applications |
| Departments | Departments |
| Offices | Offices |
| Users | Recruiters, hiring managers, and admins |
| User emails | User email addresses |
| Email templates | Email templates for candidate communication |
Additional resources
For additional information not covered here, reach out to Coupler.io support at contact@coupler.io, or visit the Coupler.io Help Center at docs.coupler.io.