Requirements
Disqus requires an active account and an API access token from your account settings to connect — both are set up on its own site.[3]
Get your Disqus credentials
Disqus - API Key
- Public KeytextRequired
Your application's public key. Create an application at disqus.com/api/applications, then open its Details tab.
[1] - Secret KeypasswordRequired
The secret key for the same application, on the same Details tab. Treat it like a password.
[1] - Access TokenpasswordRequired
The account owner Access Token shown on the same Details tab. It does not expire and authenticates every request as the application owner. Most Disqus endpoints refuse to run without it.
[1]
Disqus
You’ll be redirected to sign in and approve access — your password is never shared with WEXTL.
- Public KeytextRequired
Your application's public key. Add this app's redirect URI to the application's Trusted Domains.
[1] - Secret KeypasswordRequired
The secret key for the same application. Treat it like a password.
[1]
Connect Disqus in WEXTL
- Log in to your WEXTL account, add the Disqus node module to your workflow, and click Create new credential.
- Optional: In the Credential name field, enter a name for the credential.
- Enter the authentication credentials you copied from your Disqus account, or follow the on-screen instructions to create the credential.
- If prompted, authenticate your account and confirm access.
- If you want to make changes to your credential in the future, follow the steps in Manage credentials →
Notes
Credentials are org-scoped; share them with teammates from the Credentials picker on any of its nodes.For detailed information on connecting an application, see Connect an application →
Disqus node modules
The list below is a reference of every Disqus node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.
Browse every Disqus node module below — each one opens to show its input parameters, outputs, and connection requirements.
| Field | Type |
|---|---|
ID | text |
Created at | text |
Message | text |
| Field | Type |
|---|---|
ID | text |
Created at | text |
Title | text |
| Field | Type |
|---|---|
ID | text |
Name | text |
Status | text |
Created at | number |
Updated at | number |
Data | text |
| Field | Type |
|---|---|
ID | text |
Name | text |
Status | text |
Created at | number |
Updated at | number |
Data | text |
| Field | Type |
|---|---|
Code | number |
Response | text |
| Field | Type |
|---|---|
ID | text |
Name | text |
Status | text |
Created at | number |
Updated at | number |
Data | text |
Templates
Look for Disqus templates in the WEXTL template library.
Browse templates →Explore alternative apps
- Aircall[2]Business phone system for teams, with calls, messages, and AI notes.
- AWS SESSend transactional email and manage Amazon SES identities, templates, contacts, suppressions, and configuration sets.
- AWS SQSSend, receive, and manage messages on Amazon SQS queues.
- CallRailCall tracking — calls, SMS, form submissions, companies, and trackers.
- BatchDialerCloud predictive dialer for sales and collections teams with contacts and campaigns.
References
- WEXTL® Disqus Source Code connector implementation.
- Our users use cases and automations.
- Official API Documentation for Disqus.
- WEXTL® visual workflow builder data.
Last updated: Sep 3, 2026 08:02