How to Connect the Universal Webhook for Any Lead Source

Most CRMs give you a fixed list of integrations and leave you stranded the moment a portal is not on it. India has dozens of niche lead sources — Practo for clinics, 99acres and MagicBricks for property, MakeMyTrip for travel, LinkedIn Lead Gen, admission portals — and no CRM ships a native connector for every one. The ASH universal webhook is the answer: a single URL that any portal, tool or backend can post a lead to, with source attribution built in.

One URL, any source

Open Settings → Integrations, choose Universal Lead Webhook and click Connect. ASH generates a private URL for your workspace. Anything that can send an HTTP request — a portal's own webhook, a Zapier or Make automation, an n8n flow, or your own server — can post JSON to it. The field mapping is the same forgiving logic used across ASH: name, phone, email, company, city, message and product or course are all recognised under their common variants.

Attribute the portal with ?source=

This is what makes the universal webhook more than a dumping ground. Add a query parameter to the URL — ?source=practo, ?source=99acres, ?source=linkedin, whatever fits — or include a source field in the body. ASH saves it as a lead tag, so even though these leads share one endpoint, you can filter your pipeline by the exact portal each came from. You finally get a clean answer to which portal is actually worth the subscription.

Track campaigns with UTM tags

You can pass utm_source, utm_medium and utm_campaign as query parameters or body fields. ASH stores them as tags, so campaign performance is filterable alongside the portal source. Combine both — a source and a UTM campaign — to attribute the portal and the campaign in one shot.

A typical setup for a portal with no push API

• Connect the universal webhook and copy the URL.
• In Zapier or Make, trigger on the portal's lead email with an email-parser step, or use its export.
• Add a "Webhooks → POST" action pointing at your ASH URL with ?source= set to the portal name.
• Map the enquiry's name, phone and message to the matching fields.
• Use the Test button to confirm auth, then send a real enquiry.

Where it fits

This is how property teams pull in portal enquiries and clinics route patient enquiries from aggregators that offer no direct integration. For your own site and landing pages, the dedicated website forms webhook is a cleaner fit, but when in doubt, the universal webhook will take the lead and tag it correctly.