# How to connect Evenium to OpenClaw (paste one key, 12 tools) > Connect Evenium to OpenClaw with ClawLink: paste your Evenium key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/evenium The usual route to Evenium 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 Evenium setup: install one ClawHub skill, connect Evenium in the browser, and OpenClaw can call real Evenium 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 Evenium. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Evenium** — 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 evenium # connect Evenium (browser OAuth) npx -y @useclawlink/cli actions evenium # list available actions npx -y @useclawlink/cli run evenium --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 Evenium in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Evenium API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Evenium, 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 Evenium is connected in the dashboard, that agent calls the same 12 Evenium 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). ## Evenium MCP for OpenClaw Looking for a Evenium MCP server for OpenClaw? ClawLink connects Evenium to OpenClaw and exposes 12 Evenium 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 Evenium integration](https://claw-link.dev/hermes/evenium) works the same way. ## What the OpenClaw Evenium integration can do 12 Evenium 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 12. ### 11 of 12 Evenium tools for OpenClaw | Tool | What it does | |---|---| | **Get contact** `evenium_get_contact` | Retrieve a single contact by ID from Evenium | | **Get contact by custom ID** `evenium_get_contact_by_custom_id` | Retrieve a specific contact from Evenium by their custom ID (external database ID) | | **Get contact events** `evenium_get_contact_events` | Retrieve all events that a contact has been invited to or registered for | | **Get contact events by custom ID** `evenium_get_contact_events_by_custom_id` | Retrieves all events a contact has been invited to using their custom ID | | **Get contacts** `evenium_get_contacts` | Retrieve a list of contacts from Evenium | | **Get events** `evenium_get_events` | Retrieves a paginated list of events from Evenium with optional filtering and sorting | | **Create contact** `evenium_create_contact` | Create a new contact in the Evenium address book | | **Import contacts** `evenium_import_contacts` | Import multiple contacts at once (batch import) | | **Update contact** `evenium_update_contact` | Update an existing contact in Evenium by contact ID | | **Update contact by custom ID** `evenium_update_contact_by_custom_id` | Update a contact in Evenium by custom ID (external ID from your CRM/database) | | **Logout** `evenium_logout` | Log out the current user and invalidate the session token | ## Example prompts **Get Contact** > Pull the relevant data from Evenium, summarize it in plain English, and point out anything that needs attention. **Get Contact By Custom Id** > Pull the relevant data from Evenium, summarize it in plain English, and point out anything that needs attention. **Get Contact Events** > Pull the relevant data from Evenium, summarize it in plain English, and point out anything that needs attention. **Get Contact Events By Custom Id** > Pull the relevant data from Evenium, 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 Evenium working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Evenium API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Evenium 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 Evenium. | 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 Evenium actions to the runtime in a format your agent can reliably use. | 12 tools for Evenium are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Evenium 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 Evenium in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Evenium 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 Evenium skill but can't call the tools The ClawHub skill teaches OpenClaw about Evenium, but the calls run through the ClawLink plugin and your connected account. Make sure Evenium 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 Evenium 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 Evenium tools Evenium 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 Evenium 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. ### Evenium 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 Evenium has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Evenium integration? Yes. ClawLink is the fastest way to connect OpenClaw to Evenium: link your Evenium account once in the browser and OpenClaw can call the Evenium API through 12 ready-made tools — no custom code or token handling. ### How do I add Evenium to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Evenium skill from ClawHub, then you click Connect in the dashboard to authorize Evenium. OpenClaw calls the tools from the next message — no config files, and the Evenium key you paste is stored server-side instead of in your environment. ### How long does it take to connect Evenium to OpenClaw? About two minutes. Sign in, click Connect next to Evenium in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Evenium 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 Evenium working from chat. ### OpenClaw installed the Evenium skill but can't call the tools The ClawHub skill teaches OpenClaw about Evenium, but the calls run through the ClawLink plugin and your connected account. Make sure Evenium 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 - [Cal.com](https://claw-link.dev/openclaw/cal) — Schedule and manage bookings through Cal.com - [OpenClaw Bookingmood integration](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. - [Eventbrite](https://claw-link.dev/openclaw/eventbrite) — Create and manage events, tickets, and attendees