Content & Documents · Integration
WoodWing Studio
Add WoodWing Studio to your product for your customers, and give your AI agents governed access to it.
WoodWing Studio is the editorial side of the same house, and it is a different object model from a media library. Studio holds publications, issues and the articles and layouts that fill them, and each of those moves through a status a publisher defined for itself: written, edited, subbed, approved, placed. An embedded Studio integration creates and reads articles, reads issue and layout structure, moves an item to its next status when your product has a reason to, and lists what is sitting at each stage of the production calendar. Because this is where InDesign and InCopy work is coordinated, a layout is a real object with placed content rather than a file attachment, which is why an integration reads structure rather than downloading a document. Keep it distinct from WoodWing Assets: Studio is the workflow, Assets is the library it draws on. fastn holds each customer's credentials 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 WoodWing Studio environment so editorial work stays in the system their production team already runs.
Create an article from content your product produced, filed against the right publication and issue.
Move an item to its next status when an approval happens in your product, so both systems agree on where a story is.
Read the production calendar to show what is due for an issue and what remains unfinished.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which articles for the next issue are short of approval and who is holding them.
An agent files a drafted piece into the right publication and status inside scoped permissions, with the action logged.
An agent summarises what changed in an article between two workflow statuses.
Example prompt
What is still unapproved for next week's issue in WoodWing Studio, and who is it waiting on?
Set up WoodWing Studio in 4 steps
- 01Enable the WoodWing Studio connector in your fastn dashboard.
- 02Have each customer authorise their own Studio environment so editorial permissions stay with their team.
- 03Map that publisher's own workflow statuses, publications and article properties before you enable any writes.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the WoodWing Studio integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a WoodWing Studio integration without building it. Your customers connect their own WoodWing Studio 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 WoodWing Studio update is not your on-call problem.
- One integration serves your product and your agents. The same governed WoodWing Studio 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
WoodWing Assets
Contentful
Adobe Experience ManagerOften used alongside
Tools the same teams tend to run next to WoodWing Studio, across other categories.
Shopify
Stripe
Jira
AsanaWoodWing Studio integration FAQ
How do I add a WoodWing Studio integration to my product?
Enable the WoodWing Studio connector in your fastn dashboard, then let each customer authenticate their own WoodWing Studio account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no WoodWing Studio client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own WoodWing Studio account?
Yes. Every connection is scoped to the individual customer, so each authorises their own WoodWing Studio 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 WoodWing Studio 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 reports which articles for the next issue are short of approval and who is holding them.
Who maintains the WoodWing Studio integration?
fastn does. When WoodWing Studio 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 WoodWing Studio integration run under?
Each customer's own WoodWing Studio grant. Where WoodWing Studio 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 WoodWing Studio automatically?
Where WoodWing Studio 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 WoodWing Studio integration?
A common starting point: let each customer connect their own WoodWing Studio environment so editorial work stays in the system their production team already runs. 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 WoodWing Studio integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding WoodWing Studio does not change your per-connector cost. You can start free with 3 connected accounts.
Add WoodWing Studio to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.