With Sense’s talent engagement solutions, accelerate hiring, strengthen your brand, and exceed recruiting targets. Sense provides solutions for every step of your talent lifecycle.

  • Omni-channel Messaging: Move seamlessly from 1:1 text messaging, Whatsapp or email to customized broadcasts, and engage talent with automated, personalized check-ins.
  • AI Engagement: Let Sense do the work through AI driven automation. Engage and convert candidates with powerful, personalized communication delivered at scale all while keeping your ATS with the latest information.
  • Chatbot:Screen and schedule qualified talent in minutes with your digital recruiter
  • Referrals:expand your talent pipeline with high quality referrals while shortening time-to-fill and reducing job board spend. Track and manage submissions, payouts, and rewards from one centralized platform
  • Discover: Connect qualified candidates to open roles through Search and Match AI
  • Scheduler: Reduce interview scheduling friction using automation

Sense’s integration with Greenhouse Recruiting enhances candidate/lead establishment, applicant engagement, offer/hire engagement (onboarding) and employee engagement.

Set up the Sense integration

Create a Harvest API key

To configure the Sense integration, you’ll need to create a Harvest API key.

Follow the steps in this article to create the key, and verify that the permissions below are selected when configuring the Sense integration.


In the Create New Credential box, make the following selections:

  • API Type:Harvest
  • Partner: Sense or Unlisted Vendor
  • Description: Sense Harvest API key


Sense requests access to all Harvest API permissions.

If you are unable to give Sense access to all permissions, please verify that the following permissions are selected for the Sense integration:


  • GET: Retrieve application
  • GET: List applications
  • PATCH: Update application
  • POST: Advance application
  • POST: Hire application
  • POST: Move application
  • POST: Reject application
  • POST: Moves application to Job
  • POST: Unreject application
  • POST: Add Attachment to application
  • PATCH: Convert a prospect
  • PATCH: Update a rejected application's rejection reason


  • GET: Retrieve Candidate
  • GET: List Candidates
  • PATCH: Edit Candidate
  • POST: Add Candidate
  • POST: Add Note
  • POST: Add E-mail
  • POST: Add Attachment
  • POST: Add application
  • POST: Add Education
  • POST: Add Employment
  • POST: Add Prospect
  • PUT: Anonymize Candidate
  • PUT: Merge two candidates


  • GET: List tags applied to candidate
  • GET: List candidate tags
  • POST: Add new candidate tags
  • PUT: Add a candidate tag


  • GET: Retrieve user
  • GET: List users
  • PATCH: Update a user
  • GET: List user future job permissions
  • GET: List user job permissions
  • GET: List pending approvals
  • PATCH: Enable user
  • PUT: Add a job permission
  • PUT: Create a future job permission
  • POST: Add user
  • POST: Add user E-mail address


  • GET: Retrieve EEOC Data for application
  • GET: List EEOC


  • GET: Retrieve application's scorecard
  • GET: List scorecards for application
  • GET: Retrieve scorecard
  • GET: List scorecards


  • GET: List application's offers
  • GET: Retrieve application's current offer
  • GET: Retrieve offer
  • GET: List offers
  • PATCH: Update application's current offer

Scheduled Interviews

  • GET: List Interviews for application
  • GET: Retrieve Interview
  • GET: List Interviews
  • Delete: Delete a scheduled interview
  • POST: Create a scheduled interview
  • PATCH: Update a scheduled interview

Activity Feed

  • GET: Retrieve Activity Feed


  • GET: Retrieve Department
  • GET: List Departments
  • POST: Create a new department
  • PATCH: Update a department

Email Templates

  • GET: Retrieve Email Template
  • GET: List Email Templates

Custom Locations

  • GET: Retrieve Custom Location for Job Board


  • GET: Retrieve Job
  • GET: List Jobs
  • PATCH: Update Job
  • POST: Create a new job
  • GET: Get hiring team
  • POST: Add hiring team member
  • PUT: Replace hiring team

Job Posts

  • GET: List Job Posts
  • GET: Retrieve Job Post for Job
  • GET: List Job Posts for Job
  • PATCH: Update job posts

Job Stages

  • GET: Retrieve Job Stage
  • GET: List Job Stages
  • GET: List Job Stages for Job

Job Openings

  • GET: List Openings For a Job
  • POST: Create openings
  • PATCH: Edit openings


  • GET: Retrieve Office
  • GET: List Offices
  • POST: Create a new office
  • PATCH: Update an office

Rejection Reasons

  • GET: List Rejection Reasons


  • GET: List Sources

User Roles

  • GET: List User Roles

Prospect Pool

  • GET: Retrieve Prospect Pool
  • GET: List Prospect Pools

Tracking Links

  • GET: Retrieve job tracking link

Custom Fields

  • GET: Get custom fields
  • POST: Create custom field
  • PATCH: Update custom field

Custom Field Options

  • GET: Custom field options
  • POST: Create custom field options
  • PATCH: Update custom field options

Close Reasons

  • GET: Get close reasons


  • GET: Get degrees
  • GET: Get disciplines
  • GET: Get schools


  • GET: List Approval Flows For Job
  • PUT: Update an Approval Flow
  • GET: Get single approval flow
  • POST: Request approvals
  • PUT: Replace an approver

Provide your API credentials to Sense

Copy the API key info to Onetimesecret.com (a secure data transferring service)

  • This ensures the key is sent securely/not stored in plain text in an email. Feel free to generate a password.
  • Send the link to your Sense implementation manager and let them know the password (if you used one).

Create an Intergration service user (ISU)

To sync note writebacks for the Sense integration, you’ll need to create a Site Admin integration service user for Sense. This user will be shown as the note poster in Greenhouse for any Sense activity.

Follow the steps below to create the user, and verify that the permissions below are selected when configuring the admin user.

Navigate to the Configure > Users and select +New Users. Enter an email you want associated with this user, for example sense_integration@COMPANYDOMAIN.com and assign Site Admin permissions along with three developer permissions

Save when finished.

Send the User’s ID and email to Sense as the final step. 

Create webhooks and complete setup 

Next, you’ll need to create three webhooks. Follow the steps in this article to create your webhooks. Use the values listed below to configure the webhooks:

Webhook #1

  • Name: Sense - Deleted Candidate
  • When: Delete Candidate
  • Endpoint URL: The Endpoint URL provided by Sense
  • Secret Key: The Secret Key provided by Sense

Webhook #2

  • Name: Sense - Job Deleted
  • When: Job Deleted
  • Endpoint URL: The Endpoint URL provided by Sense
  • Secret Key: The Secret Key provided by Sense

Webhook #3

  • Name: Sense - Deleted application
  • When: Delete application
  • Endpoint URL: The Endpoint URL provided by Sense
  • Secret Key: The Secret Key provided by Sense

Use the Sense integration with Greenhouse Recruiting

Sense will use the same user ID for all actions. Sense initiates a full sync that gives them a copy of your Greenhouse data so they can craft audiences and triggers to send communication. After the full sync, updates will be made to applicable entities.

Below is an outline of the data used for each Sense product:

  • Messaging(SMS + Whatsapp):Your recruiters can access your ATS candidates within Sense messaging to easily send a text message. Conversations can then be posted back to the Activity Feed to reference.
  • Scheduler: Recruiters can create meetings templates to allow candidates to seamlessly find a time, book a meeting and meet with the recruiter. Meeting details can be posted back to the Activity feed to reference.
  • Engage: The Greenhouse<>Sense integration allows you to create automation targeting specific audiences within your ATS, for example, candidates in specific application stages. Each touchpoint built within a journey can be customized with variables like candidate name, job name, recruiter name, etc. Each of these touchpoints will be triggered based on an ATS action (ex: status change), a static time and date or a recurring schedule.
  • Chatbot: Chatbots can be attached to a journey so you can target specific audiences within your ATS. New applicants can receive a prescreening chatbot which would ask the candidate various qualifying questions specific to the job applied for. If the candidate passes the prescreen, we can then offer them your scheduler link to book an interview.
  • Discover: Sense uses information from the job order to provide job matching for candidates. Information like location, job type, skills etc can be used to pinpoint the job that best fits the candidate.
  • Referrals: Candidate info, job order and employee data are used within the product to streamline the entire referral process. Sourcing, keeping track of referrals, and managing payouts.

Additional resources

For additional information on features or integration troubleshooting, reach out to support@sensehq.com or review the Sense support site