OAuth setup
Create a connection with user consent through the supported workflow without manually sharing an API key.
Business / Client, workspace and OAuth consent
Authorize a compatible MCP client through OAuth and review its accessible modules, permission validity and revocation options.
PRODUCT VIEW
Connect a compatible MCP client to the Hubz data you authorize it to use. During setup, add Hubz’s remote MCP address to the client, sign in to Hubz and choose the correct workspace before reviewing requested access. The connection list keeps the client name, creation and last-use information and granted scopes visible. CRM reading, supported workspace record operations, inbox reading, private planning and communication are separate permissions. New access requires a fresh consent decision.
FROM NEED TO OUTCOME
Connecting an assistant without explicit data and operation boundaries can create an expectation of excessive authority. Assuming an old connection automatically gains new capabilities also makes the permission decision invisible.
Know which client is connected to which workspace and with what scope. Manage permission validity, renewal requirements and revocation as parts of the connection lifecycle.
STEP BY STEP
Add Hubz’s remote MCP address in a compatible client and use supported OAuth authorization.
In the Hubz session, select the correct workspace and review resources, read/create/edit/delete actions, separate inbox access and any communication scope.
Check granted permissions, usage and expiry information, and renew or revoke the connection when needed.
INSIDE THE MODULE
Create a connection with user consent through the supported workflow without manually sharing an API key.
Authorize supported reading, creation, editing and deletion separately across CRM, tasks, catalog and quotes, support, social content and eligible automation resources.
Current revisions, workspace access and team roles are checked for every operation. Audit and execution history remain read-only; archive-based removal is identified explicitly.
Export bounded record pages or import a bounded batch with creation permission on eligible resources. Imports do not silently overwrite existing records; a failed batch rolls back.
Prepare appointment creation, rescheduling or cancellation. The actual change follows separate approval in Hubz, with existing availability and limit checks.
Do not treat private planning, mail reading and external communication as one permission.
Check visible permission expiry and renewal guidance to manage continued access deliberately.
Remove the relevant connection to invalidate its existing access and refresh tokens.
IN EVERYDAY WORK
The correct workspace and modules are explicitly approved, and later access requests are assessed through new consent.
Scenarios are illustrative; they are not customer testimonials or measured performance claims.
KNOW WHAT IS INCLUDED
MCP is available only on Business. Authorize each connection for the appropriate workspace and permissions, and review actions requiring separate approval. An earlier authorization does not remove the requirement for an eligible Business subscription.
YOUR QUESTIONS
MCP requires Business. Mail and social-provider connections follow their own plan and permission rules.
That connection’s access and refresh tokens become invalid. Provider accounts may have separate permission-revocation procedures.
RELATED WORKFLOW GUIDES
MODULES THAT WORK TOGETHER
Set up email, calendar, task-file and approved communication connections with the correct account, permissions and action scope.
Choose which Hubz resources a compatible client can read and which supported records it can create, edit or delete. Keep inbox and communication permissions separate.
Arrange team access through workspace membership, existing roles, enabled modules and connection permissions.