Summary and recommendation
Customer.io supports SCIM 2.0, but with significant limitations that undermine its usefulness for most IT teams. While SCIM is available on Premium/Enterprise plans, it only works with Cloudflare and JumpCloud identity providers—leaving Okta, Microsoft Entra, and Google Workspace users without automated provisioning. Even when SCIM is available, you cannot define user permissions through your IdP; all role assignments must be configured manually within Customer.io.
This creates a substantial operational gap for marketing and product teams that rely on Customer.io for customer engagement campaigns. Without broad IdP support, IT teams are forced into manual user management or workarounds like JIT provisioning through SSO, which doesn't address account deprovisioning when employees leave. For compliance-conscious organizations, this manual overhead introduces security risks around orphaned accounts and inconsistent access controls.
The strategic alternative
Customer.io gates SCIM behind Premium/Enterprise. Skip the Premium/Enterprise plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0, OpenID Connect |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ❌ | SSO only |
| Microsoft Entra ID | ✓ | ❌ | SSO only |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Customer.io accounts manually. Here's what that costs:
The Customer.io pricing problem
Customer.io gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Essentials | $100/month (5,000 profiles) | ||
| Premium | $1,000/month (annual) | ||
| Enterprise | $28,000-$55,000/year |
Note: Customer.io uses profile-based billing (maximum uniquely identified users), not traditional per-seat pricing. SCIM requires Enterprise tier and specific IdP compatibility.
What this means in practice
For organizations not using Cloudflare or JumpCloud as their primary IdP, accessing Customer.io's SCIM requires both a pricing tier upgrade and an identity infrastructure change:
Pricing Impact
Infrastructure Impact
Additional constraints
Summary of challenges
- Customer.io supports SCIM but only at Enterprise tier ($28,000-$55,000/year (negotiated))
- Google Workspace users get JIT provisioning only, not full SCIM
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What the upgrade actually includes
Customer.io doesn't sell SCIM à la carte. It's bundled with Premium/Enterprise features that most teams won't need:
The catch? Customer.io's SCIM implementation only works with Cloudflare and JumpCloud IdPs. If you're using Okta, Entra ID, or Google Workspace, you'll need to either switch identity providers or stick with JIT provisioning through SSO.
Stitchflow Insight
Even if you can use supported IdPs, you're paying $28,000-$55,000/year primarily for marketing automation features. We estimate ~80% of Premium/Enterprise capabilities are irrelevant for IT teams that simply want reliable user provisioning across their existing identity infrastructure.
What IT admins are saying
Community sentiment on Customer.io's SCIM limitations is mixed, with IT admins frustrated by the narrow IdP support and high enterprise pricing barriers.
- SCIM 2.0 only works with Cloudflare and JumpCloud - excluding major IdPs like Okta and Entra
- Enterprise pricing starts at $28K/year just to get automated provisioning
- User permissions still require manual configuration in Customer.io after SCIM sync
- High-watermark billing model creates unpredictable costs for growing teams
High-watermark billing can be expensive
The recurring theme
Customer.io's newly launched SCIM feels like an afterthought - limited IdP compatibility forces most organizations to stick with manual provisioning or expensive workarounds.
The decision
| Your Situation | Recommendation |
|---|---|
| On Essentials/Premium, need SCIM | Use Stitchflow: avoid the $27K-54K/year Enterprise upgrade |
| Using Okta or Entra ID for provisioning | Use Stitchflow: Customer.io's SCIM only works with Cloudflare and JumpCloud |
| Already on Enterprise with supported IdP | Use native SCIM: you're paying $28K+ for it |
| Need Enterprise features beyond SCIM | Evaluate Enterprise: SCIM comes bundled if you use supported IdPs |
| Small marketing team, low turnover | Manual may work: but watch for workspace access gaps |
The bottom line
Customer.io's SCIM requires both an Enterprise upgrade (starting at $28K/year) and using Cloudflare or JumpCloud as your IdP. For teams on lower tiers or using Okta/Entra, Stitchflow delivers provisioning automation without the massive tier jump or IdP constraints.
Make Customer.io workflows AI-native
Customer.io gates SCIM behind Premium/Enterprise. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Enterprise
Prerequisites
None
Key limitations
- SCIM 2.0 currently supports Cloudflare and JumpCloud IdPs
- SSO on Premium/Enterprise plans
- Custom roles on Premium+ only
- Cannot define user permissions via IdP - must be set in Customer.io
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Where to enable
Docs
Okta SSO supported. SCIM not available through Okta - use Cloudflare or JumpCloud for SCIM.
Use Stitchflow for automated provisioning.
Unlock SCIM for
Customer.io
Customer.io gates SCIM behind Premium/Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works


