Lead Capture
Platform-native lead capture — no API key or setup required. Activate by setting {"type": "leads"} as the action in configure_form. Submissions are stored centrally in papi_leads. Use get-leads to retrieve them, update-status to track follow-up progress.
⚡ Built-in — No Setup Required
This integration is built into the WebsitePublisher platform. All endpoints are available immediately — no API key needed.
Endpoints (3)
POST
submit-lead
Store a lead from a form submission.
| Field | Type | Required | Description |
|---|---|---|---|
form_name |
string | No | Form identifier (e.g. "contact", "offerte"). Defaults to "default". |
fields |
array | ✓ Yes | Form field values as key-value object (e.g. {"name": "Jan", "email": "jan@example.nl"}) |
metadata |
array | No | Optional metadata: UTM parameters, IP address, referrer, etc. |
GET
get-leads
Retrieve leads captured via configure_form with action type "leads". Supports filtering by status, form_name, and date range.
| Field | Type | Required | Description |
|---|---|---|---|
page |
integer | No | Page number (default: 1) |
per_page |
integer | No | Records per page (default: 25, max: 100) |
status |
string | No | Filter by status: new, contacted, converted |
form_name |
string | No | Filter by form name |
date_from |
string | No | Filter from date (Y-m-d) |
date_to |
string | No | Filter to date (Y-m-d) |
POST
update-status
Update the status (and optionally metadata) of a lead.
| Field | Type | Required | Description |
|---|---|---|---|
lead_id |
integer | ✓ Yes | Lead ID to update |
status |
string | ✓ Yes | New status: new, callback, appointment, quoted, won, rejected |
metadata |
array | No | Optional metadata to merge into existing (e.g. {"offerte_bedrag": 4500.00}) |
MCP Tool Names
When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:
| Endpoint | MCP Tool Name |
|---|---|
| submit-lead | leads_submit_lead |
| get-leads | leads_get_leads |
| update-status | leads_update_status |