Sales · Okta coverage
Clay and Okta: SSO, SCIM and offboarding
Data enrichment and prospect research for building outbound lead lists. SCIM support is not published.
SCIM pricing for every app →What Okta covers for Clay, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Clay account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for Clay.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to Clay with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Clay logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Clay account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Clay roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Clay access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in Clay. | Changes the Clay password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove Clay accounts. | Pulls the Clay user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Clay. | Step level evidence for every action StitchOps takes in Clay. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Clay with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Clay logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the Clay account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes Clay roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Clay access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in Clay.
StitchOps
Changes the Clay password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Clay accounts.
StitchOps
Pulls the Clay user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Clay.
StitchOps
Step level evidence for every action StitchOps takes in Clay.
Okta coverage from the Okta Integration Network, read October 10, 2026. Clay has no OIN listing. StitchOps for Okta →
SCIM and API tax
What Clay charges to automate accounts.
Clay does not publish whether SCIM provisioning is included or which plan it needs. Ask the vendor before you count on it, or price it with your own contract in the calculator.
SSO sits on the same plan as SCIM or above it. If you need SSO anyway, that upgrade is not avoidable, and the calculator counts it that way.
Pricing notes
March 2026 overhaul: Launch $185 a month, Growth $495 a month, Enterprise custom (SSO/RBAC). Flat/credit based. SCIM not explicitly named.
Last verified 2026-06-12 (estimate). Source · SCIM pricing for every app · Method
Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.
Estimate Clay and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Clay accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the Clay account with the right role when your HR system or identity provider says someone starts.
Movers
Change Clay roles, teams and access when someone changes department or manager.
Leavers
Remove Clay access the same day someone leaves, and free the seat.
Access checks
List who can log in to Clay on a schedule, with evidence for the audit.
Common questions.
Does Clay support SCIM?
Clay does not publish it. Ask the vendor which plan includes SCIM provisioning before you rely on it.
Can Clay accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Clay accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is Clay in the Okta Integration Network?
No. As of October 10, 2026, the OIN has no listing for Clay. Okta can sign users in only through a custom app if Clay supports SAML or OIDC, and has no connector to manage Clay accounts.
Can Okta deprovision Clay users?
Not through an OIN connector. StitchOps removes Clay accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Clay passwords when someone leaves?
StitchOps logs in to Clay, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.