Pipedrive is often where SMB sales teams keep deal stages, people, organisations, and activity history, but the useful story still gets buried across pipeline views and rep activity logs. A Pipedrive AI assistant is most useful when it helps teams review pipeline movement, surface deals with no next step, pull together account context, and turn CRM movement into clearer follow-ups and Slack updates. If you are running OpenClaw yourself, Pipedrive is still one of the simpler CRM integrations to build, but Cody is the faster path if you want the assistant experience instead of the API glue.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Pipedrive — it's considerably more involved.
Connecting OpenClaw with Pipedrive: Step by Step
Step 1: Get Your Pipedrive API Token
Go to Pipedrive → Personal Preferences → API and copy your personal API token. All API requests are authenticated by appending ?api_token=YOUR_TOKEN to the URL or using it as a Bearer token. The base URL is https://{your-company}.pipedrive.com/api/v1.
Step 2: Identify Your Key Endpoints
Pipedrive's main objects are Deals, Persons, Organizations, Activities, and Pipelines. The /deals endpoint with ?status=open and ?sort=update_time+DESC gives you an always-fresh view of the pipeline. The /deals/search endpoint lets you find deals by title or person name.
Step 3: Build the Proxy and Skill File
Build a proxy around the deals, persons, and activities endpoints. Include your pipeline stage IDs in ~/.openclaw/skills/pipedrive.md (Pipedrive uses numeric IDs for stages, so translating stage names to IDs in the skill file prevents Claude from guessing wrong).
Challenges and Caveats
Pagination Applies to All List Endpoints
Pipedrive paginates results with a default limit of 100 items. If you want to summarise the full pipeline, your proxy may need to handle multiple pages. Build pagination handling in from the start.
Custom Fields Use Hashed Key Names
Pipedrive custom fields are returned with auto-generated hash keys (e.g., abc123def456), not human-readable names. You'll need to map these to readable names in your proxy or skill file.
Skip All of This — Use Cody Instead
Cody gives your team a Pipedrive AI assistant in Slack, so reps and managers can review pipeline movement, stalled deals, people, organisations, and next activities without living inside board views, filters, and CRM records all day.
Related Guides
- Connecting OpenClaw with Hubspot: A Practical Guide
- Connecting OpenClaw with Salesforce: A Practical Guide
- Connecting OpenClaw with Close Crm: A Practical Guide
Need the model-flexible version? See: How to Connect Pipedrive to OpenClaw: Setup, Models, and Workflow Guide.