First-party app
Typefully Typefully

Typefully

Write, schedule, and publish social media drafts across X, LinkedIn, Mastodon, Threads, Bluesky, and Substack Notes with Typefully.

stable Social MediaMarketing

About

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.

App id
io.w6w.typefully
Version
0.1.1
Author
w6w
Licence
MIT
Categories
Social Media · Marketing

Overview

Typefully 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.

Build with Typefully

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.

Get Followers Analytics

analytics-followers-get

Fetch a daily follower-count series for a platform. Currently X only.

List Analytics Posts

analytics-posts-list

List posts with performance metrics for a platform. Currently X only.

Add Comment

comment-create

Append a comment to an existing comment thread.

Delete Comment

comment-delete

Delete a comment. Deleting the thread's root comment deletes the whole thread.

Create Comment Thread

comment-thread-create

Anchor a new comment thread to a substring of a draft's text.

Delete Comment Thread

comment-thread-delete

Delete a comment thread and all its comments.

List Comment Threads

comment-thread-list

List comment threads on a draft. Defaults to unresolved threads only.

Resolve Comment Thread

comment-thread-resolve

Resolve a comment thread and strip its markers from the draft text. One-way.

Update Comment

comment-update

Update the text of a comment you authored.

Create Draft

draft-create

Create a draft, optionally planned, scheduled, or published immediately.

Delete Draft

draft-delete

Delete a draft.

Get Draft

draft-get

Fetch one draft's full content, status, and scheduling information.

List Drafts

draft-list

List a social set's drafts, with optional status/tag filtering and sorting.

Update Draft

draft-update

Partially update a draft's content, tags, sharing, or scheduling.

Resolve LinkedIn Organization

linkedin-organization-resolve

Resolve a public LinkedIn company/school URL into mentionable organization data.

Get Media Status

media-status-get

Check whether an uploaded media file has finished processing.

Create Media Upload

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.

Get Queue

queue-get

Fetch queue slots and their occupying drafts over a date range (max 62 days).

Get Queue Schedule

queue-schedule-get

Fetch the recurring posting-time rules that generate this social set's queue.

Replace Queue Schedule

queue-schedule-replace

Fully replace a social set's recurring posting-time rules. Requires ADMIN access.

Get Social Set

social-set-get

Fetch full detail for one social set (account), including all platforms.

List Social Sets

social-set-list

List the social sets (accounts) this API key's user can access.

Create Tag

tag-create

Create a tag on a social set. The slug is generated from the name.

List Tags

tag-list

List tags defined on a social set. Use their slugs to tag or filter drafts.

Get Current User

user-get

Fetch the Typefully user that owns this API key.

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>"
      }
    }
  ]
}

Here are some of the things you can do

  • Get Followers Analytics

    read
    analytics-followers-get
  • List Analytics Posts

    search
    analytics-posts-list
  • Add Comment

    perform
    comment-create
  • Create Comment Thread

    perform
    comment-thread-create
  • List Comment Threads

    search
    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.

Install
npm install @w6w/sdk
yarn add @w6w/sdk
pnpm add @w6w/sdk
deno add npm:@w6w/sdk
Code
import { 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);
Install the CLI
npm install -g @w6w/cli
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.

What the agent gets

Credentials it can't read

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.

A tool surface scoped to the caller

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.

A durable workflow in one call

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.

Health-aware discovery

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).

Request MCP access

Health checks

Typefully declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Typefully platform status

quota

Per-user request-rate headroom

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.