INTEGRATIONS

Zapier

Start a Zapier Zap on NoChurn events: failed payments, recoveries, cancellations, saves, disputes. Webhook URL, test events, payload and signatures.

Start a Zapier Zap whenever NoChurn recovers a payment, saves a customer or sees one cancel: post in Slack, update your CRM, add a row to a sheet, send an email. Zapier receives NoChurn’s signed webhooks: the same events, signature and retries as any other endpoint.

A native NoChurn app in Zapier’s directory is not available yet. Until then, you connect Zapier with a webhook URL, as below: nothing else to install.

Connect

  1. In Zapier, create a Zap with the trigger Webhooks by Zapier › Catch Hook and copy its URL.
  2. In NoChurn, open Integrations › Zapier, click Add a Zapier webhook, paste the URL in Catch Hook URL and pick the events.
  3. Click Send test event in NoChurn, then Test trigger in Zapier.
  4. Use the fields in any action: data.customer.email, data.customer.churn_score, data.customer.mrr_cents…

NoChurn only accepts a Zapier URL here (https:// on hooks.zapier.com). An endpoint belongs to one mode: in test mode it receives test events only. Switch the dashboard to Live to add the endpoint that receives your live events.

The signing secret is shown once, when the endpoint is created. You only need it to check signatures.

Events

The events you can start a Zap on, as the dashboard names them. The four marked “default” are ticked when you add an endpoint.

In the dashboardEvent type
A payment failed default recovery.opened
A failed payment was recovered default recovery.recovered
A customer started to cancel cancel_session.started
A customer accepted an offer and stayed default cancel_session.offer_accepted
A customer cancelled default cancel_session.completed
A customer came back winback.reactivated
A dispute was opened dispute.opened
A customer was flagged at risk customer.flagged

cancel_session.completed is sent when the cancel flow ends: read data.cancel_session.outcome to tell a cancellation from a save. With the API, an endpoint can subscribe to any type of the catalogue, or to all of them (["*"]).

Send a test event

Under each endpoint, pick an event and click Send test event. NoChurn sends a sample of that event, shaped like the real one, so that Zapier lists every field to map. The sample uses your most recently updated customer of the mode, or placeholder values named as such when you have none yet, and always carries data.test: true: filter it out of Zaps that must only run on real events. Nothing is saved in NoChurn and no decision is made.

curl -X POST https://api.nochurn.sh/v1/webhook_endpoints/whk_…/test \
  -H "Authorization: Bearer nc_test_…" \
  -H "Content-Type: application/json" \
  -d '{"type":"recovery.opened"}'

The answer is the delivery: status delivered with Zapier’s HTTP status, or the error. If Zapier refuses it, check the URL and that the trigger is listening (in Zapier, the trigger must be waiting for a request).

Payload

Every event has the same envelope (id, type, livemode, created, data). Every event about a customer carries a flat data.customer block, the easiest one to map:

FieldWhat it holds
idNoChurn customer id (cst_…).
email, nameAs known to NoChurn.
external_id, stripe_customer_idYour own user id and the Stripe customer id, when there is one.
churn_scoreThe churn score, 0 to 100; null until the customer is scored.
churn_levellow, medium or high; null until scored.
mrr_centsMonthly recurring revenue in the smallest unit of the currency (4900 = 49.00).
currencyISO code in lower case (eur).
statustrialing, active, in_recovery, paused, churned or none.

The rest of data depends on the type. A failed payment, as built by the API (example ids and values):

{
  "id": "nevt_9xQ2mV7pLk4Rt8Ws",
  "object": "event",
  "type": "recovery.opened",
  "livemode": false,
  "created": 1798675200,
  "data": {
    "customer": {
      "id": "cst_4fJ8sK2pQ9wLm3Xz",
      "stripe_customer_id": null,
      "external_id": "u_123",
      "email": "jenny@example.com",
      "name": "Jenny Rosen",
      "churn_score": 74,
      "churn_level": "high",
      "mrr_cents": 4900,
      "currency": "eur",
      "status": "active"
    },
    "invoice": {
      "id": "ninv_2Kq8sP4mVx9LdT3a",
      "external_id": "in_5521",
      "stripe_invoice_id": null,
      "status": "open",
      "amount_due_cents": 4900,
      "amount_remaining_cents": 4900,
      "currency": "eur",
      "subscription": {
        "id": "nsub_7Hd2kQ9xLm3VbN7p",
        "external_id": "sub_8812",
        "stripe_subscription_id": null
      }
    },
    "reason": "Payment failed: insufficient_funds",
    "flow_run": {
      "id": "run_6Tq1wZ8cHn3Lp5Vd",
      "flow": "recovery",
      "state": "running",
      "outcome": null,
      "confirmation": null,
      "holdout": false,
      "started_at": "2026-12-01T09:00:00Z",
      "outcome_at": null
    }
  }
}

Every type with its example: Webhook events.

Verify signatures

Each request carries a NoChurn-Signature header. Anyone who knows the Zapier URL can post to it, so check the signature if the URL could leak, for example in a Code by Zapier step before the actions, with the endpoint’s signing secret. How the signature is computed, with code in Node, Python and Ruby: Verify the signature.

Retries and duplicates

Zapier must answer with a 2xx. Anything else, or no answer within 10 seconds, is retried (7 attempts over about a day and a half); failed deliveries are listed in API keys & webhooks and can be replayed. A retry or a replay carries the same event id: if a Zap must not run twice, keep the ids already handled (a Zapier table or a lookup step works) and stop on a known one. Details: Retries and Handle duplicates.

Example automations

Ideas to start from. They are patterns, not results: what they bring depends on your customers.

  • Alert the account owner on a failed payment. recovery.opened → filter on data.customer.mrr_cents above your threshold → message in a Slack channel with the customer’s email and score.
  • Log saves and cancellations in a sheet. cancel_session.completed → one row per event with the email, data.cancel_session.outcome, data.cancel_session.reason and the MRR.
  • Hand a high-risk customer to a person. customer.flagged → filter on data.customer.churn_level = high → create a task in your CRM or help desk.
  • Prepare a dispute. dispute.opened → notify the finance channel with data.dispute.reason and data.dispute.evidence_due_by. NoChurn itself gathers the evidence: see Chargebacks.
  • Celebrate a comeback. winback.reactivated → message to the customer success team.

To write NoChurn’s score and status on CRM contacts without building a Zap, use the native HubSpot CRM or Salesforce sync.

API

The dashboard drawer calls the webhook endpoints API with app: "zapier", which only checks that the URL is a Zapier one:

curl -X POST https://api.nochurn.sh/v1/webhook_endpoints \
  -H "Authorization: Bearer nc_test_…" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://hooks.zapier.com/hooks/catch/…","app":"zapier","events":["recovery.opened","recovery.recovered","cancel_session.completed"]}'

A URL on another host answers 422 with the fix. PATCH /v1/webhook_endpoints/{id} changes the events or rotates the secret; DELETE removes the endpoint, and your Zapier Zaps stop receiving events. Reference: Developers.

← All integrations