Content & Documents · Integration
Duda
Add Duda to your product for your customers, and give your AI agents governed access to it.
Duda's API lives at api.duda.co/api and authenticates with HTTP Basic using an API user and password issued per account, with a separate api.eu.duda.co host for accounts provisioned in the EU region that will simply reject credentials issued on the other one. Every call is keyed on site_name, which is a generated identifier and not the site's domain, so any integration has to store that mapping when the site is created rather than deriving it later. Editing content and publishing are distinct steps: writes to pages and to the content library sit in the draft site until you call the publish endpoint, so a customer who does not see their change live is usually looking at an unpublished draft. Collections back Duda's dynamic pages, which means a bulk content sync is a collection row write rather than a page write, and the page templates then render from it. The nouns here are documents and versions in a loose sense only; the real objects are sites, pages and collection rows, which is worth saying plainly. fastn holds each customer's Duda credential, routes to the right regional host, and keeps the connection alive without you building account-level key storage.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Duda account so your app can create and update sites under their reseller plan.
Push product or listing data into a Duda collection so their dynamic pages regenerate from your system.
Update page content and site business details from your product, then trigger a publish when the customer approves.
Report which of a customer's sites are published, unpublished or still in draft inside your own dashboard.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent draft content library changes for a named site and require a human to trigger the publish step.
Have an agent audit which sites have unpublished drafts across a tenant, with the read logged per tenant.
Allow an agent to update a site's business address or opening hours across every page that renders them.
Example prompt
Which Duda sites in this account have draft changes that were never published?
Set up Duda in 4 steps
- 01Enable the Duda connector from your fastn dashboard.
- 02Have each customer authorise their own Duda account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Duda integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Duda integration without building it. Your customers connect their own Duda 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 Duda update is not your on-call problem.
- One integration serves your product and your agents. The same governed Duda 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
Box
DocusignOften used alongside
Tools the same teams tend to run next to Duda, across other categories.
Shopify
Stripe
Jira
AsanaDuda integration FAQ
How do I add a Duda integration to my product?
Enable the Duda connector in your fastn dashboard, then let each customer authenticate their own Duda account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Duda client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Duda account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Duda 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 Duda integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent draft content library changes for a named site and require a human to trigger the publish step.
Who maintains the Duda integration?
fastn does. When Duda 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 Duda integration run under?
Each customer's own Duda grant. Where Duda 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 Duda automatically?
Where Duda 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 Duda integration?
A common starting point: let a customer connect their own Duda account so your app can create and update sites under their reseller plan. 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 Duda integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Duda does not change your per-connector cost. You can start free with 3 connected accounts.
Add Duda to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.