Marketing · Okta coverage
GetResponse and Okta: SSO, SCIM and offboarding
Email marketing, landing pages and marketing automation. There is no SCIM on any plan.
SCIM pricing for every app →What Okta covers for GetResponse, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the GetResponse account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 8 of 8 capabilities for GetResponse.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to GetResponse with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares GetResponse logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the GetResponse account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes GetResponse roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes GetResponse access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in GetResponse. | Changes the GetResponse password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove GetResponse accounts. | Pulls the GetResponse user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside GetResponse. | Step level evidence for every action StitchOps takes in GetResponse. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to GetResponse with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares GetResponse logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the GetResponse account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes GetResponse roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes GetResponse access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in GetResponse.
StitchOps
Changes the GetResponse password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove GetResponse accounts.
StitchOps
Pulls the GetResponse user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside GetResponse.
StitchOps
Step level evidence for every action StitchOps takes in GetResponse.
Okta coverage from the Okta Integration Network, read October 10, 2026. GetResponse on okta.com StitchOps for Okta →
SCIM and API tax
What GetResponse charges to automate accounts.
GetResponse does not offer SCIM provisioning on any plan. There is no SCIM tax to pay, and no plan that lets your identity provider create, change and remove GetResponse accounts through SCIM.
SSO sits on the same plan as SCIM or above it. If you need SSO anyway, that upgrade is not avoidable, and the calculator counts it that way.
Pricing notes
Contact based pricing, not per user. No SCIM provisioning publicly documented on any tier including MAX (enterprise).
Last verified 2026-06-12. Source · SCIM pricing for every app · Method
Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.
Estimate GetResponse and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate GetResponse accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the GetResponse account with the right role when your HR system or identity provider says someone starts.
Movers
Change GetResponse roles, teams and access when someone changes department or manager.
Leavers
Remove GetResponse access the same day someone leaves, and free the seat.
Access checks
List who can log in to GetResponse on a schedule, with evidence for the audit.
Common questions.
Does GetResponse support SCIM?
No. GetResponse does not offer SCIM provisioning on any plan, so accounts are created and removed by hand, by file import, or by a tool that works in GetResponse the way an admin would.
Can GetResponse accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes GetResponse accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is GetResponse in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists GetResponse with SWA sign in and no provisioning.
Can Okta deprovision GetResponse users?
Not through an OIN connector. StitchOps removes GetResponse accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate GetResponse passwords when someone leaves?
StitchOps logs in to GetResponse, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.