Content & Documents · Integration
WoodWing Assets
Add WoodWing Assets to your product for your customers, and give your AI agents governed access to it.
WoodWing Assets is the digital asset management half of WoodWing, where a brand or a publisher keeps its master images, video and artwork with the metadata that makes any of it findable. An embedded Assets integration searches that library, reads and updates asset metadata, uploads new files into the folder a customer nominates, and works with versions and the check out and check in cycle that stops two people overwriting each other. Assets was sold as Swivle before it was rebuilt, and the current line is Assets 10. What shapes the build is that findability here is entirely a metadata problem: two customers describe the same photograph with different fields and different vocabularies, so search terms and field mapping are per-tenant configuration rather than anything you can settle once in code. fastn keeps each library's credentials per tenant and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own WoodWing Assets library so your product pulls approved artwork instead of a copy somebody emailed.
Search assets by the metadata fields that customer genuinely maintains, rather than by a schema you fixed in advance.
Upload a generated file into a nominated folder and set its metadata in the same step.
Read versions and check out state so your product never hands somebody a file another person is editing.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the approved image for a campaign and returns the asset rather than describing it.
An agent updates metadata on an asset within scoped permissions, with the field it changed recorded.
An agent reports which assets in a folder are missing the metadata that customer requires.
Example prompt
Find the approved product shots for this launch in WoodWing Assets and tell me which lack usage rights.
Set up WoodWing Assets in 4 steps
- 01Enable the WoodWing Assets connector in your fastn dashboard.
- 02Have each customer authorise their own Assets environment so folder permissions stay theirs.
- 03Map that customer's metadata fields and decide which folders your product may search and write into.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the WoodWing Assets integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a WoodWing Assets integration without building it. Your customers connect their own WoodWing Assets 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 Assets update is not your on-call problem.
- One integration serves your product and your agents. The same governed WoodWing Assets 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
Bynder
Cloudinary
WoodWing StudioOften used alongside
Tools the same teams tend to run next to WoodWing Assets, across other categories.
Shopify
Stripe
Jira
AsanaWoodWing Assets integration FAQ
How do I add a WoodWing Assets integration to my product?
Enable the WoodWing Assets connector in your fastn dashboard, then let each customer authenticate their own WoodWing Assets account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no WoodWing Assets 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 Assets account?
Yes. Every connection is scoped to the individual customer, so each authorises their own WoodWing Assets 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 Assets 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 image for a campaign and returns the asset rather than describing it.
Who maintains the WoodWing Assets integration?
fastn does. When WoodWing Assets 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 Assets integration run under?
Each customer's own WoodWing Assets grant. Where WoodWing Assets 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 Assets automatically?
Where WoodWing Assets 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 Assets integration?
A common starting point: let each customer connect their own WoodWing Assets library so your product pulls approved artwork instead of a copy somebody emailed. 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 Assets integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding WoodWing Assets does not change your per-connector cost. You can start free with 3 connected accounts.
Add WoodWing Assets to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.