STEP 1
Connect Ashby and Payworks
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Ashby and Payworks Integration
Keep Ashby and Payworks in sync by integrating their events and actions. When hr events happen in Ashby, update the Payworks automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Ashby and Payworks
Detailed info you need to know about Ashby and Payworks integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Ashby to Payworks
Set up your Ashby and Payworks integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Ashby and Payworks nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Ashby and Payworks. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Ashby and Payworks work in WEXTL?
WEXTL exposes actions and triggers for Ashby and Payworks that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Ashby triggersPayworks actions
Ashby modules
- Add a Candidate to a ProjectAdds a candidate to an existing project.
- Anonymize a CandidateAnonymizes a candidate. This action cannot be reversed and requires all of the candidate's applications to be in the archived or hired state.
- Archive an OpeningArchives an opening.
- Create a CandidateCreates a Candidate.
- Create a Candidate NoteCreates a new note for a candidate.
- Create a JobCreates a Job.
- Create a Job OpeningCreates a Job Opening.
- Get a CandidateRetrieves a single candidate by ID.
- Get a JobRetrieves details for a specific job.
- Get a Job PostingRetrieves details for a specific job posting.
- List Candidate Client InfoRetrieves a list of client information for a specified candidate.
- List Candidate NotesRetrieves a list of notes for a candidate.
- List CandidatesRetrieves a list of candidates.
- List InterviewsRetrieves a list of interviews.
- List Job PostingsRetrieves a list of job postings.
- List JobsRetrieves a list of jobs.
- List OpeningsRetrieves a list of openings.
- Make an API CallPerforms an arbitrary authorized API call.
- Search CandidatesSearches for candidates by name or email.
- Search OpeningsSearches for openings matching the given criteria.
- Tag a CandidateSets a specified tag to a candidate.
- Update a CandidateUpdates a Candidate with new field values.
- Update a JobUpdates a Job with new field values.
- Update a Job PostingUpdates a Job Posting with new field values.
- Update a Job StatusUpdates the status for a specified job.
- Update an OpeningUpdates an Opening with new field values.
- Update an Opening StateUpdates a state of the opening.
- Update Job CompensationUpdates compensation rates for a specified job.
- Upload a Candidate ResumeUploads a candidate's resume, parses it, and updates their information.
- Upload a File to a CandidateUploads a file to a candidate record.
- Watch EventsTriggers when a specific event occurs.
Payworks modules
- Add Employee EarningAdds earning information for an employee.
- Create a ScheduleCreates a schedule for users, allowing them to organize tasks, events, or appointments.
- Create a Schedule ShiftCreates a schedule shift for an employee with specified details.
- Create a TimesheetCreates a new timesheet entry for tracking work hours.
- Create an EmployeeCreates an employee record in the system.
- Create Payroll EntriesCreates payroll entries based on the provided data.
- Get a ScheduleRetrieves a schedule from the service.
- Get a Schedule ShiftRetrieves a schedule shift.
- Get an EmployeeRetrieves an employee's information from the database.
- Get EmployeesRetrieves a list of employees from the service.
- Get HolidaysRetrieves holidays from the specified service.
- Get Journal Entries by Schedule IDRetrieves journal entries associated with a specific schedule ID.
- Get Pay PeriodsRetrieves pay periods from the service.
- Get Pay StatementsRetrieves pay statements for a specific employee or time period.
- Get Pay StatementsRetrieves pay statements (reports) for a user or employee.
- Get Schedule ShiftsRetrieves schedule shifts from the service.
- Get SchedulesRetrieves schedules from the service.
- Get Timeoff RequestsRetrieves timeoff requests.
- Get TimeSheetsReturns a single timesheets.
- Make an API CallPerforms an arbitrary authorized API call.
- Update a ScheduleUpdates a schedule with the provided details.
- Update an EmployeeUpdates an employee's details in the system.
- Watch HolidaysTriggers when a new holiday is added.
- Watch Pay PeriodsTriggers when there is an update to a pay period.
- Watch SchedulesTriggers when a new schedule is created or updated.
- Watch Timeoff RequestsTriggers when a new timeoff request is made.
- Watch TimesheetsTriggers when a new timesheet is created or updated.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Ashby and Payworks integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Ashby and Payworks.
Connect your Ashby and Payworks 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]
Example: when Ashby's "Watch Events" fires, WEXTL can "Add Employee Earning" in Payworks. Ashby has 1 trigger (including Watch Events); Payworks has 22 actions (including Add Employee Earning, Create a Schedule, and Create a Schedule Shift). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Ashby-to-Payworks automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Ashby (or Payworks) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Ashby + Payworks automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Ashby and Payworks integration.
- Ashby and Payworks integration source code, module specs and credentials implementation.
- Our Ashby and Payworks integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Ashby and Payworks — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Ashby integration information
- Payworks integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library