Ashby and Greenhouse Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build hr workflows between Ashby and Greenhouse on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Ashby and Greenhouse

Detailed info you need to know about Ashby and Greenhouse integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Ashby

    • HR
    • 1 trigger
    • 12 searches
    • 18 actions

    All-in-one recruiting ATS with analytics, scheduling, and candidate CRM.[5]

  • Greenhouse

    • HR
    • 4 triggers
    • 62 searches
    • 84 actions

    Recruiting software: create and update candidates, applications, jobs, interviews, scorecards and offers, and react to new candidates and hires.[6]

How to connect Ashby to Greenhouse

Set up your Ashby and Greenhouse integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Ashby and Greenhouse work in WEXTL?

WEXTL exposes actions and triggers for Ashby and Greenhouse that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Ashby triggersGreenhouse actions

Ashby modules

  • Add a Candidate to a Project Puts a candidate into one of your Ashby projects, by Candidate ID and Project ID.
  • Anonymize a Candidate Anonymizes a candidate in Ashby. This cannot be reversed, and every application of the candidate must already be archived or hired.
  • Archive an Opening Archives or restores an opening, depending on the Archive switch.
  • Create a Candidate Registers a candidate in Ashby from their Name. Add an Email, LinkedIn URL, GitHub URL, Source ID or Location to complete the profile, and Custom Fields for your own data.
  • Create a Candidate Note Records a comment on a candidate profile. Use Note to supply the Value in plain Text or HTML. Switch on Send Notifications to inform users subscribed to the candidate.
  • Create a Job Opens a new job under a Title, assigned to a Team ID and a Location ID. Use Job Template ID to start from a template, and Default Interview Plan ID for the interview stages.
  • Create a Job Opening Creates an opening for one or more Job IDs, due by the Target Hire Date and starting on the Target Start Date. Set the Employment Type, and use Opening State to begin as draft, approved or open.
  • Get a Candidate Looks up one candidate, either by Candidate ID or by the External Mapping ID your other system assigned, depending on Retrieve by.
  • Get a Job Reads a single job by its ID. Turn on Include Unpublished Job Postings IDs to also see postings that are not published.
  • Get a Job Posting Reads a single job posting. Switch on Include Unpublished Job Postings IDs to cover postings not yet published.
  • List Candidate Client Info Shows the browser and network details recorded for one candidate, each entry with its IP Address, User Agent and Related Entity Type. Set Limit to see fewer entries.
  • List Candidate Notes Fetches the notes written about a candidate, each with its Content and Author. Set Limit to read only the first few.
  • List Candidates Pulls every candidate in Ashby with their Primary Email Address, Tags and Company. Use Limit to read just the first batch.
  • List Interviews Collects interviews with their Title, Is Debrief flag and Instructions Html. Use Include Archived for archived ones, and Include Non-Shared Interviews to add interviews tied to specific jobs.
  • List Job Postings Returns job postings with their Workplace Type, Employment Type and Application Deadline. Use Listed Only to skip unlisted ones, or Department, Location and Job Board ID to focus the list.
  • List Jobs Gets jobs narrowed to one Status, or to a date window with Opened After, Opened Before, Closed After and Closed Before.
  • List Openings Lists openings together with their Opening State, Opened At time and Closed At time. Use Limit when you only need a sample.
  • Make an API Call Calls the Ashby REST API directly with a free-form request under your saved credential.
  • Search Candidates Finds people by Email or by Name. Set Limit when only the first few hits matter.
  • Search Openings Looks up openings by their Identifier, which is required. Use Limit to keep only the first matches.
  • Tag a Candidate Gives a candidate one of your Ashby tags, so recruiters can group and find people by it. Use Tag ID to say which tag.
  • Update a Candidate Edits a candidate by changing the Name, Email, Phone Number or Location, or by adding Social Links such as LinkedIn or GitHub. Use Source ID to credit where they came from.
  • Update a Job Edits a job: its Title, Team ID, Location ID or Default Interview Plan ID, and its Custom Fields.
  • Update a Job Posting Retitles a posting with Title, edits its Description, or changes its Workplace Type. Use Suppress Description Opening or Suppress Description Closing to drop the opening or closing text from the brand.
  • Update a Job Status Changes the stage of a job to draft, open, closed or archived, using Status.
  • Update an Opening Shifts the Target Hire Date or Target Start Date of an opening, and revises its Employment Type, Identifier or Description. Switch Is Backfill on to mark a replacement hire.
  • Update an Opening State Moves an opening to a new stage: draft, approved, open or closed. Add a Close Reason ID when closing it.
  • Update the Compensation of a Job Sets the pay ranges for a job through Compensation Tiers. Each tier has a Title and Components, and each component has a Compensation Type, Interval, Minimum Value and Maximum Value.
  • Upload a Candidate Resume Saves a resume against a candidate in Ashby, using Resume File.
  • Upload a File to a Candidate Stores a document on the profile of a candidate, read from File.
  • Watch Events Fires the instant Ashby sends a webhook, handing the event Action and its Data to the workflow.

Greenhouse modules

  • Add a Department to a Custom Field Lets one department see a custom field by scoping the field to that single department.
  • Add a Future Job Permission to a User Gives a User a Role on jobs that will be created later, narrowed by Department, Office or their External IDs.
  • Add a Hiring Manager to a Job Assigns a user as a hiring manager on a job requisition, linking the two records.
  • Add a Job Permission to a User Grants a User a Role on one Job, which sets what they can do there.
  • Add a Location to a Job Post Adds a place to a Job Post ID. Use Type to say whether it is an office or plain text, and Value to supply it.
  • Add a Tag to a Candidate Labels a candidate with a Candidate Tag. Tag IDs come from Create a Candidate Tag.
  • Add an Email to a User Attaches an extra Email address to a Greenhouse User. Turn on Send Verification to mail a confirmation link.
  • Add an Office to a Custom Field Gives a single office access to a custom field and ties the field to that location.
  • Add an Owner to a Job Makes a User an owner of a Job with a given Type. Use Candidate Responsibility to set candidate handling for recruiter and coordinator owners.
  • Anonymize a Candidate Removes personal data of a Candidate ID. Use Fields to choose which personal data goes.
  • Change a Prospect to a Candidate Turns a prospect Application ID into a real candidate application on a Job.
  • Create a Blocked Spam Source Blocks a sender by Source Type and Value so its applications are treated as spam. Add a Note to explain.
  • Create a Candidate Registers a person as a candidate from their First Name and Last Name. Fill Company, Title, Phone Numbers, Email Addresses and Addresses to keep contact details.
  • Create a Candidate Education Records a school entry for a Candidate ID, using custom field options for the school, degree and discipline.
  • Create a Candidate Employment Records a job held by a Candidate ID at a Company Name, with Title, Start Date and optional End Date.
  • Create a Candidate Tag Defines a new tag called Name to label candidates with.
  • Create a Custom Field Defines an extra data field by Name, Value Type and Field Type. Add Custom Field Options, a Description, mark it Private, or turn on Generate Email Token.
  • Create a Custom Field Option Adds a choice called Name to a Custom Field ID at a Sort Order position, with an optional External ID.
  • Create a Department Adds a department called Name. Use Parent ID or External Parent ID to nest it, and External ID to match another system.
  • Create a Job Creates a job by copying a Template Job, with Number Of Openings. Override with Job Name, Job Post Name, Notes, Department or Office IDs.
  • Create a Job Note Writes a Body note on a Job for a User, shown with the chosen Visibility.
  • Create a Job Post Publishes a posting from a Template Job Post ID to a Job Board. Override the Title, Content, Internal flag or Status.
  • Create a Note Writes a Body note of a Note Type with chosen Visibility. Use Candidate ID or Application ID to link it, and User to set the author.
  • Create a Referrer Adds a referrer with a Name for tracking where candidates come from.
  • Create a Scorecard Submits interview feedback from an Interviewer for an Application ID, with Interviewed At and a Submitter. Add Notes, Private Notes and a Candidate Rating.
  • Create a User Provisions a Greenhouse login from a First Name, Last Name and Primary Email. Turn on Send Email Invite and add Job Title, Employee ID, Office IDs or Department IDs.
  • Create an Application Puts a candidate on a job with an Application Type. Add Source, Recruiter, Coordinator or Referrer to record the origin and the people involved.
  • Create an Approval Flow Defines how a Job gets approved, by Approval Type and Approver Groups. Turn on Sequential to make groups approve in order, and set Offer ID for an offer.
  • Create an Attachment Adds a file to an Application ID under a Filename and Type. Provide File Content or a URL, and set Visibility.
  • Create an Interview Schedules an interview for an application from Starts At to Ends At with the chosen Interviewers. Use External Event ID to tie it to the event on your external calendar, and add a Location or Video Conferencing URL.
  • Create an Offer Drafts an offer for an Application ID. Set Starts Date, choose an Opening, and fill Custom Fields.
  • Create an Office Adds an office called Name with a Location. Nest it with Parent ID and name a Primary In House Contact User.
  • Create an Opening Adds an opening slot to a Job. Set Opening ID to your own reference and fill Custom Fields.
  • Delete a Blocked Spam Source Lifts a spam block from a source, with the Deleted flag in the result.
  • Delete a Candidate Deletes a candidate record, confirming with the Deleted flag.
  • Delete a Candidate Education Removes an education entry from a candidate profile.
  • Delete a Candidate Employment Removes a work history entry from a candidate profile.
  • Delete a Candidate Tag Deletes a tag definition from the account.
  • Delete a Custom Field Deletes a custom field, with the Deleted flag in the result.
  • Delete a Custom Field Option Removes one choice from a custom field.
  • Delete a Job Note Removes a note written on a requisition.
  • Delete a Note Deletes a note written on a candidate or application.
  • Delete an Application Deletes an application, confirmed by the Deleted flag in the result.
  • Delete an Attachment Removes a file attached to an application and returns the Deleted flag.
  • Delete an Interview Deletes a scheduled interview from an application.
  • Delete an Opening Deletes an opening slot from a job.
  • Get a Rejection Reason Reads one rejection reason with its Name and Type. Set Fields to trim the properties that are returned.
  • List Application Stages Traces how applications moved through the pipeline, with Entered At, Exited At and Days In Stage. Add Current to see only the stage each application sits in now.
  • List Applications Retrieves applications across all jobs. Combine Candidate IDs, Job IDs, Source IDs, Referrer IDs and Status to pick the subset, and Last Activity From with Last Activity Until to bound recent activity.
  • List Approval Flows Returns approval processes with their Approval Type, Sequential setting and Version. Restrict the result to some jobs or offers using Job IDs or Offer IDs.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Ashby and Greenhouse integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Ashby and Greenhouse on WEXTL®

Claim your 3-day trial to build Ashby with Greenhouse integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Ashby and Greenhouse.

How do I connect Ashby and Greenhouse?

Connect your Ashby and Greenhouse accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Ashby and Greenhouse?

Example: when the "Watch Events" trigger in Ashby fires, WEXTL can "Add a Department to a Custom Field" in Greenhouse. Ashby has 1 trigger (including Watch Events). Greenhouse has 146 actions (including Add a Department to a Custom Field, Add a Future Job Permission to a User, and Add a Hiring Manager to a Job). Add filters and transforms between steps when you need them.[1]

Can Ashby trigger actions in Greenhouse, and Greenhouse in Ashby?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Ashby and Greenhouse?

No. Ashby-to-Greenhouse automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Ashby integrate with Greenhouse in real time?

Yes. Trigger-based automations start the moment Ashby (or Greenhouse) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Ashby + Greenhouse integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Ashby with Greenhouse?

You can build your Ashby + Greenhouse automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Ashby and Greenhouse integration.

  1. Ashby and Greenhouse integration source code, module specs and credentials implementation.
  2. Our Ashby and Greenhouse integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Ashby and Greenhouse, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Ashby integration information
  6. Greenhouse integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Ashby and Greenhouse integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Ashby and Greenhouse, or get started