STEP 1
Connect Ashby and iCIMS
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 iCIMS Integration
Build hr workflows between Ashby and iCIMS 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 trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Ashby and iCIMS
Detailed info you need to know about Ashby and iCIMS integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Ashby to iCIMS
Set up your Ashby and iCIMS integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Ashby and iCIMS 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 iCIMS. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Ashby and iCIMS work in WEXTL?
WEXTL exposes actions and triggers for Ashby and iCIMS 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 triggersiCIMS 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.
iCIMS modules
- Create a Job ProfileCreates a job profile in the system with specified details.
- Create a New Hire Category ProfileCreates a new hire category profile.
- Create an Onboard Workflow EntryCreates a new onboard workflow entry in the system.
- Create a Person ProfileCreates a profile for a person.
- Create a Recruiting Workflow EntryCreates a new entry in the recruiting workflow.
- Delete a Recruiting Workflow EntryDeletes a recruiting workflow entry.
- Get a Job PostRetrieves details of a specific job post.
- Get a New Hire Category ProfileRetrieves a new hire category profile.
- Get a Person ProfileRetrieves a person profile by using the specified identifier.
- Get a Recruiting WorkflowRetrieves a recruiting workflow by its ID.
- Get a Recruiting Workflow Submittal LogRetrieves a recruiting workflow submittal log for a specified job or candidate.
- Get a System ID Using an External IDRetrieves the system ID of a job, person, or company using an external ID.
- Get Job PostingsRetrieves all postings for a specific job.
- Get JobsRetrieves a list of all jobs.
- Make an API CallPerforms an arbitrary authorized API call.
- Post a Job to a PortalPosts a job to a portal by creating or submitting the job listing on the specified platform.
- Unpost a JobUnposts a job from a portal.
- Update a New Hire Category ProfileUpdates a new hire category profile in the system.
- Update a Person ProfileUpdates a person's profile with new details provided by the user.
- Update a Recruiting Workflow EntryUpdates a recruiting workflow entry with new information.
- Watch Job PostingsTriggers when a new job posting is created.
- Watch JobsTriggers when a new job is created.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Ashby and iCIMS 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 iCIMS.
Connect your Ashby and iCIMS 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 "Create a Job Profile" in iCIMS. Ashby has 1 trigger (including Watch Events); iCIMS has 20 actions (including Create a Job Profile, Create a New Hire Category Profile, and Create an Onboard Workflow Entry). 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-iCIMS 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 iCIMS) 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 + iCIMS 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 iCIMS integration.
- Ashby and iCIMS integration source code, module specs and credentials implementation.
- Our Ashby and iCIMS integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Ashby and iCIMS — 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
- iCIMS integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library