Your enquiries arrive from a Meta ad, a Google Form, a property portal, a WhatsApp message and a spreadsheet somebody keeps on their laptop. Nexvork's integrations hub collects all of them, maps the fields once, scores what comes in and starts the follow-up. This page says plainly which connections are built in, which run through a webhook, and which we scope with you during onboarding.
Software companies love the word "integration". We use three words instead, so you know before you buy whether a connection is switched on in an afternoon or scoped as a small project.
Switched on from the integrations hub inside your workspace. No third-party tool, no extra subscription, no developer. Your onboarding team usually does it with you on the first call.
Nexvork sends and receives; a middle tool you already use — Zapier, Make, Pabbly Connect, a Google Sheet — does the plumbing. Reliable, but it is one more thing you own and pay for.
Set up per customer, not switched on by default. These depend on your own accounts, keys and software versions, so ask us before you assume one is already there.
These live inside Nexvork. Every one of them feeds the same lead record, the same scoring and workflow engine and the same WhatsApp inbox, so a customer who arrives from an ad and later messages your number stays one person.
Salon & spa: tomorrow's appointment reminder with Confirm and Reschedule buttons. Real estate: a site-visit invite in Marathi with two slot buttons.
Gym & fitness: a free-trial ad at 11 PM creates the lead, scores it and sends the first WhatsApp long before your counsellor is awake.
Clinics & hospitals: a health-camp registration form fills the OPD list and triggers a reminder the evening before the camp.
Interior design: a visitor asks for a 3BHK estimate at midnight, the assistant qualifies the budget and books a site measurement.
Medical & pharmacy: two years of billing history imported once gives the refill engine something real to predict from.
Gym & fitness: the renewal reminder carries the exact amount and a UPI link, so the member pays from the same chat instead of promising to visit.
Real estate: the site-visit confirmation carries the exact plot location. Clinics: the branch pin travels with the OPD token.
lead.created, lead.updated, deal.won, appointment.booked, whatsapp.message_in and more.Any business: push enquiries from a custom site, or receive won deals into your own dashboard. The payload is printed in full below.
Builders & developers: a channel partner's enquiry is logged at the site office and the sales head sees it on the web the same second. Ask for the app link at your demo.
There is no partnership badge here and none is needed. Nexvork exposes a signed inbound endpoint and fires outbound events, so any automation tool in the middle can join your stack to the CRM. You own that tool and its subscription — we are just honest about where the line is.
Coaching & education: the counsellor's enquiry sheet keeps filling itself while the CRM runs the follow-ups.
Interior design: a won deal creates the project folder and pings the site supervisor without anyone retyping the client's name.
Clinics & hospitals: enrich a camp enquiry with its pin code, then create it in the nearest branch's pipeline.
Salon & spa: an appointment marked done drops the customer into a review-request workflow the next morning.
Any business: billing software, a booking engine, an in-house portal — no special partnership needed on either side.
Real estate: a portal enquiry is de-duplicated against your existing leads, scored, matched to inventory and assigned by locality. What a feed can do varies by portal and by the plan you hold with them, so we check yours during onboarding. More on the real estate edition.
Nothing in this list is switched on by default, and none of it is a checkbox in your workspace. Each one leans on accounts, keys and software versions that belong to you, so we scope it with you during onboarding, tell you what it will take, and say no when the honest answer is no.
Collect on a link and have the CRM mark the invoice paid on its own. Needs your own merchant account, completed KYC and API keys; we design the flow with you and connect it during onboarding.
Push customers, invoices or GST-ready summaries out of the CRM. What is possible depends heavily on the version and hosting of your accounting software, so we look at yours before promising a date.
Mirror appointments, site visits and OPD slots to the calendars you choose, so a doctor or designer sees the day without opening the CRM. Configured per workspace and per calendar.
Click-to-call, recording links against the lead and missed-call numbers turned into enquiries. This depends entirely on what your telecom vendor's API exposes, which varies by vendor.
A text for customers who do not use WhatsApp. Under Indian rules this needs your own DLT registration, a sender ID and templates approved on the DLT portal before a single message goes out.
Inventory, billing or ERP software written for you. If it exposes an API or can send a webhook we can usually meet it; if it cannot, a scheduled file exchange is the honest answer and we will say so.
Five steps, the same for a Meta lead form and a webhook from your own software. Nobody on your team writes code, and nobody re-types a phone number.
Choose a native source and sign in, or paste the endpoint and secret for a webhook. Nexvork asks for the smallest permission that makes the connection work, stores the token encrypted, and lets you revoke it from the same screen the day you change your mind.
Drag the incoming fields onto CRM fields — name, phone, budget, locality, requirement, campaign. Phone number is the de-duplication key, so a customer who arrives twice stays one record with both sources on it. Anything that has no home becomes a custom field in a click.
The lead is scored on budget, urgency, source and behaviour, matched against your inventory or services, and assigned to the right person by locality, branch, doctor or product line — with a response deadline attached. This is the same engine described on the AI automation page.
The first WhatsApp goes out in the customer's language with a brochure, a slot button, a Maps link or a UPI link. A task appears for the assigned staff member, and outbound webhooks tell your other systems that a lead now exists.
Every lead keeps its source, campaign and first-touch time all the way to the won deal, so the monthly report answers the only question that matters: which of these connections paid for itself, and which one you should switch off.
One inbound endpoint per workspace, outbound events for everything that happens inside it, and a payload with no surprises. If your developer reads one section of this page, make it this one.
The same hub, wearing six different uniforms. Each recipe is switched on during onboarding for the edition you pick — you can change any part of it later.
Every integration is a credential somebody is trusting you with. Here is how Nexvork treats yours.
Each connection carries its own token, stored encrypted and never displayed again after setup. Outbound calls are signed with an HMAC SHA-256 secret so your endpoint can prove the request came from Nexvork. Rotate or revoke anything from the hub.
An integration belongs to exactly one workspace. A webhook, an automation tool or the AI assistant can only touch records inside it — never another customer's data, and never a sibling branch you have not given access to.
Your CRM, its integration logs and every payload we keep run on cloud infrastructure in India, encrypted in transit with TLS, behind role-based access and daily backups.
Every delivery is recorded with its status, latency and response body. Failed calls retry with back-off and then alert you, duplicates collapse on phone number, and you can replay a payload once your endpoint is healthy again.
More detail on how the platform is built and secured is on the AI automation page, and the full policy lives in our privacy policy.
Straight answers on what is built in, what runs through a webhook, and what we will not promise.
The native tier on this page: WhatsApp Business API, Meta lead ads for Facebook and Instagram, Google Forms, website forms and the Nexvork chat widget, Excel and CSV import and export, UPI payment links inside WhatsApp messages, Google Maps links for visits and appointments, inbound and outbound webhooks, and the Nexvork mobile app for Android and iOS. Those are switched on from the integrations hub inside your own workspace, with no third-party subscription in between.
No, and we would rather say so plainly. Portal enquiries are brought in as a lead source — through the feed, forwarding or webhook your portal account supports, or a scheduled Excel import — so they are de-duplicated, scored and assigned like any other lead. Nexvork does not publish, update or withdraw your listings on those portals, and what a feed can do varies by portal and by the plan you hold with them.
Yes. Nexvork connects your business number to the official WhatsApp Business API from Meta. The number is verified, message templates are submitted for approval in English, Hindi or Marathi, and opt-ins and opt-outs are recorded against each contact. We do not use unofficial bulk-sending tools — that is what keeps a business number safe.
Not for the native tier. Connecting a source, mapping its fields and choosing what happens next is done from menus inside your workspace. A developer is only needed if you want to push data in from a custom system or receive our outbound webhooks, and even then it is one signed HTTPS endpoint. Our team sits with yours during onboarding and does the first one together.
These are on-request integrations. They are scoped with you during onboarding and set up per customer rather than switched on by default, because each one depends on your own accounts, keys and software versions. Tell us what you run at your demo and we will say honestly what is possible, what needs a file exchange instead, and what is not worth building.
Every delivery is logged with its status and response body. A failed outbound call retries with exponential back-off and then alerts you, and you can replay the payload from the hub once your endpoint is fixed. Incoming leads are de-duplicated on phone number, so the same person arriving from an ad and a portal becomes one record carrying both sources.
If it can send or receive a webhook, this is usually a short conversation. If it cannot, we will say so instead of selling you a maybe. Bring your list to the demo and we will mark every item native, connector or on request before you sign anything.
One AI platform, tuned to your business. Book a personalised demo — our team sets it up for your industry and walks you through it in English, Hindi or Marathi.
We use cookies for website analytics and to measure our ads, so we can improve Nexvork for you. See our Cookie Policy.