Content & Documents · Integration
Bloomfire
Add Bloomfire to your product for your customers, and give your AI agents governed access to it.
Embed a Bloomfire integration so your customers can search and contribute to their own knowledge base from inside your product, with governed agent access to the same content. Access runs through each customer's own Bloomfire grant, so their existing permissions apply and your product cannot read a post the connected account could not read itself. fastn handles per-tenant auth and API upkeep, so onboarding another knowledge base is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers search their own Bloomfire knowledge base from inside your product and open the matching post in context.
Read posts, series, and their metadata so your product can surface the right article at the right step.
Create and update posts from your product so answers written by your users land back in the knowledge base.
Trigger your product when a post is published or updated so dependent content can be refreshed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent searches the knowledge base and cites the post it answered from.
An agent drafts a new post from a resolved question within governed permissions.
An agent reacts to a published post and notifies the teams that rely on it.
Example prompt
Search the knowledge base for posts about refund policy and list the most recently updated ones.
Set up Bloomfire in 4 steps
- 01Open the Bloomfire connector from your fastn dashboard.
- 02Have each customer authenticate their own Bloomfire community with the scopes your product needs.
- 03Map the post, series, 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 Bloomfire integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Bloomfire integration without building it. Your customers connect their own Bloomfire 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 Bloomfire update is not your on-call problem.
- One integration serves your product and your agents. The same governed Bloomfire 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
BoxWorks well with
ZendeskOften used alongside
Tools the same teams tend to run next to Bloomfire, across other categories.
Shopify
Stripe
Jira
AsanaBloomfire integration FAQ
How do I add a Bloomfire integration to my product?
Enable the Bloomfire connector in your fastn dashboard, then let each customer authenticate their own Bloomfire account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Bloomfire client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Bloomfire account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Bloomfire 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 Bloomfire 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 searches the knowledge base and cites the post it answered from.
Who maintains the Bloomfire integration?
fastn does. When Bloomfire 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 Bloomfire integration run under?
Each customer's own Bloomfire grant. Where Bloomfire 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 Bloomfire automatically?
Where Bloomfire 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 Bloomfire integration?
A common starting point: search their own Bloomfire knowledge base from inside your product and open the matching post 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 Bloomfire integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Bloomfire does not change your per-connector cost. You can start free with 3 connected accounts.
Add Bloomfire to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.