FrancodesystemsFran<code>systems
WorkspaceCustom integration

Holded Google Workspace integration

Gmail, Calendar, Drive and Contacts connected to Holded in real time.

HoldedHolded
Google Workspace

Implementation time · 5-9 días laborables

Diagnosis

The problem

If your company lives in Gmail, Calendar and Drive, Holded gets relegated to a tab only finance opens. Sales reps don't see Holded contacts in their Gmail, client meetings aren't logged in the CRM, and quotes the client signs end up in some personal Drive with no traceability. For a company of 15 to 100 employees with Workspace as its digital fabric, this is operational friction: duplicated documents, uncoordinated contacts, and a CRM (Holded) nobody feeds because it isn't where people work.

Proposal

The solution

For companies with Google Workspace (formerly G Suite) as the backbone of their day-to-day. Holded contacts show up in Gmail, Calendar events reflect meetings with active clients, and generated documents (quotes, invoices, contracts) are automatically filed in Drive with per-team permissions. Support for Workspace Business Starter, Standard, Plus and Enterprise.

Scope

What we automate

  • Holded contacts and Google Contacts synced (labels, groups)
  • Calendar: events with Holded clients flagged automatically
  • Drive: quotes and invoices filed in the client's folder with permissions
  • Gmail: emails tagged with a client, annotated in Holded
  • Sent attachments (contracts) filed in the client's Drive
  • Reps assigned to Holded clients get automatic Drive permissions
  • Chat (Spaces) notifications: payment received, invoice overdue, deal signed
  • Weekly reports generated in Sheets from Holded data
Who uses it

Real use cases

These are the profiles that most ask us for the HoldedGoogle Workspace integration and what they get in the end.

Case 01

Digital agency, 30 employees, on Workspace

Before: Sales reps never opened Holded. Client meetings not logged in the CRM.

After: Gmail shows a Holded client panel on every email. Calendar logs meetings as CRM activities.

Case 02

Consultancy with Drive as the central repository

Before: Signed quotes stayed in the rep's personal Drive.

After: Every quote in the client's folder on the shared Drive with automatic permissions.

Case 03

Company with high sales-rep turnover

Before: When a rep left, their clients' Drive access had to be cleaned up by hand.

After: Permissions via domain Google Groups: when the employee leaves, permissions are cleaned up automatically.

Before / After

What changes exactly

Without the integration

  • Sales reps never open Holded as a CRM
  • Documents in personal Drive with no traceability
  • Meetings not logged against the client
  • Manual permissions on employee onboarding/offboarding

With the integration

  • Gmail shows a contextual Holded client panel
  • Shared Drive as the single source per client
  • Calendar as the source of CRM activities
  • Permissions via Groups: automatic onboarding/offboarding
Architecture

How we build it

Google APIs (People, Calendar, Drive, Gmail) with OAuth2 authentication and a service account for domain-level flows. Events are processed in near real-time via push notifications. Drive permissions are managed via domain Google Groups so that onboarding and offboarding of employees is reflected automatically. A service external to Workspace: we don't install add-ons in Gmail or Calendar that you'd later have to maintain.

flow.ts
webhook google workspace.event
queue.enqueue(jobId)
worker.handle() // idempotent
holded.api.call() // retries with backoff
log.emit({ status: 'ok' })
FAQ

Frequently asked questions

Do I need to be a workspace admin?

For the app registration phase and authorizing access to domain APIs, yes. After that, day-to-day use requires no special permissions.

Does it work with personal @gmail.com accounts?

No. It requires Workspace (your own domain). Personal accounts don't support service accounts or domain-wide delegation.

Does it support Google Drive Shared Drives?

Yes. We prefer Shared Drives over 'My Drive' for organizational ownership. If your structure is per-client with a specific Shared Drive, we file into the right one automatically.

What about permissions when an employee leaves?

If permissions are managed via domain Google Groups, you just remove the employee from the Group and all Drive access disappears. It's the recommended practice and the one we configure by default.

Do we have to install add-ons in Gmail or Calendar?

No. If you want a contextual sidebar in Gmail showing client data, we can build it as an optional Workspace Add-on. But the base functionality requires none.

How long does it take?

Between 5 and 9 business days. If you want a Gmail add-on with a native UI, add 3 to 5 days to build and publish it.

Shall we talk about your Google Workspace integration?

A 30-minute call, no strings. You leave with scope and a price.