HubSpot Integration

Overview

The HubSpot integration uses HubSpot's OAuth 2.0.

Skills that use this integration:

• int-hubspot-crm — Contact/deal CRUD, note and task creation, sequence enrollment
• util-newsletter-compose — optional; uses HubSpot as an ESP when enabled alongside

Agents that typically enable this integration:

• Lead Generation Manager
• Newsletter Manager (HubSpot as ESP)
• Any custom agent with CRM capabilities

Availability

Prerequisites

• A Wiro API key — Authentication.
• A deployed agent — Agent Overview.
• A HubSpot account the connecting user is an admin of.
• (Own mode) A HubSpot developer account — developers.hubspot.com.
• An HTTPS callback URL.

Wiro Mode

Call OAuthConnect with credentialkey: "hubspot" and without authmethod, redirect, parse hubspot_connected=true&hubspot_portal=<id>&hubspot_name=<name>.

Complete Integration Walkthrough — Own Mode

Step 1: Create a HubSpot App

1. developers.hubspot.com → sign in → Create app.
2. Set App name and App description (shown on consent).

Step 2: Configure Auth

1. Open the Auth tab.
2. Redirect URL:

   https://api.wiro.ai/v1/UserAgentOAuth/HubSpotCallback

3. Scopes — Wiro requests a fixed scope string plus optional_scopes. Enable all of the following in your HubSpot app's Auth tab:

   Required scope (mandatory — OAuth fails if any is missing):

   • crm.objects.contacts.read
   • crm.objects.contacts.write
   • crm.lists.read
   • crm.lists.write
   • oauth

   optional_scope (granted on consent if enabled, otherwise skipped — Wiro doesn't fail if missing):

   • crm.objects.companies.read
   • crm.objects.companies.write
   • crm.objects.deals.read
   • crm.objects.deals.write
   • crm.objects.owners.read
   • crm.schemas.contacts.read
   • content
   • transactional-email
   • files
4. Save.

Step 3: Copy Client ID and Client Secret

Auth tab → copy Client ID and Client Secret.

Step 4: Save credentials to Wiro

curl -X POST "https://api.wiro.ai/v1/UserAgent/CredentialUpsert" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "fields": [
      { "credentialkey": "hubspot", "fieldname": "clientid",     "fieldvalue": "YOUR_HUBSPOT_CLIENT_ID" },
      { "credentialkey": "hubspot", "fieldname": "clientsecret", "fieldvalue": "YOUR_HUBSPOT_CLIENT_SECRET" },
      { "credentialkey": "hubspot", "fieldname": "authmethod",   "fieldvalue": "own" }
    ]
  }'

Step 5: Initiate OAuth

curl -X POST "https://api.wiro.ai/v1/UserAgentOAuth/OAuthConnect" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "credentialkey": "hubspot",
    "redirecturl": "https://your-app.com/settings/integrations",
    "authmethod": "own"
  }'

Response:

{
  "result": true,
  "authorizeUrl": "https://app.hubspot.com/oauth/authorize?client_id=...&redirect_uri=...&scope=...&state=...",
  "errors": []
}

Step 6: Handle the callback

Wiro exchanges the code, then calls GET https://api.hubapi.com/oauth/v1/access-tokens/<access_token> to fetch hub_id (portalid) and hub_domain (portalname).

Success URL:

https://your-app.com/settings/integrations?hubspot_connected=true&hubspot_portal=12345678&hubspot_name=My%20Workspace

Step 7: Verify and Start

curl -X POST "https://api.wiro.ai/v1/UserAgentOAuth/OAuthStatus" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "credentialkey": "hubspot"
  }'

Response:

{
  "result": true,
  "connected": true,
  "accounts": [
    { "id": "Acme Corp HubSpot", "name": "Acme Corp HubSpot" }
  ],
  "connectedat": "2026-04-17T12:00:00.000Z",
  "tokenexpiresat": "2026-04-17T12:30:00.000Z",
  "errors": []
}

Note: For HubSpot, the unified OAuthStatus mirrors the saved portalname into both accounts[0].id and accounts[0].name (HubSpot has no separate picker — there's exactly one portal per OAuth grant). The numeric portalid is captured by HubSpotCallback as hubspot_portal=<id> on the redirect URL but is not re-surfaced by OAuthStatus.

curl -X POST "https://api.wiro.ai/v1/UserAgent/Start" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{ "guid": "your-useragent-guid" }'

API Reference

POST /UserAgentOAuth/OAuthConnect

GET /UserAgentOAuth/HubSpotCallback

Query params: hubspot_connected=true&hubspot_portal=<id>&hubspot_name=<name> or hubspot_error=<code>. The callback path is per-provider — HubSpot's stays HubSpotCallback.

POST /UserAgentOAuth/OAuthStatus

Body: { useragentguid, credentialkey: "hubspot" }. Response: connected, accounts: [{id, name}] (1-element with the saved portalname mirrored into both id and name), connectedat, tokenexpiresat (~30 min).

POST /UserAgentOAuth/OAuthDisconnect

Body: { useragentguid, credentialkey: "hubspot" }. Clears HubSpot credentials (no remote revoke).

Token lifecycle

Wiro maintains the HubSpot connection automatically while the agent is running. If HubSpot revokes the authorization or OAuthStatus reports connected: false, reconnect through OAuth.

Using the Skill

curl -X POST "https://api.wiro.ai/v1/UserAgent/CustomSkillUpsert" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "skillkey": "lead-enrichment",
    "enabled": true,
    "interval": "0 */4 * * *",
    "value": "Enrich new contacts with company information"
  }'

Troubleshooting

403 Forbidden on API calls

Usually a missing scope. Look up the specific HubSpot API endpoint you're hitting, add the required scope in your app's Auth tab, then disconnect and reconnect (scope changes require re-consent).

Token expired error at runtime

HubSpot's 30-minute token lifetime makes continuous authorization important. If you see a token-expired error:

• The agent is stopped (status 0/1/6). Start it: POST /UserAgent/Start.
• The authorization may have been revoked in HubSpot's app management UI. Reconnect the user.
• If the agent is running and reconnection does not resolve it, contact Wiro support.

Multi-Tenant Architecture

1. One HubSpot developer app per product — submit to the HubSpot App Marketplace for listed visibility, or stay private.
2. One Wiro agent instance per customer.
3. Portal IDs are unique per customer's HubSpot account.
4. Per-app rate limits apply — see HubSpot's API usage guidelines.

Related

• Agent Credentials & OAuth
• Agent Overview
• Agent Skills
• HubSpot Developer docs