PipMCP CONNECTORS
ONE LEADADAPTER API KEY

Read and export captured leads

Read workspace-scoped leads, apply documented filters and paginate the API export into your own destination mapping.

Use the project that fits your workflow

Use the repository release matching the documented SDK/bridge version; existing repository publication does not prove every newer asset is released.

Provider setup and evidence

Full LeadAdapter solution, SDK resources and remote MCP bridge

Access and approval

An export is API data, not a preconfigured connector to every third-party CRM.

Start from the matching SDK release

Node.js

client.leads.export({limit: 10})

Python

client.leads.export(limit=10)

Resource examples assume an initialized SDK client with your workspace key. The fixture workflow executes synthetic backend responses; it makes no provider calls. Live execution requires the documented account access and checkpoint/review options.

Capability and evidence

Contract-tested client code; version-specific release required. Not established by task discovery. A published repository, a discovered tool and a successful provider result are different facts.

Selected operation IDs: list_leads_get, export_leads_get.

Machine-readable task definitions