Content & Documents · Integration
ConversionTools
Add ConversionTools to your product for your customers, and give your AI agents governed access to it.
ConversionTools splits every job into three calls: upload the file to get a file id, create a task naming the conversion type and its options, then poll that task until it reports success and hands back an output file id to download. There is no synchronous convert endpoint, so even small files go through the queue and callers must treat conversion as asynchronous. Authentication is a bearer token, and an unauthenticated request returns a JSON body complaining about an invalid user id rather than a conventional 401 message. Each conversion type takes its own options object, so an XML-to-CSV task accepts different keys from an Excel-to-JSON one and unknown keys are rejected outright. Uploaded inputs and generated outputs are removed after a retention window, so a download cannot be deferred indefinitely. fastn keeps each customer's token, drives the upload, task and poll cycle and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own ConversionTools account so conversions run on their quota and retention terms.
Turn a supplier XML feed into CSV automatically whenever a new file lands in your product.
Generate PDF output from customer-supplied spreadsheets without shipping a conversion library yourself.
Poll task status and surface a clear failure reason when a malformed input is rejected.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to convert an attached file and return the output link, with each task audited per tenant.
Have an agent check the status of a queued conversion and report why it failed.
Let an agent pick the right conversion type and options for a file the user described in plain English.
Example prompt
Convert this supplier XML feed into a CSV I can open in Excel.
Set up ConversionTools in 4 steps
- 01Enable the ConversionTools connector from your fastn dashboard.
- 02Have each customer authorise their own ConversionTools account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions 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 ConversionTools integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a ConversionTools integration without building it. Your customers connect their own ConversionTools account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a ConversionTools update is not your on-call problem.
- One integration serves your product and your agents. The same governed ConversionTools connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to ConversionTools, across other categories.
Shopify
Stripe
Jira
AsanaConversionTools integration FAQ
How do I add a ConversionTools integration to my product?
Enable the ConversionTools connector in your fastn dashboard, then let each customer authenticate their own ConversionTools account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ConversionTools client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ConversionTools account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ConversionTools account and only ever sees their own files, documents and versions. 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 ConversionTools integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to convert an attached file and return the output link, with each task audited per tenant.
Who maintains the ConversionTools integration?
fastn does. When ConversionTools 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.
Whose permissions does the ConversionTools integration run under?
Each customer's own ConversionTools grant. Where ConversionTools holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in ConversionTools automatically?
Where ConversionTools supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the ConversionTools integration?
A common starting point: let a customer connect their own ConversionTools account so conversions run on their quota and retention terms. 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 ConversionTools integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ConversionTools does not change your per-connector cost. You can start free with 3 connected accounts.
Add ConversionTools to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.