Data & Storage · Integration
Revalize
Add Revalize to your product for your customers, and give your AI agents governed access to it.
Revalize sells CPQ, PLM and design automation to manufacturers of configured products, so the data is a product model rather than a catalogue: rules deciding which options can legally be combined, part numbers generated from a valid configuration, and the quote or drawing that comes out of it. Every manufacturer's model is its own, which is the entire reason the software exists, so option and field mapping is configuration per customer and there is no fixed schema to code against. Revalize is a suite assembled from several products, so which surface a given manufacturer runs is part of their setup rather than something your integration can assume. The useful discipline is to read a configuration rather than reimplement its rules, because the rules are the product. fastn owns the credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each manufacturer connect their own Revalize environment so your product reads the product model their engineers maintain.
Read a valid configuration and the part numbers it generates instead of reimplementing the option rules in your own code.
Write a configuration or quote record back so what your product priced is what the manufacturer's system holds.
Treat each customer's own product model, and the Revalize surface they run, as configuration rather than a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a configuration and explains which options drove the part numbers it produced.
An agent creates or updates a quote record within scoped permissions, with the write attributed.
An agent answers what a configured product includes without anyone opening the configurator.
Example prompt
What does this configuration include, and which part numbers did it generate?
Set up Revalize in 4 steps
- 01Enable the Revalize connector in your fastn dashboard.
- 02Have each manufacturer connect their own environment, and record which Revalize product surface they run.
- 03Map the configuration options, part number fields and quote records your product reads and writes, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Revalize integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Revalize integration without building it. Your customers connect their own Revalize 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 Revalize update is not your on-call problem.
- One integration serves your product and your agents. The same governed Revalize 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
Propel
AkeneoWorks well with
SAPOften used alongside
Tools the same teams tend to run next to Revalize, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceRevalize integration FAQ
How do I add a Revalize integration to my product?
Enable the Revalize connector in your fastn dashboard, then let each customer authenticate their own Revalize account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Revalize client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Revalize account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Revalize 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 Revalize 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 a configuration and explains which options drove the part numbers it produced.
Who maintains the Revalize integration?
fastn does. When Revalize 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 Revalize 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 Revalize 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 Revalize integration?
A common starting point: let each manufacturer connect their own Revalize environment so your product reads the product model their engineers maintain. 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 Revalize integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Revalize does not change your per-connector cost. You can start free with 3 connected accounts.
Add Revalize to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.