Ashby and WebHR Integration

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

Connect Ashby and WebHR to automate hr workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about Ashby and WebHR

Detailed info you need to know about Ashby and WebHR 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]

  • WebHR

    • HR
    • 32 triggers
    • 86 searches
    • 21 actions

    WebHR is a cloud HR platform for managing employees, attendance, leave, recruiting and projects.[6]

How to connect Ashby to WebHR

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

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

WEXTL exposes actions and triggers for Ashby and WebHR 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 triggersWebHR 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.

WebHR modules

  • Add a Booking Creates a booking for a room on a Booking Date, from its Start Time to its End Time. Use Participants and External Participants to list who attends, and Status to mark it Booked or Cancelled.
  • Add a Leave Request Submits leave requests. Use Leave Data to pass a JSON array whose entries hold a UserName, Leave From and Leave To dates, a Leave Type and a Leave Duration.
  • Add a Performance Designer Creates a performance designer. Use Performance Designer Data to pass an object with a Performance Title and Objective KPIs, each with an Objective Title, Objective Type, Objective Weightage and Objective Order.
  • Add a Poll Creates a poll with a Question and between two and six answers, from Answer 1 to Answer 6. Use Poll Start Date to set when it opens and Poll End Date to set when it closes.
  • Add a Ticket Opens a ticket, giving it a Subject and Message. Use Ticket Category ID to file it in a ticket category, and add a Priority and Deadline.
  • Add an Attendance Entry Records attendance entries. Use Data to give a JSON array whose entries hold an Access Code, Date, Time, Type and Work Shift.
  • Add an Employee Creates an employee record with a First Name and User Name. Place the person in a Company Name, Division Name, Station Name or Department Name, with a Designation, Grade and Work Shift.
  • Add Candidates Creates a candidate. Use Candidate Data to pass an object with a Job Field, First Name, Last Name, Date of Birth, Email Address and Phone Number.
  • Add Employee Hours Logs time worked by an employee on a given date, split between Regular hours and Overtime hours. Add a Project task ID to link the entry to a task, and a Jira worklog ID when the time also exists in Jira.
  • Add Project Clients Adds clients to your projects. Pass a JSON array through Project Clients, with a Client Name, First Name, Last Name, Email Address, Phone Number or Address for each.
  • Add Project Tasks Creates tasks under a project. Use Data to send the tasks as a JSON array, each with a Task, Task Type, Project Title, Deadline and Assigned To.
  • Add Projects Adds a project. Use Data to pass a ProjectTitle and a list of ProjectEmployees.
  • Delete Employee Hours Removes logged employee hours from WebHR.
  • Delete Project Clients Deletes a client entry attached to your projects.
  • Delete Project Tasks Deletes one task of a project in WebHR and returns a Message.
  • Delete Projects Removes a project from the projects stored in WebHR.
  • List Achievements Reads the achievements in your WebHR account. Use Limit to cap the number of results.
  • List Announcements Fetches the announcements in WebHR. Use Limit to cap how many results are returned.
  • List Asset Order Request Collects the order requests for assets in WebHR. Use Limit to return fewer results.
  • List Asset Purchase Orders Retrieves the purchase orders for assets. Use Limit to set a maximum number of results.
  • List Asset Vendors Shows the vendors for assets in WebHR. Use Limit to return fewer results.
  • List Assets Returns the assets in WebHR. Use Limit to return fewer results.
  • List Attendance Gathers attendance entries. Restrict them to one UserName, to the days from StartDate until EndDate, or to a ProjectCode.
  • List Bookings Shows bookings stored in WebHR. Filter by Title, Level or a numeric Status, or use Search to find bookings containing certain text.
  • List Budgets Fetches budgets, optionally by Approval status, by dates from Start date until End date, or by User name.
  • List Candidate Forms Returns the forms filled in for candidates. Use FormType to read one type of form, ApprovalStatus for one approval state, and UserName for one person.
  • List Candidates Lists candidates. Use Email Address to find one candidate, or give an Applied On Start Date, an Applied On End Date or both to look at one stretch of application dates.
  • List Check-in Rooms Looks up rooms for check-in. Filter by Title or Level, or by a numeric Status, and use Search to match text.
  • List Checkouts Pulls checkout records out of WebHR, one result per checkout. Set Limit to stop after a fixed number of results.
  • List Companies Returns the companies set up in WebHR. Use Limit to set a maximum number of results.
  • List Complaints Brings up the complaints filed in WebHR. Set a maximum number of results with Limit.
  • List Completed Courses Gathers completed courses, one result each. Add a Limit to receive fewer records.
  • List Contact Tracing Pulls contact tracing records. Use Start Date to keep results from a date onward, User Name for one person, and Search for matching text.
  • List Cost Centers Looks up the cost centers defined in WebHR. Set Limit to the maximum number of results you want.
  • List Custom Fields Reads the custom field definitions, each with a Component name, Custom field name, Custom field type and whether it is a Mandatory field.
  • List Departments Returns the departments of your organisation. Add a Limit to receive fewer records.
  • List Divisions Lists the divisions of your organisation. Add a Limit to receive fewer records.
  • List Employee Exits Displays employee exits from a Start Date through an End Date.
  • List Employee Forms Reads employee forms. Narrow by UserName, or combine FormType with ApprovalStatus.
  • List Employee Grade Shows employee grades. Use Search for a case-insensitive partial match on the grade name.
  • List Employee Hours Collects hours logged by employees, filtered by Start Date, End Date, User Name or a numeric Status.
  • List Employee KPI Reads KPI results for employees. Use User Name to see one person and Start Date with End Date for a period.
  • List Employee Rehire Returns rehire records. Use UserName to limit them to one employee.
  • List Employee Survey Retrieves employee surveys, filtered by Status or cut off at an End Date.
  • List Employee Trainings Reads employee trainings stored in your WebHR account. Use Limit to read only part of the list.
  • List Employee Types Lists the employee types. Use Search for a case-insensitive partial match on the name.
  • List Employees Returns employee records, one result for each person. Set Limit to the maximum number of people you want.
  • List eSignature Returns eSignature requests. Use User Name to see the requests of one person, and Start Date to read from a given day.
  • List eSignature Documents Fetches documents sent for eSignature. Filter on Status or End Date, and add Search text to find specific ones.
  • List Events Budgets Gets budgets set for events, optionally limited to an Approval status or matched against Search text.

Explore alternative integrations

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

Automate Ashby and WebHR on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Ashby and WebHR.

How do I connect Ashby and WebHR?

Connect your Ashby and WebHR 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 WebHR?

Example: when the "Watch Events" trigger in Ashby fires, WEXTL can "Add a Booking" in WebHR. Ashby has 1 trigger (including Watch Events). WebHR has 107 actions (including Add a Booking, Add a Leave Request, and Add a Performance Designer). Add filters and transforms between steps when you need them.[1]

Can Ashby trigger actions in WebHR, and WebHR 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 WebHR?

No. Ashby-to-WebHR 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 WebHR in real time?

Yes. Trigger-based automations start the moment Ashby (or WebHR) 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 + WebHR 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 WebHR?

You can build your Ashby + WebHR 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 WebHR integration.

  1. Ashby and WebHR integration source code, module specs and credentials implementation.
  2. Our Ashby and WebHR integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Ashby and WebHR, 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. WebHR 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 WebHR integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Ashby and WebHR, or get started