Skip to main content
No. ClawLink stores provider credentials on its side, encrypted at rest. Your local client stores only the ClawLink device credential created during pairing.
ClawLink supports a growing catalog of 100+ apps across communication, productivity, developer tools, CRM, payments, analytics, storage, marketing, AI, and commerce. The docs site covers the most common categories and setup guides, but the dashboard catalog is the current source of truth.
Install the plugin, start browser pairing, approve the device, then connect apps from Dashboard > Connections. See OpenClaw setup for the full walkthrough.
Open Dashboard > Install, copy the Hermes bootstrap prompt, paste it into Hermes, approve the browser pairing flow, then connect apps from the dashboard. See Hermes setup.
Use Dashboard > Request App if it is available in your account, or open an issue in the main ClawLink repository.
Older docs mixed together install, pairing, and edge-case support articles. The current recommended path is simpler: install once, pair once, connect apps from the dashboard, then use them from your agent.
No for normal use. If you want to extend the platform or contribute integrations, that does require working in the main codebase.
ClawLink retries transient failures when it can. If a request still fails, the failure is recorded in Usage so you can inspect the integration, action, status, and latency.
There is a 30-day trial. After that, ClawLink costs $4.99/month if you want to keep access active. See the Billing page for details.
For bugs or feature requests, open an issue on the ClawLink repository. For account-related questions, use the dashboard support or feedback path available in your workspace.