Security & Identity · Integration
Softr
Add Softr to your product for your customers, and give your AI agents governed access to it.
Softr's public API is served from studio-api.softr.io rather than api.softr.io, and it is scoped to the users of a published app instead of to the app builder itself. You list applications, then create, update and remove application users, which is how teams provision access from their own onboarding flow rather than asking people to sign up in Softr. Users belong to user groups, and it is group membership that decides which pages and blocks someone can see, so writing a user without setting groups produces an account that can sign in and see nothing. The API key is workspace level rather than per application, so one credential reaches every app in the account and needs careful scoping in a multi tenant product. fastn keeps each customer's Softr key isolated in its own tenant and maintains the connector as the API moves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Softr workspace so users you provision appear in their published app
Create a Softr app user with the right group the moment a seat is bought in your product, and remove it on cancellation
Keep group membership in step with plan tier so downgrades lose access to gated pages
Show a customer which of their Softr app users have never signed in so they can reclaim seats
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent add or remove a Softr app user on an approved request, with the actor, target user and group change logged per tenant
Have an agent audit which users sit in privileged groups and report anything unexpected
Let an agent fix group membership that does not match the plan recorded in your own billing system
Example prompt
Who has access to the admin pages of our Softr portal?
Set up Softr in 4 steps
- 01Enable the Softr connector from your fastn dashboard.
- 02Have each customer authorise their own Softr account, so calls run under their credentials rather than a shared key.
- 03Decide which users, groups and roles your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Softr integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Softr integration without building it. Your customers connect their own Softr account inside your product and work their users, groups and roles there, with no per-customer code on your side.
- Handle the part that actually costs time: the blast radius of an error is large, so least-privilege and auditability are non-negotiable. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Softr update is not your on-call problem.
- One integration serves your product and your agents. The same governed Softr connection powers in-product features and gives AI agents scoped, audited access, so you keep access and identity in step across a customer's estate without wiring it twice.
Used by these teams
Compare with
Okta
Microsoft Entra ID
Cisco UmbrellaOften used alongside
Tools the same teams tend to run next to Softr, across other categories.
ServiceNow
Datadog
PagerDuty
AWS CloudWatchSoftr integration FAQ
How do I add a Softr integration to my product?
Enable the Softr connector in your fastn dashboard, then let each customer authenticate their own Softr account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Softr client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Softr account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Softr account and only ever sees their own users, groups and roles. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Softr integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent add or remove a Softr app user on an approved request, with the actor, target user and group change logged per tenant
Who maintains the Softr integration?
fastn does. When Softr changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
What permissions does the Softr integration need?
Only the scopes required for the actions you enable. Each customer grants access to their own Softr tenant, permissions are scoped per tenant, and every call is recorded so an access change can be traced to its source.
Can access changes be automated safely?
Yes. Provisioning and deprovisioning can be driven from your product or an agent within governed permissions, with every action audited, which is what makes automated access changes reviewable after the fact.
What can I build with the Softr integration?
A common starting point: let a customer connect their own Softr workspace so users you provision appear in their published app. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Softr integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Softr does not change your per-connector cost. You can start free with 3 connected accounts.
Add Softr to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.