Content & Documents · Integration
Kapost
Add Kapost to your product for your customers, and give your AI agents governed access to it.
Embed a Kapost integration so your customers can manage their own marketing content operations from inside your product. Access runs through each customer's own Kapost account, so their existing permissions apply and your product cannot read content the connected account could not read itself. fastn handles per-customer authentication, field mapping, and API upkeep, so a team with its own content types and stages needs no code from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own content assets into your product, mapped to their own fields.
Create or update a content item from your product so a request becomes real work without re-entry.
Read production status and stage so content progress is visible where users already work.
Read asset metadata and tags so your product can group content the way the customer does.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a content item and its status before it summarises what is ready to publish.
An agent updates an asset's metadata or stage within governed permissions, with each action logged.
An agent finds content items stalled at a stage and reports who owns each one.
Example prompt
List content items that have been in review for more than a week and show the owner of each.
Set up Kapost in 4 steps
- 01Open the Kapost connector from your fastn dashboard.
- 02Have each customer authenticate their own Kapost account.
- 03Map their content types, stages, and metadata fields, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Kapost integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Kapost integration without building it. Your customers connect their own Kapost 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 Kapost update is not your on-call problem.
- One integration serves your product and your agents. The same governed Kapost 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
Contentful
Adobe Experience ManagerWorks well with
MarketoOften used alongside
Tools the same teams tend to run next to Kapost, across other categories.
Shopify
Stripe
Jira
AsanaKapost integration FAQ
How do I add a Kapost integration to my product?
Enable the Kapost connector in your fastn dashboard, then let each customer authenticate their own Kapost account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Kapost client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Kapost account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Kapost 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 Kapost 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 reads a content item and its status before it summarises what is ready to publish.
Who maintains the Kapost integration?
fastn does. When Kapost 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 Kapost integration run under?
Each customer's own Kapost grant. Where Kapost 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 Kapost automatically?
Where Kapost 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 Kapost integration?
A common starting point: read their own content assets into your product, mapped to their own fields. 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 Kapost integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Kapost does not change your per-connector cost. You can start free with 3 connected accounts.
Add Kapost to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.