Webhooks
Send every new lead as JSON to a URL of your own: your app, Make, n8n or any tool that takes a webhook.
Connect the MCP server, then just ask.
| create_automation | Creates an automation that is active straight away and runs whenever a lead matches it. | Changes data |
| test_webhook | Sends a sample lead, as automations send them, to a URL so you can check your endpoint receives and parses it. | Changes data |
| get_automation_runs | The runs of one automation, newest first: which lead each run handled, when, and whether it succeeded (and why not). | Read-only |
Use case
Send every new lead to my n8n webhook.
Called create_automationShow input
{
"websiteId": "64b7f0a1c2d3e4f5a6b7c8d9",
"name": "New leads to n8n",
"trigger": {
"then": "trigger-webhook",
"actions": {
"sentToWebhook": {
"url": "https://n8n.example/webhook/leads",
"whenToPush": "every-time"
}
}
}
}Use case
Test my webhook with a sample lead.
Called test_webhookShow input
{
"websiteId": "64b7f0a1c2d3e4f5a6b7c8d9",
"webhook": "https://n8n.example/webhook/leads"
}Your assistant reports the status your endpoint answered. A failing URL is the usual reason a webhook automation shows failed runs.
Use case
Did my n8n webhook receive yesterday's leads?
Called get_automation_runsShow input
{
"websiteId": "64b7f0a1c2d3e4f5a6b7c8d9",
"automationId": "64b7f0a1c2d3e4f5a6b7c8e3",
"limit": 50
}Each run names the lead, when it ran and whether your endpoint accepted it (and why not). Failed ones can be sent again with rerun_automation_for_lead (type webhook).