Merge supports SCIM provisioning. Stepwork automates Merge provisioning with 98% accuracy — no API required.
Complex mapping/configuration Complexity Vector: Integration-heavy permissions and tokens complicate automation
It’s frustrating when integration platforms rely on precise mappings that can drift without enforcement. …which is why teams use Stepwork to automate Merge flows with 98% accuracy without needing an API.
Merge supports SAML and OIDC sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
Stepwork automates Merge 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 Merge 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 lifecycle drift happens when complex integrations aren’t consistently enforced.. Additional risks include token sprawl; role drift; evidence collection overhead. 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 and OIDC, mirroring your organization's security posture.
See how Stepwork provisions users in Merge with 98% accuracy — in a 15-minute demo.
Book a Demo