Data & Storage · Integration
Reltio
Add Reltio to your product for your customers, and give your AI agents governed access to it.
Reltio is cloud master data management, so the object at the centre is the profile: one surviving record assembled from many source records, with a crosswalk back to each contributing system and a survivorship rule deciding which value won. Relationships connect profiles to each other, and match rules decide what merges. That structure is why reading from an MDM platform is not a normal read. Every value you get has a lineage, and writing means contributing through your own crosswalk rather than overwriting the surviving record, so survivorship still decides the outcome and nobody loses an audit trail. Each tenant defines its own entity types and attributes in its configuration, so mapping is per customer and a model change is a mapping update rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Reltio tenant so your product reads mastered profiles rather than one system's copy of them.
Write back through your own crosswalk, so your contribution is attributed to your product and survivorship still picks the winning value.
Read relationships between profiles so your product can show a household, a hierarchy or an affiliation instead of a flat record.
Read the tenant's own entity types and attributes from its configuration, since two Reltio tenants rarely model the same thing.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers which source a particular attribute value came from, and when it arrived.
An agent proposes a merge or writes an attribute within scoped permissions, with the crosswalk it used logged.
An agent traverses relationships to explain how two profiles are connected.
Example prompt
Which source is this customer's current address coming from, and what do the other sources say?
Set up Reltio in 4 steps
- 01Enable the Reltio connector in your fastn dashboard.
- 02Have each customer authorise their own Reltio tenant so calls run under their credentials.
- 03Read that tenant's entity types and attributes, map the profiles and relationships your product uses, and register the crosswalk you write through.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Reltio integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Reltio integration without building it. Your customers connect their own Reltio 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 Reltio update is not your on-call problem.
- One integration serves your product and your agents. The same governed Reltio 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
Snowflake
DatabricksWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to Reltio, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceReltio integration FAQ
How do I add a Reltio integration to my product?
Enable the Reltio connector in your fastn dashboard, then let each customer authenticate their own Reltio account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Reltio client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Reltio account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Reltio 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 Reltio 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 which source a particular attribute value came from, and when it arrived.
Who maintains the Reltio integration?
fastn does. When Reltio 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 Reltio 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 Reltio 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 Reltio integration?
A common starting point: let each customer connect their own Reltio tenant so your product reads mastered profiles rather than one system's copy of them. 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 Reltio integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Reltio does not change your per-connector cost. You can start free with 3 connected accounts.
Add Reltio to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.