For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

DOSClaw Connectors allow your AI agents to query live data, perform actions, and integrate business workflows with external platforms—including e-commerce stores, CRMs, social scheduling tools, accounting software, and developer services.

How Connectors Work

User in Chat
     │
     ▼
[AI Agent] ─── Decides to call tool (e.g. search_products)
     │
     ▼
[DOSClaw Model Context Protocol (MCP) Runtime]
     │
     ▼
[Connector Cache Shield] (Singleflight + In-memory TTL Cache)
     │
     ▼
[DOS-Me Vault] (Secure OAuth Tokens & API Credentials)
     │
     ▼
[Third-Party Service API] (Haravan, Shopee, HubSpot, etc.)

Two-Layer Security & Connection Architecture

Following the DOS Platform security model:

  1. Authentication & Token Storage (DOS-Me): OAuth connections, API tokens, and secret credentials are encrypted and stored in public.provider_connections and secured in the DOS-Me Vault. Raw secrets are never exposed to browser clients, agent containers, or LLM reasoning prompts.

  2. Agent Binding & Governance (DOS.AI): Individual AI agents are bound to provider connections via dosai.agent_connection_bindings. Workspace admins specify:

    • Enabled Tools: Selectively turn on or off specific capabilities (e.g. allow search_products and check_order_status, but disable create_order).

    • Governance Policy:

      • autonomous: Agent executes allowed read and write tools automatically.

      • approval_required: Agent prepares action parameters and requests human confirmation before mutating data.

      • draft_only: Agent can only read and prepare drafts; never commits live records.


Connector Directory

E-Commerce & Retail

CRM & Marketing

Finance & Invoicing

Productivity & Developer

  • Google Workspace — Google Sheets, Calendar & Meet, Drive documents.

  • GitHub — Issue triage, PR summaries, commit history.

  • Notion — Company wiki search, database queries, meeting notes.


Connector Cache Shield

High-traffic bots serving peak concurrent customer queries benefit from the built-in Connector Cache Shield:

  • Singleflight Requests: Prevents thundering herds by de-duplicating simultaneous requests for identical resources (e.g. 50 customers asking about the same flash-sale product).

  • Fast Read Cache: Safe read operations (product searches, category lists) are cached in memory for sub-10ms response times.

  • Fail-Closed Write Safety: Write and mutation operations (create_order, refund) always bypass the cache with strict idempotency keys.

Last updated