Sendoso does not currently offer SCIM-based user provisioning. Stepwork automates Sendoso provisioning with 98% accuracy — no API required.
No native SCIM support. Complexity Vector: Budget routing and campaign permissions lack centralized provisioning endpoints.
You are correct; Sendoso does not natively support SCIM. This means standard Sendoso integrations cannot provision users, forcing IT to rely on manual spreadsheets, which is why teams use Stepwork to automate Sendoso flows with 98% accuracy without needing an API.
Sendoso supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Sendoso does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Sendoso 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 Sendoso 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 native scim. Additional risks include budget-based permissions, campaign-level access drift, manual user lifecycle sync. 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 Sendoso with 98% accuracy — in a 15-minute demo.
Book a Demo