Quartz 5

🎙️ Session: 18 11:59 CDT - Notes by Gemini

Properties1
tagsintelligence--active

6 min read

🎙️ Session: 18 11:59 CDT - Notes by Gemini

Executive Summary

The CLG Jam session focused on critical refinements to HubSpot email configurations and a significant strategic pivot in workflow automation for client learning paths. Initial efforts streamlined email template variables, ensured consistent formatting, and established an ‘In Progress’ trigger for onboarding. A key architectural shift occurred in managing projects on ‘on hold’ status: moving from complex date calculation scripts to a more robust “self-healing milestone pattern” implemented via a daily scheduled workflow. This new approach pauses email timers and maintains participant position during holds, greatly enhancing system flexibility and reliability. The session concluded with defined next steps for workflow updates, documentation, and further stakeholder discussions.

Key Architectural Frameworks & Core Principles

  • Self-Healing Milestone Pattern: A core principle adopted for workflow automation, ensuring system flexibility by using milestone checkboxes to instantly halt and safely resume execution when a project’s status changes (e.g., ‘on hold’ to ‘in progress’), rather than relying on complex, error-prone date recalculations.
  • Prioritization of Backend Functionality over High-Level Design: During development, the team explicitly focused on verifying workflow functionality and technical infrastructure over incorporating elaborate design elements or images beyond essential branding, setting boundaries for future client design requests.
  • Contact Object as Central Data Source: Emails and associated properties (like Zoom links) are explicitly tied to the HubSpot Contact object to ensure data accessibility and consistency across the system, resolving issues with object type mismatches (e.g., ‘project task’).
  • Daily Scheduled Trigger for Robust State Management: The final architecture for handling ‘on hold’ projects utilizes a daily scheduled workflow with a specific ‘on hold’ pipeline status condition. This trigger employs custom code to effectively pause email timers by pushing them forward 24 hours daily, ensuring project participants remain in place without being dropped from the workflow.
  • Standardized Email Variable Fallback: Implemented a consistent approach for email personalization, using a ‘Contact Owner First Name’ variable with a fixed fallback value (‘CLG Team’) to guarantee automated communication consistency.

Flight Plan Action Items

  • [Kevin Dockman] Update Workflow: Update the workflow configuration for proper operation.
  • [Kevin Dockman] Update Documentation: Adjust the project documentation to ensure accuracy.
  • [Brenn Almario] Clear Formatting: Remove existing formatting from email templates to resolve display issues.
  • [Kevin Dockman] Research Session Date: Identify the method for pulling the session date variable within the email system.
  • [Kevin Dockman] Format Workflow: Apply consistent formatting to the remaining workflow documentation.
  • [Kevin Dockman] Discuss Hourly Delays: Consult with stakeholders regarding limitations with hourly email delays in the system.
  • [Kevin Dockman] Discuss Timestamps: Discuss timestamp requirements with relevant stakeholders.
  • [Kevin Dockman] Update Documentation: Update the specification document workflow and push the final commit to GitHub.
  • [Kevin Dockman] Retrieve File: Retrieve the necessary email or file mentioned in the discussion.

Key Structural Sections of the Discussion

HubSpot Email Configuration and Content Development

  • Email Configuration Resolution: Brenn Almario and Kevin Dockman resolved issues with email subscription types and contact owner IDs. Kevin guided Brenn to use the “Personalized token” feature for owner names and emails, setting a fallback of “CLG team” for functionality.
  • Content and Functionality Priority: Discussions on the “Coaching circles” campaign emphasized verifying workflow functionality over high-level design. It was agreed that for the staging/development environment, images beyond the logo were unnecessary.
  • Variable and Link Management: For welcome emails, Kevin advised Brenn to use generic hyperlinks or placeholders for missing variables, prioritizing template cleanliness over waiting for specific system variables. Unnecessary brackets were removed.
  • Formatting and Cleanup: Kevin requested Brenn clear all formatting from copied text (from Google Docs) to resolve display issues, focusing on cleaning spacing, tabs, and layout to finalize the three emails.
  • Email Organization & Project Scope: Brenn organized emails into a “Learning Path notifications” folder. Kevin reiterated their role as technical architects, not designers, setting boundaries for client design requests.
  • Session Date Integration: The need to include session dates in the “Join live session” email was noted. Since the variable logic was undetermined, Brenn agreed to highlight this section for later adjustment.
  • Property Syncing for Email Data: Brenn’s difficulty adding Zoom links due to “project task” defaulting led Kevin to clarify that Learning Path properties sync with Contact properties. Consequently, emails were tied to the Contact object to ensure data accessibility.

Workflow Automation Development & Strategic Pivot

  • Learning Path Onboarding Workflow:

    • Kevin directed Brenn to configure the “Learning Path Onboarding and Initialization” workflow.
    • Trigger set for new Learning Path creation when “Start Date” is known.
    • Workflow action copies “HS Start Date” to “Start Date Adjusted” for tracking.
    • Workflow trigger was restricted to ‘In Progress’ status for initial execution.

  • Initial Date Shifter Workflow Attempt:

    • Kevin provided custom JavaScript for duration calculations in a “Learning Path On-Hold Date Shift” workflow.
    • Brenn pasted the code into a trigger set for pipeline stage changes to “In Progress” or “On Hold.”
    • The workflow was published for testing despite script performance uncertainties.
    • Input properties (start date, adjusted date, time on hold) and output properties (status, new adjusted date, cohort drift days) were mapped for the script.

  • Email Nurture Workflow Configuration:

    • Brenn created the nurture sequence with delays based on “Start Date Adjusted.”
    • A HubSpot limitation regarding hourly scheduling was identified, leading to all email delivery times being set to 8:00 a.m. Eastern time. Kevin planned to discuss this with the client.

  • Strategic Pivot to Self-Healing Milestone Pattern:

    • During testing discussions, Kevin expressed concerns about the complexity of date shifting while projects are on hold.
    • He proposed a shift from date calculation to a “self-healing milestone pattern,” using milestone checkboxes to halt execution instantly when paused and resume safely when reactivated.
    • This led to the decision to deactivate the existing email nurture sequence and “date shifter” workflow.
    • A new alternate workflow, specifically for the “learning path daily on hold date shift,” was to be created.

  • Daily Date Shifter Implementation (Final Architecture):

    • Kevin guided Brenn to set up a new scheduled trigger for the “Learning Path Daily On Hold Date Shift” workflow.
    • Configured to run daily at 12:00 a.m. with a condition for the pipeline stage to be “on hold.”
    • The action was set to “run custom code” using the Data Ops trigger, with “start date adjusted” and “cohort drift days” as inputs.
    • Workflow Logic: Participants remain in their current delay steps. While on hold, their email timers are pushed forward by 24 hours daily. When the project returns to “in progress,” the daily trigger stops, locking the final shifted date.

Documentation & Next Steps

  • Kevin confirmed the specification document for the workflow has been updated and committed to GitHub.
  • He noted an upcoming meeting and expressed an intention to involve Brenn in future meetings.

Graph View

Backlinks