# How to connect Typefully to OpenClaw (paste one key, 16 tools) > Connect Typefully to OpenClaw with ClawLink: paste your Typefully key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/typefully The usual route to Typefully access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Typefully setup: install one ClawHub skill, connect Typefully in the browser, and OpenClaw can call real Typefully actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Typefully. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Typefully** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect typefully # connect Typefully (browser OAuth) npx -y @useclawlink/cli actions typefully # list available actions npx -y @useclawlink/cli run typefully --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Typefully in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Typefully API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Typefully, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Typefully is connected in the dashboard, that agent calls the same 16 Typefully tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Typefully MCP for OpenClaw Looking for a Typefully MCP server for OpenClaw? ClawLink connects Typefully to OpenClaw and exposes 16 Typefully tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Typefully integration](https://claw-link.dev/hermes/typefully) works the same way. ## What the OpenClaw Typefully integration can do 16 Typefully tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 16. ### 15 of 16 Typefully tools for OpenClaw | Tool | What it does | |---|---| | **Get current user** `typefully_get_current_user` | Get the current authenticated user's information | | **Get draft** `typefully_get_draft` | Retrieves a single draft by its ID with full details including platform-specific content, tags | | **Get media status** `typefully_get_media_status` | Check the processing status of an uploaded media file | | **Get queue** `typefully_get_queue` | Get the scheduled content queue for a social set within a date range | | **Get queue schedule** `typefully_get_queue_schedule` | Get the queue schedule configuration for a social set, including posting slots and timezone | | **Get social set** `typefully_get_social_set` | Get detailed information about a specific social set, including all connected platforms (X | | **List drafts** `typefully_list_drafts` | List drafts for a social set with filtering and sorting options | | **List social sets** `typefully_list_social_sets` | List all social sets (groups of connected platform accounts) accessible to the authenticated | | **List tags** `typefully_list_tags` | List all tags for a social set | | **Resolve linked in organization** `typefully_resolve_linked_in_organization` | Resolve a LinkedIn organization from its public URL | | **Create draft** `typefully_create_draft` | Create a new draft with platform-specific content for multi-platform publishing | | **Create tag** `typefully_create_tag` | Creates a new tag for organizing drafts within a social set in Typefully | | **Initialize media upload** `typefully_initialize_media_upload` | Initializes a media upload by returning a presigned URL | | **Update draft** `typefully_update_draft` | Update an existing draft with partial update semantics | | **Update queue schedule** `typefully_update_queue_schedule` | Replace the queue schedule configuration for a social set | ## Example prompts **Get Current User** > Pull the relevant data from Typefully, summarize it in plain English, and point out anything that needs attention. **Get Draft** > Pull the relevant data from Typefully, summarize it in plain English, and point out anything that needs attention. **Get Media Status** > Pull the relevant data from Typefully, summarize it in plain English, and point out anything that needs attention. **Get Queue** > Pull the relevant data from Typefully, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Typefully working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Typefully API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Typefully account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Typefully. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Typefully actions to the runtime in a format your agent can reliably use. | 16 tools for Typefully are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Typefully to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Typefully in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Typefully key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Typefully skill but can't call the tools The ClawHub skill teaches OpenClaw about Typefully, but the calls run through the ClawLink plugin and your connected account. Make sure Typefully is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Typefully from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Typefully tools Typefully tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Typefully call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Typefully returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Typefully has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Typefully integration? Yes. ClawLink is the fastest way to connect OpenClaw to Typefully: link your Typefully account once in the browser and OpenClaw can call the Typefully API through 16 ready-made tools — no custom code or token handling. ### How do I add Typefully to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Typefully skill from ClawHub, then you click Connect in the dashboard to authorize Typefully. OpenClaw calls the tools from the next message — no config files, and the Typefully key you paste is stored server-side instead of in your environment. ### How long does it take to connect Typefully to OpenClaw? About two minutes. Sign in, click Connect next to Typefully in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Typefully up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Typefully working from chat. ### OpenClaw installed the Typefully skill but can't call the tools The ClawHub skill teaches OpenClaw about Typefully, but the calls run through the ClawLink plugin and your connected account. Make sure Typefully is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [OpenClaw Benchmark Email integration](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp tools](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences