Workflow v1 — Follow Up

Source: Miro board "design" → frame "workflow v1 - follow up"

Extracted: 2026-07-14

6Steps

2Parts

4HubSpot Actions

1Drive Folder

1. Overview

The Follow Up frame is the final stage of the v1 call workflow — the output and persistence layer. Everything generated upstream (in the Post-Call frame) lands here. It pulls Cloud Latitude's brand design assets from a Google Drive folder, applies them to the generated content, saves all artifacts into a per-account plan folder, then mirrors everything into HubSpot as notes, deal updates, tasks, and file attachments.

Source / apply step

Save / persist step

Board transcription note

HubSpot action

2. Frame Flow

┌──────────────────────┐
│ PART 1 — SOURCE      │   pull brand assets from Drive
│  & APPLY CONTENT      │   → apply to generated content
└──────────┬───────────┘
           ▼
┌──────────────────────┐
│   SAVE OUTPUTS       │   [Account_Name]_plan in Drive
└──────────┬───────────┘
           ▼
┌──────────────────────┐
│ PART 2 — UPDATE      │   add note · update deal
│   HUBSPOT (×4)        │   create task · attach files
└──────────────────────┘

3. Step-by-Step Workflow

1 Get Cloud Latitude design assets source

Pull the brand design source material from the linked Google Drive folder. Three assets are required:

GET CLOUD LATITUDE
DESIGN.MD, DESIGN SYSTEM,
UI KIT FROM THIS FOLDER >

Drive folder (as written on the board):

Verbatim from board https://drive.google.com/drive/folders/1o41Z-2jYiW_d_mN6z9TvO7yvZxZgca?usp=drive_link

⚠ Transcription note: The Drive URL on the original board appears slightly mangled (rendered across line breaks as 1o41Z- / 2jYiW_d_mN6z9TvO7yvZxZgca / N?usp=drive_link). Documented as-is above; treat the full URL as the intended link.

↓

2 Apply to content apply

Take the Design System and UI Kit pulled in Step 1 and apply them to the content generated upstream (the post-call deliverables — one-pagers, slides, summary emails). This is the brand-application step.

APPLY TO CONTENT

↓

3 Save outputs to Google Drive persist

Every generated artifact is saved into a per-account folder in Google Drive, named with the account name.

Verbatim from board Save all outputs to [Account_Name_plan] in google drive

Convention: [Account_Name]_plan — one plan folder per account acts as the single source of truth for that account's generated materials.

↓

4 Update HubSpot integration · 4 actions

Mirror the call's outputs into the CRM record. Four sequential actions, each a write to HubSpot:

#	Action	Verb on board	What it does
4a	add note	`add note`	Create a note on the contact/deal record capturing the call summary
4b	update deal	`update deal`	Update the deal record (stage, fields, BANT/MEDDPIC, next steps)
4c	create task	`create task`	Create a follow-up task (e.g. next-step reminder)
4d	attach files	`attach follow up items as files`	Attach generated artifacts (one-pager, slides, summary email) as files to the record

Verbatim from board update hubspot add note update deal create task attach follow up items as files

4. Verbatim Inventory (as on board)

Strict top-to-bottom reading order of every text element inside the frame, transcribed exactly.

#	Part	Verbatim text
1	Source	`GET CLOUD LATITUDE`
2	Source	`DESIGN.MD, DESIGN SYSTEM,`
3	Source	`UI KIT FROM THIS FOLDER >`
4	Apply	`APPLY TO CONTENT`
5	Save	`Save all outputs to`
6	Save	`[Account_Name_plan] in`
7	Save	`google drive`
8	HubSpot	`update hubspot`
9	HubSpot	`add note`
10	HubSpot	`update deal`
11	HubSpot	`create task`
12	HubSpot	`attach follow up items as files`
13	URL	`https://drive.google.com/drive/folders/1o41Z-2jYiW_d_mN6z9TvO7yvZxZgca?usp=drive_link` ⚠ mangled on board

5. Notes

Two logical parts. The frame combines a content-source/apply block (top) with the HubSpot follow-up block (bottom). They read as one flow: source → apply → save → mirror to CRM.
Drive URL transcription. The Google Drive link is split across line breaks on the original board (1o41Z- / 2jYiW_d_mN6z9TvO7yvZxZgca / N?usp=drive_link). Reassembled above as the intended URL; verify the folder ID before relying on it.
Folder naming. Board writes [Account_Name_plan] — convention is one _plan folder per account.
HubSpot order. The four actions read top-to-bottom: note → deal → task → files. Logical sequence: capture the summary, update the record, schedule the follow-up, attach the artifacts.