Blog publishing on n8n for SiteSwarm and Duda
A marketing agency writes its clients' blog articles with blogr.ai, an AI writing tool. These two n8n workflows publish each article to the right client's SiteSwarm or Duda website automatically, keep old links working, send the new page to Omega Indexer so search engines find it, and log every article.
- Client
- Digital marketing agency, 13 client blogs
- My role
- Designed and built both workflows, then moved every blog across
- Period
- Oct to Nov 2026
- Status
- Live, 13 blogs publishing
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
All off, none deleted, so any blog can go back.
Illustration of the final result
- 13
- blogs moved, 10 on SiteSwarm and 3 on Duda
- 18 of 18
- old zaps switched off, none deleted
- 84 and 120
- automatic tests passing across the two workflows
- 255
- lines in the how-to guide
The problem
The agency published to its 13 client blogs through Zapier, with a separate copy of an 11-step automation (a "zap") for each blog. Every new client meant setting up another copy by hand. Articles sent twice had already caused duplicate posts on client blogs, and the Zapier account had used all 1,500 of its included tasks for the billing cycle and was charging for every task on top. The agency owner asked whether Zapier could be cancelled. That meant moving 13 live blogs to n8n without a missed post or a duplicate, while clients kept publishing.
The workflow
The SiteSwarm publisher (10 blogs)
The Duda publisher (3 blogs)
What I built
- One n8n workflow for the 10 blogs on SiteSwarm. It receives each article from blogr.ai, checks that it is complete and really came from blogr.ai, publishes it under the brand's author name, adds redirects so old links still work, updates the sitemap (the list of pages search engines read), sends the new address to Omega Indexer and logs the article.
- A second workflow does the same for the 3 blogs on Duda, plus a daily check that their redirects still work. The team gets an email only when one needs attention.
- No duplicates: if an article is sent again, the workflow returns the live address instead of posting it twice. An article that would change a post already live is held for a person to decide.
- Each blog can be switched on or off on its own, and its access key is never stored in readable form.
- If any run fails, the team gets one email saying what failed, with a link to the run.
- A 255-line how-to guide (a runbook) covers adding a blog, going back to the old setup and reading the log.
How the move went
- Four blogs moved first, each with a real test article and a 24-hour watch, then the rest in batches.
- A zap was switched off only after a real article had posted correctly, and none were deleted, so any blog could go back.
- Each blog's secret access key was handled inside the Zapier page, so no key was recreated or saved anywhere else.
- Posts were compared field by field with what the zap used to publish, using a script with 18 checks.
The result
All 13 blogs now publish through n8n on the agency's own server. The 18 old zaps are switched off but kept, so any blog can still go back, and adding a new client blog means following the how-to guide rather than building another zap.
Tools used
- n8n (data tables, workflows written as code)
- SiteSwarm REST API and MCP
- Duda MCP
- blogr.ai
- Omega Indexer
- Gmail
- Healthchecks.io