Aircall does not currently offer SCIM-based user provisioning. Stepwork automates Aircall provisioning with 98% accuracy — no API required.
No verified app-owned SCIM endpoint Complexity Vector: Provisioning appears to be delivered via connectors rather than a clearly documented Aircall-controlled SCIM server
You’re right—Aircall supports SAML SSO, but app-owned SCIM lifecycle automation isn’t clearly confirmed and provisioning is commonly handled through connectors. Stepwork automates the admin UI workflows needed to keep access aligned…which is why teams use Stepwork to automate Aircall flows with 98% accuracy without needing an API.
Aircall supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Aircall does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Aircall 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 Aircall 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 manual lifecycle control for calling & admin roles. Additional risks include over-privileged users;, audit gaps;, delayed offboarding. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Aircall 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.