How to connect Exist to OpenClaw
Connect Exist to OpenClaw with ClawLink in one click — 12 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
ExistOAUTH2MCPTrack and analyze personal health, fitness, and lifestyle data. Once connected, OpenClaw can read and act on Exist from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Exist 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 Exist setup: install one ClawHub skill, connect Exist in the browser, and OpenClaw can call real Exist actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Exist skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Exist" (hith3sh/exist) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/exist
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Exist.
1Install 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
Connect Exist
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Exist?"
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-pluginThen 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 Exist in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Pull the relevant data from Exist, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Exist is connected in the dashboard, that agent calls the same 12 Exist tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Exist MCP for OpenClaw
Looking for a Exist MCP server for OpenClaw? ClawLink connects Exist to OpenClaw and exposes 12 Exist tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Exist integration works the same way.
What the OpenClaw Exist integration can do
12 Exist tools are ready for OpenClaw once the account is connected.
All 12 Exist tools for OpenClaw
| Tool | What it does |
|---|---|
Get attribute templates exist_get_attribute_templates | Retrieve a paged list of supported attribute templates |
Get attributes with values exist_get_attributes_with_values | Retrieve attributes with their current values for the authenticated user |
Get averages exist_get_averages | Retrieve the most recent average values for each tracked attribute, with one set per week |
Get correlations exist_get_correlations | Retrieve a paginated list of correlations discovered between tracked attributes in the last week |
Get insights exist_get_insights | Retrieve automatically-generated insights about patterns in tracked data for the authenticated |
Get owned attributes exist_get_owned_attributes | Retrieve attributes owned by your service for the authenticated user |
Get user attributes exist_get_user_attributes | Retrieve a paged list of the user's attributes without values |
Get user profile exist_get_user_profile | Retrieve the authenticated user's profile details and preferences |
Oauth2 authorize exist_oauth2_authorize | Constructs an OAuth2 authorization URL for Exist.io |
Acquire attribute ownership exist_acquire_attribute_ownership | Acquire ownership of attributes for the authenticated user |
Increment attribute values exist_increment_attribute_values | Increment attribute values by a delta amount rather than setting totals |
Release attribute ownership exist_release_attribute_ownership | Release ownership of attributes for the authenticated user |
Try it: find the Exist tool you need
Browse the 12 Exist tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Exist, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Exist, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Exist, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Exist, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Exist working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Exist app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Exist through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Exist. | 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 Exist actions to the runtime in a format your agent can reliably use. | 12 tools for Exist are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Exist 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 Exist in the browser, and the 12 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Exist skill but can't call the tools
The ClawHub skill teaches OpenClaw about Exist, but the calls run through the ClawLink plugin and your connected account. Make sure Exist 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 Exist 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 Exist tools
Exist 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 Exist 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.
Exist 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Exist and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Exist integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Exist: link your Exist account once in the browser and OpenClaw can call the Exist API through 12 ready-made tools — no custom code or token handling.
How do I add Exist to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Exist skill from ClawHub, then you click Connect in the dashboard to authorize Exist. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Exist to OpenClaw?
About two minutes. Sign in, click Connect next to Exist in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Exist up myself?
The alternative to ClawLink is usually manual OAuth app 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 Exist working from chat.
OpenClaw installed the Exist skill but can't call the tools
The ClawHub skill teaches OpenClaw about Exist, but the calls run through the ClawLink plugin and your connected account. Make sure Exist 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.
