Skip to content

Integration · HR and recruiting

Greenhouse in Skyller.

Connect Greenhouse to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Actions and events

Greenhouse

Applicant tracking and recruiting software to optimize your entire recruiting process

Actions
134
Events
0
Composio catalog
Sign in to the service account
Global — no specific country
re-read from the vendor every 24 hours
www.greenhouse.io

134 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

SIGN IN TO THE SERVICE ACCOUNT

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in Greenhouse and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in Greenhouse.

  1. Input

    A team member asks, in the conversation, for something that today requires opening Greenhouse — inside their area's space, with their login.

  2. What Skyller does

    1. 01Picks, among the enabled functions, a query action and looks the information up in Greenhouse with the person's own credential.
    2. 02If the request requires writing something in Greenhouse, shows the card with what it is about to do and waits for Approve.
    3. 03Returns the result in the conversation and records who asked, which action was used and when.
  3. Result

    Greenhouse stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

  • The available actions are the ones the vendor publishes for Greenhouse; in your company only the functions turned on by the administrator are available.
  • If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
  • Being in this catalog does not mean being installed, with a valid login, working in your company.

Where this helps your work

Greenhouse inside the conversation where the work happens.

Three common situations for people who use Greenhouse every day. What Skyller does in each one depends on the functions your company turns on.

Looking after people

“Which candidates for the opening have not been reviewed yet?”

The HR analyst asks and Skyller queries Greenhouse with her login and lists the pending candidates for that opening.

The opening's queue in the conversation

Recording

“Move the candidate to the interview stage.”

Changing a stage is a write action: Skyller shows the card with the name and the stage and changes it in Greenhouse after Approve.

Change with approval

Administering

“People data calls for the least access possible.”

The administrator turns on only the HR functions in Greenhouse, restricts them to the right group and keeps deletions off. Every call goes in the record.

Function by function, with a record

Actions and events

What the vendor offers in Greenhouse.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

  • Reactivate Greenhouse user

    GREENHOUSE_ACTIVATE_USER

    Reactivate a previously deactivated Greenhouse user via the Harvest v3 API so they can sign in again.

  • Anonymize Greenhouse candidate

    GREENHOUSE_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.

  • Apply Greenhouse candidate tag

    GREENHOUSE_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.

  • Bulk create Greenhouse blocked spam sources

    GREENHOUSE_BULK_CREATE_BLOCKED_SPAM_SOURCES

    Tool to add multiple blocked spam sources to Greenhouse in a single request via the Harvest v3 API.

  • Bulk create Greenhouse custom field options

    GREENHOUSE_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.

  • Bulk create Greenhouse openings

    GREENHOUSE_BULK_CREATE_OPENINGS

    Tool to asynchronously create many Greenhouse openings across one or more jobs in a single Harvest v3 call.

  • Bulk deactivate Greenhouse users

    GREENHOUSE_BULK_DEACTIVATE_USERS

    Tool to asynchronously deactivate many Greenhouse users in a single Harvest v3 call, up to the bulk-endpoint cap per request.

  • Bulk delete Greenhouse custom field options

    GREENHOUSE_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.

  • Bulk update Greenhouse blocked spam sources

    GREENHOUSE_BULK_UPDATE_BLOCKED_SPAM_SOURCES

    Tool to asynchronously update the note on many Greenhouse blocked spam sources in a single Harvest v3 call.

  • Bulk update Greenhouse custom field options

    GREENHOUSE_BULK_UPDATE_CUSTOM_FIELD_OPTIONS

    Tool to asynchronously edit many Greenhouse custom field options in a single Harvest v3 call.

  • Bulk update Greenhouse departments

    GREENHOUSE_BULK_UPDATE_DEPARTMENTS

    Tool to asynchronously update many Greenhouse departments in a single call via the Harvest v3 API.

  • Bulk update Greenhouse offices

    GREENHOUSE_BULK_UPDATE_OFFICES

    Tool to asynchronously update many Greenhouse offices in a single Harvest v3 call.

Before you start

What your company needs to use Greenhouse.

Login
Each person signs in to their own Greenhouse account. Skyller guides the sign-in and stores the credential encrypted, visible only to the person who created it.
Who installs
An administrator connects Greenhouse for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
134 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide

Common doubts before connecting Greenhouse.

Next step

Connect Greenhouse and try it with your team.

Try it free with your team or book a demo: together we pick the Greenhouse functions to enable and show the first approved action, with fictitious data.