Event Management
Workflows handling event registration, confirmation, and attendee tracking
| Metric | Value |
|---|---|
| Workflows | 4 |
| Priority | medium |
| Grouping Confidence | 70% — Mixed marketing (registration) and sales (follow-up) activities with unclear scope boundaries |
| Consolidation | Create unified event workflow with registration confirmation, attendee routing, and follow-up task assignment |
Workflows in this Group
| Workflow | Trigger | Outcome | Type | Complexity |
|---|---|---|---|---|
| [RVSP Confirmation] December 2024: NYC Event | Contact RSVPs for December 2024 NYC event | Contact receives RSVP confirmation email with event details and is added to event attendee tracking | Notification | medium |
| Events | Contact registers for or attends an event | Sync event attendee data to Clay | DataSync | low |
| Assign Crescendo Live NY call tasks | Contact is identified for Crescendo Live NY event follow-up calling campaign | Contact is assigned to specific team members and enrolled in appropriate sequence for event follow-up | Routing | medium |
| Event test | Test trigger for event-related functionality | Validates event data integration with Clay | DataSync | low |
Key fields: hubspot_owner_id
Dependencies: Event management platform, Task assignment logic
Domain Summary
Mixed collection of event-related automations with unclear scope boundaries. Contains event-specific confirmation emails, external data sync to Clay, sales follow-up assignment, and test workflows. Current implementation lacks unified event management strategy and relies heavily on external systems.
Current Problems
- Event-specific workflows (December 2024 NYC) create maintenance overhead and lack scalability
- Heavy reliance on external Clay system for event data processing instead of native CRM functionality
- No unified event management - registration confirmation and sales follow-up are disconnected
- Test workflow remains active in production environment
- Ambiguous scope between marketing events and sales meetings creates ownership confusion
Rearchitecture Approach
Consolidate into event lifecycle management with clear marketing/sales handoff. Eliminate external Clay dependency by implementing native Salesforce Campaign and Campaign Member functionality. Create reusable event templates instead of event-specific workflows.
Recommended Automations
Event Registration Handler
| 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: Process event registrations and trigger appropriate confirmation flows based on event type
Trigger: Contact record update with event registration data
Entry Criteria Formula: N/A
Logic Overview: Evaluate event type and registration status, create Campaign Member record, route to appropriate confirmation flow based on event category (marketing vs sales)
Replaces: [RVSP Confirmation] December 2024: NYC Event, Events
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Event_Type__c | Categorize events as marketing or sales-driven for routing logic | read | N/A | Yes | New field needed to distinguish between marketing events and sales meetings |
| Event_Registration_Status__c | Track registration status (registered, confirmed, attended, no-show) | both | N/A | Yes | Replaces event-specific tracking with standardized status field |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Sales Event Follow-up Router
| 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: Assign sales team members and enroll attendees in appropriate follow-up sequences for sales-focused events
Trigger: Campaign Member record indicates attended status for sales event
Entry Criteria Formula: N/A
Logic Overview: Query event type and attendee characteristics, assign to available team member using round-robin or territory rules, create follow-up tasks and sequence enrollment
Replaces: Assign Crescendo Live NY call tasks
Required Fields:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Event_Follow_up_Required__c | Flag indicating if event requires sales follow-up | read | N/A | Yes | Automates decision logic for follow-up requirements |
| OwnerId | Assign contact owner for follow-up activities | write | hubspot_owner_id | No | Standard Salesforce field, maps directly from HubSpot owner |
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
- Deactivate test workflow (Event test)
- Map existing event data to Salesforce Campaign and Campaign Member objects
- Build Event Registration Handler with reusable event templates
- Implement Sales Event Follow-up Router with team assignment logic
- Migrate event-specific confirmation emails to Marketing Hub
- Establish data sync between Marketing Hub events and Salesforce Campaigns
- Decommission Clay integration for event data
Architecture Diagram
graph TD
A[Contact Registration] --> B{Event Type?}
B -->|Marketing| C[Marketing Hub Confirmation]
B -->|Sales| D[Create Campaign Member]
D --> E{Attendance Status?}
E -->|Attended| F[Sales Follow-up Router]
E -->|Registered| G[Wait for Attendance Update]
F --> H[Assign Owner]
F --> I[Create Follow-up Tasks]
F --> J[Enroll in Sequence]
C --> K[Sync to Campaign Member]
K --> E</code></pre>