{
  "@type": "help_guide",
  "id": "lead-intel-hubspot-push",
  "title": "Push lead research to HubSpot",
  "kind": "feature",
  "summary": "After the account research and contact discovery are reviewed, Nexus can write them into the client's HubSpot: competitors, positioning summary, messaging gap and why-now angle on each company, and the contacts with their persona and personalization angle, linked to their company. Every write is tagged with a session id, so a whole push can be undone.",
  "aliases": [
    "push enrichment to hubspot",
    "push contacts to hubspot",
    "sync accounts to hubspot",
    "write to the crm",
    "roll back hubspot push",
    "undo hubspot push",
    "rollback session"
  ],
  "engine": "lead_intel",
  "agents": [],
  "related": [
    {
      "id": "lead-intel-pipeline",
      "page": "https://nexus.effiqs.com/help/lead-intel-pipeline"
    },
    {
      "id": "hubspot-connection",
      "page": "https://nexus.effiqs.com/help/hubspot-connection"
    },
    {
      "id": "lead-intel-engine",
      "page": "https://nexus.effiqs.com/help/lead-intel-engine"
    }
  ],
  "reviewed": "2026-10-15",
  "sections": [
    {
      "heading": "What it does",
      "key": "what-it-does",
      "markdown": "After the account research and contact discovery are reviewed, Nexus can write them into the client's HubSpot: competitors, positioning summary, messaging gap and why-now angle on each company, and the contacts with their persona and personalization angle, linked to their company. Every write is tagged with a session id, so a whole push can be undone."
    },
    {
      "heading": "Use it",
      "key": "use-it",
      "markdown": "Each push has two steps:\n\n1. **Preview.** **\"Push the enrichment to HubSpot.\"** shows how many companies would be created and updated, and the session tag. Nothing is written yet.\n2. ✋ **Confirm.** Reply **\"yes\"** to write. Nexus creates the custom fields it needs (once), then updates each company by its domain. Empty research fields never overwrite data already in HubSpot.\n\nContacts work the same way: **\"Push the contacts to HubSpot.\"** previews, then **\"yes\"** writes. Contacts in restricted regions, or flagged for review, are written without an email address: name, title, persona and company only."
    },
    {
      "heading": "Roll back",
      "key": "roll-back",
      "markdown": "✋ **\"Roll back HubSpot session [token].\"** (the session tag from the push) previews how many companies and contacts carry that tag; reply **\"yes\"** to clear the fields Nexus wrote. The companies and contacts themselves, and everything else on them, stay as they were. A rollback always needs the session tag and a confirmation."
    },
    {
      "heading": "Troubleshooting",
      "key": "troubleshooting",
      "markdown": "- **The push fails with a permission or scope error.** The client's HubSpot was connected before write access was added. **\"Reconnect HubSpot.\"** posts a new link; someone with portal admin rights approves it, then push again.\n- **Nexus says there are no enrichments or no contacts to push.** The account research or contact discovery hasn't run yet for this client."
    },
    {
      "heading": "Prompts",
      "key": "prompts",
      "markdown": "- \"Push the enrichment to HubSpot.\"\n- \"yes\"\n- \"Push the contacts to HubSpot.\"\n- \"Roll back HubSpot session [token].\"\n- \"Reconnect HubSpot.\""
    }
  ],
  "prompts": [
    {
      "text": "Push the enrichment to HubSpot.",
      "tool": "lead_push_enrichment_to_hubspot"
    },
    {
      "text": "yes",
      "tool": null
    },
    {
      "text": "Push the contacts to HubSpot.",
      "tool": "lead_push_contacts_to_hubspot"
    },
    {
      "text": "Roll back HubSpot session [token].",
      "tool": "rollback_lead_intel_session"
    },
    {
      "text": "Reconnect HubSpot.",
      "tool": "reconnect_hubspot_for_client"
    }
  ],
  "page": "https://nexus.effiqs.com/help/lead-intel-hubspot-push",
  "markdown": "https://nexus.effiqs.com/help/lead-intel-hubspot-push.md"
}