Threadly Now Works Inside n8n and OpenClaw — Not Just Its Own Dashboard

August 18, 2026 · Threadly Blog

The whole premise of Threadly is that a human reads every reply before it posts. That only holds up if reviewing a draft is actually convenient — not one more dashboard to remember to check. So instead of asking you to come to Threadly, we've started bringing Threadly to the tools you're probably already running.

n8n

n8n-nodes-threadly is a community node for n8n. A trigger node fires whenever Threadly discovers a new relevant conversation on X — no polling, it registers a real webhook — and action nodes let a workflow list conversations, list drafts awaiting review, and approve or reject a specific draft. If you already have an n8n instance running your other automations, this lets Threadly's output land in the same place instead of a separate tab. Source and setup instructions are on GitHub.

OpenClaw

threadly is a ClawHub skill for OpenClaw agents — the same set of operations (list conversations, list/approve/reject drafts, list published replies, manage webhook subscriptions), written as instructions an agent can follow directly. One thing we were deliberate about: the skill explicitly tells the agent to only approve or reject a draft when a human has instructed it to do so for that specific draft, in that conversation turn — never autonomously, never in a batch. An agent that can act on its own is exactly the case where the human-approval gate matters most, not least. Install it with openclaw skills install @thumbflipcontact-ops/threadly, or read the source on GitHub.

Same rule, more places to apply it

Neither integration changes what Threadly actually does: conversation discovery and reply drafting stay fully automated, and nothing posts under your account until you personally approve it. What changes is where you get to make that call — your n8n canvas, your OpenClaw agent, or Threadly's own Approval Inbox, whichever you already have open.

Start a 7-day free trial — no card required.