The Duda connection publishes generated articles into your Duda site's blog through the Duda Partner API. Articles arrive with their body, description and hero image, as drafts you can open in Duda's blog editor.
New connections publish as drafts by default, so nothing goes live on your site until someone presses publish in Duda. Flip that per connection once you trust the pipeline. Duda's own import rule helps here: an imported post always lands unpublished, and going live is a separate call we make only when the connection says so.
Note: This connector was built from Duda's API reference and has not yet been watched importing a post into a live Duda site, which is why the page carries the beta label. The tile stays greyed on the Publishing grid until that happens. If you are on Duda and want to be the first, tell us.
What to know before you start
Connect it once per Duda site, before the first calendar batch for that project. Duda hands out API access per account rather than per site, so one API user can serve every site in the account; each site is still its own connection here.
The site itself has to be published in Duda for posts to be reachable. The connection test tells you if it is not.
Connect Duda
To connect Duda:
- In your Duda dashboard, request API access (under the account settings, or through Duda support if the option is not shown). Copy the API user and the API password. The password is shown once.
- Open the site in the Duda editor and copy the site name from the address bar, the short code after
/site/. - In your project's
Publishingtab, choose Duda, paste the site name, the API user and the password. Set the region toeuonly if your dashboard lives atmy.eu.duda.co. - Send a test publish and check that the post appears in Duda's blog editor as a draft.
What happens after you publish
Published articles appear in the project's content views with their publish state and, once live, their public URL. The verifier fetches that URL and records what came back. A post that Duda accepted but that never became a reachable page shows as not live, not as success.
The article's hero image is passed to Duda as the post's main image and thumbnail, so the post shares with a picture. The edited SEO title goes into Duda's own meta title field; the meta description goes into the post description, which is the one description-shaped field Duda has.
Limits and usage
- The API password is the credential. Treat it like one, and regenerate it in Duda if it leaks; the connection then needs the new value.
- Re-publishing an article creates a new post. Duda's API can update a post's title and metadata but not its body, so there is no honest way to update in place.
- Duda's blog stores the body as HTML. Structured data is appended to the body; whether Duda keeps a script tag in an imported post is not something we have verified yet.
- One connection targets one site. A second site is a second connection with the same API user.
If something isn't working
Authentication fails immediately. The API user and password were not copied whole, or the account's API access was revoked. Regenerate the pair in Duda and paste both again.
Signed in, but the test says the API user has no access to the site. The site belongs to a different Duda account, or to a client account the API user cannot reach. Use credentials from the account that owns the site.
The test says there is no site with that name. The site name is the code from the editor URL, not the site's domain. If your dashboard is at my.eu.duda.co, the region also has to be eu.
The post exists in Duda but the page 404s. The site has not been published in Duda since the post was created, or the post is still a draft. Publish the site, or switch the connection to publish live.