How to connect an HR system with no API to Okta
Most HR and payroll systems have no Okta connector, or charge extra for the API. A practical guide to making any HR system the source of truth for Okta.
Thomas Bieser, Cofounder and CEO ·
Okta works best when the HR system tells it who works here. A hire in HR creates the Okta user. A move changes their groups. A termination ends their access everywhere. That chain is called HR driven provisioning, and it fails at the first link when the HR system cannot talk to Okta.
That first link is missing more often than most teams expect. Our research on the Okta Integration Network found 92 HR source integrations out of 8,430. Many payroll and HR platforms used by mid market companies are not on the list, and some that are listed charge extra for the API behind it.
Four ways teams connect HR to Okta today
| Approach | What it takes | Where it breaks |
|---|---|---|
| Manual tickets | HR emails IT about each hire and termination | Late starts, missed leavers, no audit trail |
| Scheduled CSV import | Someone exports a report and Okta imports it | Forgotten runs, changed columns, terminations between runs |
| Vendor API plus custom code | An API fee, a developer and ongoing maintenance | Cost, and every vendor change breaks the script |
| HR source through StitchOps | A login to the HR system and agreed rules | Rules need agreeing up front |
Step 1: write down the rules before you connect anything
Most HR to Okta projects stall on rules, not technology. Agree these first.
- Which field is the person's unique ID. Usually the employee number, never the email.
- When a new hire becomes an Okta user. A fixed number of days before the start date works for most teams.
- How departments and titles map to Okta groups. These drive which apps a person gets.
- What a termination does, and when. Deactivate on the last day, or at a set hour on the last day.
- How contractors, leaves of absence and rehires are handled. These are where manual processes fail most.
Step 2: choose how the HR system is read
If your HR system has an Okta integration on the plan you already pay for, and it covers movers and rehires, use it. If it does not, StitchOps reads hires, changes and terminations the way your HR team sees them. We use the vendor's API where one is available to you and the system's own interface where it is not, anywhere a person can log in and act.
Step 3: connect Okta to the apps behind it
The HR system starts the chain. Okta then has to reach every app. Only about 10% of catalog integrations can both create and remove users. StitchOps carries the Okta event into the rest on the plans you already have, so you do not pay a SCIM tax to finish the job.
Step 4: prove it
Every change StitchOps makes is logged with evidence: who, what, which system and when. When an auditor asks how fast a leaver lost access, you send the record instead of rebuilding it from screenshots.
Systems we connect
HR Source works with any HR system, with or without an API. Common ones include ADP, BambooHR, Dayforce, Gusto, Paychex, Paycom, Paylocity, Rippling and UKG. If yours has a login, it can often be connected in a day. Read the Paycom to Okta walkthrough for a worked example.
Not on Okta
StitchOps works the same way with Microsoft Entra ID, Google Workspace and other identity providers. Your HR system drives your identity provider, and your identity provider drives every app.
What it costs
HR Source is one price per HR system per year, set by company size. It covers joiners, movers, leavers, write back of email and username, and edge cases. No HRIS API fee, no SCIM fee and no custom development, even when your HR system already has an Okta integration.
See how it works on HR driven provisioning.
Frequently asked questions
- Can an HR system without an API be connected to Okta?
- Yes. StitchOps reads hires, changes and terminations through the HR system's own interface, the way your HR team sees them, and turns each one into an Okta lifecycle event.
- How many HR systems have an Okta connector?
- Our November 2026 research on the Okta Integration Network found 92 HR source integrations out of 8,430, about 1% of the catalog.
- Should I use CSV imports instead?
- A scheduled CSV export works until someone forgets to run it, a column changes or a termination lands between runs. It also gives you no record of what changed and when.
- What if my HR system already has an Okta integration?
- Use it if it covers joiners, movers and leavers on the plan you have. If the vendor charges an API or integration fee, or the integration skips movers or rehires, HR Source covers the gap without that fee.
- How long does it take?
- A new HR system with a login can often be connected in a day, once the rules for departments, contractors and rehires are agreed.
Okta is a trademark of Okta, Inc. Other names may be trademarks of their respective owners. Catalog counts are from StitchOps' review of the public Okta Integration Network catalog on November 17, 2026.