Data & Storage · Integration
Softools
Add Softools to your product for your customers, and give your AI agents governed access to it.
Softools is a no-code platform, so what a customer keeps in it is whatever they built: a risk register, an audit, an incident log, an assessment, each one an app with its own fields. An embedded Softools integration creates, reads and updates the records in those apps, fetches a single record by id, and reads list reports so your product can pull a view the customer already defined rather than a query you guessed at. Every tenant's apps and fields differ by design, which makes discovery and mapping the integration itself, and when they add a field it gets remapped rather than rebuilt. fastn keeps each customer's credentials, handles pagination and rate limits, and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Softools apps so your product reads and writes the records they already keep there.
Read a list report so your product uses a view the customer defined rather than one you assembled.
Create a record from an event in your product, into whichever app that customer uses for it.
Map each tenant's own fields as configuration, since two customers never build the same app the same way.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads records from a nominated app to answer a question about the customer's own process.
An agent creates or updates a record within scoped permissions, with the write attributed per tenant.
An agent fetches one record by id and quotes what it actually contains.
Example prompt
Pull the open items from the risk register app and tell me which of them have no owner.
Set up Softools in 4 steps
- 01Enable the Softools connector in your fastn dashboard.
- 02Have each customer authorise their own Softools account so their apps stay theirs.
- 03List the apps and fields in scope, map them to your own model, then enable the record actions you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Softools integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Softools integration without building it. Your customers connect their own Softools account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Softools update is not your on-call problem.
- One integration serves your product and your agents. The same governed Softools connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Quickbase
kintone
KnackOften used alongside
Tools the same teams tend to run next to Softools, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceSoftools integration FAQ
How do I add a Softools integration to my product?
Enable the Softools connector in your fastn dashboard, then let each customer authenticate their own Softools account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Softools client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Softools account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Softools account and only ever sees their own records, datasets and fields. 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 Softools integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads records from a nominated app to answer a question about the customer's own process.
Who maintains the Softools integration?
fastn does. When Softools 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.
Does the Softools integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Softools reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Softools integration?
A common starting point: let each customer connect their own Softools apps so your product reads and writes the records they already keep there. 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 Softools integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Softools does not change your per-connector cost. You can start free with 3 connected accounts.
Add Softools to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.