Ashby and e-days Integration

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

Connect Ashby and e-days 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 e-days

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

  • e-days

    • HR
    • 4 triggers
    • 69 searches
    • 67 actions

    Manage absences, leave, rotas and time records in e-days.[6]

How to connect Ashby to e-days

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

How does the integration between Ashby and e-days work in WEXTL?

WEXTL exposes actions and triggers for Ashby and e-days 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 triggerse-days 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.

e-days modules

  • Adjust a User Entitlement Sets the balance of an entitlement element for a user to the Annual Entitlement amount. Add a Booking Period to adjust one period, and a Time Unit to state what the amount is measured in.
  • Apply Rotas to Users Applies the assigned rotas to several users at once. Turn on Update Absences to update the absences of the affected users for the new rota.
  • Create a Group Adds a group under a group type, with its own Group Partner ID and Name. Set Priority to rank its display and Minimum Staffing Level to set the staffing minimum.
  • Create a Group Type Makes a group type with a Group Type Partner ID and Name. Turn on Required Field to make selecting a group of this type compulsory, and Allow Multiple Selections to allow several.
  • Create a Template Custom Day Adds a custom day Pattern to a user template. The options are in List Custom Days.
  • Create a Template Email Notification Registers an additional email notification on a user template for an Email Address and Email Notification Type. Narrow it with Record Type Discriminator, Record Types and Record Status.
  • Create a Template Public Holiday Gives a user template a public holiday Pattern. List Public Holidays has the patterns on offer.
  • Create a Template Role Gives a user template a Role. Role options come from List Roles.
  • Create a Template Rota Adds a Rota to a user template, using List Rotas for the choices.
  • Create a User Adds a user to e-days from a Partner ID, with optional First Name, Last Name, Email, Login and Job Title. Use Settings Template ID to apply a user template, and FTE with Hours Per Day for the full-time equivalent and daily hours.
  • Create a User Authorisation Gives a user an authorisation hierarchy, with a Step One Authoriser Partner ID and a Step Two Authoriser Partner ID. Alternative authorisers can be added for each step.
  • Create a User Custom Day Attaches a custom day Pattern to a user, taken from the patterns in List Custom Days.
  • Create a User Email Notification Registers an extra email notification for a user, sent to an Email Address for the chosen Email Notification Type. Narrow it with Record Types and Record Status.
  • Create a User Public Holiday Gives a user a public holiday Pattern. The available patterns are listed in List Public Holidays.
  • Create a User Role Adds a Role to the roles a user already holds, taken from List Roles.
  • Create a User Rota Puts a user on a Rota from a Start Date. The rota comes from List Rotas.
  • Create a User Template Makes a user template, giving it a Name and a Partner ID.
  • Create an Absence Records an absence for a user, from an Absence Type ID, Start Time and End Time. Add Details as free text, or turn on Is Open for an open-ended absence.
  • Create an SSO Certificate Uploads a certificate under a Name, with its Base64-encoded Value.
  • Create Multiple Authorisations Saves up to 500 authorisation hierarchies at once, each for one User Partner ID. An entry can list a step-one and a step-two authoriser, with alternative authorisers for each step.
  • Create Multiple Users Creates up to 500 user records in one request, each with a Partner ID. A record can add First Name, Last Name, Email, Job Title, Employment Start Date and more.
  • Create User Group Memberships Puts users into groups from a list of Memberships, each pairing a User Partner ID with its Group Partner IDs.
  • Delete a Group Removes a group belonging to a group type.
  • Delete a Group Type Deletes a group type from e-days.
  • Delete a Template Custom Day Deletes a custom day assigned to a user template.
  • Delete a Template Email Notification Removes an additional email notification set up for a user template.
  • Delete a Template Public Holiday Removes a public holiday pattern that applies to a user template.
  • Delete a Template Role Removes a role assignment held by a user template.
  • Delete a Template Rota Deletes a rota entry on a user template.
  • Delete a User Removes a user account held in e-days.
  • Delete a User Custom Day Deletes a custom day pattern assigned to a user.
  • Delete a User Email Notification Removes an additional email notification set up for a user.
  • Delete a User Public Holiday Removes a public holiday pattern that applies to a user.
  • Delete a User Role Removes a role assignment held by a user.
  • Delete a User Rota Deletes a rota entry from the rotas applied to a user.
  • Delete a User Template Deletes a user template in e-days.
  • Delete an Absence Deletes an absence entry saved in e-days.
  • Delete an SSO Certificate Deletes a single sign-on certificate by its Certificate Name.
  • Delete User Group Memberships Deletes group memberships for several users in one request, each pairing a User Partner ID with Group Partner IDs.
  • Get a Group Reads a group of a group type. Output includes its Group Partner ID, Name, Priority and Minimum Staffing Level.
  • Get a Group Type Looks up a group type. Output includes its Group Type Partner ID, Name, Priority, Required Field and Allow Multiple Selections.
  • Get a Template Absence Type Reads one absence type from a user template. Output includes its Name and Record Type Discriminator.
  • Get a Template Email Notification Reads one email notification belonging to a user template, with Email Address, Email Notification Type and Record Status.
  • Get a Template Entitlement Request Type Fetches a single entitlement request type from a user template, with its Name, Record Type Discriminator and booking flags.
  • Get a Template Overtime Type Retrieves an overtime type from a user template. Output includes the Name and Can Book Others.
  • Get a User Loads one user. Output includes their Partner ID, First Name, Last Name, Email, Login and Payroll Number.
  • Get a User Authorisation Gets the step one and step two authorisers set for a user, with alternates, as rows keyed by User Partner ID.
  • Get a User Email Notification Reads one additional email notification of a user. Output includes its Email Notification Type, Email Address, Record Types and Record Status.
  • Get a User Entitlement Returns balance rows of one entitlement for a user. Output includes the Element Name, Booking Period, Annual Entitlement, Taken, Untaken and Remaining.
  • Get a User Template Fetches a user template. Output includes its Name, ID and Partner ID.

Explore alternative integrations

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

Automate Ashby and e-days on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Ashby and e-days.

How do I connect Ashby and e-days?

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

Example: when the "Watch Events" trigger in Ashby fires, WEXTL can "Adjust a User Entitlement" in e-days. Ashby has 1 trigger (including Watch Events). e-days has 136 actions (including Adjust a User Entitlement, Apply Rotas to Users, and Create a Group). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Ashby and e-days, or get started