Data & Storage · Integration
Propel
Add Propel to your product for your customers, and give your AI agents governed access to it.
Embed a Propel integration so your product can work with the product data a manufacturer already maintains rather than asking for another export. Propel is cloud product lifecycle management built natively on the Salesforce platform, covering items and their revisions, bills of materials, change requests and change orders, and the quality records tied to them. Because it runs on Salesforce, every deployment carries its own custom fields and record types, so schema and field mapping is configuration per customer rather than a code change and a release on your side. fastn handles per-customer authorisation, pagination, throttling and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Propel org so your product reads their items, revisions and bills of materials directly.
Write attribute or status updates back so the record engineering works from stays consistent with what your product knows.
Read change orders and quality records per tenant so your product shows what is in flight on a part.
Absorb each customer's own custom fields and record types as mapping 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 an item, its revision and its bill of materials before answering a sourcing question.
An agent updates a record or opens a change request within governed permissions, with every write logged.
An agent reports which change orders are waiting on approval and who holds each one.
Example prompt
Show the bill of materials for this item's latest revision and flag any parts with an open change order.
Set up Propel in 4 steps
- 01Open the Propel connector from your fastn dashboard.
- 02Have each customer authorise their own Propel org with OAuth.
- 03Map the item, bill of materials, change and quality fields your product reads and writes, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Propel integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Propel integration without building it. Your customers connect their own Propel 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 Propel update is not your on-call problem.
- One integration serves your product and your agents. The same governed Propel 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
Salesforce
NetSuiteOften used alongside
Tools the same teams tend to run next to Propel, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FacePropel integration FAQ
How do I add a Propel integration to my product?
Enable the Propel connector in your fastn dashboard, then let each customer authenticate their own Propel account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Propel client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Propel account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Propel 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 Propel 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 an item, its revision and its bill of materials before answering a sourcing question.
Who maintains the Propel integration?
fastn does. When Propel 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 Propel 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 Propel 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 Propel integration?
A common starting point: connect their own Propel org so your product reads their items, revisions and bills of materials directly. 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 Propel integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Propel does not change your per-connector cost. You can start free with 3 connected accounts.
Add Propel to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.