Skip to main content

Documentation Index

Fetch the complete documentation index at: https://f4c7a9e2d8b1-docs.tenzo.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Link Greenhouse once, and Tenzo can sync jobs and applicants, run your interview flows, and write results back (for example notes, attachments, and stage changes), depending on how your team configures the integration. How that works end-to-end is covered in the ATS integrations overview.
Tenzo’s connection modal walks you through the full setup, including creating the Harvest API key (what to choose in Greenhouse, which permissions to enable, and what to paste back) and configuring webhooks (URL, secret, and each event to subscribe to). The values and checklists for both steps live there—treat that flow as the single source of truth and match it exactly in Greenhouse.
For a longer walkthrough (including visuals), see How to Connect Greenhouse to Tenzo in Notion.

​
Before you start

​
Tenzo

  • Admin access to connect Admin → ATS integrations → Add integration → Greenhouse

​
Greenhouse

Ask your Greenhouse administrator to confirm you have the right Greenhouse developer and user permissions before you invest time in the wizard:
PermissionNotes
Developer: Manage ALL organization’s API CredentialsRequired so you can open Configure → Dev Center → API Credential Management, create keys, and set Harvest permissions. If you cannot see API Credential Management, an admin must complete setup or grant this permission.

​
Connect

  1. In Tenzo, open Admin → ATS Integrations
  2. Click Add integration and choose Greenhouse
  3. Follow every step in the modal in order. The same wizard covers the API key and webhooks phases; it tells you what to create in Greenhouse and which values to paste back into Tenzo.

​
API key (Harvest)

The modal explains this step in full (field-by-field in Greenhouse and what to copy into Tenzo). In Greenhouse go to Configure (cog) → Dev Center → API Credential Management → Create New API Key. Use the API type, partner, and description your Tenzo connection flow specifies (typically a Harvest key and a Custom integration partner, with the description/name the wizard gives you). After the key exists, open Manage permissions for that credential and enable every Harvest V1 permission listed in the Tenzo modal — not only a subset. Saving with missing scopes is a frequent cause of “works in UI, fails on sync or write-back” issues. If required scopes change, the live checklist in Tenzo updates; older screenshots or external guides may not.

​
Webhooks

The modal explains this step in full (which events to subscribe to, the endpoint URL and secret, and what to enter in Greenhouse). After the Harvest key is verified, Tenzo moves you into the webhook phase of the same flow.
  1. In Greenhouse: Dev Center → Webhooks → Webhooks
  2. For each webhook event shown in your Tenzo connection flow, create a separate webhook in Greenhouse (repeat the webhook setup once per listed event—you cannot rely on a single webhook row for everything).
  3. Copy the endpoint URL, secret, and any other fields exactly as the modal shows
  4. Include the application updated / application changed–style event Tenzo asks for — Greenhouse labels vary, but the modal names the exact event — plus every other event the flow lists. Skipping events can delay or omit applicant updates.
Greenhouse sometimes does not show a newly saved webhook in the list until you refresh the page. The webhook can still be saved correctly.
After a new connection, message your Tenzo contact so they can help with defaults, mappings, and any full historical sync you need. Big backfills can take a long time; day-to-day sync is usually much quicker.

​
After you connect

Tune stages, scores, and write-back on the integration and under ATS settings. Use the rules engine to limit which jobs Tenzo touches; use manual job sync if something doesn’t show up automatically.

​
Next steps