C
Cody
OpenClaw Integrations

How to Connect Close CRM to OpenClaw: Setup, Models, and Workflow Guide

·5 min read

If you're searching for "how to connect Close CRM to OpenClaw", the real question is usually not just whether the connection is possible. It's how to make Close CRM usable inside an OpenClaw workflow with the right model, the right context, and the right level of control.

That's the practical framing.

OpenClaw gives you the orchestration layer: connectors, skills, tools, prompts, approvals, and the ability to run workflows where your team already works. Close CRM provides the domain context. The integration becomes valuable when those two pieces are connected cleanly.

What “Connect Close CRM to OpenClaw” Actually Means

In practice, connecting Close CRM to OpenClaw usually involves four layers:

  • Authentication so OpenClaw can securely access Close CRM
  • Tooling or proxy endpoints that expose the right Close CRM actions and data
  • Skills/instructions that tell OpenClaw how to reason over Close CRM context
  • Model selection so the assistant uses the right LLM for the job

That last piece matters more than most people expect.

Which Models Can You Use?

OpenClaw is model-flexible, so a Close CRM integration does not need to be tied to a single provider. Depending on your setup, teams commonly want to use:

  • OpenAI models like GPT-4o, GPT-4.1, and o3 for broad reasoning and tool use
  • Anthropic models like Claude 3.5 Sonnet, Claude Sonnet 4/4.5, and Claude Opus for strong writing, analysis, and long-context work
  • Google models like Gemini 1.5 Pro or newer Gemini models for multimodal and large-context workflows
  • Other model backends if your OpenClaw environment exposes them

The practical point: you can connect Close CRM to OpenClaw once, then run different workflows with different models depending on the job.

For example:

  • Use Claude for nuanced summarisation or drafting
  • Use OpenAI for structured extraction, tool-heavy workflows, or general-purpose copiloting
  • Use Gemini when multimodal or very large context windows matter

A Good Integration Pattern for Close CRM

A strong Close CRM + OpenClaw setup usually looks like this:

  1. OpenClaw receives a request in chat or from an automation
  2. It calls the right Close CRM endpoint or proxy
  3. The selected model reasons over the returned context
  4. OpenClaw returns an answer, draft, classification, or action
  5. High-risk actions stay behind approvals or structured guardrails

That is what makes the setup operational rather than just experimental.

Step-by-Step: Connect Close CRM to OpenClaw

Step 1: Get Your Close API Key

Log into Close and go to Settings → Developer → API Keys. Create an API key. The Close REST API base URL is https://api.close.com/api/v1/. Authentication uses HTTP Basic with the API key as the username and an empty password.

Step 2: Use the Lead and Activity Endpoints

Key endpoints: /lead (search and list leads), /lead/{id}/ (lead detail with contacts and activities), /activity (log of all activities across leads — calls, emails, notes), /opportunity (deal pipeline and stage data). Close uses a _search query parameter on most list endpoints for flexible filtering.

Step 3: Build the Proxy and Skill File

Build your proxy around lead search and opportunity endpoints. Write ~/.openclaw/skills/close.md with your pipeline stage names and common query patterns. Close's activity log is particularly useful — include instructions for querying recent call/email activity for a specific lead.

Model-Specific Workflow Ideas

Close CRM + OpenAI

Use this when you want a strong general-purpose setup for extraction, classification, action planning, and tool-driven workflows around Close CRM.

Close CRM + Claude

Use this when you want better writing quality, clearer summaries, stronger nuance, and reliable long-context reasoning over Close CRM data.

Close CRM + Gemini

Use this when the workflow benefits from large context windows, multimodal inputs, or Google-native ecosystem alignment.

Common Mistakes

Most teams do not fail because the model is bad. They fail because:

  • the Close CRM connection is too thin
  • the model lacks the right live context
  • prompts are vague
  • no structured outputs are enforced
  • permissions and approvals are skipped
  • one model is forced to do every job, even when another would be a better fit

The best setup is usually one integration layer, multiple model options, and clear guardrails.

Challenges and Caveats

Lead vs Contact vs Opportunity Hierarchy

Close organises data as Leads (companies) → Contacts (people) → Opportunities (deals). Understanding this hierarchy is essential for writing a useful skill file. A query about "a deal" maps to Opportunities; "a person" maps to Contacts under a Lead.

Rate Limits Apply

Close's API has rate limits that vary by plan. For teams with many reps all using OpenClaw simultaneously, parallel queries can hit limits. Build retry logic and caching into your proxy.

Want Close CRM Connected to OpenClaw Without Building the Whole Stack Yourself?

Cody has Close CRM integration built in. Query deals and activity history from Slack without API configuration.

Get started with Cody →

Related OpenClaw Guides

Looking for a more workflow-first angle? See: Close CRM AI Automation and Close CRM AI Assistant.

← Back to all guides