Skip to content


Repository files navigation


Chrome Extension for SugarCRM from Gmail inbox.

Try out: Yathit CRMinInbox: SugarCRM for Gmail or LTS edition

Home page


Suggestion and feedback

Design Goal

API will be designed so that it is secure, easy to use, flexible and powerful enough to common use case in CRM applications in Gmail.

All UI code (and associate data model, configuration, build script) will be open source so that the app can be easily extensible.

Multiple backend service including GData, SugarCRM, AWS S3 and AWS DynamoDB will be supported.

Security consideration:

  1. No loading of insecure code (no eval, no inline script).
  2. Use sandbox iframe for third party.
  3. All SSL connection. (Including SugarCRM that don't support https?)
  4. All resources (images) must be serialized, i.e., image file are loaded by XMLHttpRequest and render using canvas or datauri.
  5. Request only absolutely necessary host permission. Avoid host access to, since the stakes are too high. All hosts permission is definitely not acceptable.
  6. Reduce permission request. Use optional permission. Remember we are just an app, not managing browser. Don't stalk other tabs.
  7. Use sandbox iframe. Use encryption.
  8. Don't delete or hide Gmail DOM element.


  1. Authentication and authorization of sugarcrm, AWS and Google GData services.
  2. CRUD operation of SugarCRM Module Record and GData Entry.
  3. Synchronizing SugarCRM modules between SugarCRM instance and client side database.
  4. Synchronizing GData entries (contact, task, calender, sites) between Google server and client side database.
  5. Caching relationship table.
  6. Conversion and synchronizing between GData Entry and SugarCRM module record.
  7. Promise base centralized communication between extension pages.
  8. Customizable full text search.

Backend server

Google AppEngine (Java) backend server provides authentication and authorization. For SugarCRM, hash password is kept in the browser with encryption. User setting as stored in Chrome storage. Backend server also provide proxy with authorization header.

Please contact to to use YDN backend server for your extension. A new application id, ydn.crm.base.APP_ID will be created for your extension. A valid (paid) user login is required to use the service.


This repo is packaging for Chrome Extension and source codes are in the following repositories. Most of the main codes are in CRM Core and SugarCRM repo.

  1. Closure library
  2. Base utility library
  3. Database library
  4. Authentication and authorization
  5. Full text search
  6. Dependency for ydn-db-fulltext
  7. Dependency for ydn-db-fulltext
  8. CRM Core
  9. CRM extra feature
  10. SugarCRM model and UI
  11. CRM backend


This project use Google Translator Toolkit for translation. Send an email to us if you want to join in translation effort. Any language is accepted.


You should be able to load this repo folder as unpacked Chrome Extension. You will need compiles dependency files, which are available in


Open source does not mean zero cost. Open source means that you can change source code to suite your use case and inspect them for security or privacy concern. I would expect pricing will be around $5~10/user/month.


All UI components, data models and base utilities are released under GNU Lesser General Public License. Backend and database synchronization will not be open source, but license to partners.


Chrome Extension for SugarCRM from gmail inbox.







No packages published