Skip to main content

Answers

inploi and your ATS: integrations

Which applicant tracking systems inploi integrates with, what reaches the ATS with each application, what inploi needs to connect, and changing ATS.

Updated

inploi is the hiring experience platform for large frontline employers. Agents do the admin. Humans do the hiring. It all runs on the ATS you already have. This page answers the questions buyers ask about connecting inploi to an applicant tracking system (ATS): which systems, what moves in each direction, what inploi needs from you and how long it takes. Each answer opens with a direct reply; the links go to the page on www.inploi.com that covers the topic.

Which ATS systems does inploi integrate with?

inploi integrates with 100+ ATSs, through direct integrations and through Kombo, its integration partner; jobs come out of the ATS and completed applications go back in.

  • Direct and partner-routed integrations cover Workday, Oracle Recruiting Cloud, SAP SuccessFactors, Cornerstone, Dayforce, Tribepad, Eploy, Harri, Pinpoint, Talos360, Teamtailor, Recruitee, Talentsoft (Cegid), TalentFunnel, iCIMS, SmartRecruiters, Greenhouse, Lever, Workable and others.
  • Tested in production with: Workday, Cornerstone, Dayforce, Tribepad, Eploy, Talos360 and TalentFunnel, with jobs in and applications out.
  • For other systems inploi builds on the ATS’s documented API; what each ATS allows (answers as fields, CV, source, scores, outcomes) varies, and inploi confirms it per ATS during scoping.
  • Don’t see your ATS? inploi reviews it against the ATS’s own API before you sign.

Related: https://www.inploi.com/data/integrations

Does inploi integrate with Workday?

Yes: inploi reads live jobs and their application questions from Workday and submits completed applications, with answers, CV and source, into Workday Recruiting.

  • Applications arrive in Workday as normal Workday applications, so recruiters work in the queue they already use.
  • Your Workday team sets up an Integration System User with the right security group and domain permissions; that access is the main dependency.
  • Candidates who apply through the inploi chat or form are recorded in Workday like any other applicant.

Related: https://www.inploi.com/data/integrations

Does inploi integrate with SAP SuccessFactors?

Yes: inploi builds on SuccessFactors’ Recruiting API, which supports reading jobs and full apply.

  • Your SuccessFactors administrator registers an OAuth client and grants Recruiting permissions; enablement sometimes needs your implementation partner or SAP support.
  • Timing is set by that enablement on your side.

Related: https://www.inploi.com/data/integrations

Does inploi integrate with Oracle Recruiting Cloud or Taleo?

Yes: for Oracle Recruiting Cloud inploi reads jobs and their questions and submits applications through Oracle’s Direct Apply, and for Oracle Taleo inploi builds on Taleo’s documented API.

  • Oracle Recruiting Cloud: the customer provisions the integration and grants Job Site REST Services duties, with separate test and production credentials.
  • Oracle Taleo: the Taleo Enterprise API uses a customer-issued account with web service permissions.

Related: https://www.inploi.com/data/integrations

Does inploi integrate with iCIMS?

inploi can build on iCIMS’s REST API, provisioned by your iCIMS team; jobs can be read, and whether applications can be submitted into your iCIMS account is confirmed during scoping.

  • iCIMS charges integration fees for provisioning; plan for them in the business case.
  • Which fields can carry answers and scores is confirmed with your iCIMS configuration during scoping.

Related: https://www.inploi.com/data/integrations

Does inploi integrate with Tribepad, Eploy, Cornerstone, Harri, Pinpoint, Talos360 or Teamtailor?

Yes: inploi has built jobs and applications for each of these.

  • Tribepad: direct integration; jobs, answers, source and consents, with scores written back after submission.
  • Eploy and Cornerstone: live jobs and each job’s own application questions pulled every 30 minutes; applications pushed back instantly. Eploy requires a paid Eploy API licence on the customer’s side.
  • Harri: jobs and their questions in, applications into Harri with answers as fields.
  • Talos360 and Pinpoint: jobs in, applications back, with source.
  • Teamtailor: jobs, questions and applications built.

Workable: built on its documented API during scoping. Jobtrain: jobs today; applications confirmed per account.

Related: https://www.inploi.com/data/integrations · https://www.inploi.com/data/integrations/eploy · https://www.inploi.com/data/integrations/cornerstone · https://www.inploi.com/data/integrations/harri · https://www.inploi.com/data/integrations/pinpoint · https://www.inploi.com/data/integrations/talos360

What gets delivered to the ATS with each application?

Each completed application is posted to your ATS with every answer in its field and, where the ATS allows, the CV and the source.

  • Answers: as structured fields where the ATS accepts them.
  • Source: the channel that brought the candidate, where the integration supports it.
  • Where the ATS takes it, the score and its breakdown are written to the candidate: Tribepad, Workday and SmartRecruiters all accept it.
  • inploi checks delivery against the ATS: an application finished on inploi’s page is not counted as delivered until the ATS has accepted it.

Related: https://www.inploi.com/experience/conversational-apply · https://www.inploi.com/use-cases/more-from-your-ats

Will candidates have to enter their details twice, once in inploi and once in our ATS?

No: the candidate applies once on inploi and the application is posted into your ATS.

  • Some ATSs ask candidates to create an account or confirm details by email; where that applies, inploi maps it during scoping so the candidate is not asked twice for the same thing.
  • Each ATS handles custom questions and duplicates differently, so the flow is tested end to end before go-live.

Related: https://www.inploi.com/experience/conversational-apply

Do the custom application questions from our ATS come through?

On ATSs that expose them by API, yes: inploi reads each job’s own questions so candidates answer the ATS’s questions inside inploi’s application.

  • Built today for Workday, Oracle Recruiting Cloud, Cornerstone, Dayforce and Eploy, and in part for others.
  • Where an ATS does not expose its questions, inploi builds the application from your question set and maps the answers to ATS fields.

Related: https://www.inploi.com/data/integrations

What does inploi need from us to connect our ATS?

inploi needs access to your ATS: credentials or a service account with the right permissions, plus any API licence your ATS vendor charges for.

  • Typical asks: an integration user (Workday), an OAuth client (SuccessFactors, Tribepad), provisioning from the vendor (iCIMS, Oracle), or a paid API licence (Eploy).
  • A named contact on your side who can grant permissions keeps the timeline short.
  • inploi does the build and the testing.

Related: https://www.inploi.com/enterprise

What if we change ATS later: does inploi move with us?

Yes: the careers site, the application and the agents sit above the ATS, so only the integration is redone when you move.

  • Candidates keep the same experience through the change.
  • Ask for the re-integration terms in your contract up front, so moving ATS does not mean paying twice.

Related: https://www.inploi.com/insight/change-your-careers-site-before-your-ats

How do candidates apply from Indeed or a job board and still land in our ATS?

A click from Indeed, Google for Jobs or another board lands on the inploi job page and application, which posts the finished application into your ATS with its source attached.

  • The same flow works for every channel, so attribution is consistent.
  • Jobs from ATSs that integrate directly with Indeed reach Indeed through that integration or through sponsorship; inploi plans distribution around that.

Related: https://www.inploi.com/platform/job-distribution

We run two or more ATSs. Can one inploi site handle that?

Yes: one careers site can route each brand or business unit’s applications to its own ATS.

  • Candidates see one site; each application reaches the right system behind it.
  • Useful after acquisitions or for joint ventures that keep separate systems.

Related: https://www.inploi.com/data/integrations · https://www.inploi.com/experience/careers-sites

How long does an ATS integration take and who builds it?

inploi builds the integration, and the time it takes is set mainly by how quickly ATS access is granted on your side; it runs inside the eight to twelve weeks of a standard implementation.

  • inploi scopes the integration once, against your ATS’s API and configuration.
  • inploi uses Kombo where it fits and a direct integration otherwise.

Related: https://www.inploi.com/data/integrations · https://www.inploi.com/enterprise

Can outcomes such as shortlisted, interviewed and hired flow back for reporting?

Status read-back is built in part for several ATSs, including Cornerstone, Dayforce, Talos360 and Tribepad; how far through to hire it reaches varies by ATS.

  • Others are built on the ATS’s API or webhooks during scoping.
  • Scores and reasoning go into the ATS where the integration supports it, and are always visible in Studio.

Related: https://www.inploi.com/data/analytics · https://www.inploi.com/use-cases/prove-hiring-roi

Agents do the admin. Humans do the hiring.

Let’s find the admin your team shouldn’t be doing.

The hiring experience audit takes four minutes.