Greenhouse integration

Business connector, available on Zeplik

Greenhouse is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Greenhouse and Zeplik can act on your business operations for you: Applicant tracking and recruiting software to optimize your entire recruiting process. You stay in the conversation while the assistant does the work in Greenhouse directly.

Zeplik exposes 44 read actions and 56 write actions for Greenhouse. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Greenhouse without your consent.

Try Greenhouse on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with Greenhouse

Read from Greenhouse (44)

Runs automatically in any conversation.

  • List applications

    List the applications in your Greenhouse organization, which associate candidates with jobs (candidate applications attach to exactly one job; prospect applications attach to zero or more). Use when you need to look up application ids, statuses, current pipeline stages, or the candidate/job/source/referrer ids tied to each application, or to filter applications by time range, status, stage, or kind. Supports rich filtering, field selection, and cursor-based pagination.

  • List application stages

    List the application stage history rows in your Greenhouse organization — one row per interview stage an application has occupied, with entered_at and exited_at timestamps. Use when you need the canonical source for stage-history reporting, such as time-in-stage analysis or reconstructing a candidate's pipeline movement for one or more applications. Supports filtering by application ids, interview stage ids, current/past, time ranges, and cursor-based pagination.

  • List approval flows

    Tool to list the approval flows in a Greenhouse organization via the Harvest v3 API. Use when you need to enumerate or search the multi-step approval definitions attached to jobs or candidate offers, optionally filtering by approval flow ids, job_ids, offer_ids, approval_type, or creation/update date ranges. Results are paginated; pass the cursor from the previous response to fetch the next page.

  • List approver groups

    Tool to list the approver groups in a Greenhouse organization via the Harvest v3 API. Use when you need to enumerate the ordered tiers of approvers that make up the approval flows on jobs or offers, optionally filtering by approver group ids, approval_flow_ids, or creation/update date ranges. Results are paginated; pass the cursor from the previous response to fetch the next page.

  • List approvers

    Tool to list approver records in a Greenhouse organization via the Harvest v3 API. Use when you need to enumerate or search the individual users assigned to approve a job, offer, or other approvable resource, optionally filtering by approver record ids, approver group ids, assigned user ids, status, or creation/update date ranges. Results are paginated; pass the cursor from the previous response to fetch the next page.

  • List attachments

    List the attachments in your Greenhouse organization, which are files associated with applications such as resumes, cover letters, take-home tests, offer documents, and e-signed agreements. Use when you need to discover attachment ids, filenames, types, or time-limited download URLs, or to scope attachments to specific applications, candidates, types, or time ranges. Each returned url is a temporary download link that expires after seven days. Supports field selection and cursor-based pagination.

  • List bulk requests

    List the asynchronous bulk requests submitted to Greenhouse Harvest v3, each tracking a batch operation with its record, success, and failure counts and current status. Use when you need to monitor or audit previously submitted bulk jobs, find a bulk_action_uuid, or check overall progress across many bulk operations. Returns paginated bulk requests; use cursor for subsequent pages. Fetch a single request's per-row result files with the Get bulk request action.

  • List candidate educations

    Tool to list candidate educations in a Greenhouse organization via the Harvest v3 API. Candidate educations are the school/degree/discipline entries (with start/end dates) recorded on candidates' profiles. Use when you need to enumerate or look up education entries, optionally filtering by entry ids, candidate ids, or creation/update timestamps. Results are paginated; pass the next_cursor from the previous response as the cursor parameter to fetch the next page.

  • List candidate employments

    Tool to list candidate employments in a Greenhouse organization via the Harvest v3 API. Candidate employments are the work-history entries (company, title, and start/end dates) recorded on candidates' profiles. Use when you need to enumerate or look up employment entries, optionally filtering by entry ids, candidate ids, or creation/update timestamps. Results are paginated; pass the next_cursor from the previous response as the cursor parameter to fetch the next page.

  • List candidates

    List the candidates (active applicants and prospects) in your Greenhouse organization, returning each candidate's profile: names, contact methods, tags, custom fields, and timestamps. Use when you need to look up candidate ids, search by email or tag, or sync candidate records, optionally filtering by id, creation/update/activity windows. Supports field selection and cursor-based pagination; nested application/attachment data lives on its own resource endpoints.

  • List candidate tags

    Tool to list the candidate tags configured in a Greenhouse organization via the Harvest v3 API. Candidate tags are the org-wide library of tag names available to apply to candidates. Use when you need to enumerate or look up available candidate tags, for example before applying a tag to a candidate. Results are paginated; pass the cursor from the previous response to fetch the next page.

  • List close reasons

    Tool to list the close reasons configured in a Greenhouse organization via the Harvest v3 API. Close reasons are the organization-defined dictionary of outcomes recorded when an opening is closed. Use when you need to enumerate or look up close reasons for filtering, reporting, or when closing an opening, optionally filtering by ids or creation/update timestamps. Results are paginated; pass the cursor from the previous response to fetch the next page.

and 32 more.

Act in Greenhouse (56)

Runs only after you enable write access.

  • Activate user

    Reactivate a previously deactivated Greenhouse user via the Harvest v3 API so they can sign in again. Use when you need to restore sign-in access for a user account that was previously deactivated, for example when an employee returns. Reactivation restores access only; job permissions that were removed during deactivation are not restored. The call is safe to repeat on an already-active user.

  • Anonymize candidate

    Tool to anonymize selected categories of personally identifiable data on a Greenhouse candidate via the Harvest v3 API, for GDPR or right-to-be-forgotten requests. Use when you must permanently redact specific classes of a candidate's PII (such as full name, contact details, tags, attachments, or notes) while retaining the candidate record. WARNING: anonymization is irreversible — the selected fields are permanently cleared or redacted and cannot be recovered, so verify the candidate id and the field selection carefully before calling.

  • Apply candidate tag

    Tool to apply an existing candidate tag to a candidate via the Greenhouse Harvest v3 API. Use when you want to label a candidate with a tag that already exists in the organization's candidate-tag dictionary. Both the candidate and the tag must already exist; the tag is not created by this action.

  • Bulk create blocked spam sources

    Tool to add multiple blocked spam sources to Greenhouse in a single request via the Harvest v3 API. Use when you need to block several IP addresses, email addresses, CIDR ranges, and/or email domains at once so future applications from them are automatically rejected. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion.

  • Bulk create custom field options

    Tool to add many custom field options at once to select-type custom fields via the Greenhouse Harvest v3 API. Use when you need to create multiple options across one or more single_select/multi_select custom fields in a single call. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion and the created option ids.

  • Bulk create openings

    Tool to asynchronously create many Greenhouse openings across one or more jobs in a single Harvest v3 call. Use when you need to add headcount slots in bulk and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; openings are created independently, so some rows may succeed while others fail.

  • Bulk deactivate users

    Tool to asynchronously deactivate many Greenhouse users in a single Harvest v3 call, up to the bulk-endpoint cap per request. Use when you need to revoke sign-in access for several users at once (for example when offboarding a group of employees) and want one submission that Greenhouse processes in the background. Deactivation only blocks sign-in: each user's record and history are preserved and any user can be reactivated later, so the operation is reversible. Returns a bulk_action_uuid and status_url to poll for per-row results; users are processed independently, so some rows may succeed while others fail.

  • Bulk delete custom field options

    Tool to archive many custom field options at once by id via the Greenhouse Harvest v3 API. Use when you need to remove multiple options from one or more select-type custom fields in a single call. This is destructive: archived custom field options are removed from the field and can no longer be selected, so restoring them requires re-creating the options. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion.

  • Bulk update blocked spam sources

    Tool to asynchronously update the note on many Greenhouse blocked spam sources in a single Harvest v3 call. Use when you need to revise notes on multiple blocklist entries at once and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; only the note can be changed (source_type and value are immutable here), and rows are processed independently so some may succeed while others fail.

  • Bulk update custom field options

    Tool to asynchronously edit many Greenhouse custom field options in a single Harvest v3 call. Use when you need to rename, reorder, or set external ids on several options at once and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; each option is updated independently, so some rows may succeed while others fail.

  • Bulk update departments

    Tool to asynchronously update many Greenhouse departments in a single call via the Harvest v3 API. Use when you need to rename or re-key several departments at once, each identified by its Greenhouse id, up to Greenhouse's bulk-endpoint cap per request. The request is processed asynchronously: Greenhouse validates and updates each department independently and returns a bulk request uuid plus a status URL to poll for the final per-row outcome.

  • Bulk update offices

    Tool to asynchronously update many Greenhouse offices in a single Harvest v3 call. Use when you need to rename offices, set or clear their location or external_id, or reposition them in the office tree in bulk, and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; offices are updated independently, so some rows may succeed while others fail.

and 44 more.

How to connect Greenhouse

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Greenhouse immediately.

  2. Connect Greenhouse

    Open Settings and go to Connectors, then press Connect on Greenhouse. You can also connect from the Greenhouse page in the app.

  3. Approve access to Greenhouse

    Approve access on Greenhouse's secure consent screen. You are returned to Zeplik and can start giving instructions that use Greenhouse.

Frequently asked questions

Can I use Greenhouse with Zeplik?
Yes. Greenhouse is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Greenhouse account inside any conversation.
What can Zeplik do with Greenhouse?
Once connected, Zeplik has 44 read and 56 write actions for Greenhouse. Applicant tracking and recruiting software to optimize your entire recruiting process.
How do I connect Greenhouse to Zeplik?
You connect Greenhouse with a secure one-click sign-in (OAuth): press Connect in Settings under Connectors and approve access on Greenhouse's consent screen.
Does Zeplik change things in Greenhouse without asking?
No. Zeplik reads from Greenhouse by default. Any action that changes data in Greenhouse requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting Greenhouse cost?
Connecting Greenhouse is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related business integrations

Connect Greenhouse to your AI assistant

Every model, one chat. Bring Greenhouse into Zeplik and let the assistant do the work.