Log in Book a demo
Integrations

HubSpot — OAuth & mapping.

Connect HubSpot in 30 seconds, map call outcomes to deal stages, and decide which fields update from voice.

Connect

  1. In IzzyOps: Integrations → HubSpot → Connect.
  2. You'll be redirected to HubSpot's OAuth screen. Pick the portal you want to connect.
  3. Approve the scopes (read/write contacts, deals, calls).
  4. You're back in IzzyOps. The connection card flips to "Connected" with a green dot.
Scopes we ask for. We request the minimum needed: contacts (read + write), deals (read + write), calls (read + write), owners (read). We do not request access to attachments, sequences, or marketing data.

Mapping

Click Configure on the HubSpot card to set up field mapping.

Contact creation

By default, IzzyOps creates a new contact when a call comes from an unknown number. You can change this to create only when the workflow explicitly requests — useful if you don't want every random caller in your CRM.

Field mapping

For each piece of data the AI captures during a call, decide whether to write it to a HubSpot field. Defaults:

  • Caller name → firstname + lastname
  • Phone → phone
  • Email → email (if captured)
  • Address → address, city, state, zip
  • Call summary → custom property last_call_summary (we create this if it doesn't exist)
  • Call intent → custom property last_call_intent

Deal stages

If you use the HubSpot Sales Hub, map call outcomes to deal stage transitions. Example: "intent = qualified_lead AND outcome = booked" → move deal to "Demo Scheduled".

Two-way sync

IzzyOps subscribes to HubSpot webhooks for the objects you mapped. When a contact's do_not_call flag is updated in HubSpot, we honour it on the next outbound campaign. When a deal stage changes, we can trigger an outbound workflow.

Disconnecting

Disconnect from Integrations → HubSpot → Disconnect. We revoke the OAuth token immediately and stop reading or writing. Historical data already in HubSpot stays put.