Ashby and StaffCloud Integration

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

Build hr workflows between Ashby and StaffCloud 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 StaffCloud

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

  • StaffCloud

    • HR
    • 18 triggers
    • 36 searches
    • 28 actions

    Manage employees, clients, work times and payslips in StaffCloud.[6]

How to connect Ashby to StaffCloud

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

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

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

StaffCloud modules

  • Create a Client Adds a client with a Company name, an address and a Status of Active or Inactive. Fill Address line 1, City, Country and ZIP to record the location.
  • Create a Contact Creates a contact from a First name, Last name, Email and Mobile number, and links it to a client through Client ID. Set Status to Active or Inactive.
  • Create a Notification Sends a notification to a list of users, with a Subject and Text. Use Channels to add Email or SMS, and include Inbox for a push notification.
  • Create a Payslip Adds a payslip for an employee in a pay run, using the ID of an existing payslip file.
  • Create a Work Time Proposal Creates a work time proposal for new Start Date-Time and End Date-Time values. Add Break Start Date-Time, Break End Date-Time, Remarks or Source if needed.
  • Create an Employee Adds an employee with Street, Address line 2, City, Country, Birthday and Communication language. Use Marital status, Work team or CV to record those details, and Contract Type to link a contract.
  • Create an Employee Note Writes a note against an employee. HTML tags in the note text are sanitized.
  • Create an Employee Picture Creates an employee picture entry. Use Is Profile Picture to mark the main photo and Order index to place it in the sequence.
  • Create an Employee Wage Override Adds a custom wage rule for an employee. Use Custom rate to replace the rated wage type rate or fixed amount, and Valid from and Valid to to bound the dates.
  • Delete a Client Sets a client to Inactive in Staff.cloud.
  • Delete a Contact Changes a contact to Inactive in Staff.cloud.
  • Delete a File Deletes a file from Staff.cloud.
  • Delete a Payslip Removes a payslip of an employee from Staff.cloud.
  • Delete a Work Time Proposal Deletes a proposal that suggested new work times.
  • Delete an Employee Changes an employee to state 6 in Staff.cloud.
  • Delete an Employee Note Removes a note that was written about an employee.
  • Delete an Employee Picture Deletes a stored picture of an employee from Staff.cloud.
  • Delete an Employee Wage Override Deletes a wage override from an employee in Staff.cloud.
  • Get a Client Retrieves a client with its Relation ID, Status and Created at date.
  • Get a Contact Fetches the Client ID, Status and Updated at values of a single contact.
  • Get a Document Shows a document, including its Name, Document template name, Planner name and Signed at.
  • Get a File Gets the Path, Name, Mime and Public URL of a stored file.
  • Get a Form Loads a form, giving its Identifier and Name.
  • Get a Notification Gets a notification and shows its Subject, Text and whether it Is read.
  • Get a Pay Line Brings back a pay line: its Rate, Quantity, Amount and Wage type ID.
  • Get a Pay Run Collects a pay run along with its Name, Description, Exported at and Paid at.
  • Get a Payslip Returns a payslip together with its Pay run name, Amount and File public URL.
  • Get a Project Reads a project and shows its Name, Client ID, Contact ID and Project tags.
  • Get a Time Slot Provides the Name, Week days, From and To of a time slot.
  • Get a Work Time Proposal Checks a work time proposal for its Start, End, Remarks and Source, as well as Accepted at and Rejected at.
  • Get an Employee Looks up an employee and returns the Status, Employment type, Last active at and Wage profile ID.
  • Get an Employee Note Reads a note written about an employee, giving its Content and Planner ID.
  • Get an Employee Picture Returns one picture of an employee: its File ID, Order and Is profile picture.
  • Get an Employee Wage Override Pulls a wage override, covering its Wage type ID, Qualification ID, Value, Valid from and Valid to.
  • List Clients Lists clients with their Relation ID, Status and Updated at date. Use Fields to trim the response to chosen fields.
  • List Contacts Finds contacts and shows each Client ID and Status. Use Envelope to wrap the response in an envelope object.
  • List Documents Gets documents with Name, Document template name, Status and Signed at. Use Callback to supply a JSONP function name, which turns envelope mode on.
  • List Employee Availability Lists employee availability entries, each with a Date, Employee ID, Availability request name and Completed at. Use Sort with a - prefix for descending order.
  • List Employee Notes Collects employee notes with their Content, Employee ID and Planner ID. Add Limit to stop at a given count.
  • List Employee Pictures Retrieves employee pictures, each with a File ID, an Order and Is profile picture.
  • List Employee Teams Lists employee team entries with the Employee ID, Team ID, Team name and Team created at of each.
  • List Employee Wage Overrides Pulls wage overrides, giving the Wage type ID, Qualification ID, Value, Valid from and Valid to of each.
  • List Employees Lists employees with Status, Employment type, Contract type ID and Last logged in at. Set Limit to keep the list short.
  • List Forms Lists forms in Staff.cloud, each with an Identifier and a Name.
  • List Notifications Returns notifications with Subject, Text, Is read and Created at for each.
  • List Pay Lines Collects pay lines: the Pay run ID, Employee ID, Rate, Quantity and Amount of each.
  • List Pay Runs Retrieves pay runs, listing their Name, Description, Exported at and Paid at.
  • List Pay Sheets Shows pay sheets by Assignment ID, with the Is approved flag and the Wages.
  • List Pay Slips Finds payslips with the Employee name, Pay run name, Amount and File name.
  • List Projects Returns projects with their Name, Client ID, Planner ID and Project tags. Use Embed to pull related records into the response.

Explore alternative integrations

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

Automate Ashby and StaffCloud on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Ashby and StaffCloud.

How do I connect Ashby and StaffCloud?

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

Example: when the "Watch Events" trigger in Ashby fires, WEXTL can "Create a Client" in StaffCloud. Ashby has 1 trigger (including Watch Events). StaffCloud has 64 actions (including Create a Client, Create a Contact, and Create a Notification). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Ashby and StaffCloud, or get started