Social & Community · Integration
Circle
Add Circle to your product for your customers, and give your AI agents governed access to it.
Circle is a community platform, and the unit everything hangs off is the space: posts live in spaces, comments live under posts, and a member's access is decided by which spaces and space groups they belong to. Adding somebody to the community and giving them something to read are therefore two separate operations, which is the mistake most integrations make on their first day. There are two APIs and they are not interchangeable. The admin API acts as a community administrator and is what an embedded integration uses to invite members, publish, moderate and manage space membership. The headless member API acts as an individual member and is what you use when the community is being rendered inside your own product rather than on Circle. Custom profile fields are defined per community, so they are read before they are written, and each community connects its own credentials.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each community connect their own Circle account so a post your product publishes appears under their brand and their moderation rules.
Invite a member and add them to the right spaces as two deliberate steps, since joining and having access are not the same thing.
Publish a post into a space as draft or published, pinned where it needs to stay at the top.
Read and write the custom profile fields that community defined, rather than a field set you chose for them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent triages new comments in a space and flags the ones that need a human answer.
An agent posts an approved announcement to the right space, with the space and post id recorded.
An agent reports which members joined this month and have not posted since.
Example prompt
Which questions in this space are still unanswered, and who in the community usually answers that kind of thing?
Set up Circle in 4 steps
- 01Enable the Circle connector in your fastn dashboard.
- 02Have each community authorise their own account, choosing the admin API for administrative work or the headless member API where members act as themselves.
- 03Map that community's spaces, space groups and custom profile fields, then decide what your product publishes and where.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Circle integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Circle integration without building it. Your customers connect their own Circle account inside your product and work their posts, pages and comments there, with no per-customer code on your side.
- Handle the part that actually costs time: anything published is public immediately, and each network gates access behind its own review process. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Circle update is not your on-call problem.
- One integration serves your product and your agents. The same governed Circle connection powers in-product features and gives AI agents scoped, audited access, so you publish and listen from inside your product instead of a separate social tool without wiring it twice.
Used by these teams
Works well with
Discord
Skool
SlackOften used alongside
Tools the same teams tend to run next to Circle, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMCircle integration FAQ
How do I add a Circle integration to my product?
Enable the Circle connector in your fastn dashboard, then let each customer authenticate their own Circle account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Circle client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Circle account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Circle account and only ever sees their own posts, pages and comments. 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 Circle 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 triages new comments in a space and flags the ones that need a human answer.
Who maintains the Circle integration?
fastn does. When Circle 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.
Can my product publish to a customer's own Circle account?
Yes. Each customer authorises their own account, so a post goes out as them, under their permissions, never from a shared account you own. That also means a customer revoking access affects only their own connection.
Can I read engagement back from Circle?
Yes. Comments, reactions and reach come back scoped per tenant, so your product can act on them or show them in your own reporting without one customer's numbers mixing with another's.
What can I build with the Circle integration?
A common starting point: let each community connect their own Circle account so a post your product publishes appears under their brand and their moderation rules. 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 Circle integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Circle does not change your per-connector cost. You can start free with 3 connected accounts.
Add Circle to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.