Make does not currently offer SCIM-based user provisioning. Stepwork automates Make provisioning with 98% accuracy — no API required.
SSO without SCIM. Complexity Vector: Automation roles and tokens require repeatable offboarding workflows.
It’s frustrating when SSO exists but provisioning is still manual. Stepwork automates repeatable admin workflows around Make access, which is why teams use Stepwork to automate Make flows with 98% accuracy without needing an API.
Make supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Make does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Make 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 Make 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 lifecycle.. Additional risks include sso is enterprise-tier, role cleanup is manual, api tokens persist.. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. 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.
See how Stepwork provisions users in Make with 98% accuracy — in a 15-minute demo.
Book a Demo