> ## Documentation Index > Fetch the complete documentation index at: https://docs.autonudge.dev/llms.txt > Use this file to discover all available pages before exploring further. # HubSpot mode > Keep HubSpot as the source of truth; let Nudge work it If your team already lives in HubSpot, you do not migrate. Nudge connects with a private app token and sits on top: HubSpot stays the record, Nudge does the outreach. ## What Nudge pulls Intake is derived from your automations. Nudge pulls exactly the contacts your **enabled triggers** care about, matched by their conditions and owner audiences, and keeps them fresh on a schedule you set. Enable a trigger and its audience starts flowing in; there is no separate import step to keep in sync. The fields Nudge reads are the ones in your [fields registry](/settings/workspace), so a HubSpot property becomes filterable, displayable and usable as a message variable the moment you register it. ## What Nudge writes back Every outcome goes home to HubSpot: * possibility/state changes, from manual edits, sends and call outcomes * sent messages and call results Writes go through a durable queue with retries and backoff. A HubSpot outage delays the sync; it does not lose it. If a write permanently fails, admins get a bell notification and, if enabled, an email alert. ## Conflicts Edits made in Nudge win for a short grace window, so a rep's manual state change is not stomped by the next sync pulling slightly stale data. After that, HubSpot is the truth. ## Working in both Contact pages in Nudge show recent HubSpot notes read-only and link straight to the HubSpot record. A **Refresh** button pulls a single contact on demand when you need the freshest state right now. Standalone (native CRM) workspaces skip all of this: contacts, deals and forms live in Nudge and no HubSpot account is involved.