Communication · Integration
Embed a Disqus integration in your product
Add Disqus to your product for your customers, and give your AI agents governed access to it.
Embed a Disqus integration so your customers can work their own discussion threads, comments, and commenters from inside your product, with governed agent access to the same records. Each customer connects their own Disqus site, so moderation happens with their permissions rather than through a shared account, and actions are deduplicated per event so a retry does not post the same reply twice. fastn handles per-customer authentication and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, customized per customer, maintained by fastn.
Let customers read comments and threads from their own Disqus site into your product.
Post replies or moderation decisions from your product without opening the Disqus admin.
Surface commenter history so moderators have context before they act.
Trigger your product when a comment is posted, flagged, or approved.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a thread and summarises what is being asked before a human replies.
An agent approves, flags, or replies to a comment within governed permissions, with the action audited.
An agent reacts to a newly flagged comment and routes it to the right moderator.
Example prompt
Show comments flagged in the last day, grouped by thread, with the commenter's previous flagged history.
Set up Disqus in 4 steps
- 01Open the Disqus connector from your fastn dashboard.
- 02Have each customer authenticate their Disqus account with OAuth.
- 03Map the sites, threads, and moderation actions your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Disqus integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Disqus integration without building it. Your customers connect their own Disqus account inside your product and work their messages, conversations and participants there, and nothing lands on your team.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Disqus update is not your on-call problem.
- One integration serves your product and your agents. The same governed Disqus integration powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Works well with
Often used alongside
Tools the same teams tend to run next to Disqus, across other categories.
More in Communication
Other Communication apps your customers can connect the same way. All Communication integrations
Disqus integration FAQ
How do I add a Disqus integration to my product?
Enable the Disqus connector in your fastn dashboard, then let each customer authenticate their own Disqus account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Disqus client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Disqus account?
Yes. Every integration is scoped to the individual customer, so each authorises their own Disqus account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Disqus integration?
Yes. The same integration is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a thread and summarises what is being asked before a human replies. A prompt that works on day one: "Show comments flagged in the last day, grouped by thread, with the commenter's previous flagged history."
Who maintains the Disqus integration?
fastn does. When Disqus changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' integrations keep working.
Does each customer connect their own Disqus account?
Yes. Every customer authorises their own Disqus account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Disqus integration?
A common starting point: read comments and threads from their own Disqus site into your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Disqus integration cost?
It is included. Pricing is based on customer connections, not on how many connectors you enable, so adding Disqus does not change your cost. You can start free with 3 customer connections.
Add Disqus to your product
Start free with 3 customer connections. No sales call required, and no per-customer integration code.