Script.It does not currently offer SCIM-based user provisioning. Stepwork automates Script.It provisioning with 98% accuracy — no API required.
No native SCIM support. Complexity Vector: Manual provisioning remains due to lack of identity federation and role control.
You are correct; Script.It does not natively support SCIM. This means standard Script.It integrations cannot provision users, forcing teams to use manual spreadsheets, which is why teams use Stepwork to automate Script.It flows with 98% accuracy without needing an API.
No. Script.It does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Script.It 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 Script.It 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. Additional risks include manual account provisioning, no role sync, limited api access. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Script.It 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, mirroring your organization's security posture.