Hubz.

Connections / Google Workspace and communication providers

CRM integrations for email, calendars and connected accounts

Set up email, calendar, task-file and approved communication connections with the correct account, permissions and action scope.

PRODUCT VIEW

See how it works.

Connecting a service does not mean every action in that service becomes available inside Hubz. Which account is used, which data can be read and whose approval is needed for an action are separate decisions. Hubz uses tools such as Google Workspace mail and calendar connections, Drive configuration for task attachments, approved-sender email delivery and signed website intake within the permissions you grant.

Hubz.Workspace / IntegrationsDK
EXPLORE THE PRODUCT

Integrations

Sample view
◎Google Workspace mailAccount and permissionsDepends on setup
↗Google CalendarAccount and permissionsDepends on setup
⊙Drive for task attachmentsAccount and permissionsDepends on setup
◇Approved email deliveryAccount and permissionsDepends on setup
⌁Website intakeAccount and permissionsDepends on setup
01Define the need
02Connect the correct account
03Use the connection within scope
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

DETAILED FEATURE GUIDES

Explore the features in this module.

Integration centerReview Google, communication, task-file and website-intake connections with their statuses and requirements.

FROM NEED TO OUTCOME

Where this helps.

Seeing a service name in an integration list can suggest that the team’s need has already been met. Without clear account licensing, permissions and workspace mapping, the expected action may not be available.

WHAT YOU CAN WORK TOWARDS

Keep the purpose of each connection, the account being used and the user-granted scope clear.

STEP BY STEP

How to use it.

  1. 01

    Define the need

    Identify a concrete purpose such as mail synchronization, appointment calendars, task attachments or campaign delivery. Assess each connection against that purpose.

  2. 02

    Connect the correct account

    Connect the relevant user or authorized person’s provider account with explicit permission. Verify which workspace owns the sender and channel scope.

  3. 03

    Use the connection within scope

    Use it through the relevant Hubz workflow. Provider limits, separate usage fees and any required human review continue to apply.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
Integrations
Scope●Permission○Review○
Define the need

Google Workspace mail

Authorize the relevant account for Gmail synchronization and individual conversations. Normal mail licensing and provider usage limits apply separately.

FOCUS 02▤
Integrations
Scope○Permission●Review○
Connect the correct account

Google Calendar

Set up calendar connections for the relevant planning and appointment need. Establish the user profile and actual availability separately.

FOCUS 03↗
Integrations
Scope○Permission○Review●
Use the connection within scope

Drive for task attachments

Use available task-file tools with appropriate Drive configuration. Match file-upload and connection conditions to the workspace requirement.

FOCUS 04◇
Integrations
Scope●Permission○Review○
Define the need

Approved email delivery

Use approved sender and provider configuration in campaigns and related communication workflows. Treat software access and sending capacity separately.

FOCUS 05⌁
Integrations
Scope○Permission●Review○
Connect the correct account

Website intake

Connect suitable website inquiries through signed intake tools. Custom forms and field-mapping needs are scoped separately.

IN EVERYDAY WORK

What it looks like in practice.

Sales team

The team will use Gmail and calendars, but access differs by user.

Connect each account within its own permissions, clearly separating application access from provider access.

Marketing operations

Campaign software is enabled but the sender and usage capacity still need preparation.

Review connection setup alongside commercial usage scope to clarify preparation before sending.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

Standard integration access is included in Professional and Business. MCP and AI client connections are separately authorized within Business only.

  • Provider licenses, fees and permissions apply separately.
  • Planned connections are not presented as shipped features; custom development is separately scoped.
  • WhatsApp business messaging and independent number setup require separate technical acceptance.
Compare plans

YOUR QUESTIONS

About this feature.

01What integration approach is included in Professional?

Professional includes standard integration scope. Mail, calendar and other suitable provider connections require setup and permission. MCP requires an eligible Business subscription.

02Does connecting a service include its license?

No. Access to a Hubz module is not a license or free usage allowance for an external service. Its account terms, permissions and usage charges apply separately.

03Are WhatsApp marketing campaigns ready to use?

Business messaging requires separate review of the number, provider eligibility and technical acceptance. The existing individual-reply bridge is different from a general campaign service or a dedicated line for every subscriber.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Calendar and appointments

Connect meetings, events and appropriately configured appointments to the team’s daily work.

02

Inbox and Gmail

Use in-app notifications for daily work, and connect authorized Gmail conversations with Professional and Business.

03

MCP and AI connections

Connect compatible clients to permitted CRM context, with separate review and authorization for private plans and communications.