Duda

· #307 most-used

Build, publish, and automate client websites at agency scale

MarketingEcommerceDesignAutomationWebsite & CMSNo-Code

Duda is the website builder platform built for digital agencies and SaaS companies that need to create, manage, and publish professional websites at scale. Its REST API and webhook system let agents provision new client sites from templates, publish blog posts, manage Duda client records, update site-wide content placeholders, and sync collection data — all without opening the Duda editor. Connect Duda to Actionist and your agents can automate the full client website lifecycle: site creation at deal close, content publishing from your calendar tool, form lead routing to the CRM, store order fulfilment, and portfolio health monitoring across every client site.

Try Duda with Actionist Visit Duda

Average time saved

10 hours

per person · per month

≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of logging into the Duda dashboard to provision sites, publish blog posts, check form submissions, monitor site comments, and update client records — tasks that individually take 5–20 minutes but accumulate to hours across a typical agency portfolio.

Schedule

What your Duda agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs

7Agents at work

24/7Always on

Agents

Tue–Thu

Tue

Wed

Thu

10a

11a

12p

Multi-app workflows

Duda × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows

6Apps spanned

~27 hrsSaved / week

6Personas served

For agency operations

Featured4 apps

New client site live the moment a deal closes

When a deal closes in HubSpot, the agent creates the Duda client record, provisions a site from the right template, injects the client's brand details into the Content Library, posts the editor link to Slack, and logs everything to the onboarding sheet — a fully set-up client site before anyone opens their email.

~6 hrs

Time saved for your team — every week, on autopilot

The flow

Trigger·When a HubSpot deal moves to Closed Won

Trigger

Step 1

HubSpot

Deal stage changes to Closed Won

write

Step 2

Duda

Create a Client with the deal contact's name, email, and company

write

Step 3

Duda

Create a Site from the industry-appropriate template

write

Step 4

Duda

Update Content Library with the client's business name, phone, and logo URL

write

Step 5

Slack

Post new client site URL to #new-clients with editor link

write

Step 6

Google Sheets

Log client name, site name, and Duda editor URL to the onboarding sheet

Result

Create a Client with the deal contact's name, email, and companyCreate a Site from the industry-appropriate templateUpdate Content Library with the client's business name, phone, and logo URLPost new client site URL to #new-clients with editor linkLog client name, site name, and Duda editor URL to the onboarding sheet

The win

Saved per run

45 min

Runs / week

~8×

Project team has a provisioned site before they read the welcome email

Driven bySales Agent

ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

Sales
25 min / week
Manual site setup after deal close
The account manager logs into Duda, selects a template, types the client name, adds their email, and then separately updates the brand placeholders — a 20-minute manual task per new client.
Sales Agent
0 min
Agent provisions site at deal close
When a deal closes in HubSpot, the agent creates the Duda client and site from the right template and injects brand details — a ready-to-design site exists before the project manager reads the notification.
Marketing
30 min / week
Manual blog post entry in Duda
Content writers or coordinators log into the Duda editor, copy text from the approved document, paste it into the blog post interface, add the thumbnail, set the author, and schedule — 15 minutes per post.
Marketing Agent
0 min
Agent publishes from the content calendar
When a content calendar row is marked Ready to Publish, the agent creates the blog post in Duda with the approved copy, author, and publish date — the content team never opens the Duda editor.
Customer Support
20 min / week
Manual comment monitoring
Project managers log into each client's Duda site to check for new comments, copy the text into a task, and notify the team — a daily sweep that misses overnight feedback until someone logs in.
Customer Support Agent
0 min
Agent routes site comments to tasks instantly
When a client leaves a comment in the Duda editor, the agent creates a revision task in the project tracker and posts to Slack — the team sees client feedback within about a minute without checking Duda.
Human Resources
15 min / week
Manual team page updates
HR or marketing staff log into the Duda editor, navigate to the team section, add the new hire's name, title, and headshot, and publish — 10 minutes per hire, plus delays when no one is available to do it.
Human Resources Agent
0 min
Agent updates team directory collection automatically
When a new hire is added to the HR system, the agent adds their profile to the Duda team collection — the public directory reflects the change within about a minute, no editor login needed.
Finance
20 min / week
Manual order export and logging
Finance staff log into the Duda store interface, export orders, and paste them into the revenue spreadsheet — a daily manual task that creates a 24-hour lag in the finance team's data.
Finance Agent
0 min
Agent logs store orders to finance sheet automatically
When a Duda native store order arrives, the agent appends it to the revenue tracking sheet with customer details and order total — no one checks the Duda dashboard to capture revenue.
Operations
35 min / week
Manual portfolio audit
An operations team member logs into Duda, opens each client site, and manually checks publish status and domain connection — a 90-minute Monday morning task for agencies with 30+ client sites.
Operations Agent
0 min
Agent syncs portfolio health from Duda to the tracker
Every Monday, the agent lists all Duda sites, checks publish status and domain connections, and flags any issues to the operations team — a full portfolio audit before the morning standup, with no manual login.
Legal
18 min / week
Manual policy page updates
Legal or operations staff log into each client site individually, navigate to the privacy policy or terms page, update the text or link, and publish — 10 minutes per site for a regulatory change that affects all clients.
Legal Agent
0 min
Agent pushes policy updates site-wide in one call
When a policy update is needed, the agent calls Update Content Library for all active client sites simultaneously — updated legal copy is live site-wide before the legal team finishes their morning coffee.

+ 100s of other Duda automations

Average time saved

16 hrs / person / month

Calculator

Calculate what your team saves

Team size

5 people

Hourly rate

$75 / hr

Hours saved / week

Hours saved / year

625

Annual ROI

$46,875

Based on Duda's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Duda into Actionist

Pick the connection method that suits your environment.

Connect using your Duda API User and API Key from Account Settings → API Access. Requires a Duda Team or Agency plan. Actionist uses HTTP Basic Auth with these credentials for all API calls.

Find your API credentials

Log in to your Duda account. Navigate to Account Settings → API Access. Note your API User and generate an API Key if you haven't already. API access requires a Duda Team or Agency plan.

Copy your API User and API Key

Copy your API User (this is typically your account email or a dedicated API user identifier) and your API Key.

Paste into Actionist and test

Paste both credentials into Actionist and click Test connection. Actionist makes a read-only test call to verify access before any actions run.

Credentials you'll need

API User*

Duda account → Account Settings → API Access → API User

API Key*

Duda account → Account Settings → API Access → API Key

Actions

14 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

FAQs

Questions about Duda + Actionist

How does Actionist connect to Duda?

Go to the Apps tab in Actionist, find Duda, and click Connect. Enter your Duda API username and API key (found in your Duda account under Account Settings → API Access). Actionist runs a test call to verify the credentials before any actions run. You'll need a Duda Team or Agency plan to access the REST API.

What credentials and plan level do I need for the Duda API?

Duda's REST API uses HTTP Basic Authentication with your API user and API key. These credentials are tied to your Duda account and carry the same permissions as your account role. API access is available on Duda Team and Agency plans. Webhook-based triggers require you (or Duda support for older accounts) to register an HTTPS endpoint on your account.

Can I connect Duda to other apps in the same agent task?

Yes. Duda is most powerful when combined with the tools your agency already uses. Common combinations: create a Duda site when a new client is won in HubSpot or Pipedrive; push new store orders to a Google Sheet; notify your team in Slack when a form submission or blog post is published; sync client details from your CRM into Duda's client management system. Any of Actionist's connected apps can participate in the same agent task alongside Duda.

What are the most common things agents do with Duda?

The four patterns agencies use most often: (1) site creation automation — spawn a new site from a template the moment a client contract is signed; (2) content pipeline — publish approved blog posts to Duda on a schedule without logging in; (3) order routing — when a native store order arrives, push it to fulfilment tools like a Google Sheet or Slack channel; (4) client onboarding — create the Duda client record, invite them, and notify the project manager, all in one coordinated sequence.

Can the agent create a branded Duda site from a template automatically?

Yes. The Create a Site action lets you specify a template name or template ID, the site's default domain, and initial metadata. You can also immediately update the Content Library for that new site in a follow-up step, injecting the client's brand name, logo URL, and contact details — so the agent delivers a pre-populated site rather than an empty shell.

How quickly do Duda webhook triggers fire after an event?

Duda's webhook events fire within about a minute of the triggering action inside the editor or via the API. For Published Blog Post, New Form Response, New or Updated Site Comment, Member events, and store events, the agent receives a payload and can immediately execute downstream actions — notifying a Slack channel, logging to a CRM, or updating a Google Sheet.

How does the Add Collection Row action work, and when would I use it?

Add Collection Row lets the agent append structured data to any Duda Collection (what Duda calls site databases or content collections). This is useful for keeping a site's dynamic content — a team directory, a product catalogue, an events list — up to date from external sources without anyone logging into the Duda editor. Pair it with a Google Sheets trigger or a scheduled agent task to push new rows on a defined cadence.

When should I use Update Content Library versus editing a specific page?

Update Content Library modifies the shared content placeholders used across all pages of a Duda site — things like the business name, phone number, address, hours, and logo. This action is the right choice when you need to push a content change that should propagate site-wide rather than editing a specific page or section. It's particularly useful for keeping franchisee or multi-location sites in sync when contact details change.