Metaview is an AI recruiting platform that helps teams capture structured interview notes, review applicants, source candidates, and keep recruiting work connected to their ATS.
The Metaview integration with Greenhouse Recruiting connects through OAuth 2.0 and Harvest API v3. Once authorized, Metaview securely reads the recruiting data needed to match interviews and candidates, support recruiting workflows, and write selected updates back to Greenhouse Recruiting. Greenhouse Recruiting remains the source of truth for ATS data.
Configure the Metaview integration
Greenhouse Site Admin required: A Greenhouse Site Admin must authorize the connection. If you cannot access Metaview's integration settings, ask a Metaview workspace admin to help with the setup.
Open Metaview's integration settings. Sign in to Metaview and go to Settings > Integrations. Find Greenhouse and select Connect Greenhouse.
Open: https://my.metaview.app/?settings=integrations
Enter your Greenhouse subdomain. Enter the part of your Greenhouse URL before .greenhouse.io. For example, enter acme for https://acme.greenhouse.io.
Authenticate with Greenhouse. Select Authenticate with Greenhouse. Metaview redirects you to Greenhouse to sign in.
Authorize Metaview. Review the permissions requested by Metaview, then select Authorize. Metaview recommends authorizing using a service account so the integration is owned by your organization and does not depend on one employee's account.
Wait for the initial sync. Greenhouse redirects you to Metaview. The integration appears as In progress while Metaview imports the data needed by your workspace. This can take up to 48 hours for large Greenhouse accounts. Metaview emails you when the connection is ready.
Access requested by Metaview
Metaview requests the Greenhouse permissions below. Some permissions support optional features. If an optional permission is not granted, the main sync can still work, but the related feature will be unavailable.
| Area | Greenhouse permissions requested |
| Applications | List applications and application stages; create, update, move, and reject applications |
| Candidates | List, create, and update candidates; list candidate tags and applied tags; list and create candidate education; create candidate employment |
| Jobs | List jobs, job posts, openings, job interview stages, job interviews, hiring managers, and job owners |
| Interviews and scorecards | List interviews, interviewers, interview kits, scorecards, scorecard questions, answer options, and answers; create or update scorecard answers and answer options |
| Notes and attachments | List and create candidate notes; list attachments and create application attachments |
| Organization data | List departments, offices, sources, close reasons, rejection reasons and details, email templates, custom fields and options, prospect pools, and referrers |
| Users and permissions | List users, user email addresses, user roles, and user job permissions |
Scorecard permission boundary: The OAuth permission set includes scorecard write permissions. Metaview does not currently use them to automatically submit completed scorecards. Users review and submit scorecards in Greenhouse.
How Greenhouse data syncs to Metaview
Initial sync
After authorization, Metaview first imports jobs, stages, templates, users, and other setup data needed to make the integration usable. It then imports candidates, applications, interviews, scorecards, attachments, and supporting metadata. You can see In progress in Metaview while this work is underway.
Some job-specific workflows may become available before the full historical import completes. Metaview sends a confirmation email when the integration is ready.
Ongoing sync
Metaview checks Greenhouse for updates approximately every 30 minutes. Processing time varies, so new candidates, applications, stage changes, interviews, and other ATS updates can take longer than 30 minutes to appear. Workflows that need the latest applicants for one job can request a targeted refresh instead of waiting for the next regular sync.
Greenhouse Recruiting remains the source of truth. Metaview uses a workspace-specific copy of the permitted data to make product searches and joins fast. Updates sent from Metaview are written directly to Greenhouse, then reflected in Metaview through the normal sync.
Data mapping
Metaview reads the following Greenhouse fields for product workflows:
| Greenhouse data | Fields read by Metaview | Customer use |
| Jobs and job posts | Job ID, name, status, department, office, openings, hiring managers, owners, interview stages, job interviews, job post details, configured custom fields, and custom field options | Select roles, match interviews, configure reviews, and provide job context |
| Candidates | Candidate ID, first and last name, email addresses, phone numbers, addresses, social links, company, title, tags, employment, education, and attachments including resumes | Build candidate profiles, match interviews, review applicants, and avoid duplicate sourcing |
| Applications | Application ID, candidate, job, current stage, status, source, referrer, application date, prospect status, rejection reason, and rejection details | Keep applicant pipelines current and support progress or rejection decisions |
| Interviews and scorecards | Interview ID and time, interview stage, interviewers, interview kit, scorecard ID, questions, answer options, and submitted answers | Match calls to Greenhouse records and prepare scorecard content |
| Users and organization settings | User ID, name, email addresses, roles, job permissions, offices, departments, sources, close reasons, rejection reasons, email templates, prospect pools, and referrers | Respect Greenhouse permissions and apply the correct workspace configuration |
Fields written to Greenhouse
| Customer action | Greenhouse record | Fields created or changed |
| Post a conversation link, AI Notes, summary, or sequence activity | Candidate note | Note body, visibility, and the acting Greenhouse user |
| Post AI Notes or a transcript as a PDF | Application attachment | PDF file, filename, attachment type, and visibility |
| Create a sourced candidate or prospect | Candidate | First name, last name, typed email addresses, typed phone numbers, home address, social links, company, and title |
| Add history to a newly created sourced candidate | Candidate employment and education | Employment company, title, start date, and end date; education school, degree, discipline, start date, and end date. These records are created, not updated. |
| Associate a sourced person with a role | Application or prospect relationship | Candidate, job, optional initial stage, Metaview source, optional referrer, and prospect status |
| Progress an applicant | Application | Current stage used for validation before moving the application to its next stage |
| Reject an applicant | Application | Rejection reason and, when an email is selected, the email template, send time, and Greenhouse sender |
| Record candidate consent, when configured | Candidate custom field | The designated consent field is set to the configured opt-in or opt-out value; other candidate custom fields are preserved |
Metaview does not edit Greenhouse jobs or general organization settings. Customer workflows described here create new sourced candidate records and do not otherwise overwrite core profile fields on existing Greenhouse candidates. If consent sync is configured for the workspace, Metaview can update the designated candidate consent custom field.
Use the Metaview integration
AI Notes and interview workflows
- Schedule the interview in Greenhouse with the correct candidate, role, stage, and interviewers.
- Metaview matches the conversation to the Greenhouse candidate, application, job, and interviewers.
- The matched Greenhouse record enriches the conversation with candidate, role, stage, and resume context.
- Open the Greenhouse candidate or job directly from the Greenhouse link in Metaview.
- After the conversation, review the generated notes and use the Greenhouse action in Metaview to post the conversation link, notes, or summary as a candidate note. Where enabled, Metaview can attach AI Notes or a transcript PDF to the matched application.
- Greenhouse recruiter and hiring manager roles can be used to provide access to the relevant conversations in Metaview.
Scorecards
When Metaview matches a conversation to a Greenhouse interview with a scorecard, select Fill Scorecard in Metaview to view the Greenhouse scorecard and prepare factual content from the interview. Metaview intentionally leaves subjective or evaluative fields blank. Review the suggested content, add your own assessment, and submit the scorecard in Greenhouse.
Scorecard submission: Metaview does not automatically submit completed scorecards through the Harvest API v3 integration. Users review and submit scorecards in Greenhouse. The Metaview browser extension can autofill the Greenhouse scorecard page without overwriting fields the user has already completed.
Application Review
- Create an Application Review in Metaview and select the Greenhouse job and stage you want to review.
- Metaview imports the candidates, applications, resumes, application history, scorecards, and stage details needed for the review.
- Review the candidates in Metaview, then progress or reject an application when the workflow is configured to write decisions back.
- For Greenhouse rejections, Metaview can use an available Greenhouse rejection reason and, when selected, a Greenhouse rejection email template.
Sourcing and Sequences
- Search existing Greenhouse candidates from Metaview so your team can find people already known to the business.
- Push a person found through Metaview Sourcing to Greenhouse as a candidate or prospect.
- Associate the person with a Greenhouse job by creating an application or prospect relationship.
- Add contact details, employment, and education details when available.
- Record outreach and sequence activity on the Greenhouse candidate so recruiters can see the latest engagement in the ATS.
Sourcing prerequisites: Create a Metaview source in Greenhouse before pushing sourced candidates. This keeps source attribution clear. Greenhouse-backed Sourcing must also be enabled for your Metaview workspace. Contact support@metaview.ai to request it.
Write-backs to Greenhouse
Metaview sends write-backs directly to Greenhouse when a user completes the relevant action. Depending on the Metaview products enabled for your workspace and the permissions granted during OAuth, these updates can include:
- Candidate notes containing a Metaview conversation link, interview notes, a summary, or sequence activity
- AI Notes and transcript PDFs attached to the matched application
- New candidates or prospects with contact, employment, and education details
- Applications or prospect relationships for existing candidates
- Application stage changes and rejections
- A Greenhouse rejection email when the user selects an available template
Before Metaview changes an application stage or rejection state, it checks the current Greenhouse record. This helps prevent a delayed action in Metaview from overwriting a newer recruiter action in Greenhouse.
Troubleshooting
The connection fails
- Confirm that the person authorizing Metaview is a Greenhouse Site Admin.
- Confirm that the Greenhouse subdomain entered in Metaview matches the account being authorized.
- Review the OAuth permissions and grant the permissions required by the Metaview features your team uses.
- Try the connection again. If it still fails, contact support@metaview.ai.
A candidate, call, or scorecard does not match
- Allow up to 30 minutes for Greenhouse changes to appear in Metaview.
- Confirm that the candidate and interview exist in Greenhouse and are associated with the correct job and stage.
- Check for duplicate candidate or interview records.
- Confirm that the participants and candidate email in the calendar invite match Greenhouse.
- Set the Metaview meeting type to Job interview or Debrief.
If the issue continues, contact Metaview Support with the workspace name and specific Greenhouse candidate, application, or job IDs. Examples make matching issues much faster to investigate.
A feature is unavailable
Some capabilities depend on optional Greenhouse permissions. For example, resume ingestion requires attachment access, and write-backs require the corresponding create, update, move, or reject permission. Reauthorize the integration with the required permission, or contact Metaview Support for help.
Disconnect the integration
In Metaview, go to Settings > Integrations, open Greenhouse, and select Disconnect Greenhouse. This stops new Greenhouse reads and write-backs. Calls that were already scheduled may still proceed, so separately update your Metaview Notetaker scheduling rules if you also want to stop future Notetaker joins.
Additional resources
Metaview Greenhouse setup guide: support.metaview.ai/integrations/ats-integrations/greenhouse
Metaview browser extension: Chrome Web Store
For setup or troubleshooting help, contact support@metaview.ai.