​

HubSpot Integration

HubSpot connects operator-only CRM account and contact context to Woes. Use it when your support team needs to understand the company, contact, owner, lifecycle stage, or deal context behind a conversation without leaving the support workflow.

​

At A Glance

​

What the HubSpot integration does

The HubSpot integration gives Woes permission to read CRM context that can help operators understand who they are helping.

​

What Woes can read

When you authorize HubSpot, Woes requests read access for:

• HubSpot contacts
• HubSpot companies
• HubSpot deals
• HubSpot owners

This lets Woes support CRM-aware views such as account identity, relationship ownership, lifecycle stage, and related sales/customer context where those surfaces are available in the workspace.

​

What Woes does not do yet

The current HubSpot integration is read-oriented. Woes does not currently:

• Create HubSpot tickets.
• Create HubSpot tasks.
• Write support notes back to HubSpot records.
• Update HubSpot contact, company, deal, or owner records.
• Turn HubSpot into a customer support inbox channel.

Use Woes Issues, Jira, Linear, Slack, email, Discord, or live chat workflows for support actions and customer communication.

​

Setup

1. Open Workspace Settings > Integrations.
2. Find HubSpot.
3. Click Connect.
4. Review the requested HubSpot permissions.
5. Choose the HubSpot account and portal you want Woes to use.
6. Approve the connection.
7. Return to Woes and confirm the HubSpot card shows Connected.

After connection, the HubSpot card shows the connected portal and authorizing HubSpot user when that information is available. Open the HubSpot management dialog and click Sync CRM context to add HubSpot records to the Context Library.

​

Permissions Woes requests

Woes requests the minimum HubSpot OAuth permissions needed for CRM context: Woes does not request write permissions for HubSpot CRM records in the current version.

​

Data visibility

HubSpot data is workspace-scoped support context.

• Operators and admins may see HubSpot connection status and CRM context inside Woes.
• Synced HubSpot records appear in the Context Library as operator-only CRM context.
• Customers using the chat widget, email, Discord, or Slack do not receive HubSpot records.
• Public REST API responses do not expose HubSpot access tokens or raw integration credentials.
• Disconnecting HubSpot stops new CRM syncs. Already synced Context sources remain until an admin deletes them.

​

Disconnect HubSpot

1. Open Workspace Settings > Integrations.
2. Select HubSpot.
3. Open the HubSpot management dialog.
4. Click Disconnect.

Disconnecting removes the Woes connection to HubSpot. If you reconnect later, an admin will need to approve HubSpot access again.

​

Troubleshooting

​

The HubSpot card still says Connect

Refresh Woes after returning from HubSpot. If it still says Connect, try connecting again and make sure the HubSpot authorization screen is approved rather than cancelled.

​

The wrong HubSpot portal is connected

Disconnect HubSpot in Woes, then connect again and choose the correct HubSpot portal during authorization.

​

I do not see CRM context

Confirm that:

• HubSpot shows Connected in Workspace Settings > Integrations.
• You clicked Sync CRM context after connecting HubSpot.
• The Context Library shows a HubSpot source with indexed records.
• Your Woes role has access to the operator surfaces where CRM context is shown.

​

I want Woes to create HubSpot tickets or notes

HubSpot write-back is not part of the current integration. Use Woes Issues, Jira, Linear, or your public API workflows for ticketing and follow-up automation.

​

Related docs

• Integrations Catalog
• Settings Overview
• Clients