Content & Documents · Integration
Uberflip
Add Uberflip to your product for your customers, and give your AI agents governed access to it.
Uberflip is where marketing content gets arranged for someone to read, so the pieces are a hub, the streams inside it and the items those streams hold. Source streams pull items in from wherever the content already lives, a blog feed, a video channel, a document library, while marketing streams curate a selection of those items for one audience, and calls to action sit among them as tiles that ask the reader to do something. An embedded Uberflip integration reads what a customer has published, creates and updates items and streams so a collection your product assembled becomes a real destination, applies the tags that decide what appears where, and reads engagement back so you can tell which content actually held attention. An item can be a copy of something published elsewhere, so its identity in Uberflip is not the same as its identity at the source. fastn holds the token per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Uberflip account so content experiences are assembled where your users already work.
Create a stream and fill it with the items your product selected, so a curated collection becomes a page a reader can open.
Apply tags so an item appears in the streams a customer's own taxonomy says it belongs to.
Read engagement per item so your product can tell which content was read rather than only which was published.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent assembles a stream for an account from items already in the hub and shows it for review before publishing.
An agent reports which items get read to the end and which are opened and abandoned.
An agent tags or updates an item within scoped permissions, with the hub it wrote to recorded.
Example prompt
Which items in this hub held attention longest last month, and which streams are they in?
Set up Uberflip in 4 steps
- 01Enable the Uberflip connector in your fastn dashboard.
- 02Have each customer authorise their own Uberflip account so their hubs and streams stay theirs.
- 03Map the hubs, streams, tags and item attributes your product uses, per customer, as configuration.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Uberflip integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Uberflip integration without building it. Your customers connect their own Uberflip 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 an Uberflip update is not your on-call problem.
- One integration serves your product and your agents. The same governed Uberflip 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
SeismicOften used alongside
Tools the same teams tend to run next to Uberflip, across other categories.
Shopify
Stripe
Jira
AsanaUberflip integration FAQ
How do I add an Uberflip integration to my product?
Enable the Uberflip connector in your fastn dashboard, then let each customer authenticate their own Uberflip account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Uberflip client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Uberflip account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Uberflip 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 Uberflip 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 assembles a stream for an account from items already in the hub and shows it for review before publishing.
Who maintains the Uberflip integration?
fastn does. When Uberflip 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 Uberflip integration run under?
Each customer's own Uberflip grant. Where Uberflip 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 Uberflip automatically?
Where Uberflip 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 Uberflip integration?
A common starting point: let each customer connect their own Uberflip account so content experiences are assembled where your users already work. 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 Uberflip integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Uberflip does not change your per-connector cost. You can start free with 3 connected accounts.
Add Uberflip to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.