Cross-vendor cross-substrate reactive alert. Subscribes to inbound mail (`data.mail.**.created` — mail has no canonical CRM-alias sugar, so the raw bus pattern is the idiomatic form); for each inbound message looks up the sender's canonical email as a contact target_id in BOTH `lifecycle_stage_inferred` (HubSpot) AND `lifecycle_stage_inferred_salesforce` (Salesforce) topics via the `core.data.enrichment.list` op. Dispatches a notification when EITHER vendor's lifecycle inference is `customer` — a single alert covers cross-CRM customer matching without forcing the user to install per-vendor variants. The two topics are read in parallel since the cross-vendor lifecycle topic split (D-130 P6 § 11) requires harmonising at the alert layer. Shares `variant_group: notify-new-inquiry-from-existing-customer` with the per-vendor variants and carries `variant_kind: 'cross_vendor'`.

How it works 13 steps

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

Process (13 steps)

■ from_email default

Apply default

■ subject default

Apply default

■ hubspot_lifecycle_rows ?

skip: step.from_email is_null

■ salesforce_lifecycle_rows ?

skip: step.from_email is_null

■ hubspot_stage default

Apply default

■ salesforce_stage default

Apply default

■ hubspot_is_customer compare

Check if hubspot stage equals customer

■ salesforce_is_customer compare

Check if salesforce stage equals customer

■ either_is_customer any

Check if any of the conditions are true

■ matched_vendor ternary

Apply ternary

■ should_alert all

Check if all conditions are true

■ notify ?

skip: step.should_alert equal false

■ card to_summary

Format results as a summary card

Settings 1 configurable

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

channels setting = in_app