
HubSpot connection screen observed in staging on September 7, 2026. The staging interface was displayed in Spanish.
Before you connect
You need a HubSpot user who can install apps. This is normally a Super Admin or a user with App Marketplace access. Nexor connects through HubSpot OAuth. You do not create or paste a HubSpot API key into Nexor. During authorization, HubSpot shows the portal and permissions before access is granted.Permissions and data Nexor can access
Authorization asks only for the permissions the integration uses. HubSpot shows them before access is granted, and you can revoke them from HubSpot at any time.Connect the portal
Open HubSpot in Nexor
Choose the portal
Grant access
Configure Inputs
Open Inputs → Input doors → Add input door. Each door defines which HubSpot contacts enter Nexor and, when applicable, which Agent receives them.Configure Outputs
Open Outputs to decide what Nexor may write to HubSpot. The current screen groups controls into:- Current data for configured contact data.
- Interaction history, with independent controls for notes, meetings, and calls.
- Stages and statuses for configured lifecycle and status relationships.
- HubSpot tools for actions available to Agents.
Owners and External IDs
An organization member can store their HubSpot External ID under Organization. This creates an identity link that applicable routing and ownership settings can use.Deals and advanced configuration
HubSpot tools are configured per Agent under Settings → Tools → Configure for this agent. The integration does not provide a separate deal management screen. Bulk owner mapping is available through the API and MCP tools. Use the MCP Server reference or a Nexor-assisted setup for these advanced controls. Do not follow older instructions that reference a separate HubSpot deals screen.Protected stages
The deal sync, Lead sync, and deal update tools include Protected stages. Select stages from your HubSpot account’s pipelines and save the Agent configuration. No stages are protected by default: each organization chooses which ones to preserve. Before writing, the tool reads the current HubSpot state. If it is protected, the tool preserves both its stage and pipeline, even when the destination is also protected. A record that is not yet protected can still move into a protected stage.- Protection is per Agent, object, and pipeline. Leads and deals have independent settings.
- Both deal tools respect protections configured in either tool while they are active. To remove a protection, deselect it in every active tool where it is selected.
- Other deal data, such as owner or amount, can still be updated without changing the protected stage.
- If the configuration cannot be verified, or the current stage cannot be read when protection is configured, the stage change fails without overwriting the record.

The actual protected stages selector, running locally with example data.
Tickets from support cases
Ticket automations are an optional feature that your Nexor team enables on request. With them, a support Agent files each case in your HubSpot ticket pipeline when the case reaches a stage you choose, for example resolved, redirected, or escalated to your team.Grant ticket access
Choose the stages
Cases are filed automatically
- Subject: the case summary the Agent collected.
- Description: the case details you choose, one line per field, such as the escalation reason or the email address the customer was redirected to.
- Contact: the HubSpot contact that owns the email the customer gave, so the ticket is not attached to a duplicate. If no contact has that email, Nexor finds or creates one by email or phone.
- One ticket per case. If the case later reaches another of the chosen stages (escalated, then resolved), Nexor moves the same ticket to the new stage instead of creating a second one.
- Your edits are kept. After the ticket is created, Nexor only changes its stage. Edits your team makes to the subject or description in HubSpot stay.
- If you delete the ticket in HubSpot, the next chosen stage creates a new one.
Troubleshooting
Imported contacts are not assigned to an Agent
Imported contacts are not assigned to an Agent
A recurring list has not been reviewed yet
A recurring list has not been reviewed yet
Activities have no HubSpot owner
Activities have no HubSpot owner