HubSpot

HubSpot provides CRM context for companies, contacts, deals, owners, and pipelines. oper8r uses that context to ground account workflows and connect CRM records to calls, documents, Slack context, and graph entities.

Connection Pattern

HubSpot is typically connected through OAuth by an organization admin.

Common read scopes include:

• Companies.
• Contacts.
• Deals.
• Owners.
• Users or settings needed for owner mapping.

Write scopes should only be added for explicitly approved workflows.

Data Used

oper8r can use HubSpot records such as:

• Company name, domain, lifecycle stage, owner, and recent activity.
• Contact name, email, company association, title, and owner.
• Deal name, stage, amount, close date, pipeline, owner, and reason fields.
• Owner records for routing and accountability.

Example API-Backed Workflow

curl -X POST "https://YOUR_OPER8R_HOST/api/tools/org/YOUR_ORG_SLUG/oper8r_get_account_context" \
  -H "Authorization: Bearer $OPER8R_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "account": {
      "externalIds": [
        {
          "provider": "hubspot",
          "id": "982734",
          "type": "company"
        }
      ]
    },
    "purpose": "renewal prep"
  }'

Graph Curation Example

{
  "name": "Jane Smith",
  "type": "person",
  "externalIds": [
    {
      "provider": "hubspot",
      "id": "123456",
      "type": "contact"
    },
    {
      "provider": "email",
      "id": "jane.smith@example.com",
      "type": "work_email"
    }
  ]
}

Recommended Setup

1. Connect HubSpot with read-only scopes.
2. Validate company, contact, deal, and owner counts.
3. Select example accounts for testing.
4. Confirm how company domains map to website and call sources.
5. Add write workflows only after the read and synthesis workflows are trusted.

Limitations

• CRM records may be stale or incomplete.
• Owner and association fields vary by HubSpot configuration.
• Deal stages and pipelines should be interpreted with customer-specific context.
• Customer-facing outputs should cite supporting evidence beyond CRM fields when possible.