Everything connects to WatEase

How WatEase integrations work

Every integration on WatEase is shipped as a first-party connector — no Zapier middleman, no copy-paste API keys, no per-action usage fee. Each connector handles its own OAuth flow, webhook registration, retry / backoff policy, and reconciliation cadence, so a misbehaving upstream never silently drops orders. The sections below explain what each category covers, the actual providers we connect to, and the operational invariants we maintain on top.

Payments — Razorpay, PhonePe, Paytm, direct UPI

Indian buyers expect UPI as a first-class option, with cards and netbanking as second. WatEase wires UPI deep-links directly so customers tap once and pay from PhonePe, Google Pay, Paytm, or BHIM without leaving WhatsApp. Razorpay covers cards, netbanking, and wallet rails; PhonePe and Paytm are available as alternative UPI/wallet processors. Refunds, partial refunds, and dispute evidence flow back into the order timeline automatically. Stripe and PayPal are intentionally not on the integration list — their Indian rates are non-competitive and the merchant-of-record model conflicts with Indian GST invoicing.

E-commerce — Shopify, WooCommerce

A store you already run stays where it is. Shopify connects through OAuth or custom-app credentials and syncs products, inventory, orders, customers and abandoned checkouts, with a three-step WhatsApp recovery ladder on top. WooCommerce connects with the REST API keys the store issues and syncs products and orders by webhook and a scheduled catch-up pull; orders WatEase takes on WhatsApp are published back into the store, and shipped or cancelled states are written through. Neither needs a migration — WhatsApp ordering, marketing, the inbox and the agents run on top of the store.

Shipping — Shiprocket, with Delhivery and Blue Dart on its network

Shiprocket aggregates the major Indian carriers behind one API and is the default for Tier-1/2/3 reach without negotiating individual carrier contracts; Delhivery and Blue Dart ride on its courier network rather than as separate connectors. WatEase books the courier, generates the AWB and label, and pushes shipment events back to the customer over WhatsApp — picked up, in transit, out for delivery, delivered, returned to origin — with each movement driving the order's own state.

Messaging — WhatsApp, Facebook, Instagram, Email

WatEase connects to WhatsApp Business Cloud API — access is included in every plan, with template management, opt-in capture, quality-rating monitoring, and conversation categorisation handled inside the product. Facebook Messenger and Instagram Direct flow into the same unified inbox so an agent replies once across every surface. Email rounds out the stack for transactional alerts.

Analytics — Google Analytics 4, Meta Pixel, Google Ads, Sheets

GA4 receives e-commerce events (view_item, add_to_cart, begin_checkout, purchase) so attribution and funnel reports work without taping events together by hand. Meta Pixel + Conversions API ship server-side events (deduplicated against client-side) so retargeting works under iOS 14.5+ and stays accurate when cookies get blocked. Google Ads enhanced conversions, offline conversions, and customer match audiences are fed from the CRM. CSV data exports are available across plans for teams that want raw data outside the dashboard.

Back office — Tally, Zoho, webhook API

Tally is the canonical Indian SMB accounting target — WatEase exports invoices, payments, and stock in Tally-importable XML. Zoho Books is on the public roadmap — planned, not yet connectable — and sync with Zoho CRM, HubSpot, Salesforce, Freshsales or Pipedrive is available as a customisation on request. The generic webhook API exposes every WatEase event (order.created, payment.captured, message.received, etc.) so internal ERPs or custom integrations can plug in. Webhook payloads are HMAC-signed with a per-tenant secret, carry idempotency keys, and retry on 5xx before surfacing as a delivery failure in the dashboard.

Security & compliance

API credentials are encrypted at rest and scoped per integration so a single key compromise does not expose the whole tenant. OAuth tokens are refreshed on each provider's mandated schedule (Google, Meta, Razorpay all rotate on the order of weeks). Webhook payloads are HMAC-signed with a per-tenant secret and include replay protection. Data sits in India, aligned to India's DPDPA 2023. Independent SOC 2 attestation is on our roadmap, not currently in place — we will publish the report when it is.