OpenClaw skill
Connect OpenClaw agents to third-party services through Scalekit. Supports LinkedIn, Notion, Slack, Gmail, and 50+ connectors.
Use the Scalekit AgentKit skill for OpenClaw to let your AI agents execute actions on third-party services directly from conversations. Search LinkedIn, read Notion pages, send Slack messages, query Snowflake, and more, all through Scalekit Connect without storing tokens or API keys in your agent.
When you ask Claude to interact with a third-party service, the skill:
- Finds the configured connector in Scalekit (e.g., Gmail connection setup) and identifies which connection to use based on the requested action
- Checks if the connection is active. For OAuth connections, it generates a magic link for new authorizations. For API key connections, it provides Dashboard guidance for setup
- Retrieves available tools and their parameter schemas for the connector, determining what actions are possible
- Calls the right tool with the correct parameters and returns the result to your conversation
- If no tool exists for the action, routes the request through Scalekit’s HTTP proxy, making direct API calls on your behalf
Your agent never stores tokens or API keys. Scalekit acts as a token vault, managing all OAuth tokens, API keys, and credentials. The skill retrieves only what it needs at runtime, scoped to the requesting user.
Prerequisites
Section titled “Prerequisites”- OpenClaw installed and configured
- A Scalekit account with AgentKit enabled: sign up at app.scalekit.com
python3anduvavailable in your PATH
Get started
Section titled “Get started”-
Install the skill
Section titled “Install the skill”Install the skill from ClawHub:
Terminal window clawhub install scalekit-agent-auth -
Configure credentials
Section titled “Configure credentials”Add your Scalekit credentials to
.envin your project root:.env TOOL_CLIENT_ID=skc_your_client_id # Your Scalekit client IDTOOL_CLIENT_SECRET=your_client_secret # Your Scalekit client secretTOOL_ENV_URL=https://your-env.scalekit.cloud # Your Scalekit environment URLTOOL_IDENTIFIER=your_default_user_identifier # Default user context for tool callsParameter Description TOOL_CLIENT_IDYour Scalekit client ID Required TOOL_CLIENT_SECRETYour Scalekit client secret Required TOOL_ENV_URLYour Scalekit environment URL Required TOOL_IDENTIFIERDefault user context for all tool calls Recommended -
You: Show me my latest unread emails
OpenClaw will automatically:
- Look up the
GMAILconnection - Verify it’s active (or generate a magic link to authorize if needed)
- Fetch the
gmail_list_emailstool schema - Return your latest unread emails
You: Read my Notion page https://notion.so/My-Page-abc123OpenClaw will:
- Look up the
NOTIONconnection - If not yet authorized, generate a magic link for you to complete OAuth
- Fetch the
notion_page_gettool schema - Return the page content
- Look up the
Supported connectors
Section titled “Supported connectors”Any connector configured in Scalekit works with the OpenClaw skill, including Notion, Slack, Gmail, Google Sheets, GitHub, Salesforce, HubSpot, Linear, Snowflake, Exa, HarvestAPI, and 50+ more.
Common scenarios
Section titled “Common scenarios”How do I authorize a new connection?
When you request an action for a connection that isn’t yet authorized, the skill automatically generates a magic link. Click the link to complete OAuth authorization in your browser. After authorization, return to your OpenClaw conversation and retry the action.
For API key-based connections (like Snowflake), you’ll need to configure credentials directly in the Scalekit Dashboard under Connections.
How do I switch between different user contexts?
Set TOOL_IDENTIFIER in your .env file to define a default user context. All tool calls will execute with that user’s permissions and connected accounts.
To use a different user context for a specific conversation, you can override the identifier by setting it in your OpenClaw configuration or passing it as a parameter when invoking the skill.
Why am I seeing a “connection not found” error?
This error occurs when the skill cannot find a configured connection for the requested connector. Check the following:
- Verify the connection exists: Go to Dashboard > Connections and confirm the connector is configured
- Check connection status: Ensure the connection shows as “Active” in the dashboard
- Verify environment: Confirm you’re using the correct
TOOL_ENV_URLfor your environment
How do I debug tool execution issues?
Enable debug logging in your OpenClaw configuration to see detailed information about tool calls:
TOOL_DEBUG=trueThis logs the tool name, parameters, and response for each execution, helping you identify issues with parameter formatting or API responses.