INTEGRATIONS
Salesforce
Write each customer's churn score, risk factors, failed payment, cancel flow, win-back and MRR on the matching Salesforce Contact or Lead.
NoChurn writes what it knows about each customer on the matching Salesforce Contact (or Lead), 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. It only writes the NoChurn fields: your other fields are never changed or deleted.
Create the fields
NoChurn does not create fields in Salesforce: your Salesforce admin creates them first, in Setup › Object Manager › Contact (or Lead) › Fields & Relationships › New. The API names below are the defaults; you can use other names and change them in the mapping, or skip some fields and turn them off after connecting.
| NoChurn field | API name | Suggested type | Value |
|---|---|---|---|
| Churn score | NoChurn_Churn_Score__c | Number(3, 0) | The churn score, 0 to 100. Empty until the customer is scored. |
| Churn risk | NoChurn_Churn_Band__c | Text(10) | low, medium or high. |
| Risk factors | NoChurn_Risk_Factors__c | Long Text Area(1000) | The three factors that raise the score most, with their points, separated by ; (for example Prepaid card (+25)). |
| MRR | NoChurn_MRR__c | Number(16, 2) | Monthly recurring revenue in units of the currency (49.00, not cents). |
| Currency | NoChurn_Currency__c | Text(3) | ISO code in capitals (EUR). |
| Customer status | NoChurn_Status__c | Text(20) | trialing, active, in_recovery, paused or churned. |
| Failed payment | NoChurn_Recovery_Status__c | Text(20) | The latest failed payment: open, recovered or lost. Empty if none. |
| Cancel reason | NoChurn_Cancel_Reason__c | Text(80) | The reason picked in the latest finished cancel flow (its key, like too_expensive). |
| Cancel flow outcome | NoChurn_Cancel_Outcome__c | Text(20) | saved, canceled, abandoned or reverted. |
| Offer accepted | NoChurn_Offer_Accepted__c | Checkbox | Whether the customer accepted an offer in that cancel flow. |
| Win-back | NoChurn_Winback_Status__c | Text(20) | The latest win-back: in_progress, won_back, lost or stopped. |
| Last NoChurn event | NoChurn_Last_Event__c | Text(80) | The type of the latest event on the customer’s NoChurn timeline. |
| Last NoChurn event at | NoChurn_Last_Event_At__c | Date/Time | When it happened. |
| NoChurn customer ID | NoChurn_Customer_Id__c | Text(32) | The customer’s NoChurn id (cst_…). |
| NoChurn link | NoChurn_URL__c | URL(255) | A link to the customer’s page in the NoChurn dashboard. |
Salesforce adds __c to a custom field’s name: enter NoChurn_Churn_Score as the field name to get
NoChurn_Churn_Score__c. Make the fields visible and editable for the profile of the user who connects NoChurn: a field that user
cannot see counts as missing.
NoChurn writes only what it knows: when there is no value (a customer never in a recovery, not scored yet), the field is cleared, never filled with a guess. No card data is ever written.
Connect
- In NoChurn, open Integrations › Salesforce. The drawer lists the fields to create.
-
For a sandbox, tick Sandbox org (signs in on test.salesforce.com). Otherwise NoChurn signs in on
login.salesforce.com. - Click Connect Salesforce, sign in with a user who can edit the NoChurn fields, and allow access. NoChurn asks to manage data through the API and to keep access (refresh token), nothing else.
- Back in NoChurn, the drawer shows the org, the last sync and what is waiting. Before writing, NoChurn checks that every mapped field exists on the object; if one is missing, the sync stops and names it.
Owners and admins can connect, change the settings and disconnect. By default NoChurn writes your live customers only, whatever mode the dashboard is in. To try it on a sandbox org with your test data, connect the sandbox and set Customers to write to Test customers.
Contact or Lead
NoChurn writes on Contacts by default. If your customers live as Leads, set Salesforce object to Lead and create the fields on the Lead object. A connection writes on one object at a time; changing it writes every customer again on the new object.
Matching records
NoChurn finds the contact or lead 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
Salesforce field API name that holds it (for example App_User_Id__c).
- The match is made again at every write, so a contact or lead merged or recreated in Salesforce is found again.
- When several records 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 records are off by default. A customer without a matching contact or lead 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
(and, as Salesforce requires,
LastNameset to the customer’s name, or the email when there is none; a Lead also getsCompanyset the same way).
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 Salesforce. 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 Salesforce 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 Salesforce’s own
message).
Settings and mapping
| Setting | Default | What it does |
|---|---|---|
| Customers to write | Live customers | Live or test customers, never both. Test data only reaches Salesforce when you choose Test customers, for example to try it on a Salesforce sandbox org. |
| Salesforce object | Contact | Write on Contacts or on Leads. The fields must exist on the object you choose. |
| Match customers by | Email, your user id (external_id) or the Stripe customer id, with the field that holds it. | |
| Create a contact when none matches | Off | Off: those customers are skipped. |
| Field mapping | Every field, default names | Each NoChurn field goes to the Salesforce field API name on the right. Turn a field off to stop writing it, or point it to another field. Default mapping puts the default names back. |
Field names are API names: letters, digits and _, like NoChurn_Churn_Score__c. A field can receive one NoChurn field only.
Errors and limits
- Access revoked or expired: the drawer shows Needs reconnecting and a Reconnect Salesforce button; nothing is written until then.
- Missing fields: the sync stops and names each missing field by its API name, with the path to create it (Setup › Object Manager › Contact or Lead › Fields & Relationships). Create them, or turn them off in the mapping, then click Sync now.
- Salesforce refuses a value (a field of the wrong type, for example): the sync stops with Salesforce’s own message. Fix the field or the mapping, then click Sync now. A record Salesforce refuses on its own (a validation rule, for example) is counted as refused; the others are written.
- Rate limits: when the org has used its daily API request allowance, NoChurn waits an hour before trying again. 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 Salesforce and stops writing. What NoChurn already wrote stays on your records: it is your data. To use it again, connect it anew.
API
The dashboard calls POST /v1/integrations/salesforce/authorize (with {"sandbox": true} for a sandbox; returns the
Salesforce URL to open), then PATCH /v1/integrations/{id} with a crm object for the settings
(object: contact or lead), POST /v1/integrations/{id}/sync for Sync now and
DELETE /v1/integrations/{id} to disconnect. Reference: Integrations.