Bombora does not currently offer SCIM-based user provisioning. Stepwork automates Bombora provisioning with 98% accuracy — no API required.
No SCIM; SSO not documented. Complexity Vector: Access spans multiple downstream activations (CRM, MAP, ABM), so lifecycle hygiene requires repeatable UI permission checks.
You are correct; Bombora does not publicly document SCIM provisioning. That means access and role hygiene across intent workflows stays manual…which is why teams use Stepwork to automate Bombora flows with 98% accuracy without needing an API.
No. Bombora does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Bombora 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 Bombora 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 scim lifecycle automation.. Additional risks include seat cleanup manual., access drift across teams., ui audits required.. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Bombora 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.