Social & Community · Integration
X
Add X to your product for your customers, and give your AI agents governed access to it.
X, the platform that was Twitter, is a simple publishing surface and a complicated commercial one. What an integration does is straightforward: post on behalf of an account that authorised you, read that account's own posts and the replies and metrics attached to them, look up users, and search recent posts within whatever access you hold. The complication is that access. There is no free tier worth designing a feature on, calls are metered rather than bundled generously, and the deeper capabilities such as full archive search sit behind enterprise agreements, so the honest sequence is to price the access before you promise the feature, in the same way LinkedIn's partner review has to come before anybody sells one. Every connection is one customer's own account, so what gets published carries their name and the metered cost lands on them. fastn keeps those authorisations per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer authorise their own X account so anything published goes out as them, never from an account you own.
Publish or schedule a post from inside your product, so a social team does not leave your app to send it.
Read replies and post metrics back so engagement appears beside the content that earned it.
Be explicit with customers about which access level a feature needs, since calls are metered and the deeper endpoints are priced separately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent drafts a post and waits for a person to approve it before anything becomes public.
An agent publishes an approved post to the authorised account, with the account it used recorded.
An agent reports how recent posts performed from that account's own metrics.
Example prompt
How did our posts on X perform this week, and which replies still need an answer?
Set up X in 4 steps
- 01Enable the X connector in your fastn dashboard.
- 02Confirm which API access level your feature requires and what it costs, before you build against it.
- 03Have each customer authorise their own account, then map the post, reply and metric fields your product uses.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the X integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an X integration without building it. Your customers connect their own X 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 an X update is not your on-call problem.
- One integration serves your product and your agents. The same governed X 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
LinkedInOften used alongside
Tools the same teams tend to run next to X, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMX integration FAQ
How do I add an X integration to my product?
Enable the X connector in your fastn dashboard, then let each customer authenticate their own X account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no X client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own X account?
Yes. Every connection is scoped to the individual customer, so each authorises their own X 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 X 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 drafts a post and waits for a person to approve it before anything becomes public.
Who maintains the X integration?
fastn does. When X 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 X 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 X?
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 X integration?
A common starting point: let each customer authorise their own X account so anything published goes out as them, never from an account you own. 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 X integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding X does not change your per-connector cost. You can start free with 3 connected accounts.
Add X to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.