Social & Community · Integration
Heartbeat
Add Heartbeat to your product for your customers, and give your AI agents governed access to it.
Heartbeat's API sits at api.heartbeat.chat/v0 with a bearer token generated inside the community's settings, and that token is scoped to one community, so a customer running several communities needs a separate connection for each. The object model is threads inside channels rather than a flat message feed, so replying means posting a comment against a thread id, and a channel read gives you thread records rather than message bodies. Members are addressed by their internal user id, not by email, so anything driven from your own user table needs a lookup step first, and invitations are their own resource separate from users. Groups control what a member can see, so a thread that exists in the community can be invisible to a given member and the API reflects that membership rather than ignoring it. Events carry their own RSVP records, which is how attendance is read rather than through the user object. fastn holds each community's token, keeps it bound to the right tenant, and handles the upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Heartbeat community so your product can add and remove members as their subscriptions change.
Post a thread into the right channel when something notable happens in your product, using the customer's own token.
Read event RSVPs and attendance so a customer can see which members turn up and which have gone quiet.
Sync group membership from your billing tiers so paying customers get the private channels they are entitled to.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to summarise the week's threads in a channel, with reads audited per tenant.
Let an agent identify members with no activity for a set period so a human can decide on outreach.
Have an agent draft a thread for review while posting stays an approved action.
Example prompt
Which questions in our community went unanswered this week, and who usually replies to that channel?
Set up Heartbeat in 4 steps
- 01Enable the Heartbeat connector from your fastn dashboard.
- 02Have each customer authorise their own Heartbeat account, so calls run under their credentials rather than a shared key.
- 03Decide which posts, pages and comments your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Heartbeat integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Heartbeat integration without building it. Your customers connect their own Heartbeat 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 Heartbeat update is not your on-call problem.
- One integration serves your product and your agents. The same governed Heartbeat 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
Compare with
Buffer
Hootsuite
FacebookOften used alongside
Tools the same teams tend to run next to Heartbeat, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMHeartbeat integration FAQ
How do I add a Heartbeat integration to my product?
Enable the Heartbeat connector in your fastn dashboard, then let each customer authenticate their own Heartbeat account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Heartbeat client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Heartbeat account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Heartbeat 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 Heartbeat integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to summarise the week's threads in a channel, with reads audited per tenant.
Who maintains the Heartbeat integration?
fastn does. When Heartbeat 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 Heartbeat 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 Heartbeat?
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 Heartbeat integration?
A common starting point: let a customer connect their own Heartbeat community so your product can add and remove members as their subscriptions change. 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 Heartbeat integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Heartbeat does not change your per-connector cost. You can start free with 3 connected accounts.
Add Heartbeat to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.