Social & Community · Integration
Typefully
Add Typefully to your product for your customers, and give your AI agents governed access to it.
Typefully has moved to a v2 API at api.typefully.com and switched off v1 access by API key, so an older integration now receives an explicit error telling it to migrate rather than failing quietly. Authentication is a bearer token issued per account in Typefully's settings, and that token is tied to the social profiles the account has connected rather than to a shared workspace credential. The core object is the draft: you post content, optionally split into a thread, then either schedule it for a specific time or ask for the next free slot in the account's own posting queue. Because publishing happens on the connected X or LinkedIn account, anything the platform itself rejects surfaces at the scheduled time rather than when the draft was created, so success on create is not success on publish. fastn holds each customer's Typefully token in its own tenant and keeps the v2 migration and error handling in one place.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Typefully account so content generated in your product becomes a draft there
Schedule approved posts into the customer's queue instead of picking arbitrary times
Show which drafts published successfully and which were rejected by the underlying network
Keep a content calendar in your app in step with what is actually queued in Typefully
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent create a draft and place it in the next free slot, with the draft ID and scheduled time recorded per tenant
Have an agent review queued drafts and flag any that repeat a recent post
Let an agent reschedule a draft when an embargo date moves, leaving the content untouched
Example prompt
What is queued to publish in Typefully this week, and is anything scheduled twice?
Set up Typefully in 4 steps
- 01Enable the Typefully connector from your fastn dashboard.
- 02Have each customer authorise their own Typefully 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 Typefully integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Typefully integration without building it. Your customers connect their own Typefully 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 Typefully update is not your on-call problem.
- One integration serves your product and your agents. The same governed Typefully 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 Typefully, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMTypefully integration FAQ
How do I add a Typefully integration to my product?
Enable the Typefully connector in your fastn dashboard, then let each customer authenticate their own Typefully account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Typefully client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Typefully account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Typefully 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 Typefully integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent create a draft and place it in the next free slot, with the draft ID and scheduled time recorded per tenant
Who maintains the Typefully integration?
fastn does. When Typefully 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 Typefully 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 Typefully?
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 Typefully integration?
A common starting point: let a customer connect their own Typefully account so content generated in your product becomes a draft there. 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 Typefully integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Typefully does not change your per-connector cost. You can start free with 3 connected accounts.
Add Typefully to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.