Integrations

OnGravy meets your business where it already runs: your inbox, WhatsApp, Slack, your calendar, Tally, your e-commerce channels and your courier. Every integration below is live in the product today — where one needs credentials or a partner registration, the section says so plainly. Most are managed from Settings → Integrations; a few have dedicated dashboard pages, noted per section.

Gmail

Connect Gmail and OnGravy reads incoming mail for you — pulling supplier bills into the OCR inbox and routing government notices to the tax-notice agent. Access is read-only: OnGravy never sends, deletes, or modifies your mail. OAuth tokens are encrypted at rest.

Go to Settings → Integrations and click Connect Gmail.
Approve the read-only OAuth consent screen with the Google account that receives your business mail.
Choose a scan mode (you can change it later):

Mode	What it does
Invoices	Supplier bills and invoices found in mail become pending drafts in your OCR inbox — nothing posts without your review.
Notices	GST, Income Tax, MCA and TDS notices are routed to the tax-notice agent. It recognises common formats such as `DRC-01`, `ASMT-10`, `143(1)` and `148`.
Both	Every matched mail is auto-classified as a bill or a notice and routed accordingly.

Once connected, OnGravy scans automatically every 15 minutes — there is nothing to trigger manually.

Email-in OCR (no connection needed)

Every business gets its own inbound mailboxes — no OAuth, no setup. Forward (or ask suppliers to send) documents straight to them and they land as drafts in the OCR inbox for review. Nothing auto-posts; a human always confirms the draft.

Mailbox	Use for
`bills@<your-business-slug>.ongravy.in`	Supplier bills and purchase invoices
`expenses@<your-business-slug>.ongravy.in`	Expense claims and petty spends
`receipts@<your-business-slug>.ongravy.in`	Payment receipts and slips

.ongravy.com works as an alias for all mailboxes if your mail server prefers it.
Plus-tags tag the resulting draft: mail sent to bills+PROJECT-X@… arrives tagged PROJECT-X, so project- or site-wise filing costs you nothing.

WhatsApp assistant

The WhatsApp assistant is the most-used integration in OnGravy — a full front door to your books from the app your team already lives in. Message it in the language you prefer (it is multi-language) and it can:

Record transactions — sales, purchases and payments, by text or a voice note.
Read invoice photos — snap a bill and OCR turns it into a draft.
Answer with reports — ask for outstanding, sales this month, cash position and more.
Switch businesses — if you run more than one, tell it which books to work in.
Onboard staff — it hands out staff join codes (see Teams & permissions).
Answer credit inquiries — how much a party owes, and since when.

Outbound messages (payment reminders, filing confirmations and the like) use approved message templates. Manage them at Settings → WhatsApp templates, and control what OnGravy is allowed to send at Settings → WhatsApp policy.

Slack & Microsoft Teams

OnGravy pushes business events into Slack and Teams via incoming webhooks — no bot install, no workspace-level app approval. Slack messages arrive as rich blocks; Teams messages arrive as adaptive cards.

In Slack or Teams, create an incoming-webhook URL for the channel you want notified.
In OnGravy, go to Settings → Notifications and add the webhook URL as a notification channel.
Pick which events that channel should receive — each channel gets its own event selection, so #finance and #sales can hear about different things.

Event	Fires when
`gst_filed`	A GST return is filed
`tds_filed`	A TDS return is filed
`payment_received`	A customer payment is recorded
`invoice_paid`	An invoice is fully settled
`compliance_due`	A compliance deadline is approaching
`compliance_overdue`	A compliance deadline has passed unactioned
`bank_reconciled`	A bank reconciliation completes
`new_client`	A new client is added (CA practices)

These are notification pushes into chat. For programmatic, signed event delivery to your own systems, use API & webhooks instead.

Calendar

Compliance deadlines belong in the calendar you actually look at. OnGravy offers two ways to get them there:

1. Subscribe by URL (works with every calendar app)

In OnGravy, generate your private iCal feed URL.
In Google Calendar, Outlook or Apple Calendar, choose Add calendar from URL and paste it.
All your compliance deadlines appear and stay updated automatically as due dates shift or get done.

The URL is a private token — anyone holding it can read your deadline calendar. If it leaks, regenerate it: the old URL is revoked immediately.

2. Google Calendar two-way sync (OAuth)

Go to Settings → Calendar sync and connect your Google account.
OnGravy auto-pushes deadlines as events into your calendar — no feed refresh lag, and changes flow both ways.

Outlook auto-sync is coming soon; until then the subscribe-by-URL feed covers Outlook fully.

Tally (two-way)

Moving from Tally — or running both side by side — is a first-class path, not an afterthought. Three pieces work together:

Migration — /dashboard/migrate imports your Tally exports (masters and vouchers) into OnGravy.
Ongoing sync — /dashboard/integrations/tally keeps both systems in step using the ODBC connector protocol, with a conflict resolver for entries edited on both sides.
The Tally guide — /dashboard/tally-guide maps every Tally menu and F-key to its OnGravy screen, so muscle memory transfers instead of fighting you.

DigiLocker (credential-gated)

At /dashboard/digilocker, OnGravy can pull your PAN, GSTIN and incorporation documents via DigiLocker OAuth — typically during onboarding, so registration details are verified from source rather than typed in.

Credential-gated: DigiLocker requires a partner registration before the OAuth flow works for your organisation. Add your partner credentials at Settings → Partner credentials; without them the page explains what is needed rather than failing silently.

E-commerce channels

Shopify, Amazon and Flipkart are the live adapters. Once connected, OnGravy auto-syncs hourly: orders flow into your books, and marketplace settlements are reconciled against them — fees, commissions and TCS broken out instead of lumped. You can also upload settlement files manually for any period. The /dashboard/d2c-recon dashboard shows channel-wise order-to-settlement reconciliation in one place.

Go to Settings → Integrations and connect your channel (Shopify store, Amazon seller account, or Flipkart seller account).
Orders and settlements start syncing hourly — no manual pulls.
Review the reconciliation at /dashboard/d2c-recon; upload settlement files there if you prefer file-based recon.

Roadmap: WooCommerce and Meesho adapters are planned but not yet available. ONDC support today is manual order tracking only — automatic order ingestion arrives once our network-participant registration completes.

Logistics — Delhivery & Shiprocket

Book shipments without leaving your books, from /dashboard/logistics:

Book from the invoice — create a Delhivery or Shiprocket shipment against a sale.
E-way bill auto-fires — when the consignment crosses the e-way bill threshold, OnGravy generates it automatically (see GST & compliance).
Status webhooks — the courier’s tracking events update delivery state in OnGravy, so “delivered” in your books means delivered.

India rails

A set of India-specific connections, credential-gated where noted:

Rail	What it does	Where
UPI Autopay	Set up recurring-collection mandates so retainers and subscriptions collect themselves.	`/dashboard/integrations/upi-autopay`
TRACES / 26AS	TDS credit data pulled against your books for matching.	TDS workspace (credential-gated)
MCA21	Company-master and filing data for ROC work.	Compliance workspace (credential-gated)
RBI-FEMA validation	Validates foreign-exchange transactions against FEMA rules.	Runs inside relevant flows

Gotchas & good to know

Drafts, never auto-posts. Gmail scan, email-in, and WhatsApp photo OCR all land as pending drafts in the OCR inbox. Review is the design, not a limitation — see Automation for what can be safely automated beyond drafts.
Gmail is read-only. If your security review asks: the OAuth scope cannot send or modify mail, and tokens are encrypted at rest.
The iCal URL is a secret. Treat it like a password; regenerate it to revoke access instantly.
Slack/Teams webhooks are one-way. They push notifications out; they do not let chat users act on your books. The WhatsApp assistant is the conversational surface.
Per-channel event selection. Each Slack/Teams channel has its own event list — a noisy channel usually just means every event is ticked on one URL.
E-commerce sync is hourly. An order placed a moment ago may take up to an hour to appear; settlement recon depends on the marketplace publishing the settlement.
DigiLocker needs partner credentials first (Settings → Partner credentials) — the connect button is not broken, it is gated.
Google Drive sync is on the roadmap and not yet connectable from settings.
Building your own integration instead? Start with API & webhooks.

← Previous

👥 Payroll & TDS

⚙️ Automation