Hootsuite

Enable the Hootsuite connector in your fastn dashboard, then let each customer authenticate their own Hootsuite account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Hootsuite client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Hootsuite 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.

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 drafts and schedules a post within governed permissions, with each action logged.

fastn does. When Hootsuite 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.

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.

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.

A common starting point: schedule a post to their own connected profiles from inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Hootsuite does not change your per-connector cost. You can start free with 3 connected accounts.