Connector
Greenhouse
Last updated:
Visier can retrieve data through this connector if the following requirements are met.
For more information about the data that is retrieved through this connector, see Connector Definitions.
Prerequisites
Acquire the Greenhouse BI Connector through Greenhouse. This connector is included with the Expert plan. If you don't have the Expert plan, please contact your Greenhouse account manager.
Determine whether your Greenhouse data is stored in Amazon Redshift or Amazon S3.
If using Amazon Redshift, select Redshift when providing connector credentials in Visier.
If using Amazon S3, select Amazon S3 when providing connector credentials in Visier.
Create an integration user in your database (Amazon Redshift or Amazon S3).
Note:
We recommend that you use Greenhouse with Amazon Redshift.
If you’re working out of the Greenhouse EU silo, your only option is Amazon S3.
Integration user
Create an integration user in your source system and assign it the appropriate security access so that Visier can retrieve your source data through this user.
Access | Description |
|---|---|
If using Amazon Redshift, SELECT access | Assign SELECT access to the tables you want Visier to retrieve. |
If using Amazon S3, READ access | Assign READ access to the S3 bucket you want Visier to retrieve. |
Connector credentials
You need to provide the following credentials to Visier so that we can retrieve data from your source system. If using Amazon Redshift with Greenhouse, provide the following credentials.
Credential | Description | Example |
|---|---|---|
Endpoint | The URL associated with the Amazon Redshift database. | redshift.greenhouse.io |
Port | The Amazon Redshift port number. | 5439 |
Database | The name of the Amazon Redshift database. | mydatabase |
Schema | The schema in the database to retrieve database objects from. | schema_1 |
Username | The integration user’s username. | IntegrationUser |
Password | The integration user’s password. | Password1234 |
If using Amazon S3 with Greenhouse, provide the following credentials.
Credential | Description | Example |
|---|---|---|
Customer API Key | The customer account’s API key. | 4b5435d937c6ae0d2f69d7a0dc457be9-3 |
Data files
Before the data connector can start retrieving data from your source system, you must provide access to your data files through either Amazon Redshift or Amazon S3:
Data | Description |
|---|---|
Amazon Redshift | If you don’t know your Amazon Redshift credentials, log a support ticket with Greenhouse to retrieve them. Log a support ticket with Greenhouse to add the following IP addresses to an allowlist for the Greenhouse BI Connector according to your jurisdiction: US: 100.25.224.28/32 34.205.12.155/32 35.169.9.177 3.209.36.139 18.215.76.61 Canada: 15.156.15.141/32 3.97.172.148/32 52.60.89.120 52.60.179.226 99.79.133.101 Europe: 3.75.25.88 3.64.51.142/32 18.195.228.12 3.65.101.208 18.192.64.158 |
Amazon S3 | If using Amazon S3, you must maintain an S3 bucket. After setting up an S3 bucket, log a support ticket with Greenhouse to request that the Greenhouse BI Connector targets the S3 bucket for data dumps. |
The Greenhouse data connector retrieves Requisition, Applicant, and Candidate data for use in Visier.For other data, you must provide that data through alternative methods such as SFTP or Visier’s other data connectors.
How the connector loads data
Initially, data connectors retrieve a full history for each subject to generate an initial history of events. In each subsequent data retrieval, each connector handles the data load differently.
Full load: All data from the source system is loaded into Visier.
Delta load: Only changed data is loaded into Visier. A delta load may take either the entire history or a specific number of years of history for each changed record.
Snapshot load: All data at a particular point in time. A snapshot load does not contain historical records or show changes over time.
Partial load: A subset of data is loaded into Visier.
How data is retrieved after the initial load depends on where the data is stored:
If you’re using Amazon Redshift with Greenhouse, the connector only retrieves data for changed records.
If you’re using Amazon S3 with Greenhouse, we recommend that you only provide data files for records that changed. However, you can send a full restatement if that's your preferred method.