Data & Storage · Integration
Reftab
Add Reftab to your product for your customers, and give your AI agents governed access to it.
Reftab tracks equipment and who currently has it: assets grouped into categories, loans and reservations against them, the users those loans belong to, plus kits and software licences. The fact that decides how an integration is built is that fields are defined per category, not per account, so a laptop and a projector genuinely carry different attributes and no two customers share a field set. That means a mapping screen has to be generated from the customer's own metadata rather than from a list you shipped, and a schema change on their side becomes a mapping update instead of a release on yours. Reftab's API is token-based and public, reads are paginated, and fastn holds each customer's token per tenant and keeps up with 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 Reftab account so your product reads and writes their asset records with no per-customer code.
Build your mapping screen from that customer's own categories and custom fields, because Reftab defines field sets per category.
Create or close a loan when your product hands equipment out or takes it back, so the record matches reality.
Read licence records so your product can show what a customer already owns before it suggests buying more.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers who currently holds an asset and when it is due back.
An agent updates an asset's fields within scoped permissions, with the record it changed logged.
An agent reports on overdue loans across one customer's account only.
Example prompt
Which assets are checked out past their due date, and who is holding each of them?
Set up Reftab in 4 steps
- 01Enable the Reftab connector in your fastn dashboard.
- 02Have each customer supply a token for their own Reftab account so calls run under their credentials.
- 03Read their categories and the custom fields each one defines, then map the asset, loan and licence fields your product uses.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Reftab integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Reftab integration without building it. Your customers connect their own Reftab 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 Reftab update is not your on-call problem.
- One integration serves your product and your agents. The same governed Reftab 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
Works well with
Jamf
ServiceNow
NexthinkOften used alongside
Tools the same teams tend to run next to Reftab, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceReftab integration FAQ
How do I add a Reftab integration to my product?
Enable the Reftab connector in your fastn dashboard, then let each customer authenticate their own Reftab account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Reftab client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Reftab account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Reftab 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 Reftab 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 answers who currently holds an asset and when it is due back.
Who maintains the Reftab integration?
fastn does. When Reftab 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 Reftab 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 Reftab 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 Reftab integration?
A common starting point: let each customer connect their own Reftab account so your product reads and writes their asset records with no per-customer code. 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 Reftab integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Reftab does not change your per-connector cost. You can start free with 3 connected accounts.
Add Reftab to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.