Lusha

@lusha list all active webhook subscriptions and show me which signals each one is tracking

Found 4 active webhook subscriptions in your Lusha account: 1. 'Sales Alerts' → tracking job_change and promotion signals, posting to https://hooks.example.com/sales 2. 'Account Updates' → tracking company_funding and company_news, posting to https://hooks.example.com/accounts 3. 'Lead Enrichment' → tracking contact_email_change, posting to https://hooks.example.com/leads 4. 'Executive Moves' → tracking job_change (C-level only filter), posting to https://hooks.example.com/exec All subscriptions are active and delivering successfully. Last delivery timestamps range from 2 hours to 1 day ago.

This example shows the MCP's read capability for subscription management. Lusha's webhook system requires you to have a publicly accessible endpoint to receive signals. The MCP lists configurations but doesn't show the actual signal payloads—those arrive at your webhook URLs in real time when events occur.

@lusha create a new webhook subscription called 'Competitor Tracking' that notifies us when any contact at Acme Corp or Globex changes jobs

Created webhook subscription 'Competitor Tracking' (ID: sub_8x9k2m4p). Configuration: - Signals: job_change - Webhook URL: https://hooks.example.com/competitor (from your default endpoint) - Company filters: Acme Corp, Globex - Status: Active This subscription will now send POST requests to your webhook URL whenever Lusha detects a job change for contacts at the specified companies. Make sure your endpoint can handle the webhook payload format and returns a 200 status code to confirm receipt.

This demonstrates the MCP's write capability for creating real-time data subscriptions. Lusha charges credits when signals fire, so overly broad subscriptions can consume your quota quickly. The MCP creates the subscription but you must implement the webhook endpoint yourself—Lusha will POST JSON payloads there when matching events occur.

@lusha pull the last 7 days of audit logs and tell me if any webhook deliveries are failing consistently

Analyzed 847 audit log entries from the past 7 days: **Webhook Delivery Health:** - Overall success rate: 94.2% (798 successful, 49 failed) - Problem subscription: 'Lead Enrichment' (sub_3k7n1x) has 41 failures (84% failure rate) - Error pattern: HTTP 503 Service Unavailable from https://hooks.example.com/leads - Other subscriptions: all above 98% success rate **Recommendation:** The 'Lead Enrichment' webhook endpoint appears to be down or overloaded. Check your server logs at hooks.example.com/leads. Consider pausing this subscription until the endpoint is stable to avoid losing signal data.

This synthesis example pairs Lusha's audit log data with AI reasoning to surface operational issues. Audit logs show webhook delivery attempts and API calls, but retention is limited (typically 30 days). Failed webhook deliveries don't retry automatically—you'll need to re-fetch missed data manually or fix the endpoint and wait for new signals.

When Lusha's webhook MCP beats manual CRM enrichment

A 6-person sales team closes 40-60 deals a month and routes leads by seniority and industry vertical. They use Lusha's job-change signals to catch decision-makers who just switched companies—prime buying windows. The MCP's Create Subscription and List Subscriptions tools let them pipe those signals straight into their CRM without a Zapier tax or manual CSV uploads. The catch: this only pays off if your team closes at least 20 deals a month where timing matters. Below that threshold, a weekly manual check in Lusha's dashboard is faster than debugging webhook delivery failures. If your close rate depends on catching people in transition, the MCP turns signal-to-outreach lag from days to minutes.

Why the audit-log tools matter for multi-tool stacks

A 3-person RevOps team runs Lusha webhooks into HubSpot, Slack, and a homegrown scoring model. When a webhook silently fails, leads go cold for 48 hours before anyone notices. The MCP's Get Audit Logs and Get Audit Log Stats tools surface delivery failures and success rates without logging into Lusha's portal. They check stats daily in a shared Switchy thread and triage errors before the sales team asks why leads aren't flowing. This scenario works if you're already running at least two downstream systems off Lusha signals. If you're only pushing to one CRM, the native Lusha dashboard is enough—the MCP adds overhead without upside. Use this when webhook reliability is a revenue blocker, not a nice-to-have.

When job-change signals drive upsell timing for CS teams

A 4-person customer success team manages 120 mid-market accounts and owns upsell quota. They subscribe to Lusha's job-change signals for their install base: when a champion gets promoted or a new VP joins, it's a re-engagement window. The MCP's Update Subscription tool lets them adjust signal filters as their ICP shifts without re-configuring webhooks in the Lusha UI. The trade-off: this only scales if your CS team already tracks account health in a tool that can ingest webhooks. If you're still living in spreadsheets, the MCP won't fix that—you'll spend more time debugging delivery than acting on signals. If your upsell motion depends on timing and you have the infrastructure to route signals, this MCP turns CS from reactive to predictive.