Skip to main content
Feedback

Greenhouse walkthrough

The Greenhouse source connector pulls recruitment and talent acquisition data from the Greenhouse Harvest API v3 into your destination.

Prerequisites

  • An active Greenhouse connection.
  • Your Greenhouse OAuth credential has read permissions for the specific resources you intend to sync.

Supported reports (Streams)

The Greenhouse connector supports the following data streams:

info

The Activity Feed report from the Greenhouse (Legacy) source isn't available in Harvest API v3. See Migrating from Greenhouse (Legacy) to Greenhouse for the full list of breaking changes.

Procedure

Setting up the data source

  1. Navigate to the Data Integration Console and click + Create Data Flow.
  2. Search for and select Greenhouse as your data source.
  3. Under Source Connection, select an existing Greenhouse connection from the dropdown, or click the field to create a new one.
  4. Click Test Connection to confirm the connection works.
  5. Click Next.

Selecting a data target

  1. Search for and select your target application, for example, Snowflake.
  2. Under Target Connection, select an existing connection from the dropdown, or create a new one.
  3. Click Test Connection to confirm the connection works.
  4. Under Data Loading Settings, select the Database and Schema for your target destination.
  5. Optional: expand Advanced Settings to configure additional target options.
  6. Click Next.

Configuring the schema

  1. Select the Greenhouse reports you want to sync, for example, applications, candidates, jobs, or notes.
  2. Optional: click Extraction Mode or Tables Definitions to change how Boomi extracts and loads data across all selected reports.
  3. Click a report's name to fine-tune its column mapping, extraction settings, or target table settings:

    • Under Table Source Settings, set the Extraction Method to Incremental to sync only new or changed records, or to All to pull the entire table.

    • For an incremental extraction, select an Incremental Type, such as Updated (filters by updated_at) or Last Activity (filters by last_activity_at).

      tip

      For the Applications report, Harvest v3 no longer exposes an applied_at field. Use Updated to approximate the legacy Created Date behavior, or use Last Activity to track records by their most recent activity.

    • Optional: for high-volume reports or sync periods longer than 30 days, lower the Exporter Chunk Size. Smaller chunks improve transfer stability and help you avoid API timeouts.

  4. Click Next.

Troubleshooting

  • Permission errors: if you encounter an error during Automapping or while running the Data Flow, verify your Greenhouse OAuth credential permissions. Each endpoint, for example, /applications, must be explicitly enabled for Read access in the Greenhouse settings.
  • Rate limiting: Greenhouse's Harvest API enforces a per-account rate limit. The connector honors the API's Retry-After header and retries automatically. If a run repeatedly logs 429 responses, reduce the number of concurrent Greenhouse rivers on the account.
  • Performance tip for initial loads: when performing a large historical load, for example, several years of data, lower the Exporter Chunk Size on the report's Table Source Settings tab. Smaller chunks break the request into pieces the Greenhouse API can process more reliably.
On this Page