Mailjet does not currently offer SCIM-based user provisioning. Stepwork automates Mailjet provisioning with 98% accuracy — no API required.
No native SCIM endpoint Complexity Vector: API and UI roles for sending permissions are not identity-centric
You’re right—Mailjet does not provide native SCIM, making lifecycle automation manual and error-prone. Stepwork automates Mailjet admin workflows in the UI…which is why teams use Stepwork to automate Mailjet flows with 98% accuracy without needing an API.
Mailjet supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Mailjet does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Mailjet 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 Mailjet 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 access control for email-sending privileges. Additional risks include security risk;, audit gaps;, delayed offboarding. 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 Mailjet with 98% accuracy — in a 15-minute demo.
Book a Demo