# How to connect Eventee to OpenClaw (paste one key, 22 tools) > Connect Eventee to OpenClaw with ClawLink: paste your Eventee key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/eventee The usual route to Eventee 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 Eventee setup: install one ClawHub skill, connect Eventee in the browser, and OpenClaw can call real Eventee 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 Eventee. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Eventee** — 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 eventee # connect Eventee (browser OAuth) npx -y @useclawlink/cli actions eventee # list available actions npx -y @useclawlink/cli run eventee --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 Eventee in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Eventee API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Eventee, 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 Eventee is connected in the dashboard, that agent calls the same 22 Eventee 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). ## Eventee MCP for OpenClaw Looking for a Eventee MCP server for OpenClaw? ClawLink connects Eventee to OpenClaw and exposes 22 Eventee 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 Eventee integration](https://claw-link.dev/hermes/eventee) works the same way. ## What the OpenClaw Eventee integration can do 22 Eventee tools are ready for OpenClaw once the account is connected. The 16 below are the ones people reach for most; your agent can call all 22. ### 16 of 22 Eventee tools for OpenClaw | Tool | What it does | |---|---| | **Get groups** `eventee_get_groups` | Retrieve all event groups from Eventee (e.g., VIP attendees, speaker groups) | | **Get participants** `eventee_get_participants` | Retrieve all participants/attendees for an Eventee event | | **Get partners** `eventee_get_partners` | Retrieve all partners/sponsors for an Eventee event | | **Get registrations** `eventee_get_registrations` | Retrieve all registrations for an Eventee event | | **Get reviews** `eventee_get_reviews` | Retrieve all reviews for your Eventee event | | **List events** `eventee_list_events` | Retrieves the content structure of your Eventee event including halls, speakers, lectures | | **Add speaker** `eventee_add_speaker` | Add a new speaker to a specific Eventee event | | **Create hall** `eventee_create_hall` | Create a new hall/stage for an event where sessions can be scheduled | | **Create label** `eventee_create_label` | Create a new label/track for categorizing event sessions by topic or theme | | **Create partner** `eventee_create_partner` | Add a new partner/sponsor to the event | | **Create pause** `eventee_create_pause` | Create a new break/pause in the event schedule (e.g., coffee break, lunch) | | **Invite attendee** `eventee_invite_attendee` | Invite attendees to your Eventee event by sending invitation emails to specified users | | **Invite registration** `eventee_invite_registration` | Invite registrants to your Eventee event by email | | **Update hall** `eventee_update_hall` | Update an existing hall/stage details in an Eventee event | | **Update lecture** `eventee_update_lecture` | Update an existing lecture/session details in Eventee | | **Update partner** `eventee_update_partner` | Update an existing partner/sponsor details | ## Example prompts **Get Groups** > Pull the relevant data from Eventee, summarize it in plain English, and point out anything that needs attention. **Get Participants** > Pull the relevant data from Eventee, summarize it in plain English, and point out anything that needs attention. **Get Partners** > Pull the relevant data from Eventee, summarize it in plain English, and point out anything that needs attention. **Get Registrations** > Pull the relevant data from Eventee, 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 Eventee working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Eventee API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Eventee 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 Eventee. | 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 Eventee actions to the runtime in a format your agent can reliably use. | 22 tools for Eventee are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Eventee 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 Eventee in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Eventee 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 Eventee skill but can't call the tools The ClawHub skill teaches OpenClaw about Eventee, but the calls run through the ClawLink plugin and your connected account. Make sure Eventee 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 Eventee 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 Eventee tools Eventee 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 Eventee 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. ### Eventee 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 Eventee has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Eventee integration? Yes. ClawLink is the fastest way to connect OpenClaw to Eventee: link your Eventee account once in the browser and OpenClaw can call the Eventee API through 22 ready-made tools — no custom code or token handling. ### How do I add Eventee to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Eventee skill from ClawHub, then you click Connect in the dashboard to authorize Eventee. OpenClaw calls the tools from the next message — no config files, and the Eventee key you paste is stored server-side instead of in your environment. ### How long does it take to connect Eventee to OpenClaw? About two minutes. Sign in, click Connect next to Eventee in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Eventee 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 Eventee working from chat. ### OpenClaw installed the Eventee skill but can't call the tools The ClawHub skill teaches OpenClaw about Eventee, but the calls run through the ClawLink plugin and your connected account. Make sure Eventee 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 - [Connect Cal.com](https://claw-link.dev/openclaw/cal) — Schedule and manage bookings through Cal.com - [Bookingmood](https://claw-link.dev/openclaw/bookingmood) — Bookingmood provides flexible, commission-free booking software for rental businesses of all sizes, enabling seamless integration with your website. - [OpenClaw Eventbrite integration](https://claw-link.dev/openclaw/eventbrite) — Create and manage events, tickets, and attendees