Trumpet does not currently offer SCIM-based user provisioning. Stepwork automates Trumpet provisioning with 98% accuracy — no API required.
SAML referenced but SCIM not documented. Complexity Vector: Rapid revenue team scaling without lifecycle sync requires UI automation to avoid plan upgrades.
Avoid upgrading to the Enterprise or higher plan just for provisioning. Stepwork allows you to automate Trumpet on your current license tier. This protects budget while maintaining control, which is why teams use Stepwork to automate Trumpet flows with 98% accuracy without needing an API.
Trumpet supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Trumpet does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Trumpet 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 Trumpet 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 scim not publicly listed.. Additional risks include sso likely enterprise gated; manual lifecycle updates; sales team churn.. 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 Trumpet with 98% accuracy — in a 15-minute demo.
Book a Demo