How to Use n8n for Comment Automation: Wiring a Moderation Queue That Runs Without You

Learning how to use n8n for comment automation gives moderation teams a way to sort, filter, and route incoming feedback before it consumes an afternoon. When comment volume grows on an editorial site, a niche publication, or a developer documentation portal, manual triage quickly becomes unsustainable. Triage drains editorial hours. It burns out community managers.

Wiring an automation workflow between your discussion platform and your team communication tools eliminates repetitive review tasks. You avoid keeping a moderation queue open in a pinned browser tab all day. Instead, you run a structured workflow that inspects context, checks commenter reputation, and routes sensitive threads to the right staff member immediately without manual sorting.

The queue you already have is the problem

Queues fail under load. On high-traffic publications and technical documentation sites, queues rarely break down because moderators lack judgment. They fail because queues force humans to perform three low-leverage tasks: sorting raw submissions, deciding which team member owns an issue, and recording decisions manually. Reading every routine compliment or repetitive support request across dozens of articles drains the editorial focus needed for genuine disputes.

Workflow automation fixes this friction. It handles three specific responsibilities in a moderation pipeline:

• Sorting: separating trusted contributors, routine technical queries, and outright abuse before an editor opens the queue.
• Routing: sending product questions to engineers, editorial critique to authors, and policy violations to senior moderators.
• Record-keeping: logging why an automated or manual decision occurred so your team maintains an auditable trail.

To implement this pipeline, you need an orchestration layer that receives comment events and coordinates with external services. The automation engine n8n fulfills this role effectively because it can be self-hosted on your own infrastructure or run in the cloud. EchoThread publishes an MIT-licensed n8n community node, @echothread/n8n-nodes-echothread, with a New Comment trigger and Approve, Reject, Mark Spam, Reply and Get actions. The EchoThread n8n node uses an EchoThread API token and needs EchoThread Starter or above. EchoThread has no Zapier or Make app.

Establish operational baselines before building. If your team has not mapped its review capacity, review our comment moderation queue throughput guide to establish baseline metrics for your human review process.

What the EchoThread n8n node actually gives you

Understanding how to use n8n for comment automation requires understanding the boundary between your commenting platform and your workflow logic. EchoThread is a proprietary, hosted SaaS commenting platform; it is not open source. Only its integrations are: the EchoThread MCP server (@echothread/mcp) and n8n node (@echothread/n8n-nodes-echothread) are MIT-licensed on GitHub.

The community node surface provides six specific primitives:

• New Comment trigger: initiates a workflow execution whenever a reader posts a comment on a selected site.
• Approve action: transitions a pending comment to published status via the EchoThread API.
• Reject action: removes a comment from the queue without permanently deleting the record.
• Mark Spam action: flags a submission and reinforces site filtering criteria.
• Reply action: posts an administrative or templated response directly to the discussion thread.
• Get action: retrieves metadata, thread context, and user history for an individual comment record.

Authentication requires an API token. You generate this credential in the EchoThread dashboard under site settings. In your n8n workspace, install the package following the standard workflow outlined in the n8n community nodes installation documentation. Once installed, create a credential record with your API token to authenticate requests across triggers and downstream actions without exposing secrets in your canvas.

The n8n comment node sits on top of a multi-tier defense architecture. EchoThread provides spam and moderation tooling in two layers: AI-assisted spam scoring through its Siftfy integration, and deterministic rules the site owner writes themselves: a restricted-words list, per-site commenter bans and trust, and auto-closing old threads. EchoThread runs the owner's restricted-words rule before the classifier, and the EchoThread moderation queue shows which of the owner's own entries fired. EchoThread is not a built-in first-party AI moderation engine, and EchoThread's owner-authored controls are rules, not AI.

When an incoming comment reaches n8n, EchoThread has already executed those initial checks. The automation workflow acts as a third layer, executing team-specific policies that simple blocklists cannot express. To configure your base deterministic rules before building workflows, follow our guide on how to set up deterministic moderation rules.

Before you build: decide what the workflow is allowed to do

Clear boundaries prevent mistakes. Automated moderation fails when teams grant workflows unrestricted authority too quickly. To preserve community trust, segment moderation decisions into three discrete operational tiers before wiring nodes together on your canvas.

1. Auto-act: actions the workflow executes without human confirmation. Restrict this tier to obvious deterministic signals, such as flagging high-confidence spam or enforcing per-site commenter bans.
2. Auto-hold: conditions that prevent a comment from appearing publicly while paging an editor. Use this for comments with external links from unverified authors or exact matches against custom phrase lists.
3. Human review: scenarios requiring contextual evaluation, such as direct complaints about authors, nuanced policy arguments, or legal pushback. Workflows route these items to a human queue without altering comment state.

Resist the urge to auto-reject comments based solely on an external probabilistic score. Machine learning models misinterpret technical jargon, dry sarcasm, and non-native phrasing. Keep your automated reject path narrow and reversible. EchoThread owners and moderators can ban or trust a commenter on a per-site basis. An EchoThread ban stops that person posting to that site only, never platform-wide, and can optionally reject that person's still-visible comments from the last 30 days. Those comments are rejected, not deleted, so the action is reversible. If an automation rule makes an incorrect judgment, an editor can restore the content directly from the dashboard.

Select your team destination early. The EchoThread n8n community node requires a personal API token and an account on the Starter plan or above, based on the official EchoThread documentation. EchoThread Starter and above allow up to 5 alert destinations per site. Alerts carry the commenter's display name, the page, and the first 300 characters of the comment, without an email or IP address. EchoThread alerts are notifications only; moderating happens in the dashboard, by email, or through the API. EchoThread does not support Telegram yet. Use n8n when you need intermediate logic: filtering notifications based on thread age, cross-referencing internal databases, or querying custom ticketing systems.

Build 1: a triage workflow that sorts the queue before anyone opens it

Triage directs comments to the people equipped to address them. A software documentation community provides a clear blueprint. Technical corrections belong in an issue tracker. Inquiries about enterprise pricing belong in a sales inbox.

Start by placing an EchoThread New Comment trigger node on your n8n canvas. Configure the credential using your EchoThread API token, select the relevant site ID, and set the trigger to fire on all incoming comments awaiting review.

Inspect the payload properties. EchoThread passes the comment body, author display name, post URL, parent comment ID, and creation timestamp. Build an initial evaluation branch checking the comment body against operational terms. For instance, if you manage technical documentation, you can identify error codes or API paths. EchoThread lets a site owner keep a restricted-words list of up to 2,000 entries, matched case-insensitively against the comment body and the author's display name. Align your n8n filter terms with your existing restricted-words list for blog comments so your workflow conditions mirror your platform settings.

Add a Switch node downstream to route messages based on the page path. When the page URL contains /docs/api/, route the payload to a branch formatted for your engineering workspace. When the URL matches an editorial opinion piece or news update, route the payload to the editorial team. Construct the payload sent to your webhook destination with concise fields: the target article title, the author name, an excerpt of the first 300 characters, and a direct URL linking back to the moderation queue in the EchoThread dashboard.

Maintain a single source of truth for moderation terms. If you configure phrase matching in both the EchoThread dashboard and within an n8n Code node, list drift will occur. Use your dashboard list for absolute boundary enforcement, and reserve n8n evaluation for routing and classification.

Build 2: auto-approve the trusted, hold the rest

Established commenters should not wait hours for a human to clear routine messages. Implementing reputation-based routing lets you automate comment moderation safely while protecting discussions from spam campaigns. Speed matters to active participants.

EchoThread includes native reputation states. EchoThread's trust setting auto-approves that person's comments on that site, bypassing pre-moderation and a restricted-word hold, but never a restricted-word reject. EchoThread seat holders cannot be banned. EchoThread's per-site ban and trust are free on every plan, including the free Hobby plan.

When an n8n workflow receives a comment event, use the Get action in the n8n comment node to fetch the author's site-level profile data. If the commenter holds trusted status, the comment has already bypassed the pending queue at the platform level. Your workflow can log the interaction and alert the author of the post that an authorized reader replied.

For untrusted or guest commenters, route the payload through an evaluation sequence before taking any action:

1. Check comment history: query your data store or internal logs to determine how many accepted comments the author has accumulated previously.
2. Scan for external links: inspect the body string for anchor tags or protocol schemes (http:// or https://). Untrusted accounts posting external URLs represent common vectors for link-building campaigns.
3. Decide state: if the author has zero prior comments and includes a link, keep the comment in the pending queue and post an alert to your internal review channel.

When an escalated comment requires human review, your workflow can notify an editor by email. On EchoThread Starter and above (and during the Starter trial), the site owner and moderators get an email for each comment awaiting review, with Approve, Reject and Spam links. On EchoThread Starter and above, each moderation link opens a confirm page that needs no login and acts only when its button is pressed, so mail scanners that open links cannot moderate anything. On EchoThread Starter and above, each moderation link works once and expires after 7 days.

Account for alert volume. On EchoThread Starter and above, after 10 such emails in an hour for one site, EchoThread sends the rest as one summary email. When building custom email steps inside n8n, incorporate a batching node during sudden spikes to prevent overwhelming editorial inboxes.

Build 3: hostile thread detection and escalation

Discussions around controversial news stories or unexpected system outages can deteriorate rapidly. In these situations, an automated system must detect sudden shifts in thread velocity and escalate the situation to an on-call team member immediately. Slow responses allow harassment to spread.

Define precise indicators for hostile or runaway discussions. A reliable trigger combines three metrics: velocity (more than 15 replies on a single thread within 30 minutes), density of held items (more than 3 comments caught by moderation rules on one page in an hour), or the presence of personal attacks flagged by your phrase list. For broader organizational protocols regarding heated community discussions, review our guide on how to implement an escalation policy for news sites.

Configure your n8n workflow to run a scheduled aggregation every 10 minutes. Use an HTTP Request node or the community node to query recent comment volume grouped by thread ID. If the count of pending flags exceeds your threshold, the workflow bypasses standard group chat channels and routes an alert directly to an on-call moderator via PagerDuty or direct message.

When personal safety or targeted harassment becomes an issue, a workflow can activate defensive measures. EchoThread provides native thread-closing settings to protect discussions. EchoThread can close a thread to new comments 30, 60, 90, 180, or 365 days after that thread was created, or leave threads open indefinitely. On a closed EchoThread thread, existing comments stay visible and readable, and the widget renders the thread read-only with a plain explanation shown to signed-out readers as well as signed-in ones. EchoThread derives the closed state at request time without writing it onto threads, so changing or clearing the setting reopens them, and a thread an owner manually re-opens stays exempt from the schedule. EchoThread's auto-close threads setting is free on every plan.

Calibrate your escalation thresholds carefully. Workflows that notify an editor for minor arguments lead to alert fatigue. When team members receive pages for ordinary disagreements, they begin ignoring critical notifications.

Testing, logging and the failure modes that bite

Real spam contains hidden Unicode characters, tracking parameters, and intentionally malformed HTML. Testing moderation automation with generic placeholder text produces brittle systems. Test your n8n workflows using historical comment data exported from your live environment or realistic staging submissions.

Maintain an execution log inside your workflow. The n8n workflow executions guide explains how to inspect and retain execution logs across complex node graphs. For every execution that alters a comment state, record four values in a persistent database or structured log aggregator:

• The EchoThread comment ID.
• The specific node or rule condition that triggered the action.
• The timestamp and n8n execution ID.
• The prior status of the comment and the resulting status.

Audit execution logs weekly. Design for idempotency. Because webhooks may retry during network drops, an automation pipeline might process the same comment event twice. Key all downstream moderation actions on the unique comment ID provided by the trigger. If an incoming event references an ID that your workflow processed within the last 10 minutes, terminate execution immediately before sending redundant messages or duplicate API calls.

Monitor your token lifecycle and rule definitions regularly. API tokens can be inadvertently revoked during site configuration updates. If a token invalidates, the EchoThread n8n node will receive HTTP 401 Unauthorized responses, halting automated triage. Audit your regular expression filters. An unescaped character in a name-matching filter can match common substrings, inadvertently holding legitimate user comments. Use the EchoThread dashboard queue to audit decisions; the queue labels each decision as the owner's own rule and displays the exact text string that matched.

What this costs, and when n8n is the wrong tool

Deploying automated infrastructure introduces hosting costs and maintenance overhead. Calculate whether your site's comment volume justifies building custom orchestration, or if native dashboard features provide sufficient control for your team.

Review the subscription tiers on the EchoThread pricing page. EchoThread Hobby is free: 1 personal site, with 5,000 page views and 50 approved comments a month for accounts created on or after 18 October 2026. EchoThread Starter is $5 a month or $50 a year for 3 sites. EchoThread Pro is $19 a month or $190 a year for 10 sites. EchoThread Business is $79 a month or $790 a year for unlimited sites. EchoThread yearly billing costs ten months' price for twelve months. Comments are unlimited on every paid EchoThread plan. EchoThread sites created on or after 1 October 2026 carry a soft monthly page-view allowance on paid plans (Starter 100,000, Pro 1,000,000, Business unlimited), while accounts created prior keep unmetered views permanently. The site owner receives an email notification when approaching and upon reaching the monthly allowance, and EchoThread hides or blocks nothing. An EchoThread customer's first payment is refundable in full for 14 days, no questions asked, via email to support.

Regarding workflow engine infrastructure, n8n provides both self-hosted options and managed plans, as detailed in the official n8n hosting guide. Self-hosting requires managing a Node.js process or Docker container, provisioning secure storage, and monitoring service uptime.

Do not over-engineer simple queues. For an independent blog receiving modest comment volume, setting up an n8n workflow adds unnecessary operational complexity. Built-in moderation features (such as approving comments directly from email confirm pages and routing native alerts to Slack or Discord) handle moderate volume efficiently. Conversely, n8n becomes valuable when you manage multiple properties, need to sync comments with a support desk, or require custom triage logic across a team of rotating moderators. For a broader comparison of external moderation strategies, read our analysis on tools to replace manual comment moderation.

A Monday morning checklist

Roll out automation methodically. If you are ready to configure comment automation this week, follow this step-by-step rollout plan:

1. Generate credentials: navigate to your site settings in the EchoThread dashboard, create an API token with appropriate permissions, and record your site identifier.
2. Install the node: add @echothread/n8n-nodes-echothread to your n8n instance and configure your credentials.
3. Build a read-only notification pipeline: create a workflow with the New Comment trigger that passes basic details (article title, author, comment excerpt) to a private review channel. Keep all action nodes disconnected.
4. Mirror your boundary rules: configure your primary phrase matching inside the EchoThread restricted-words list so the platform screens obvious violations before webhooks fire.
5. Observe for one week: allow the workflow to run purely as an observation and notification tool. Compare workflow routing against the decisions your editorial staff makes in the queue. Only connect Approve, Reject, or Mark Spam action nodes once your routing logic proves dependable.

Test every branch before launch. For additional team-based moderation frameworks, see our guide on comment moderation workflows for editorial teams.

Frequently asked questions

Does the EchoThread n8n node work on the free Hobby plan?

The EchoThread n8n community node requires a personal API token and an account on the Starter plan or above, based on the official EchoThread documentation. The free Hobby plan does not include API tokens or community node access.

Can n8n approve or reject comments automatically without a human?

Yes. The EchoThread n8n node includes explicit Approve and Reject actions. When placed downstream of your conditional logic, these nodes update the status of a comment through the EchoThread API without requiring a moderator to click a button.

What is the difference between the EchoThread n8n node and the EchoThread MCP server?

The EchoThread n8n node is an orchestration integration designed for event-driven workflows, background routing, and automated webhooks. The EchoThread MCP server (@echothread/mcp) is an MIT-licensed stdio integration that connects local AI desktop clients, such as Claude or ChatGPT desktop, directly to your comment data so an assistant can read threads and moderate through conversational prompts.

How many comments can an n8n workflow process per hour?

Comments are unlimited on every paid EchoThread plan. Workflows that trigger downstream notifications should incorporate batching logic: for example, EchoThread's native email notifications consolidate into a single summary after 10 messages within an hour for a single site to avoid flooding inboxes.

Can I use n8n with EchoThread if I do not want to self-host n8n?

Yes. You can run community nodes on n8n Cloud or on your own private infrastructure. EchoThread connects to your workflow runner over HTTPS using an API token, regardless of where your n8n instance is hosted.

Start on EchoThread Starter, create an API token, install @echothread/n8n-nodes-echothread, and run the New Comment trigger read-only for one week before you let the workflow act. Review the EchoThread pricing options before deploying your pipeline. EchoThread Starter covers three sites, and an EchoThread customer's first payment is refundable in full for 14 days.