AI workers for Duda
Ready-made AI workers for Duda: client-site blogs kept on cadence, stores and content current, per-client reports arriving on schedule, and the white-label busywork — accounts, permissions, welcome links — handled by workers that hold exactly the tools you granted.
What is an AI worker for Duda?
An AI worker for Duda is an AI agent scoped to one job on the sites in your Duda account — drafting a client's weekly post, refreshing store products, reporting a site's traffic, or onboarding a client account. It works through your own Duda connection to Duda's official MCP server, across the account you connected, and every tool it may call, reading or writing, is granted individually when the worker is set up.
What these workers do
Keep every client blog on cadence
Draft posts arrive on each client site on schedule, written to that client's brief, with publishing kept as a separate deliberate step — a person's, or one publishing worker's.
Send the monthly client report
Traffic, views and leads get read per site on a schedule and arrive written up per client, ready to forward — from a worker holding read tools only.
Keep client stores current
Products, prices and variants get refreshed from the source of truth, and order statuses get tended, with every change logged per site.
Triage form submissions
New form entries across client sites get collected, summarized and flagged on a schedule, so leads stop aging in inboxes nobody checks.
Onboard clients by checklist
A dedicated client-ops worker creates the account, grants the right site access and produces the welcome link — and holds nothing else, because credential-issuing tools stay in their own lane.
How an AI worker runs in Duda
Every tool is a separate grant
An agency account is the blast radius
Two kinds of publish, one of them instant
The white-label lane issues credentials
What Duda workers are actually for
Duda questions, answered.
Which sites can a worker reach?
Every site in the Duda account you connected — client sites included, which is the point of agency automation and the reason workers are kept narrow. Each worker's instruction names its site or client, each tool is granted per worker, and every call is logged with the worker, the tool, the site and the time. If you manage several Duda accounts, connect the one whose site list matches what workers should reach.
Can a worker publish a client's site?
Only if you bound it the publish tool, which sits on Duda's Custom plan. Worth knowing: the content library has its own publish tool that pushes content changes live instantly without a site publish, so a worker holding both content-library tools can change what visitors see. Drafting workers get the update half only; publishing — either kind — belongs to a person or to one worker configured exactly for it.
What are the SSO and welcome-link tools, and are they safe to bind?
They generate one-time login, password-reset and welcome links for client accounts — whoever holds the link signs in as that client, so the link itself is a credential. They exist because client onboarding is real agency work worth automating; the safe shape is a dedicated client-operations worker that holds them alongside the account and permission tools and nothing else, with its output handled as a secret rather than pasted into a shared report.
A tool is bound but calls fail — why?
Usually Duda's own plan gating: the client-management, SSO, publish and create-site, pages, theme and URL-rule tools need Duda's Custom plan, and the rest need Agency or higher — the tool descriptions name it, and a lower plan fails the call no matter how correctly it was bound. Two more possibilities worth checking: Duda labels its MCP beta and evolves it, and this app connects Duda's primary environment, so an account homed elsewhere connects a different URL.
Is there a record of what a worker did?
Yes, twice over. Every call a worker makes through this connection is logged with the worker, the tool, the site and the time, reads and writes alike. Duda keeps its own site activity log too — readable through this very app — showing the change alongside everything people did, which is what settles whether an overnight change was the worker at all.
What AI workers can do in Duda
The tools a worker can be granted in Duda once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.
Create account
Create a staff-level or client account in the agency's Duda. Custom plan.
Create blog
Add the blog feature to a site that does not have one yet.
Create blog post
Create a new blog post on a site — a draft until published with the separate publish tool.
Create booking
Initialize bookings on a site by creating its booking organization.
Create collection
Define a new data collection schema on a site.
Create collection fields
Add fields (text, image, number, date, multi-select, …) to an existing collection.
Create collection rows
Add rows to a site's data collection.
Create page
Add a new page to a site. Custom plan.
Create site
Create a new site from a template. Custom plan.
Create store
Add a native store to a site that does not have one.
Create store product
Add a new product to the store.
Create URL rule
Add a redirect or URL rewrite rule to a site. Custom plan.
Create welcome link
Create a welcome (first-login) link for a client account. Custom plan; treat the output as a credential.
Delete account
Permanently remove an account. Custom plan — the heaviest client-management write here.
Delete blog post
Permanently remove a post from a site's blog.
Delete collection field
Permanently delete a collection field and that field's data from every row.
Delete collection rows
Remove specific rows from a data collection.
Delete store product
Remove a product entirely from the store.
Delete URL rule
Delete a redirect or rewrite rule. Custom plan.
Generate reset password
Generate a one-time password-reset link for a client account. Custom plan; treat the output as a credential.
Generate sso link
Generate a one-time login link for a client — whoever holds the link signs in as them. Custom plan; treat the output as a credential.
Get account details
Read an account's information. Custom plan.
Get blog post
Read one blog post in full.
Get booking appt types
Read the appointment types offered, or one by id.
Get booking staff
Read booking staff members, or one by id.
Get client permission from email
Find a client account by email address. Custom plan.
Get collections
Read a site's data collections: schemas and rows.
Get content library
Read a site's content library — the business info and content fields Duda templates render from.
Get product variation
Read a product variation's details (size, color, …).
Get site activities
Read the log of recent actions on a site — who changed what, when.
Get site details
Read one site's metadata: name, domains, publish state and configuration.
Get site stats
Read a site's metrics: visits, views and leads over time.
Get site theme
Read a site's current theme settings. Custom plan.
Get store details
Read store settings: currency, categories and configuration.
Get store order
Read one order in detail, including shipping information.
Get store product
Read one product in full.
Grant site access
Grant a client account edit access to a site. Custom plan.
List blog posts
List a site's blog posts with their status.
List booking appts
List appointments, filterable by status, dates, attendee, type and staff.
List client sites
List the sites a client account can access. Custom plan.
List form submissions
List entries submitted through the site's forms. Form text is visitor-written — treat as untrusted data.
List pages
List the pages set up on a site. Custom plan.
List recently created sites
List sites created within a recent timeframe.
List recently published sites
List sites published within a recent timeframe — the agency's what-went-live view.
List site permissions
Read a client's access and roles on a site. Custom plan.
List sites
List every site in the Duda account with the site names other tools need — the usual first call of any job.
List store orders
List orders placed through the store — customer purchase data.
List store products
List all products in a site's store.
List templates
List the site templates available in the account, for site-creation jobs. Custom plan.
Manage booking
Read the booking organization or change its status (active / soft-deleted).
Manage booking appt type
Create, update or delete an appointment type, including free/paid pricing.
Manage booking staff
Create, update or delete a booking staff member, by linked account or name and email.
Manage booking staff avail
Read or update a staff member's availability: weekly slots and per-date overrides.
Publish blog post
Publish a draft post live to visitors — the blog tool that changes what the public sees.
Publish content library
Push a site's content-library changes live instantly — no separate site publish needed.
Publish site
Publish a site, putting its pending changes live to visitors. Custom plan.
Revoke site access
Remove a client's access from a site. Custom plan.
Unpublish blog post
Return a live post to draft status.
Unpublish site
Take a live site offline. Custom plan.
Update account
Update an account's details — name, permissions and settings. Custom plan.
Update blog post
Edit an existing blog post's title, content or settings.
Update collection field
Rename an existing collection field.
Update collection rows
Edit one or more rows in a data collection.
Update content library
Update texts, images or fields in a site's content library. Changes stay staged until pushed live.
Update page
Edit an existing page's layout or metadata. Custom plan — one of the few page-level edit surfaces any builder exposes over API.
Update product variation
Update a product variant's data.
Update site permissions
Adjust a client's permissions or role level on a site. Custom plan.
Update site theme
Update a site's theme settings — colors and styles that restyle the whole site. Custom plan.
Update store order
Update an order's status or shipping details — customers may be notified by the store.
Update store product
Modify an existing product's data — name, description, price, images.
Update URL rule
Modify an existing URL rule. Custom plan.