INTEGRATIONS

HubSpot CRM

Write each customer's churn score, risk factors, failed payment, cancel flow, win-back and MRR on the matching HubSpot contact, in a NoChurn property group.

NoChurn writes what it knows about each customer on the matching HubSpot contact, so that sales and success teams see churn risk where they work: the churn score and its risk factors, the failed payment in progress, the cancel flow’s outcome, the win-back, the MRR.

This is a separate connection from the HubSpot help desk connector, which reads tickets and conversations for the score and for dispute evidence, read only. They use the same HubSpot app with different permissions and tokens: you can connect either one, or both, and disconnecting one never disconnects the other.

Connect

  1. In NoChurn, open Integrations › HubSpot CRM and click Connect HubSpot.
  2. Sign in to HubSpot, pick the account and approve every permission: NoChurn asks to read and write contacts and to read and create contact properties. Without the write permissions, the first sync stops and asks you to reconnect.
  3. Back in NoChurn, the drawer shows the account, the last sync and what is waiting. The first sync writes every customer that has a matching contact.

Owners and admins can connect, change the settings and disconnect. By default NoChurn writes your live customers only, whatever mode the dashboard is in: see Customers to write.

Properties

You have nothing to create in HubSpot. On the first sync, NoChurn creates its contact properties in a property group called NoChurn, labelled “NoChurn: …” and described as written by NoChurn. It only creates the names that do not exist yet: a property that already exists, whoever created it, is never modified, and your own properties are never changed or deleted.

NoChurn fieldInternal nameHubSpot typeValue
NoChurn: Churn scorenochurn_churn_scoreNumberThe churn score, 0 to 100. Empty until the customer is scored.
NoChurn: Churn risknochurn_churn_bandDropdown select (Low, Medium, High)low, medium or high.
NoChurn: Risk factorsnochurn_risk_factorsMulti-line textThe three factors that raise the score most, with their points, separated by ; (for example Prepaid card (+25)).
NoChurn: MRRnochurn_mrrNumberMonthly recurring revenue in units of the currency (49.00, not cents).
NoChurn: Currencynochurn_currencySingle-line textISO code in capitals (EUR).
NoChurn: Customer statusnochurn_statusSingle-line texttrialing, active, in_recovery, paused or churned.
NoChurn: Failed paymentnochurn_recovery_statusSingle-line textThe latest failed payment: open, recovered or lost. Empty if none.
NoChurn: Cancel reasonnochurn_cancel_reasonSingle-line textThe reason picked in the latest finished cancel flow (its key, like too_expensive).
NoChurn: Cancel flow outcomenochurn_cancel_outcomeSingle-line textsaved, canceled, abandoned or reverted.
NoChurn: Offer acceptednochurn_offer_acceptedSingle checkboxWhether the customer accepted an offer in that cancel flow.
NoChurn: Win-backnochurn_winback_statusSingle-line textThe latest win-back: in_progress, won_back, lost or stopped.
NoChurn: Last NoChurn eventnochurn_last_eventSingle-line textThe type of the latest event on the customer’s NoChurn timeline.
NoChurn: Last NoChurn event atnochurn_last_event_atDate and timeWhen it happened.
NoChurn: NoChurn customer IDnochurn_customer_idSingle-line textThe customer’s NoChurn id (cst_…).
NoChurn: NoChurn linknochurn_urlSingle-line textA link to the customer’s page in the NoChurn dashboard.

NoChurn writes only what it knows: when there is no value (a customer never in a recovery, not scored yet), the property is cleared, never filled with a guess. Card data never leaves NoChurn: no card number, and no card details at all in the CRM.

Matching contacts

NoChurn finds the contact of each customer by email by default (case does not matter). You can match on your own id instead: in Match customers by, choose Your user id (external_id) or Stripe customer id, then name the HubSpot property internal name that holds it (for example app_user_id).

  • The match is made again at every write, so a contact merged or recreated in HubSpot is found again.
  • When several contacts match the same customer, NoChurn writes on each of them.
  • A customer without the value to match on (no email, no external id) is skipped.
  • New contacts are off by default. A customer without a matching contact is left out (“without a match” in the drawer), never created. Turn on Create a contact when none matches to create one, with the customer’s email .

When NoChurn writes

  • After each change. Anything that happens to a customer (a failed payment, a new score, a cancel flow, a win-back) marks it for HubSpot. NoChurn waits about 2 minutes, then writes everything that changed in that window in one go: a burst of events becomes one write.
  • Every day, a full pass checks every customer and writes only those whose values changed since the last write. A customer whose values did not change costs no HubSpot call.
  • Sync now in the drawer starts a full pass at once. So does connecting, and saving new settings (another mapping, another way to match, another mode): every customer is written again.
  • NoChurn writes 100 customers per batch; a large account is written over several minutes.

The drawer shows the last sync and its counts (updated, created, unchanged, without a match, skipped, refused) and how many customers are waiting. Each batch is also recorded in NoChurn’s event log (crm.synced, or crm.sync_failed with HubSpot’s own message).

Settings and mapping

SettingDefaultWhat it does
Customers to writeLive customers Live or test customers, never both. Test data only reaches HubSpot when you choose Test customers, for example to try it on a HubSpot sandbox account.
Match customers byEmailEmail, your user id (external_id) or the Stripe customer id, with the property that holds it.
Create a contact when none matchesOffOff: those customers are skipped.
Field mappingEvery field, default namesEach NoChurn field goes to the HubSpot property internal name on the right. Turn a field off to stop writing it, or point it to another property. Default mapping puts the default names back.

Property names are internal names: lower case letters, digits and _, like nochurn_churn_score. When you map a field to a name that does not exist yet, NoChurn creates it in the NoChurn group on the next sync. A property can receive one NoChurn field only.

Errors and limits

  • Access revoked or expired: the drawer shows Needs reconnecting and a Reconnect HubSpot button; nothing is written until then. If the write permissions were not approved, reconnect and approve every permission.
  • HubSpot refuses a value (a property of the wrong type, for example): the sync stops with HubSpot’s own message. Fix the property or the mapping, then click Sync now.
  • Rate limits: when HubSpot answers that too many requests were made, NoChurn waits for the next 10-second window. Nothing is lost: the customers stay waiting and are written on the next run.

Disconnect

Disconnect in the drawer (owners and admins, after a confirmation) erases NoChurn’s access to HubSpot and stops writing. What NoChurn already wrote stays on your contacts: it is your data, and the NoChurn properties stay in HubSpot until you delete them. To use it again, connect it anew.

API

The dashboard calls POST /v1/integrations/hubspot_crm/authorize (returns the HubSpot URL to open), then PATCH /v1/integrations/{id} with a crm object for the settings, POST /v1/integrations/{id}/sync for Sync now and DELETE /v1/integrations/{id} to disconnect. Reference: Integrations.

← All integrations