Sales Activity Notifications
Slack and email notifications for sales team visibility on meetings, calls, and sequence activities
| Metric | Value |
|---|---|
| Workflows | 5 |
| Priority | medium |
| Grouping Confidence | 90% — All focused on sales team notifications with shared notification patterns |
| Consolidation | Unify into comprehensive sales activity notification system with configurable channels and recipient rules |
Workflows in this Group
| Workflow | Trigger | Outcome | Type | Complexity |
|---|---|---|---|---|
| Sends a Slack notification when a new meeting is booked, including details about the owner, company, meeting date, and source. | New meeting is booked | Send Slack notification with meeting details to team | Notification | medium |
| Inbound - Gong Call Updates to Slack | Gong call recording becomes available | Send Slack notification about inbound call with delay for processing | Notification | medium |
| Outbound Sync - Sequence Replies to Slack + Email | Prospect replies to outbound sequence email | Send Slack notification and email alert with reply details | Notification | medium |
| Sends a slack notification when a BDR books a meeting | Business Development Representative successfully books a meeting with a prospect | Team receives Slack notification about the meeting booking for visibility and celebration | Notification | low |
| 2023-12 - PHS - Won Deals Attribution - Email + Task | Deal reaches won status | Send attribution email and create follow-up task for won deals | Notification | medium |
Key fields:
Dependencies: Slack API, Gong integration, Email delivery system
Domain Summary
Manages notifications to sales teams about critical activities including meeting bookings, call recordings, sequence replies, and won deals. Currently scattered across multiple notification channels with inconsistent triggers and formats.
Current Problems
- Duplicate meeting notification workflows (82458055 and 93054535) creating noise and confusion
- Inconsistent notification formats across different activity types
- Hard-coded recipient lists in individual workflows preventing dynamic routing
- No centralized notification preferences or opt-out management
- Won deal workflow (52905228) combines attribution email with task creation, violating single responsibility principle
- Gong integration workflow includes unnecessary 5-minute delay that could impact timely notifications
Rearchitecture Approach
Consolidate into a unified notification framework with configurable routing rules, standardized message templates, and preference management. Separate concerns by creating distinct automations for different activity types while sharing common notification infrastructure.
Recommended Automations
Meeting Booking Notification Router
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | high |
| Reusable | Yes |
Purpose: Centralized routing of meeting booking notifications with role-based recipient rules
Trigger: Meeting object created or updated to booked status
Entry Criteria Formula: N/A
Logic Overview: Evaluate meeting type, owner role, and company attributes to determine notification recipients and channels. Format consistent message template with meeting details and send via configured channels.
Replaces: Sends a Slack notification when a new meeting is booked, including details about the owner, company, meeting date, and source., Sends a slack notification when a BDR books a meeting
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Meeting_Type__c | Distinguish between BDR bookings, AE meetings, demo calls, etc. | read | hs_meeting_type | No | Standard HubSpot meeting type field |
| Notification_Recipients__c | Dynamic recipient list based on meeting type and owner | read | N/A | Yes | New field to support flexible recipient routing |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Call Recording Notification Handler
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | medium |
| Reusable | Yes |
Purpose: Process Gong call recordings and notify relevant team members
Trigger: Contact updated with new Gong call data
Entry Criteria Formula: N/A
Logic Overview: When call recording becomes available, format notification with call details and participant information. Route to appropriate Slack channels based on call direction (inbound/outbound) and owner team.
Replaces: Inbound - Gong Call Updates to Slack
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Gong_Call_Recording_URL__c | Link to call recording in Gong | read | Gong integration field | No | Maintained from existing Gong integration |
| Call_Direction__c | Distinguish inbound vs outbound calls for routing | read | Gong integration field | No | Available from Gong integration |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Sequence Reply Notification System
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | high |
| Reusable | Yes |
Purpose: Alert teams when prospects respond to outbound sequences
Trigger: Contact enrollment event indicates sequence reply
Entry Criteria Formula: N/A
Logic Overview: Extract reply details, sequence context, and prospect information. Send dual notifications (Slack + email) to sequence owner and team with reply content and next action suggestions.
Replaces: Outbound Sync - Sequence Replies to Slack + Email
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Last_Sequence_Reply__c | Store most recent reply content | both | enrollment_events data | No | Extract from sequence engagement data |
| Reply_Sentiment__c | Categorize reply as positive, negative, or neutral | write | N/A | Yes | New field to enhance notification context |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Won Deal Attribution Tracker
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | medium |
| Reusable | No |
Purpose: Handle attribution reporting and follow-up tasks for closed-won deals
Trigger: Opportunity stage changed to Closed Won
Entry Criteria Formula: N/A
Logic Overview: Calculate attribution metrics, generate attribution report, and create follow-up tasks. Separate from notification system to maintain single responsibility.
Replaces: 2023-12 - PHS - Won Deals Attribution - Email + Task
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Attribution_Source__c | Track original lead source for attribution | read | original_source_type | No | Map from HubSpot lead source tracking |
| Attribution_Report_Sent__c | Prevent duplicate attribution reports | write | N/A | Yes | New field to track report delivery |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Notification Preferences Manager
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | high |
| Reusable | Yes |
Purpose: Reusable component for managing user notification preferences and routing
Trigger: Called by other notification automations
Entry Criteria Formula: N/A
Logic Overview: Invocable action that evaluates user preferences, team settings, and activity type to determine notification recipients and channels. Supports opt-out management and escalation rules.
Replaces: N/A
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Notification_Preferences__c | Store user notification channel preferences | read | N/A | Yes | New field to support preference management |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Cross-Flow Interaction Model
Interaction handoffs were not provided. Add flowInteractionModel entries so build sequencing and contracts are explicit.
Migration Sequence
- Build Notification Preferences Manager as shared component
- Implement Meeting Booking Notification Router to consolidate duplicate workflows
- Deploy Sequence Reply Notification System for high-priority outbound sales
- Create Call Recording Notification Handler
- Implement Won Deal Attribution Tracker last as it has different business cycle
Architecture Diagram
graph TD
A[Meeting Booked] --> B[Meeting Booking Router]
C[Gong Call Available] --> D[Call Recording Handler]
E[Sequence Reply] --> F[Sequence Reply System]
G[Deal Won] --> H[Attribution Tracker]
B --> I[Notification Preferences Manager]
D --> I
F --> I
I --> J[Slack Notification]
I --> K[Email Notification]
I --> L[Task Creation]
H --> M[Attribution Email]
H --> N[Follow-up Task]
style B fill:#e1f5fe
style D fill:#e1f5fe
style F fill:#e1f5fe
style H fill:#fff3e0
style I fill:#f3e5f5</code></pre>