ClawLink

How to connect Thanks.io to OpenClaw

Connect Thanks.io to OpenClaw with ClawLink: paste your Thanks.io key once and 29 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Thanks.io
Thanks.io
Thanks.ioAPI KEYMCP

thanks.io is a direct mail automation platform that enables users to send personalized postcards, letters, and notecards with handwritten fonts.. Once connected, OpenClaw can read and act on Thanks.io from chat — pairing, token refresh, and tool wiring handled for you.

29 tools

The usual route to Thanks.io 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 Thanks.io setup: install one ClawHub skill, connect Thanks.io in the browser, and OpenClaw can call real Thanks.io 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 Thanks.io.

  1. 1

    Install the plugin

    Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:

    openclaw plugins install clawhub:clawlink-plugin
  2. 2

    Connect Thanks.io

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Thanks.io?"

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:

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 Thanks.io in the ClawLink dashboard — paste your Thanks.io API key once.

Verify the connection by asking OpenClaw:

List the relevant items in Thanks.io, group them by priority, and recommend what OpenClaw should do next.

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:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Thanks.io is connected in the dashboard, that agent calls the same 29 Thanks.io tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Thanks.io MCP for OpenClaw

Looking for a Thanks.io MCP server for OpenClaw? ClawLink connects Thanks.io to OpenClaw and exposes 29 Thanks.io tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Thanks.io integration works the same way.

What the OpenClaw Thanks.io integration can do

29 Thanks.io tools are ready for OpenClaw once the account is connected. The 25 below are the ones people reach for most; your agent can call all 29.

25 of 29 Thanks.io tools for OpenClaw

ToolWhat it does
List handwriting styles thanks_io_list_handwriting_stylesRetrieve available handwriting styles
List image templates thanks_io_list_image_templatesRetrieve a list of available image templates
List mailing lists thanks_io_list_mailing_listsList all mailing lists
List message templates thanks_io_list_message_templatesList available message templates
Order preview letter thanks_io_order_preview_letterPreview a letter send as PDF
Order preview notecard thanks_io_order_preview_notecardPreview a notecard send
Order preview windowless letter thanks_io_order_preview_windowless_letterPreview a windowless letter send
Orders list thanks_io_orders_listList recent orders
Orders search by address thanks_io_orders_search_by_addressSearch orders by recipient street address
Recipients get details thanks_io_recipients_get_detailsGet details for a specific recipient by ID
Recipients search by email thanks_io_recipients_search_by_emailSearch recipients by email across mailing lists
Sub accounts list thanks_io_sub_accounts_listList all available sub-accounts
Sub accounts show thanks_io_sub_accounts_showRetrieve details for a specific sub-account by ID
Add recipient to mailing list thanks_io_add_recipient_to_mailing_listAdd a new recipient to a mailing list
Create mailing list thanks_io_create_mailing_listCreate a new mailing list
Execute stored send thanks_io_execute_stored_sendExecute a previously created stored send
Mailing lists buy radius search thanks_io_mailing_lists_buy_radius_searchBuy or append a radius search mailing list based on address and radius
Recipients create multi thanks_io_recipients_create_multiCreate multiple recipients at once in a mailing list
Recipients update thanks_io_recipients_updateUpdate existing recipient details by recipient ID
Send postcard thanks_io_send_postcardSend a customized postcard
Stored send notecard thanks_io_stored_send_notecardCreate a stored send for a notecard
Stored send postcard thanks_io_stored_send_postcardCreate a stored send for a postcard
Stored send windowless letter thanks_io_stored_send_windowless_letterCreate a stored send for a windowless letter
Sub accounts create thanks_io_sub_accounts_createCreate a new sub-account
Sub accounts update thanks_io_sub_accounts_updateUpdate details for a specific sub-account

Try it: find the Thanks.io tool you need

Browse the 25 Thanks.io tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

List the relevant items in Thanks.io, group them by priority, and recommend what OpenClaw should do next.

List the relevant items in Thanks.io, group them by priority, and recommend what OpenClaw should do next.

List the relevant items in Thanks.io, group them by priority, and recommend what OpenClaw should do next.

List the relevant items in Thanks.io, group them by priority, and recommend what OpenClaw should do next.

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 Thanks.io working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Thanks.io API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Thanks.io account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Thanks.io.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Thanks.io actions to the runtime in a format your agent can reliably use.29 tools for Thanks.io are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Thanks.io 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 Thanks.io in the browser, and the 29 tools above work from chat. There is no SDK and no config file, and the Thanks.io key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Thanks.io skill but can't call the tools

The ClawHub skill teaches OpenClaw about Thanks.io, but the calls run through the ClawLink plugin and your connected account. Make sure Thanks.io 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 Thanks.io 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 Thanks.io tools

Thanks.io 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 Thanks.io 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.

Thanks.io 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 Thanks.io has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Thanks.io integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Thanks.io: link your Thanks.io account once in the browser and OpenClaw can call the Thanks.io API through 29 ready-made tools — no custom code or token handling.

How do I add Thanks.io to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Thanks.io skill from ClawHub, then you click Connect in the dashboard to authorize Thanks.io. OpenClaw calls the tools from the next message — no config files, and the Thanks.io key you paste is stored server-side instead of in your environment.

How long does it take to connect Thanks.io to OpenClaw?

About two minutes. Sign in, click Connect next to Thanks.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Thanks.io 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 Thanks.io working from chat.

OpenClaw installed the Thanks.io skill but can't call the tools

The ClawHub skill teaches OpenClaw about Thanks.io, but the calls run through the ClawLink plugin and your connected account. Make sure Thanks.io 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.