Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

OpenClaw skill

Connect OpenClaw agents to third-party services through Scalekit. Supports LinkedIn, Notion, Slack, Gmail, and 50+ connectors.

OpenClaw agentScalekit AgentKitThird-party servicesOAuth handlerToken vaultLinkedInGmailSalesforce50+ more Execute tools

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.

  1. Install the skill from ClawHub:

    Terminal window
    clawhub install scalekit-agent-auth
  2. Add your Scalekit credentials to .env in your project root:

    .env
    TOOL_CLIENT_ID=skc_your_client_id # Your Scalekit client ID
    TOOL_CLIENT_SECRET=your_client_secret # Your Scalekit client secret
    TOOL_ENV_URL=https://your-env.scalekit.cloud # Your Scalekit environment URL
    TOOL_IDENTIFIER=your_default_user_identifier # Default user context for tool calls
    ParameterDescription
    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
  3. You: Show me my latest unread emails

    OpenClaw will automatically:

    1. Look up the GMAIL connection
    2. Verify it’s active (or generate a magic link to authorize if needed)
    3. Fetch the gmail_list_emails tool schema
    4. Return your latest unread emails

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.

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:

  1. Verify the connection exists: Go to Dashboard > Connections and confirm the connector is configured
  2. Check connection status: Ensure the connection shows as “Active” in the dashboard
  3. Verify environment: Confirm you’re using the correct TOOL_ENV_URL for your environment
How do I debug tool execution issues?

Enable debug logging in your OpenClaw configuration to see detailed information about tool calls:

Terminal window
TOOL_DEBUG=true

This logs the tool name, parameters, and response for each execution, helping you identify issues with parameter formatting or API responses.