OtherReal-timeUpdated May 2026

Disqus

Disqus blog comment system

Disqus is the embeddable comment system widely used on blogs, news sites, and content platforms — a JS snippet adds comment functionality to any page. Tiny Command exposes one action, no triggers (Disqus has webhook configuration for new comments; point at a Tiny Command webhook trigger URL): List Items (recent comments on a forum or thread). The connection uses Disqus API credentials. For workflows that moderate comments programmatically (flag spam, surface engagement signals, sync comment counts to a database), Disqus's API is the source. Note: Disqus has been criticised in recent years for ad injection and tracking — many publishers have migrated to alternatives (Hyvor Talk, Commento, native Mastodon/Bluesky comments). For workflows on legacy Disqus-using sites, this connector works; for new sites, consider alternatives.

Connect Disqus

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Disqus can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
List Disqus Comments	Returns recent comments on a forum or specific thread. Useful for "moderate flagged comments" workflows or for "sync comment counts to the article DB" sync patterns.	0 fields	View →

Recipes

Pre-built Disqus workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Disqus → Slack alerts

AI-triage every Disqus event, ping the right channel only when it matters.

Disqus → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Disqus → Notion database

Turn Disqus into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Disqus once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Disqus field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Disqus integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Disqus to Tiny Command?

Open the Tiny Command workflow builder, drop in a Disqus node, and click Connect. Authorize Disqus once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Disqus triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Disqus today. Use Tiny Command's universal Webhook or Schedule trigger to start Disqus workflows, then run any Disqus action you need.

What Disqus actions can I run from a workflow?

1 Disqus action are available out of the box, covering other operations like "List Disqus Comments". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Disqus integration real-time?

Disqus actions execute synchronously inside your workflow. Tiny Command waits for Disqus's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Disqus with Tiny Command?

No. Every Disqus trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Disqus API endpoint directly.

How much does the Disqus integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Disqus integration itself has no per-app surcharge.