Write, schedule, and publish social media drafts across X, LinkedIn, Mastodon, Threads, Bluesky, and Substack Notes with Typefully.
Typefully ships in the w6w first-party pack. It declares 25 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
io.w6w.typefullyTypefully is a writing and scheduling tool for social media, and this app covers its full Public API v2 surface: create, update, list, and delete drafts across X, LinkedIn, Mastodon, Threads, Bluesky, and Substack Notes; plan a draft’s date without committing it to auto-publish, then confirm or schedule it later; reserve media uploads and poll their processing status; manage tags; read and replace a social set’s recurring queue schedule and view its upcoming queue; resolve a LinkedIn company or school URL into ready-to-use @mention syntax; and read, create, resolve, update, and delete the comment threads collaborators leave on a draft.
Account-level visibility rounds it out: list every social set (account) an API key’s user can reach, read a social set’s configured platforms and publishing quota, and pull per-post or daily-follower analytics for X.
Health checks track the per-user request-rate headroom Typefully reports on every response; the vendor publishes no independent status feed, which this app states as a verified fact rather than leaving as a silent gap.
Three routes to the same 25 actions. The Workflow tab is generated from Typefully's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
analytics-followers-get Fetch a daily follower-count series for a platform. Currently X only.
analytics-posts-list List posts with performance metrics for a platform. Currently X only.
comment-delete Delete a comment. Deleting the thread's root comment deletes the whole thread.
comment-thread-create Anchor a new comment thread to a substring of a draft's text.
comment-thread-list List comment threads on a draft. Defaults to unresolved threads only.
comment-thread-resolve Resolve a comment thread and strip its markers from the draft text. One-way.
linkedin-organization-resolve Resolve a public LinkedIn company/school URL into mentionable organization data.
media-upload-create Reserve a media slot for an image, video, GIF, or PDF and get an upload URL. Does not upload the file itself — see the action's own notes.
queue-schedule-get Fetch the recurring posting-time rules that generate this social set's queue.
queue-schedule-replace Fully replace a social set's recurring posting-time rules. Requires ADMIN access.
social-set-get Fetch full detail for one social set (account), including all platforms.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Typefully's real ids.
{
"manifestVersion": "2",
"name": "typefully-example",
"steps": [
{
"id": "analytics-followers-get",
"uses": {
"app": "io.w6w.typefully",
"action": "analytics-followers-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"socialSetId": "<socialSetId>",
"platform": "<platform>"
}
}
]
}analytics-followers-get analytics-posts-list comment-create comment-thread-create comment-thread-list +20 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Typefully, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Typefully. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "analytics-followers-get",
payload: {
socialSetId: "<value>",
platform: "<value>",
// startDate: "<value>",
// endDate: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value); npm install -g @w6w/cli w6w run conn_YOUR_CONNECTION_ID --action analytics-followers-get --payload '{"socialSetId":"<value>","platform":"<value>"}' Give an AI agent Typefully — without giving it Typefully's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.typefully#analytics-followers-get",
"input": {
"socialSetId": "<socialSetId>",
"platform": "<platform>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Typefully connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Typefully's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Typefully itself is MIT, and the runtime that executes it is source-available (FSL).
Typefully declares its own checks, so its health is a property of the app rather than something the host guesses at.
Reads X-RateLimit-User-Limit/-Remaining/-Reset off a GET /v2/me response. Does not cover the separate per-social-set operation limits (e.g. drafts.create), which only appear on the response of the operation they gate and cannot be read without triggering a real side effect.