Skip to content
Recued
Menu
← Back to recipes

Surface stalling CRM deals (cross-vendor)

by recued-core v1

Alert when a deal's velocity signal turns 'stalling' and its amount exceeds a configurable floor. The single cross-vendor stalling alert: subscribes via the canonical `on: deal.changed` sugar, which fans to every installed CRM vendor carrying the `deal` crm_alias (HubSpot deal + Salesforce opportunity today, any future vendor automatically) — so one recipe replaces the former per-vendor trio. For each fired record it reads the cross-vendor `deal_velocity_signal` enrichment and the deal's name + amount from the platform-reference `meta` snapshot the vendor reconciler writes at ingest (no per-fire vendor API call). Requires a sales-augmentation pack (HubSpot or Salesforce) installed to populate the velocity signal.

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Data fetch
velocity_rows ?
Process (7 steps)
velocity default
Apply default
amount default
Apply default
deal_name default
Apply default
vendor_label default
Apply default
should_skip any
Check if any of the conditions are true
notify ?
skip: step.should_skip equal true
card to_summary
Format results as a summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

channels setting = in_app
amount floor setting = 10000

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Send notificationsRead your HubSpot connectionRead your Salesforce connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.enrichment

About

Tags

crmhubspotsalesforcedealalertreactivecross_vendor

Details

8 steps 2 configurable settings recipe_id: surface-stalling-deals-crm