OTHER

Compute a weekly account health score and write it back to HubSpot

Once a week, blends usage, support, and billing signals into a single 0-100 health score per account, writes it to HubSpot, and posts the week's biggest decliners to Slack.

CategoryOther
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionPull usage, recency, seat utilization per accountPostgreSQLPostgres
  • ActionFetch payment status and failed invoicesStripeStripe
  • LogicCompute weighted 0-100 score and trend
  • ActionUpsert health score onto company recordHubSpotHubSpot
  • OutputPost biggest decliners to #customer-successSlack

What it does

This workflow rolls several scattered churn signals into one comparable health score per account, stores it where the revenue team already works, and surfaces who got worse this week.

When to use it

Use it when you want a durable, trended health metric in HubSpot rather than ad-hoc alerts — so segments, dashboards, and playbooks can all key off one number.

How it works

  1. 1A weekly schedule starts the run.
  2. 2A Postgres query pulls usage trend, login recency, and seat utilization for every account.
  3. 3A Stripe action fetches recent payment status and any failed or downgraded invoices.
  4. 4A logic step combines the inputs into a weighted 0-100 score and a rising/flat/falling trend label.
  5. 5A HubSpot action upserts the score and trend onto each company record.
  6. 6A Slack message posts the ten accounts whose score dropped most week-over-week to #customer-success.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect StripeCustomers, subscriptions, payments.
  3. 3
    Connect HubSpotCRM, deals, marketing, support.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.