FINANCE

Final-Notice CSM Handoff Before Cancellation

When Stripe's last retry fails and a subscription is about to cancel, assembles a full account dossier and routes a final-notice handoff task to the CSM via Outlook and HubSpot.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe final-attempt failure webhookStripeStripe
  • LogicConfirm last retry and pending cancellation
  • ActionCompile account dossier from PostgresPostgreSQLPostgres
  • ActionCreate priority CSM task in HubSpotHubSpotHubSpot
  • OutputEmail final-notice dossier via OutlookOutlook

What it does

This workflow catches the moment a subscription has exhausted automated recovery and is hours from cancellation. It builds a complete dossier and forces a human decision before the customer is lost, rather than letting Stripe silently cancel.

When to use it

Use it as the terminal stage of any dunning program where losing the account should never be automatic. Best when CSMs are willing to make a save call or offer a downgrade before cancellation.

How it works

  1. 1A Stripe webhook for the final failed attempt (subscription entering `past_due` with no retries left) triggers the run.
  2. 2A logic gate confirms this is the last attempt and the subscription is flagged for cancellation.
  3. 3It compiles lifetime value, open support tickets, and renewal date from Postgres and HubSpot into a single dossier.
  4. 4It creates a high-priority handoff task on the owning CSM in HubSpot with a hard due-date before the cancel timestamp.
  5. 5It emails the CSM the dossier and save options via Outlook.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect HubSpotCRM, deals, marketing, support.
  4. 4
    Connect OutlookMail, calendar, contacts.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.