Content & Documents · Integration
Bigtincan
Add Bigtincan to your product for your customers, and give your AI agents governed access to it.
Embed a Bigtincan integration so your customers can search, read, and publish their own sales content, hubs, and enablement assets from inside your product, with governed agent access to the same library. Access runs through each customer's own Bigtincan grant, so their existing content permissions apply and nothing is exposed that the connected account could not already see. fastn handles per-tenant auth and API upkeep, so a new customer's library is configuration rather than integration code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers search their own Bigtincan content library from inside your product and open the right asset in context.
Read hubs, files, and asset metadata so your product can recommend enablement content to a rep mid-workflow.
Upload new assets and update their metadata and tags from your product so the library stays curated.
Trigger your product when an asset is published, updated, or moved between hubs.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the approved asset for a deal stage and cites it in its answer.
An agent uploads a generated one-pager into the right hub within governed permissions.
An agent reacts to a newly published asset and notifies the relevant sales team.
Example prompt
Find approved competitive battlecards updated in the last quarter and list which hubs they sit in.
Set up Bigtincan in 4 steps
- 01Open the Bigtincan connector from your fastn dashboard.
- 02Have each customer authenticate their own Bigtincan account with the scopes your product needs.
- 03Map the hubs, asset types, and metadata fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Bigtincan integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Bigtincan integration without building it. Your customers connect their own Bigtincan 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 Bigtincan update is not your on-call problem.
- One integration serves your product and your agents. The same governed Bigtincan 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
BoxWorks well with
Brainshark
SalesforceOften used alongside
Tools the same teams tend to run next to Bigtincan, across other categories.
Shopify
Stripe
Jira
AsanaBigtincan integration FAQ
How do I add a Bigtincan integration to my product?
Enable the Bigtincan connector in your fastn dashboard, then let each customer authenticate their own Bigtincan account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Bigtincan client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Bigtincan account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Bigtincan 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 Bigtincan 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 finds the approved asset for a deal stage and cites it in its answer.
Who maintains the Bigtincan integration?
fastn does. When Bigtincan 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 Bigtincan integration run under?
Each customer's own Bigtincan grant. Where Bigtincan 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 Bigtincan automatically?
Where Bigtincan 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 Bigtincan integration?
A common starting point: search their own Bigtincan content library from inside your product and open the right asset in context. 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 Bigtincan integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Bigtincan does not change your per-connector cost. You can start free with 3 connected accounts.
Add Bigtincan to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.