Learn the practical workflow for receiving comments and filtering spam. Automate the entire process including drafting and posting replies.
It is lightweight, privacy-first, and easy to set up. This makes it a perfect first step for blog comment automation.
Once traffic grows or you want more control over operations and data, self-hosting becomes the natural next move.
Automation using webhook mechanisms and n8n workflows
When a comment is posted, Cusdis sends an event to the configured webhook API URL. We show how to set up a webhook in n8n to receive these events and build a workflow for automated processing.
If speed matters most, n8n Cloud is the smoother path. Self-hosting with Docker Compose means you own the exposure, upgrades, and security decisions.
WEBHOOK_URL=https://your-domain.com/ N8N_PROXY_HOPS=1
Replace 'your-domain.com' with the domain your n8n instance is running on.
If you are new to operations, start on n8n Cloud and move to self-hosting after the workflow has proven itself.
Cusdis webhooks need a reachable HTTPS URL. Expose your n8n instance safely using modern tunneling technology.
Self-hosted instances are usually hidden behind local networks. Since n8n practically requires HTTPS for security and reliable communication, setting up a Domain+HTTPS path is critical. Using Cloudflare is one of the easiest and most reliable ways to achieve this.
If your domain is already managed by Cloudflare, one Tunnel is all you need to expose an internal service safely — no extra server required. Unlike ngrok, the URL is stable and free.
Connect your comment system to your automation engine. Let's set up the webhook URL so n8n knows when a new comment arrives.
The Webhook node starts the entire automation flow. It is the entry point that listens for incoming signals from Cusdis.
The important part is constraining the model to return a clean JSON contract.
You are an AI assistant helping the blog owner.
Read the comment below, decide whether it is spam, and if it is a normal comment, write a short thank-you reply. (The reply should be friendly, 1-2 sentences long, and match the language of the comment.)
Comment: "{{ $json.body.data.content }}"
[Output rules]
Return exactly one pure JSON object with the structure below. Do not wrap it in Markdown.
Comment: "{{ $json.body.data.content }}"
[Output rules]
1. Return only JSON (rfc8259), with no explanation and no markdown fences.
2. Follow the JSON schema below exactly.
{
"result": "NORMAL" or "SPAM",
"reply": "The drafted reply text (empty string for SPAM)",
"approved_link": "{{ $json.body.data.approve_link }}"
}JavaScript avoids extra Python setup on a self-hosted box. Parse failures are intentionally absorbed as `ERROR`.
for (const item of $input.all()) {
try {
// Result from gemini : $json.content.parts[0].text
let rawText = item.json.content.parts[0].text;
// 2. Remove markdown letters and trim
rawText = rawText.replace(/```json/g, "").replace(/```/g, "").trim();
const parsedData = JSON.parse(rawText);
const originalLink = parsedData.approved_link;
const apiLink = originalLink.replace("/open/approve", "/api/open/approve");
item.json.ai_result = parsedData.result;
item.json.ai_reply = parsedData.reply;
item.json.ai_api_link = apiLink;
item.json.ai_approve_link = parsedData.approved_link;
} catch (error) {
item.json.ai_result = "ERROR";
item.json.ai_approve_link = "";
}
}
return $input.all();The clean path only proceeds if Gemini says the message is "NORMAL". This keeps spam from ever hitting your blog or causing delays in n8n.
Replying instantly feels robotic. A random delay makes the response feel like it came from a real person.
{{ Math.floor(Math.random() * (60 - 10 + 1)) + 10 }}The final payload is ready to go! Send the approval and reply, then publish your workflow for live operation.
{"replyContent":"{{ $json.ai_reply }}"}Congratulations! Your blog now has a smart automation loop for comment moderation.
Was this useful? If there is another lecture you want next, email [email protected].
Follow along here as well
Build an end-to-end comment moderation flow with n8n, Gemini, and Cusdis.
A practical beginner-friendly course for automating blog comment operations, from webhook wiring and AI moderation to conditional routing, approval APIs, and ops checklists.
Deliverable: a production-minded workflow that analyzes, delays, approves, and replies to safe comments automatically.
Clarify the roles of Cusdis, n8n, and Cloudflare Tunnel before touching the workflow details.
Connect Cusdis comment events to the first Webhook node in n8n.
Force the AI into a strict JSON contract and normalize it with defensive JavaScript.
Route only safe comments forward, wait for a natural delay, then send approval and reply requests.
Review the failure points, rollout checks, and next automation ideas needed for production.