Communication · Integration
inSided
Add inSided to your product for your customers, and give your AI agents governed access to it.
Embed an inSided integration so your customers can bring their own community activity into your product and post back into it. Every customer authorises their own community, so topics and replies originate from their space under their permissions rather than through a shared account. Anything posted is user-visible, so sends are deduplicated per event and a retry does not publish the same reply twice. fastn handles per-customer authorisation and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read topics and replies from their own community into your product.
Post a reply or announcement from your product so updates reach members where they already are.
Read member activity so your product can surface who is engaged and who is asking questions.
Trigger your product when a new topic or reply is published.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a topic thread before drafting a suggested answer.
An agent posts a reply within governed permissions, deduplicated per event and logged.
An agent reacts to a new question and routes it to the right team.
Example prompt
Show community topics from the last week with no reply and summarise what each one is asking.
Set up inSided in 4 steps
- 01Open the inSided connector from your fastn dashboard.
- 02Have each customer authenticate their own inSided community.
- 03Map the categories and fields 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 inSided integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an inSided integration without building it. Your customers connect their own inSided account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- 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 an inSided update is not your on-call problem.
- One integration serves your product and your agents. The same governed inSided connection 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
DisqusWorks well with
Gainsight
IntercomOften used alongside
Tools the same teams tend to run next to inSided, across other categories.
Aircall
Calendly
Gong
Google CalendarinSided integration FAQ
How do I add an inSided integration to my product?
Enable the inSided connector in your fastn dashboard, then let each customer authenticate their own inSided account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no inSided client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own inSided account?
Yes. Every connection is scoped to the individual customer, so each authorises their own inSided 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 inSided integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a topic thread before drafting a suggested answer.
Who maintains the inSided integration?
fastn does. When inSided changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own inSided account?
Yes. Every customer authorises their own inSided 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 inSided integration?
A common starting point: read topics and replies from their own community 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 inSided integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding inSided does not change your per-connector cost. You can start free with 3 connected accounts.
Add inSided to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.