A build-to-order Frappe app that deeply wires Google Workspace into ERPNext — 2-way Gmail sync on Communications, Calendar sync for Events, Drive-backed File storage, and Google SSO. ECOSIRE scopes, builds, installs, and supports it for your v15/v16 site. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that deeply wires Google Workspace into ERPNext — 2-way Gmail sync on Communications, Calendar sync for Events, Drive-backed File storage, and Google SSO. ECOSIRE scopes, builds, installs, and supports it for your v15/v16 site.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
Most teams that run ERPNext also live in Google Workspace all day — sales reps reply from Gmail, project managers schedule in Google Calendar, and finance drops proposals into Drive. ERPNext ships an Email Account (IMAP/SMTP) integration and a basic Google Calendar sync, but the seams show fast: emails land in a mailbox that is only loosely tied to the right Lead or Sales Order, calendar sync is one-directional and brittle around recurring events, attachments bloat the site's own filesystem and backups, and every user still maintains a separate ERPNext password. The result is duplicate data entry, "which system is the source of truth?" arguments, and a CRM that nobody trusts because the real conversation happened in an inbox ERPNext never saw.
2-way Gmail sync that writes inbound threads as `Communication` records linked to the correct `Lead`/`Opportunity`/`Customer`/`Issue` reference DocType
Outbound send through the Gmail API so replies composed in ERPNext appear in the user's real Gmail Sent folder
Incremental polling using Gmail history IDs via a `scheduler_events` cron so messages are never re-imported
Bidirectional Google Calendar sync: ERPNext `Event` document events upsert Google events (attendees + reminders), and a whitelisted webhook method ingests Google-side changes
Google Drive storage backend for the `File` DocType — attachments store a Drive file ID and signed link instead of a local blob to keep the site DB and backups lean
'Attach from Drive' client-script action on target DocTypes to link existing Drive files without re-uploading
The ERPNext Google Workspace Suite is a proper Frappe app (its own module, DocTypes, and hooks.py) that closes those gaps. For Gmail, we implement a 2-way sync that pulls threads via the Gmail API and writes them as Communication records linked to the correct reference DocType (Lead, Opportunity, Customer, Issue), and pushes replies composed in ERPNext back out through Gmail so the sent copy appears in the user's real Sent folder. A scheduler event (scheduler_events in hooks.py) polls incrementally using Gmail history IDs so we never re-import the same message, and doc_events on Communication fire the outbound push. Calendar sync is genuinely bidirectional: an ERPNext Event created or updated fires a document event that upserts the matching Google Calendar event (with attendees and reminders), while a webhook-backed whitelisted method ingests changes made on the Google side. Drive support adds a storage backend so File attachments can live in a chosen Drive folder — the File DocType stores the Drive file ID and a signed link instead of a local blob, keeping your site database and backups lean. Google SSO is implemented via Frappe's Social Login / OAuth so users sign in with their Workspace identity, with domain restriction and mapping to ERPNext role profiles.
Under the hood everything is built the Frappe-native way so your team can own it: OAuth credentials and per-user tokens are stored in dedicated DocTypes with encrypted fields, token refresh runs on a scheduler event, all Google calls go through whitelisted server methods (never raw client-side secrets), and connection status plus sync logs are exposed as a DocType you can filter and audit. Client scripts add the in-form actions (Sync Now, Attach from Drive, Connect Google Account); permissions and role profiles gate who can connect an account and who can see synced Communications. The REST API surface is preserved, so any of the sync methods can also be driven headlessly. The app targets Frappe/ERPNext v15 and v16 and is written to survive bench migrate cleanly.
Because this is build-to-order, ECOSIRE builds it around your actual setup rather than shipping a generic binary. We start with a short scoping call to confirm which Google services you need, your Workspace admin constraints (OAuth verification, domain-wide delegation vs per-user consent), and which ERPNext DocTypes the sync should touch. Typical delivery is 2-4 weeks from confirmed scope. You get the full installable source for your version, installation and configuration on your bench, UAT on a staging site with a documented rollback plan, a training session, and a post-go-live support window — plus handover of the git repository so the app is yours to keep and extend.
Reps who live in Gmail and want every customer email automatically attached to the right Lead or Opportunity in ERPNext, and want to reply from ERPNext without leaving a broken paper trail.
People who schedule in Google Calendar but track delivery in ERPNext, and need `Event` records and Google Calendar to stay in sync in both directions, attendees and reminders included.
Admins who want Google SSO with domain restriction and role-profile mapping, encrypted token storage, whitelisted server-side API calls, and an auditable sync log rather than a black-box integration.
Teams that attach large proposals, contracts, and scans and want them stored in a managed Google Drive folder instead of bloating the ERPNext site database and nightly backups.
Buy the license on ecosire.com and download the ERPNext Google Workspace Suite app ZIP from your account dashboard.
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install ERPNext Google Workspace Suite and apply its schema.
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Gmail integration depth | 2-way sync into linked `Communication` records; replies land in real Gmail Sent | Whatever you scope and pay to build in-house | Often inbound-only or a loose IMAP mailbox | |
| Calendar sync | Bidirectional Event↔Google with attendees, reminders, webhook ingest | Depends on effort; recurring-event edge cases are costly | Frequently one-directional or basic | |
| Drive attachment storage | Opt-in Drive backend; File stores Drive ID + signed link | Buildable but rarely prioritized | Usually not offered | |
| Google SSO | OAuth SSO with domain restriction + role-profile mapping | Configurable but you own the setup | Sometimes bundled, mapping often manual | |
| Fit to your workflow | Scoped to your DocTypes, Google admin policy, and field mapping | Fully bespoke — highest effort and cost | Fixed template you adapt to | |
| Security model | Encrypted tokens, server-side whitelisted calls, audit Sync Log | As secure as you build it | Varies by vendor; often opaque | |
| Ownership & maintainability | Full git repo handover + technical docs; yours to extend | You own it but also own all the debugging | Vendor-locked; limited source access | |
| Support & delivery | Build-to-order, 2-4 weeks, install + UAT + training + support window | Timeline and support depend on your team's bandwidth | Install-yourself; community/paid support tiers |
Because this is build-to-order, we build it around your ERPNext setup rather than handing over a generic download. Typical delivery is 2-4 weeks from confirmed scope. The clock starts once we've agreed on which Google services to sync, your Workspace admin constraints, and the target DocTypes — that's what the initial scoping call settles.
Every engagement includes a post-go-live support window for defect fixes and configuration tweaks. You also receive the full git repository, so your team can maintain and extend the app independently. We can quote a longer support/maintenance retainer or version-upgrade work (e.g. a future v16/v17 bump) separately if you want us to keep owning it.
The app is built and tested for Frappe/ERPNext v15 and v16. We pin the delivered source to your exact running version, write the code to survive `bench migrate` and `bench update`, and validate it on a staging clone before touching production.
No. This is not an off-the-shelf Marketplace download. ECOSIRE scopes, builds, installs, and supports it for your specific site. The upside is a proper Frappe app tailored to your DocTypes, Google admin policy, and workflow — not a one-size-fits-all binary you have to bend your process around.
No. Drive storage is opt-in and configurable. You choose which DocTypes or file categories route to a Drive folder; everything else keeps ERPNext's default file handling. Where Drive is used, the `File` record stores the Drive file ID and a signed link, so your site database and backups stay lean without changing how users attach files.
Yes. OAuth credentials and per-user tokens are stored in dedicated DocTypes with encrypted fields, token refresh runs server-side on a scheduler event, and every Google API call goes through whitelisted Frappe methods — no client secrets ever reach the browser. Google SSO supports domain restriction so only your Workspace users can authenticate.
Yes. The sync operations are exposed as whitelisted methods, so they can be triggered from in-form client-script actions (Sync Now, Attach from Drive) or headlessly via the Frappe REST API for automations and scheduled jobs. Sync activity is recorded in an auditable Sync Log DocType.
A build-to-order Frappe app that deeply wires Google Workspace into ERPNext — 2-way Gmail sync on Communications, Calendar sync for Events, Drive-backed File storage, and Google SSO. ECOSIRE scopes, builds, installs, and supports it for your v15/v16 site.