RevenueCat does not currently offer SCIM-based user provisioning. Stepwork automates RevenueCat provisioning with 98% accuracy — no API required.
SAML available on higher plans but no native SCIM. Complexity Vector: API key scopes and project-level roles require interface orchestration.
You are correct; RevenueCat does not natively support SCIM. Even with SSO enabled, provisioning must be handled manually. Stepwork orchestrates RevenueCat workflows with secure guardrails, which is why teams use Stepwork to automate RevenueCat flows with 98% accuracy without needing an API.
RevenueCat supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. RevenueCat does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates RevenueCat provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to RevenueCat through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is no scim provisioning.. Additional risks include project-level roles; api key permissions; enterprise sso gating.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in RevenueCat with 98% accuracy — in a 15-minute demo.
Book a DemoNo. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider via SAML, mirroring your organization's security posture.