Resources · n8n integration

Disqus n8n integrationAutomate Disqus with n8n.

Your comment data already lives in Disqus, and n8n can go and get it. The Disqus n8n integration ships one node built on a single Forum resource, with 4 operations covering forum details, categories, threads and posts. No trigger node comes with it, so a schedule starts the run.

Try the Disqus integration on n8nSee the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Disqus n8n integration actually read?

The Disqus node is a read client for one forum at a time. You hand it a forum short name, pick one of 4 operations, and the response lands in the next node of your workflow, the chain of steps n8n runs from start to finish. Everything hangs off a single resource, Forum, so the only real decision is which slice you want back: the forum itself, its categories, its threads or its posts.

Start with the comments, because that is where the work piles up. Get all posts in a forum returns the posts of one forum, and the optional Filters field narrows the response to posts carrying a given marker, Is_Flagged or Has_Link for instance. A community manager who checks the queue by hand every morning can let a workflow run that call at dawn and drop the result into a Slack channel, one message per post, ready to act on before the first coffee.

Threads are the next obvious job. Get all threads in a forum lists the discussion pages attached to the forum, and Since takes a Unix timestamp or an ISO datetime so the run only picks up what appeared after the last one. Feed that into a formatting node and out to Gmail, and the editorial team gets a weekly note of which pages started talking again, instead of clicking through the moderation panel.

Categories work differently. Get all categories in a forum gives you the list Disqus keeps for sorting discussions, and that list is usually read once at the top of a run and held in memory so later steps can match a thread against it. It is a small operation with a large effect: it is what turns a raw thread dump into something a spreadsheet or a dashboard can group.

Get a forum plays the housekeeping role. It returns the forum details, and its Attach field can bundle extra blocks such as counters or forumFeatures into the same response, which saves a second call when a report needs both the volume and the configuration.

When what you need is not one of the 4 catalogue operations, the HTTP Request node calls any endpoint of the Disqus API and reuses the same credential through its predefined authentication, so you stay inside one workflow instead of splitting the logic across two tools. That is the standard escape hatch in n8n and it is worth knowing before you start.

None of this needs a trigger from Disqus, and that shapes the design: a Schedule Trigger sets the rhythm, the Disqus node reads, the rest of the workflow decides what to do. If you are weighing platforms before you build, the n8n review covers the trade-offs, and the n8n training walks through building this kind of scheduled read from an empty canvas.

Connect

How do you connect Disqus to n8n?

  1. 01

    Register an API application on Disqus

    You need a Disqus account first, then an API application registered against it. Disqus documents the registration path in its help center, and the application page is what produces the value n8n needs. Nothing is configured on the n8n side yet at this stage, so do this one in a separate tab and keep it open: you will copy from it in the next step.

  2. 02

    Create the Disqus credential in n8n

    Open the Credentials menu in n8n and create a Disqus credential. It supports one authentication method, API access token, and asks for a single value: Access Token. Paste the API Key from your registered application into it and save. A credential is created once and then offered in the dropdown of every node that can use it, in every workflow on that instance.

  3. 03

    Point the node at a forum

    Drop a Disqus node on the canvas, select the credential you just saved, and pick the operation you want from the Forum resource. All 4 of them ask for Forum Name, the short name that identifies the forum, also called its ID. Type it in for a fixed forum, or pass it from an earlier node with an expression like {{ $json.field }} when the forum varies per item.

Actions

What can the Disqus node do?

The Disqus node exposes 4 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGetGet All CategoriesGet All PostsGet All Threads
Forum✓✓✓✓

Forum

4 operations
01

Get a forum

forum.get

What you see in n8n

Notes & use cases

Returns the details of one Disqus forum, which is how a workflow checks what it is dealing with before acting on it.

Key parameters

  • Forum Name: the short name of the forum, also called its ID. Hardcode it, or read it from an earlier node with an expression such as {{ $json.field }}.
  • Attach: an optional multi-select in Additional Fields. Values like counters, forumFeatures or forumPermissions ask Disqus to bundle extra blocks into the same response.
  • Related: set it to author to bring the related account back alongside the forum.
Use cases
a monthly check that reads counters for each forum a publisher runs and lines the results up in one report.
02

Get all categories in a forum

forum.getCategories

What you see in n8n

Notes & use cases

Disqus lets a forum sort its discussions into categories. This operation lists them, which is what a workflow needs before it can match anything against them.

Key parameters

  • Forum Name: the short name of the forum whose categories you want.
  • Return All: ticked, n8n walks the API pages and brings back every category; unticked, Limit caps how many come back in one run.
  • Order: asc or desc, set inside Additional Fields to fix the sort direction of the response.
Use cases
reading the category list once at the top of a run, so the steps that follow can group threads without a second call.
03

Get all threads in a forum

forum.getThreads

What you see in n8n

Notes & use cases

Each discussion page in Disqus is a thread. This operation lists the threads belonging to one forum, with enough filtering to keep a scheduled run from re-reading the whole archive.

Key parameters

  • Forum Name: required, and it scopes the whole call to that forum.
  • Since: a Unix timestamp or an ISO datetime, so a run started every morning only sees what came after the previous one.
  • Include: keeps open, closed or killed threads in the response.
  • Thread: looks a single thread up by ID, and without the Pro API Access addon the forum has to travel with it.
Use cases
a weekly digest of threads opened since the last run, formatted and emailed to the editorial team.
04

Get all posts in a forum

forum.getPosts

What you see in n8n

Notes & use cases

Posts are the comments themselves. This operation pulls them for one forum, and its Additional Fields are where most of the useful narrowing happens.

Key parameters

  • Forum Name: the forum the posts are read from.
  • Filters: a multi-select that restricts the response to posts carrying a marker, among them Is_Flagged, Has_Link, Has_Media and Is_Anonymous.
  • Query: a free-text value passed along to narrow the response further.
  • Related: set to thread, it returns the discussion each post belongs to, so no lookup step is needed afterwards.
Use cases
a scheduled sweep that collects posts matching Is_Flagged and posts them to the channel where moderation actually happens.
Need help

Need help automating Disqus with n8n?

A person reads every message.

FAQ

Disqus and n8n, the questions that come next

01Is the Disqus n8n integration free?
Yes, on the n8n side. The Disqus node ships with n8n, so there is nothing to install and nothing extra to pay for it, whether you run n8n Cloud, the hosted offer from n8n, or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both. What a Disqus account itself costs is a separate question and not one this page answers. The only setup cost is the credential: register an API application once, paste the value into n8n, and every workflow on that instance can reuse it.
02What credentials do you need for the Disqus node?
One credential, using API access token, the single authentication method the node supports. To build it you need a Disqus account and an API application registered against that account. The application page gives you an API Key, and that key is what goes into the Access Token field of the Disqus credential in n8n. There is no authentication selector on the node itself, so nothing else has to be chosen once the credential exists. Save it in the Credentials menu and it becomes available in the dropdown of any Disqus node you add later, across every workflow on the instance.
03What are the limits of the Disqus node in n8n?
The node covers 4 operations on one resource, Forum: forum details, categories, threads and posts. Anything the catalogue does not list goes through the HTTP Request node instead, which calls any endpoint of the Disqus API and reuses the same credential through its predefined authentication, so the logic stays in one workflow. On volume, the three list operations expose Return All and Limit: with Return All ticked, n8n chains the API pages and returns everything; with it unticked, Limit sets the ceiling. Choose deliberately, because a large forum and an unbounded read make for a long execution.
04Can a workflow react to a new Disqus comment in real time?
No, not from Disqus itself. There is no Disqus trigger node in n8n, so nothing on that side can wake a workflow up. You start it another way. A Schedule Trigger runs the workflow at a fixed interval and the Disqus node reads what has appeared since, which is what the Since field on Get all threads in a forum is for. An n8n Webhook, meaning a URL a third-party service calls, works too when something else can signal the event. A trigger belonging to another tool in the same workflow also does the job.
05n8n or Make for Disqus?
It depends on what you care about most. Make is hosted only, with no self-hosting option, and it bills per operation, so a scheduled read that pages through a busy forum is metered. n8n runs on your own infrastructure through Docker or npm, or on n8n Cloud, and the same workflow behaves identically either way, which matters when comment data has to stay on your side. Both give you a visual canvas, so the choice comes down to hosting, data control and cost model rather than features. Look at how often your Disqus reads will run before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations