BotSyncBotSync
All features
Integrations

Connect the tools you already use — keep one source of truth.

Google Calendar, Google Sheets, SMTP, the website widget, webhooks, and your WhatsApp / Instagram credentials — all wired into the same CRM. OAuth where possible. No client ever has to paste an API secret. Lead data never scatters across silos.

Start free trialSee pricing
OAuth-first connections5+ core connectorsWebhook + HTTP request actions
OAuth — no API secrets needed
app.botsync.in/integrations

Connected workspace

Integrations · 6 connected

All healthy
Live

Google Calendar

anand@niet.in · +2 others

Live

Google Sheets

leads-sheet · admissions-sheet

Live

SMTP

alerts@niet.in

Live

Website widget

niet.in · 4 pages

Live

Webhooks

3 endpoints

Live

WhatsApp Cloud API

+91 88•• ••5430

The connectors lead-ops teams actually rely on — Calendar, Sheets, SMTP, website widget, webhooks. No fake “100+ integrations” counter.

What makes BotSync integrations different

Integrations that support lead ops — not replace your CRM

Most CRMs treat integrations as a marketplace. BotSync treats them as plumbing — a small set of well-built connectors wired into the conversation, lead, and booking model. Every connector exists to keep data in one place, not pull it apart.

OAuth, not API-secret hell

Google Calendar and Sheets connect with one OAuth click. Your team never asks clients to generate an API key or paste credentials.

Lead data stays in one CRM

Integrations support the CRM — they don't replace it. Calendar events, sheet rows, and SMTP alerts all reference the same lead.

Webhooks where you need them

Outbound HTTP requests from flows hit any internal system. Lead events also publish to your endpoints for downstream pipelines.

Google Calendar

Counsellors connect their own calendar — once

Each owner OAuths their Google Calendar in two clicks. BotSync reads free/busy in real time so the in-chat slot picker only shows actual openings, and writes bookings back as proper events with a Meet link.

  • Per-user OAuth connection (no shared service account)
  • Live free/busy lookup at the moment slots are shown
  • Bookings written as calendar events with Meet link
  • Buffer time, working hours, break days respected per counsellor

Connected calendars

Synced 2s ago
AR

Anand R.

anand@niet.in

MS

Meera S.

meera@niet.in

RP

Rohan P.

rohan@niet.in

OAuth in 2 clicks. No service account, no API key, no shared mailbox.

Google Sheets

Push lead data to Sheets — for the ops you can't move yet

Workflows sometimes still live in a sheet — a partner report, an admissions checklist, a finance ledger. BotSync writes selected lead fields into your sheet in real time, and you can use the connector inside flows as a node.

  • OAuth connection (per workspace, multiple sheets)
  • Sheets-append action inside any flow
  • Choose which fields go to which columns
  • Two-way? Not yet — Sheets is write-only on purpose to keep CRM as source of truth

Google Sheets · leads-sheet

Live
RowNameStageCity
2,418Priya SharmaQualifiedDelhi
2,417Rahul KumarBookedNoida
2,416Meera SinghInterestedGurgaon
2,415Aarav NairNewDelhi
Sheets is write-only by design — your CRM stays the source of truth. Use Sheets append inside any flow.

SMTP & website widget

Email alerts and a WhatsApp chat widget for your site

Use your own SMTP to send booking confirmations, internal alerts, and team reminders — no relying on a third-party email vendor. Drop the BotSync widget on your website to give visitors a one-tap WhatsApp jump-off; the lead arrives with source attribution.

  • Bring your own SMTP — host, port, TLS, sender
  • Templated email alerts (booking, lead-assigned, daily digest)
  • Embeddable WhatsApp widget — one line of HTML
  • Per-page widget customisation and tracking

SMTP

Connected

Host

smtp.niet.in:587

Sender

alerts@niet.in

TLS

Enforced

Last sent

2 min ago

Website widget

Live
<script src="https://widget.botsync.in/v1.js"
  data-workspace="niet" defer></script>
niet.in/admissionsniet.in/jee-2026niet.in/scholarshipniet.in/blog

Webhooks & HTTP request

Outbound webhooks and incoming events for everything else

Drop an HTTP request node into any flow to call your internal ERP, partner API, or notification webhook with the lead payload. Subscribe to BotSync events (lead created, stage changed, booking confirmed) and route them to your own pipeline.

  • HTTP request node inside flows (any method, headers, JSON body)
  • Variable substitution from lead, conversation, and form data
  • Outbound event webhooks: lead, conversation, booking, message
  • Retry-on-failure with backoff and dead-letter visibility

HTTP request node

Inside a flow

Method · URL

POSThttps://ops.niet.in/v1/lead

Headers

Authorization: Bearer {{secrets.ops_token}}
Content-Type: application/json

Body

{
  "lead_id": "{{lead.id}}",
  "name": "{{lead.name}}",
  "phone": "{{lead.phone}}",
  "stage": "{{lead.stage}}"
}
Retry-on-failure with backoff. Failed requests are visible in the dead-letter view.

Connector catalog

5+ core connectors — not a 100-item directory

Each connector is built into BotSync the way lead-ops actually uses it. No third-party iPaaS, no Zapier glue layer, no “coming soon” placeholders.

Google · OAuth

  • Google Calendar (per-counsellor)
  • Google Sheets (write-only)
  • Calendar buffer / break-days
  • Meet link on every booking

Messaging channels

  • WhatsApp Cloud API (official)
  • Instagram DM (in workspaces with enabled IG)
  • Per-channel routing rules
  • Per-channel template approvals

Web & email

  • Embeddable WhatsApp widget
  • BYO SMTP — host / port / TLS
  • Templated alerts (booking, daily digest)
  • Per-page widget customisation

Developer

  • HTTP request inside flows
  • Outbound event webhooks (lead, conversation, booking)
  • Variable substitution from lead context
  • Retry-on-failure + dead-letter

From connect to live

Plug in once, use it everywhere

01

Connect

Open Integrations, pick a connector, OAuth or paste credentials. Healthy connectors show green within seconds.

02

Configure

Each connector has a dedicated setup screen — pick which sheet, which calendar, which webhook endpoints.

03

Use it everywhere

Use the connector inside bookings, flows, forms, alerts. The same OAuth backs every reference.

04

Monitor health

Connection health is checked every 5 minutes. Failed tokens prompt a one-click reconnect.

BotSync vs typical WhatsApp tool integrations

Fewer connectors, built deeper

Many WhatsApp tools advertise “100+ integrations” — most of which are shallow Zap recipes. BotSync ships a small, opinionated set that actually carries lead ops.

CapabilityBotSyncOther WhatsApp tools
OAuth-first (no API secrets to paste)API keys per client
Per-counsellor calendar connectionSingle shared calendar
Sheets append inside flowsExternal Zap
BYO SMTP for email alertsVendor-controlled email
WhatsApp widget with source attributionGeneric chat embed
HTTP request node + outbound webhooksLimited Zapier-only
Connection health monitorSilent failures

FAQ

Common questions about integrations

Do users need to create their own Google Cloud project?+

No — for normal connection. The BotSync Google app is already configured, so users connect Google Calendar or Sheets with OAuth (one click). Enterprise customers who need a private Google project can BYO Cloud project — that's supported on request.

Can WhatsApp Cloud API stay manual?+

Yes. BotSync currently supports manual Cloud API setup and intentionally avoids the coexistence / QuickConnect flow in this phase. We document the manual setup well and most teams complete it in 15–30 minutes.

Is two-way sync to Google Sheets supported?+

No — and intentionally so. Sheets is a write target, not a source of truth. Two-way sync invariably creates ambiguity about which side is authoritative. The CRM stays the source of truth and sheets get rows appended for downstream tools.

Do integrations cost extra?+

No. All connectors are included in every plan. Webhook and HTTP request actions have generous per-month limits; if you exceed them we'll work with you on a usage-priced add-on — never a hard cut-off.

What about Zapier / Make / iPaaS?+

BotSync's outbound webhooks and HTTP request actions cover most of what teams reach for Zapier for. If you do want Zapier, our outbound webhook feeds the Zapier &ldquo;Webhooks by Zapier&rdquo; trigger directly.

Can I revoke an integration cleanly?+

Yes. From Integrations, disconnect any connector — OAuth tokens are revoked, scheduled jobs cancelled, and any flow node referencing it is marked &ldquo;disconnected&rdquo; so it doesn't fail silently.

What about Salesforce / HubSpot / other CRMs?+

Not on the current roadmap — BotSync is positioned as a CRM, not a sync layer for another one. If you must keep an existing CRM as the system of record, our outbound webhooks can ship lead events to it.

Pair it with

What benefits most from integrations

Bookings

Calendar sync powers in-chat slot picking.

Learn more

Flow builder

Sheets append, webhooks, and HTTP request are flow nodes.

Learn more

Forms

Widget leads carry source into the same CRM model.

Learn more

WhatsApp Cloud API

The messaging channel underneath every connector.

Learn more

Plug in Calendar, Sheets, SMTP, widget, webhooks — in minutes

Bring your tools in — keep one CRM

14-day free trial. OAuth Google Calendar in two clicks, drop in your SMTP, paste the widget snippet on your site, and start firing webhooks the same day.

Start free trialSee pricing