# How to connect Delighted to OpenClaw (paste one key, 13 tools) > Connect Delighted to OpenClaw with ClawLink: paste your Delighted key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/delighted The usual route to Delighted 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 Delighted setup: install one ClawHub skill, connect Delighted in the browser, and OpenClaw can call real Delighted 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 Delighted. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Delighted** — 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 delighted # connect Delighted (browser OAuth) npx -y @useclawlink/cli actions delighted # list available actions npx -y @useclawlink/cli run delighted --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 Delighted in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Delighted API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Delighted, 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 Delighted is connected in the dashboard, that agent calls the same 13 Delighted 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). ## Delighted MCP for OpenClaw Looking for a Delighted MCP server for OpenClaw? ClawLink connects Delighted to OpenClaw and exposes 13 Delighted 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 Delighted integration](https://claw-link.dev/hermes/delighted) works the same way. ## What the OpenClaw Delighted integration can do 13 Delighted tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 13. ### 11 of 13 Delighted tools for OpenClaw | Tool | What it does | |---|---| | **Get autopilot email configuration** `delighted_get_autopilot_email_configuration` | Retrieve the current Autopilot configuration for email distribution | | **Get autopilot sms configuration** `delighted_get_autopilot_sms_configuration` | Retrieve the current Autopilot configuration for SMS distribution | | **List autopilot sms memberships** `delighted_list_autopilot_sms_memberships` | Retrieve all Autopilot memberships for SMS distribution platform | | **List bounced people** `delighted_list_bounced_people` | Retrieve all bounced people for your account, ordered by bounce time (oldest first) | | **List people** `delighted_list_people` | Retrieve all people for your account in creation order | | **List survey responses** `delighted_list_survey_responses` | Retrieve all survey responses for your account with pagination support and optional filtering | | **List unsubscribed people** `delighted_list_unsubscribed_people` | Retrieve all unsubscribed people for your account, ordered by unsubscribe time (oldest first) | | **Add person to autopilot email** `delighted_add_person_to_autopilot_email` | Add a person to Autopilot email or update their properties | | **Add person to autopilot sms** `delighted_add_person_to_autopilot_sms` | Add a person to Autopilot or update their properties for SMS-based surveys | | **Create person** `delighted_create_person` | Create or update a person and schedule a survey email | | **Unsubscribe person** `delighted_unsubscribe_person` | Add a person to your unsubscribe list, preventing them from receiving any future surveys via | ## Example prompts **Get Autopilot Email Configuration** > Pull the relevant data from Delighted, summarize it in plain English, and point out anything that needs attention. **Get Autopilot Sms Configuration** > Pull the relevant data from Delighted, summarize it in plain English, and point out anything that needs attention. **List Autopilot Sms Memberships** > List the relevant items in Delighted, group them by priority, and recommend what OpenClaw should do next. **List Bounced People** > List the relevant items in Delighted, group them by priority, and recommend what OpenClaw should do next. ## 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 Delighted working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Delighted API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Delighted 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 Delighted. | 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 Delighted actions to the runtime in a format your agent can reliably use. | 13 tools for Delighted are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Delighted 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 Delighted in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Delighted 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 Delighted skill but can't call the tools The ClawHub skill teaches OpenClaw about Delighted, but the calls run through the ClawLink plugin and your connected account. Make sure Delighted 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 Delighted 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 Delighted tools Delighted 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 Delighted 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. ### Delighted 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 Delighted has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Delighted integration? Yes. ClawLink is the fastest way to connect OpenClaw to Delighted: link your Delighted account once in the browser and OpenClaw can call the Delighted API through 13 ready-made tools — no custom code or token handling. ### How do I add Delighted to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Delighted skill from ClawHub, then you click Connect in the dashboard to authorize Delighted. OpenClaw calls the tools from the next message — no config files, and the Delighted key you paste is stored server-side instead of in your environment. ### How long does it take to connect Delighted to OpenClaw? About two minutes. Sign in, click Connect next to Delighted in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Delighted 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 Delighted working from chat. ### OpenClaw installed the Delighted skill but can't call the tools The ClawHub skill teaches OpenClaw about Delighted, but the calls run through the ClawLink plugin and your connected account. Make sure Delighted 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 Zendesk integration](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations - [OpenClaw Gleap integration](https://claw-link.dev/openclaw/gleap) — Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points. - [Connect Freshdesk](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations