Quartz 5

WayCup Engine Ingestion & Publish Planning

Properties1
tagscore--active

8 min read

WayCup Engine Ingestion & Publish Planning

This document details the architectural evaluation of Obsidian Publish vs. our Headless Quartz deployment, and provides a comprehensive blueprint for the WayCup Fuel Pump—our automated, multi-app ingestion pipeline.

⚖️ The Investment Verdict: Obsidian Publish vs. Quartz vs. Slack Pro/AI

FeatureObsidian Publish ($96/year)Headless Quartz + Cloudflare Pages (Current)Slack Pro (100/year)Slack AI Add-on (+$120/year)
Primary FocusRead-only public presentation of vault notes.Read-only public presentation of vault notes.Multi-app communication and integrations.Proprietary Slack-native summaries and search.
Write API / IngestionNone. Does not allow pushing notes via webhook or external integration.None directly, but compiles from physical files on “The Box” (auto-published in 90 seconds).Excellent APIs. Unlocks unlimited integrations, webhooks, and full history retention.None. The AI features are locked inside the Slack UI.
ROI VerdictREJECTED. Provides zero automation or ingestion advantages.RETAIN & EXPLOIT. Keep Quartz on Cloudflare Pages; redirect the $96 investment to integration tools.ACTIVE & INTEGRATED. Already purchased. Fully leveraged for HubSpot, Calendar, and custom Box webhooks.REJECTED. Low ROI since you don’t use Slack heavily. We can build a custom Slack summary/alert agent on The Box for free.

🤖 Slack AI vs. Custom WayCup Slack Assistant

Slack offers a proprietary AI add-on (usually costing an additional $10/mo on top of Pro/Business+). Here is why a Custom WayCup Slack Agent running on The Box is vastly superior for your workflow:

  1. Proprietary Lock-in (Slack AI): Slack’s native AI summaries exist only inside the Slack app. It does not help feed your centralized Obsidian Vault, meaning your “knowledge engine” remains fragmented.
  2. Custom Response Alerts (Fast Response Times): To solve the issue of missed client messages, we can program a background script on The Box that listens to Slack DMs/channels. If a client messages you, the script analyzes the urgency using Gemini and sends a high-priority push notification directly to your Google Chat (your single hub) or via SMS.
  3. Unified Daily Summary: The same script can compile a daily recap of all Slack activity and insert it directly into your Obsidian Daily Note alongside HubSpot and Calendar records.

💬 The UI Chaos Solution: Slack & Google Chat Consolidation

To solve the multi-app communication and UI chaos, we will consolidate client chat channels into our primary workflow using a two-pronged strategy:

[ Client Slack Workspace ]             [ Client Google Chat Space ]
           |                                       |
           |-- HubSpot Slack Integration           |-- Add kevin@waycupcreative.com
           |   (Logs conversations/DMs)            |   as Guest
           v                                       v
[ HubSpot Unified CRM Inbox ]             [ Primary Google Workspace ]
           |                                       |
           +-------------------+-------------------+
                               |
                               v (WayCup Fuel Pump daily scan)
                   [ The Box Engine Room / Vault ]

1. Slack Ingestion & Unification

  • The HubSpot Slack Integration (Active): Leveraging your active Slack Pro tier, conversations and activity in channels/DMs you care about are auto-logged directly into HubSpot’s timeline. This feeds into our HubSpot Engagements API pipeline, ensuring Slack activity lands in your Daily Notes with zero extra scripts.
  • Slack Pro Leverages: Your active Slack Pro subscription removes the 10-integration limit, allowing us to seamlessly connect HubSpot, Google Calendar, and your own custom webhook listeners on The Box to stream high-signal DMs and channel events into your environment.

2. Google Chat Consolidation

  • For Google Chat spaces that allow external access, add kevin@waycupcreative.com as a workspace guest and transition your presence there, eventually removing kevin.dockman@thedogwizard.com from those spaces.
  • This allows you to stay logged into your primary WayCup account on your devices for both Mail and Chat.

📬 Multi-Account & Inbound Air-Gap Communication Architecture

To solve the madness of three separate Google accounts (kevin.dockman@gmail.com, kevin@waycupcreative.com, and kevin.dockman@thedogwizard.com) and protect asynchronous operational boundaries, we implement a decoupled Google Workspace routing design.

[ External / Public Senders ]          [ kevin.dockman@thedogwizard.com ]
             |                                        |
             v (Send to ops@waycupcreative.com)       |-- Forward Emails (Keep logins)
  [ Group 1: Public Intake ]                          |-- Share Calendar (Full Access)
             |                                        v
             v (Silent internal forward)      [ kevin@waycupcreative.com ]
  [ Group 2: Private Ingest ]                         (Primary Hub & Workspace Vault)
             |                                        |
             v (API / Connected Inbox)                |-- Syncs Daily to:
  [ HubSpot Help Desk & Breeze AI ] <-----------------+
             |
             v (WayCup Fuel Pump daily scan)
  [ The Box Engine Room / Vault ]

1. Inbound Google Workspace Air-Gap Design

To prevent clients from circumventing submission queues and discovered ingestion endpoints:

  • Group 1 (Client-Facing Intake Layer): ops@waycupcreative.com (or requests@waycupcreative.com). A public Collaborative Inbox where external emails land. Silently forwards all traffic to Group 2.
  • Group 2 (Isolated Ingestion Layer): connect-hub@waycupcreative.com. Private / Internal-only group that blocks external senders. Only accepts mail originating from internal domains. Natively connected to the HubSpot Conversations / Help Desk inbox via a secure forwarding alias.

2. The Multi-Account Consolidation Strategy

  • Rule of Engagement: kevin@waycupcreative.com is the Primary Hub. All external activities should ideally land here.
  • The Dog Wizard Transition:
    • Email Forwarding: Set up automatic forwarding of all inbound emails from kevin.dockman@thedogwizard.com to kevin@waycupcreative.com.
    • Send-As Alias: Configure kevin@waycupcreative.com to allow “Send As” kevin.dockman@thedogwizard.com so you can reply to client emails without switching mailboxes.
    • Calendar Federation: Share the Dog Wizard calendar with full read/write permission to the WayCup account (aligned with Reclaim.ai to block calendar slots).

3. The Agent-Level Unification (Decoupled API Harvesting)

If client security policies or technical limitations prevent direct forwarding/sharing of certain data, we can leverage Multi-Token Harvesting on The Box:

  • The WayCup Fuel Pump daemon on The Box will maintain separate OAuth credentials.
  • Even if your calendars aren’t merged on Google’s side, our script queries the APIs for all accounts simultaneously, dedupes overlapping items (e.g., invites sent from one to another), and writes a unified narrative to your Daily Note.

🏗️ Architectural Blueprint: The “WayCup Fuel Pump”

To build a 99% confident, centralized capture machine on The Box (our Debian Debian 12 Engine), we will construct a lightweight, high-reliability background suite.

graph TD
    %% Source App Integrations
    subgraph Sources [Exhaust Streams]
        HS[HubSpot CRM - Primary Inbox & Logs]
        GCal[Google Calendar - 3 Accounts]
        Meet_Docs[Google Drive - Meet Recordings Text]
        Fin_API[Finance APIs - Direct Integrations]
        GChat[Google Chat / Slack]
    end

    %% Ingestion Orchestrator on The Box
    subgraph Engine [The Box Engine Room]
        FP[WayCup Fuel Pump]
        G_AI[Gemini vertex Transcription]
        Sweeper[Sweep/Curator Agent]
    end

    %% Vault & Publishing
    subgraph Storage [The Vault Layer]
        T1[Daily Notes YYYY-MM-DD.md]
        Intelligence[04_Intelligence - Client Notes & Active Projects]
        SOPs[Static Pillars: 00_Engine, 01_Attract, 02_Convert, 03_Serve]
    end

    subgraph Portal [The Public Layer]
        CF[Cloudflare Pages - Quartz]
        Web[vault.waycupcreative.com]
    end

    %% Flow lines
    HS -->|HubSpot Meeting & Engagement API| FP
    GCal -->|Daily Scan| FP
    Meet_Docs -->|Direct Text Ingestion| FP
    Fin_API -->|Direct API / No Mail Noise| FP
    GChat -->|Webhook| FP

    FP -->|Write Markdown| T1
    T1 -->|Sweep / Distill| Sweeper
    Sweeper -->|Active Client Logs & WikiLinks| Intelligence
    SOPs -.->|Read-Only References & Context| Sweeper
    T1 -->|Git Push| CF --> Web

1. Vault Partitioning: Static Pillars vs. Active Logs

To keep your context lean and avoid inflating playbook templates with daily noise:

  • Static Playbooks (00_Engine, 01_Attract, 02_Convert, 03_Serve): These remain pristine, read-only references containing SOPs, frameworks, templates, and guides. The AI references them to generate recommendations, blueprints, and email drafts, but never writes daily logs here.
  • Dynamic Logs (04_Intelligence): This is the active database. Daily activity logs mapping to active projects, research, domains, and individual client workspaces are parsed, wikilinked, and stored directly in specific folders under 04_Intelligence/.
  • Internal WayCup Work: Internal admin, marketing, ops, and finance logs are mapped directly into WayCup’s internal admin subdirectory within 04_Intelligence/ or dedicated operational notes.

2. Ingestion Sources & Integration Methods

📞 Pre-Transcribed Meetings & Audio (Zoom & Google Meet)

Rather than executing expensive local audio processing for every meeting, we leverage pre-transcribed text assets:

  • Google Meet Transcripts: Google automatically saves meeting transcripts/docs directly in your Drive “Meet Recordings” folder. The WayCup Fuel Pump scans this Drive folder for .txt, .docx, .gdoc, or .vtt text assets, processes them through Gemini for fast summarization, and commits them straight to the Vault.
  • HubSpot Meeting Notetaker Logs: Your HubSpot Notetaker joins Zoom and Google Meet calls and logs meeting summaries, recordings, and transcripts natively onto the HubSpot Meeting Engagement Object. Our HubSpot API integration fetches these fully compiled logs directly, removing any file-sync workarounds.
  • Local Audio Intake: For ad-hoc files or phone recordings dropped in 00_core/vault/Inbox/Recordings/, the Fuel Pump retains its Gemini-based local audio transcriber as a fail-safe fallback.

🤝 CRM & Sales (HubSpot API - Primary Comms Hub)

  • Mechanism: HubSpot Engagements API / Webhooks.
  • Pipeline: Instead of parsing noisy raw Gmail boxes which introduces spam and notification overload, we route all professional emails through HubSpot’s unified inbox. The WayCup Fuel Pump then queries HubSpot’s Engagements API (notes, calls, meetings, tracked emails) daily. This guarantees we only capture high-signal, customer-mapped records with zero noise.

📧 Ops (Google Calendar & Google Chat)

  • Mechanism: Workspace APIs & MCP Tools.
  • Pipeline: A daily cron runs at 11:59 PM to pull:
    • Today’s calendar meetings and attendees across accounts.
    • Chat logs where you tag a bot (e.g. /log).

💳 Finance (Ramp, Gusto, QBO)

  • Mechanism: Direct API Integrations.
  • Pipeline: Direct API calls to Ramp and Gusto (rather than Gmail notifications) to fetch approved transactions and payroll events, completely bypassing inbox spam.

🚀 Execution Strategy & Next Steps

Instead of paying Obsidian, we can allocate that energy to building the simplest possible custom API endpoint on The Box.

  1. Phase 1: Google Calendar & Hot Folder / Drive Text Transcription. Build the script that compiles your merged Google Calendar (via kevin@waycupcreative.com), scans the Google Drive “Meet Recordings” folder for text transcripts, and processes them alongside local fail-safe recordings.
  2. Phase 2: HubSpot Engagement & Meeting API Integration. Write the Python daemon on The Box to query HubSpot for both daily engagement logs and Notetaker meeting records/summaries, writing them directly to the Vault.
  3. Phase 3: Financial Direct APIs. Connect directly to Ramp/Gusto APIs for clean administrative logging.

Graph View

Backlinks