Spam filters only catch the obvious
Generic praise with a link in the author URL passes most filters and still wastes your time.
Comment moderation is a queue that only grows. Spam filters catch the obvious cases and leave a long tail of plausible-looking junk, while genuine questions from readers sit unanswered in the same list. Talos triages the queue with actual judgement about content, and can run the moment a comment is posted.
Generic praise with a link in the author URL passes most filters and still wastes your time.
A reader asking something genuinely useful sits in the same undifferentiated list as forty pieces of junk.
So the queue reaches four hundred and then it is a project rather than a task.
Hook the workflow to comment posting so triage happens immediately, with cooldowns and concurrency limits preventing a flood.
Talos reads the comment against the post it was left on, which is how you tell a real question from generic filler with a link.
Approve, hold or spam through manage_comments. Deletion can be withheld entirely, so the worst case is a comment left pending.
Genuine questions get reported so you can reply, rather than being approved and forgotten.
Talos does not improvise. Each of these is a defined tool with validated inputs, a declared risk level and its own policy setting.
Hook-triggered workflows have cooldowns and concurrency limits, so a spam burst cannot trigger hundreds of simultaneous runs.
See the full tool catalogList, read, create, edit, moderate, trash, restore and delete comments.
Load a single post or page by ID.
Keyword search across posts, pages and public post types.
Draft and inspect scheduled or hook-triggered workflows. Drafting counts as a write.
Inline structured report cards for security, SEO, health and other audits, with file and line evidence.
Inline structured data tables.
Any of this can become a workflow. You write the prompt, choose the trigger, and lock the permissions before it ever runs.
How workflows workHook · wp_insert_comment
“Read the new comment and the post it was left on. If it is spam or generic filler with a promotional link, mark it as spam. If it is a genuine question, leave it pending and note it for the daily digest. If it is a normal relevant comment, approve it.”
Immediate triage, with questions collected into a daily digest.
Triage happens on posting, not on a backlog sweep
Comments judged against the post they were left on
Deletion permission withheld — worst case is pending
Real reader questions surfaced for a reply
Spam is a recoverable state in WordPress, not a deletion, so you can restore it from the comment screen. If you would rather be cautious, scope the workflow to hold rather than spam and review the held queue yourself.
No, and running both is the better setup. Let your spam filter catch the high-volume obvious cases cheaply, and let Talos apply judgement to the ambiguous remainder it leaves behind.
Hook-triggered workflows enforce cooldowns and concurrency limits, and there is a site-wide rate limit of 30 runs per hour by default plus a per-run token budget. A burst gets throttled rather than billed.
Put recurring WordPress work on a schedule. Talos runs scoped workflows in the background, emails you a report, and never expands its own permissions.
Read moreModes, per-tool policy, approval gates, roles and budgets.
Read moreReorganize taxonomies, fix hundreds of posts, clean up drafts and migrate content structure by describing the outcome instead of writing SQL.
Read moreSpend less time clicking through admin and more time moving your site forward.