Ashby and iPayroll Integration

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

Connect Ashby and iPayroll 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 iPayroll

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

  • iPayroll

    • HR
    • 1 trigger
    • 10 searches
    • 7 actions

    Manage employees, cost centres, superannuation and custom fields in iPayroll, the cloud payroll and HR software.[6]

How to connect Ashby to iPayroll

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

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

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

iPayroll modules

  • Create a Superannuation Record Starts superannuation for an employee with a Pay Element such as SUPER or MV and a Quantity for the contribution amount or percentage. Use Superann Member Number to record the member number held with the super fund.
  • Create Cost Centres Saves a batch of cost centres in iPayroll, giving each a Code and a Description. The response gives the ID and Display Value of the new cost centre.
  • Create Employees Adds employees to iPayroll, each with a Surname, First Names, Start Date, Pay Frequency, Payment Method, Bank Account Number and Tax Number. Use Employee ID to set your own ID, otherwise iPayroll assigns one.
  • Delete a Superannuation Record Deletes a superannuation record from an employee in iPayroll.
  • Get a Cost Centre Fetches one cost centre from iPayroll, including whether it is Active and its Display Value.
  • Get a Custom Field Reads one custom field of an employee, returning its Name, Category Name and Description.
  • Get a Superannuation Record Fetches the superannuation record with its Pay Element, Amount and Super Fund Identifier for an employee.
  • Get an Employee Retrieves a single employee with Surname, First Names, Email, Start Date and Pay Frequency from iPayroll.
  • Get Cost Centres Returns the cost centres in iPayroll with their Code, Description and Display Value. Set Limit to return only part of the list.
  • Get Employee Custom Fields Lists the custom fields set on one employee, each with its Category Name and Name. Add Limit to stop after a fixed number of results.
  • Get Employee Custom Fields By Category Lists the custom fields that belong to a single category on an employee record, with their Category Name and Name. Use Limit to return fewer results.
  • Get Employees Lists the employees of your iPayroll account with the Surname, First Names and Email of each. Lower Limit to keep the list short.
  • Get Superannuation Records Lists the superannuation records held for an employee, showing Pay Element, Quantity and Cost Centre for each. Lower Limit to see fewer of them.
  • Make an API Call Runs a free-form request against the iPayroll REST API using your saved credential.
  • Search Custom Fields Looks up custom fields across iPayroll and narrows them by Category ID, Category Name, Custom Field ID or Custom Field Name. Add Employee ID to search one employee only.
  • Update a Superannuation Record Sets a different Pay Element, Quantity, Cost Centre or Super Fund Identifier on a superannuation record. Use Amount with MV, Super Sacrifice or Reportable Super pay elements.
  • Update an Employee Changes data of an employee such as Surname, Email, Pay Frequency or Bank Account Number. Several tax and KiwiSaver fields apply to NZ or AU payroll only.
  • Watch Cost Centres Polls iPayroll on a schedule and runs the workflow once for each newly created cost centre. Use Limit to cap how many cost centres each check returns.

Explore alternative integrations

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

Automate Ashby and iPayroll on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Ashby and iPayroll.

How do I connect Ashby and iPayroll?

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

Example: when the "Watch Events" trigger in Ashby fires, WEXTL can "Create a Superannuation Record" in iPayroll. Ashby has 1 trigger (including Watch Events). iPayroll has 17 actions (including Create a Superannuation Record, Create Cost Centres, and Create Employees). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Ashby and iPayroll, or get started