SendPulse does not currently offer SCIM-based user provisioning. Stepwork automates SendPulse provisioning with 98% accuracy — no API required.
No SCIM support Complexity Vector: User lifecycle actions rely on marketing workflows and APIs not designed for identity provisioning
You’re not wrong—SendPulse doesn’t natively support SCIM, forcing admins into manual user management. Its automation focuses on marketing flows rather than identity lifecycle control, which is why teams use Stepwork to automate SendPulse flows with 98% accuracy without needing an API.
No. SendPulse does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates SendPulse 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 SendPulse 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 work. Additional risks include manual onboarding; manual offboarding; role drift. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in SendPulse 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.