Data & Storage · Integration
inriver
Add inriver to your product for your customers, and give your AI agents governed access to it.
Embed an inriver integration so your customers can reach their own product data model from inside your product rather than exporting a flat file. Every customer models entities, attributes, and relationships differently, so mapping is configuration per customer and a model change on their side is a mapping update rather than a release on yours. fastn handles per-tenant authorisation, pagination for large catalogs, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their product entities and attribute values into your product, mapped to their model.
Read the entity and attribute structure at runtime so your product adapts to each customer's data model.
Write attribute values back so data enriched in your product lands in their product data platform.
Trigger your product when an entity or its relationships change.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent inspects the entity model before deciding which attributes to read.
An agent reads product data to ground an answer in the customer's own catalog.
An agent updates attribute values within governed permissions, with every write logged.
Example prompt
Show the attributes defined for this entity type and list entities missing a value on the required ones.
Set up inriver in 4 steps
- 01Open the inriver connector from your fastn dashboard.
- 02Have each customer authenticate their own inriver environment.
- 03Map the entity types, attributes, and relationships your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the inriver integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an inriver integration without building it. Your customers connect their own inriver 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 an inriver update is not your on-call problem.
- One integration serves your product and your agents. The same governed inriver 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
AkeneoWorks well with
Bynder
ShopifyOften used alongside
Tools the same teams tend to run next to inriver, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging Faceinriver integration FAQ
How do I add an inriver integration to my product?
Enable the inriver connector in your fastn dashboard, then let each customer authenticate their own inriver account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no inriver client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own inriver account?
Yes. Every connection is scoped to the individual customer, so each authorises their own inriver 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 inriver 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 inspects the entity model before deciding which attributes to read.
Who maintains the inriver integration?
fastn does. When inriver 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 inriver 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 inriver 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 inriver integration?
A common starting point: read their product entities and attribute values into your product, mapped to their model. 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 inriver integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding inriver does not change your per-connector cost. You can start free with 3 connected accounts.
Add inriver to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.