Skip to main content

Connecting Services

Most useful workspaces depend on systems that already exist somewhere else.

That might be Google Calendar, Outlook Calendar, Salesforce, HubSpot, Zendesk, Google Sheets, openlibrary.org, an internal order system, or a browser-only tool such as Shopify Admin. Worka becomes useful by bringing those systems into one workspace, but that only works when connections are clear and well-scoped.

What a connection is​

A connection is the approved link between your workspace and an external system.

It defines:

  • which service is being connected
  • which account or credentials are being used
  • what level of access is being granted
  • which workspace can use it

That last point matters. A connection should stay scoped to the workspace and purpose it was approved for.

When Worka should ask for a connection​

Worka should ask only when the workspace has reached a clear need for that service.

Good timing:

  • the workspace needs real Google Calendar or Outlook Calendar data
  • the next step requires a Salesforce or HubSpot write
  • a pack needs a live API path to become useful

Bad timing:

  • the workspace has not yet proved it needs the service
  • the request is broad and unexplained
  • the main view is still unclear

What you should review before approving a connection​

Before you approve a connection, check:

  • why this workspace needs the service
  • whether the requested access is the minimum needed
  • whether the service is the right source system
  • whether the connection is meant for this workspace only

If the answers are unclear, do not approve it yet.

Common connection types​

Different services connect in different ways.

You may see:

  • direct API tokens
  • OAuth sign-in flows
  • service-specific metadata such as account IDs, subdomains, or workspace references

You do not need to manage those low-level details manually in normal use. What matters is that Worka explains what the connection enables.

What changes after a connection is added​

Once a connection is active, the workspace can use it to:

  • populate views with live data
  • let AI team members call tools against that service
  • trigger workflow steps that depend on the service

That is why a connection prompt is important. It is not just a setup checkbox. It changes what the workspace is capable of doing.

How to keep connections under control​

Good connection discipline means:

  • adding services only when the workspace clearly needs them
  • revoking or replacing stale connections
  • avoiding broad connections that cover more than the workspace actually uses
  • reviewing high-risk actions separately even after the connection exists

A connected service does not mean every action should run automatically.

Warning signs​

Pause and review if:

  • Worka asks for a service before you understand the workspace shape
  • the access level feels broader than the job requires
  • a workspace suddenly depends on several unrelated services
  • you cannot tell what the connection will actually unlock

If any of those happen, the workspace needs a tighter plan before it gains more reach.