---
ref: tool:pipedrive/create-lead
name: Create a lead
company: company:pipedrive
workflows: []
access: [mcp, api]
tags: [capability:manage-crm, category:crm, has:api, has:mcp]
docs: https://developers.pipedrive.com/docs/api/v1/Leads#addLead
updated: 2026-09-27
---

# Create a lead

Adds a lead to the Leads Inbox, linked to an existing person, organization or both, and returns it.

Note: A lead must be linked to a `person_id` or `organization_id`, so create the person or organization first.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "pipedrive": { "url": "https://mcp.pipedrive.ai/mcp" } } }
```

Call the MCP tool `addLead`.

Server URL: https://mcp.pipedrive.ai/mcp

### API (official)

- Base URL: https://{company_domain}.pipedrive.com
- Endpoint: `POST /api/v1/leads`
- Auth: send the header `x-api-token: $PIPEDRIVE_API_KEY`
- Get a key: https://app.pipedrive.com/settings/api
- Docs: https://developers.pipedrive.com/docs/api/v1

Note: `{company_domain}` comes from `GET https://api.pipedrive.com/v1/users/me`. Persons, organizations, deals and activities are on `/api/v2/`; leads and notes on `/api/v1/`.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.