Recued
Menu
← Back to recipes

Notify decaying engagement velocity (D-139)

by recued-core v2 24 views

Use “Notify decaying engagement velocity” in Recued. It helps you complete this workflow using the connections and settings you choose.

How it works 5 steps

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

Data fetch
▼ velocity_rows core.data.enrichment.list
List data enrichment
▼
Process (4 steps)
■ defaults defaults
Apply defaults
■ should_skip any
Check if any of the conditions are true
◆ notify core.notification.send
Send notification
skip: step.should_skip equal true
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 2 configurable

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

channels setting = [object Object]
amount floor setting = 10000

Uses (2 operations)

Enrichments List data enrichment core.data.enrichment.list
Notifications Send notification core.notification.send

Trust & control

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

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.

What it's allowed to do

Read Enrichments core.data.enrichment.list read-only
Read Notifications core.notification.send external change

Data it touches

SurfacesEnrichmentsNotifications
Warehousedata.connectiondata.enrichment

About

Tags

crmhubspotsalesforcedealengagementvelocityalertreactivecross_vendor

Details

5 steps 2 configurable settings recipe_id: notify-engagement-velocity-decaying