Data & Storage · Integration
Apptus
Add Apptus to your product for your customers, and give your AI agents governed access to it.
Embed an Apptus integration so your customers can shape their own on-site search and merchandising from inside your product rather than in a second admin tool. Apptus Technologies built e-commerce search, recommendation and merchandising, and the platform is now sold as Voyado Elevate, so a customer may know it under either name. What a deployment exposes depends on the catalogue it has been fed and the merchandising rules its team has configured, which means field discovery at connect time matters more than a fixed schema. Requests run per tenant so activity is attributable to the customer that caused it. fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers adjust their own search relevance and merchandising rules without leaving your product.
Read a customer's catalogue and category structure so your product presents only what they actually sell.
Push product or availability updates so search results follow what changed rather than a nightly rebuild.
Surface which rules are currently active so a merchandiser can see why a result ranks where it does.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains why a product is ranking low and names the rule responsible, reading the customer's own configuration.
An agent proposes a merchandising change and shows the affected results before anything is applied.
An agent checks whether a product is present and searchable in the customer's catalogue, with the read audited.
Example prompt
Which merchandising rules are affecting this product's search ranking right now?
Set up Apptus in 4 steps
- 01Enable the Apptus connector from your fastn dashboard.
- 02Have each customer authorise their own Apptus account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Apptus integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Apptus integration without building it. Your customers connect their own Apptus 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 Apptus update is not your on-call problem.
- One integration serves your product and your agents. The same governed Apptus 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
AirtableWorks well with
Shopify
SalesforceOften used alongside
Tools the same teams tend to run next to Apptus, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceApptus integration FAQ
How do I add an Apptus integration to my product?
Enable the Apptus connector in your fastn dashboard, then let each customer authenticate their own Apptus account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Apptus client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Apptus account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Apptus 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 Apptus 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 explains why a product is ranking low and names the rule responsible, reading the customer's own configuration.
Who maintains the Apptus integration?
fastn does. When Apptus 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 Apptus 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 Apptus 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 Apptus integration?
A common starting point: adjust their own search relevance and merchandising rules without leaving your product. 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 Apptus integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Apptus does not change your per-connector cost. You can start free with 3 connected accounts.
Add Apptus to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.