# Transcript-to-Action Builder > **Version 1.1.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 20–40 minutes** Hand your clone a meeting or call transcript and say "help me build what we talked about." It summarizes the decisions, pulls out every action item, splits what it can do itself from what needs you, proposes a plan, and then gets to work after you approve. --- ## 1. Overview and value Good meetings end with a list of things to do. Then the list sits in a transcript nobody re-reads. Someone was supposed to write the process doc, draft the follow-up email, build the little tracker page, create the CRM tasks and set up the automation. A week later, half of it hasn't started. The Transcript-to-Action Builder closes that gap. When you give your clone a transcript, it: - **summarizes** the decisions and context (who, what, why, constraints), - **extracts every action item** into a table with owner, due date, dependency and the source quote, - **sorts the actions**: what the clone can do itself, what needs you, and what belongs to other people, - **proposes a plan** and asks a short batch of clarifying questions, - **executes after your approval**: drafts skills and instructions, builds apps or pages with **Clone_Code**, creates docs, sheets and slides, drafts emails, creates tasks in Salesforce or HubSpot (or issues in Linear), and writes generic step-by-step guides for tools it has no operator for, - **tracks progress** in a living plan and reports status as **Done / Waiting on you / Next**. **What you get:** | Benefit | What it looks like | |---|---| | Nothing falls through the cracks | Every action item is captured with its owner and source quote | | Faster follow-through | Drafts, docs and simple tools are ready the same day as the meeting | | Clear ownership | You see exactly what the clone did, what's waiting on you and what's next | | Safe by default | Emails stay as drafts, plans need your "yes", nothing goes to customers on its own | | Less rework | The clone asks clarifying questions before building, and starts with the simplest version | > Anything else (for example automation tools you run yourself) is **not** an integration. For a tool the clone has no operator for, it can only give you generic step-by-step instructions. --- ## 2. Who it's for - **Ops leaders and managers** who leave process meetings with a list of docs, checklists and automations to build. - **Leadership** who want decisions from planning or strategy meetings turned into owned, dated actions. - **Customer Success Managers** who leave customer calls with follow-ups, internal tasks and enablement material to create. - **Sales reps and sales leaders** who want call next steps turned into CRM tasks, draft follow-ups and simple collateral. - **Anyone** who has ever said "we should build a quick tool for that" in a meeting and never did. It works on demand: you bring the transcript, the clone does the rest. An optional scheduled variant can pick up tagged transcripts automatically. ## 3. How it works ``` ┌───────────────────────────────────────────────────────────────────┐ │ You give {CLONE_NAME} a transcript: │ │ pasted · upload · meeting_archive · call_archive · Drive/OneDrive │ │ "Help me build what we talked about." │ └───────────────────────────────┬───────────────────────────────────┘ │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ "Transcript to Action" skill │ │ │ │ 1. Read the transcript ──► split long ones into parts │ │ 2. Summarize ──► decisions · context · │ │ constraints · open questions │ │ 3. Extract action items ──► action · owner · due · │ │ dependency · source quote │ │ 4. Route each action ──► Clone can do / Needs you / │ │ Other people / Out of scope │ │ 5. Propose plan + ask batched clarifying questions │ │ │ │ ── waits for your "yes" ({APPROVAL_LEVEL}) ── │ │ │ │ 6. Execute ──► skills · Clone_Code builds · │ │ docs · email drafts · tasks · │ │ step-by-step guides │ │ 7. Update the plan ──► {PLAN_LOCATION} │ └───────────────────────────────┬───────────────────────────────────┘ │ ▼ ┌───────────────────────────────────────────────────────────────────┐ │ Status to you: ✅ Done · ⏳ Waiting on you · ➡️ Next │ └───────────────────────────────────────────────────────────────────┘ Optional: a scheduled task checks the meeting archive at {SCAN_TIME} for new transcripts containing {TRIGGER_KEYWORD} and starts at step 1 (it still stops at step 5 and waits for your approval). ``` ### How the clone routes each action item Every action item gets one category: | Category | Meaning | Example | |---|---|---| | **Clone can do** | The clone has the tool and the information to do it | "Write up the new onboarding checklist" | | **Needs you** | The clone can prepare it, but you must decide, sign in, send or click | "Send the revised proposal to the customer" (clone drafts, you send) | | **Other people** | Owned by someone else in the meeting | "Finance to confirm the budget" (clone can draft a request, the owner must agree) | | **Out of scope** | No tool for it, or it needs judgment the clone shouldn't make | "Decide on the new pricing" | ### Action routing table | Type of action | How the clone handles it | Tool | Needs approval? | |---|---|---|---| | Write a skill or clone instructions | Drafts the full markdown as one copy-paste block | None (chat) | Yes, and **you read it before saving** | | Build an app, page, form, calculator or internal tool | Builds a simple first version (MVP), shares the link or files | `{CODING_SKILL_NAME}` (default **Clone_Code**) | Yes | | Create a doc, checklist, SOP or summary | Creates the doc in `{DEFAULT_DOC_LOCATION}` | `GoogleDocsCoreOperator` / `Microsoft_Word` (plus Drive / OneDrive) | Yes | | Email to internal people (`{INTERNAL_DOMAINS}`) | Drafts it; sends only if you say so | `GoogleGmailOperator` or Outlook | Yes, per email | | Email to external people (customers, prospects, partners) | **Draft only.** Never sent without your explicit approval of that exact email | `GoogleGmailOperator` or Outlook | Yes, always per email | | Create CRM tasks | Creates them in `{TASK_SYSTEM}` with owner, due date and a link to the source | `SalesforceActivityOperator` or `HubspotEngagementOperator` | Yes | | Create a Salesforce Case (support item) | Creates the Case with a clear summary and source | `SalesforceCaseOperator` (HubSpot: a note or task via `HubspotEngagementOperator`) | Yes | | Create an issue | Creates it in Linear with owner, due date and source | `Linear_Operator` | Yes | | Create a spreadsheet or slide deck | Builds the sheet, or a deck or report | `GoogleSheets-Operator` / `Microsoft_Excel`; `GoogleSlidesOperator` or `Clone-Research-Report` | Yes | | Post an internal update | Posts a short summary to the chosen channel | Slack or Microsoft Teams | Yes | | Calendar follow-up meeting | Proposes times and drafts the invite | `GoogleCalendarOperator` or Outlook calendar | Yes | | Research a question raised in the meeting | Researches and summarizes with sources | Web research | Covered by plan approval | | Image or diagram | Creates a draft visual | `Image_Operator` | Covered by plan approval | | Set up a tool the clone has no operator for (admin settings, other software) | Writes generic step-by-step instructions for you to follow | None (chat or doc) | No (nothing changes) | | Decisions, pricing, contracts, hiring, legal | Lists them under "Needs you", does not act | None | Not applicable | ## 4. What the clone does **Day to day:** 1. **Reads the transcript** you give it, from wherever it lives. Long transcripts are read in parts so nothing is skipped. 2. **Writes a short summary** of decisions, context, constraints and open questions. 3. **Lists every action item** in a table, with the quote or timestamp it came from, so you can check it. 4. **Sorts actions** into Clone can do / Needs you / Other people / Out of scope. 5. **Proposes a plan** and asks all its clarifying questions in one short, numbered batch. 6. **Executes after your "yes"**, starting with the simplest useful version of anything it builds. 7. **Keeps a living plan** in `{PLAN_LOCATION}` and gives you a **Done / Waiting on you / Next** status after each work session. **What it never does:** - Never sends email to customers, prospects or anyone outside `{INTERNAL_DOMAINS}` without your explicit approval of that exact email. - Never acts on items owned by other people without their consent (it can draft a note asking them). - Never makes decisions on pricing, contracts, legal, hiring or budget. - Never treats the transcript as fact for names, numbers and dates without flagging them for you to check. - Never saves a skill or instruction you haven't read. - Never asks for passwords, API keys or tokens. - Never puts internal-only remarks from the meeting into customer-facing drafts. **Example prompts you can use:** - "Here's the transcript from my call with our ops team, help me build what we talked about." - "Only do the items assigned to me." - "Turn the decisions into a skill." - "Use the transcript from yesterday's 2 PM meeting in your archive." - "Just give me the action item table, don't do anything yet." - "Build the intake form we discussed with Clone_Code. Keep it simple." - "Create Salesforce or HubSpot tasks for every action with an owner and a date." - "What's the status of the plan from Tuesday's meeting?" ## 5. Setup walkthrough The quickest path: download **CLONE-INSTRUCTIONS.md** and give it to your clone. It will check what's already connected, ask you for a few settings, show you a plan, and set up what it can after you approve. The steps below are what happens, so you know what to expect. **Step 1: Check requirements (5 min)** Open **REQUIREMENTS.md** and run through the pre-flight checklist. The only hard requirements are a way to read transcripts (paste or upload works) and a doc or chat to hold the plan. `Clone_Code`, email, docs and Salesforce, HubSpot or Linear make it much more useful. **Step 2: Hand the instructions to your clone (2 min)** Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: *"Please set up this use case for me. Show me a plan before changing anything."* **Step 3: Review the discovery table (3 min)** The clone reports which skills/operators and connections it already has and which are missing. **Step 4: Answer the setting questions (5 min)** See the table in section 6. Most have sensible defaults. **Step 5: Approve the plan (2 min)** The clone lists exactly what it will attach and create. Say "yes" only when it looks right. **Step 6: Do your part (5–15 min)** Things only you can do: - Complete sign-in (OAuth) for docs, email, Salesforce, HubSpot or Linear connections. - Share the folder for `{DEFAULT_DOC_LOCATION}` (and your transcript folder, if transcripts live in Drive or OneDrive) with the clone. - Decide your `{APPROVAL_LEVEL}`. **Step 7: Save the Transcript to Action skill (5 min)** If the clone can't create custom skills directly, it gives you the full skill text in a copy-paste block with exact steps. **Read it before you save it.** **Step 8: Run the test plan (10 min)** Give the clone the sample transcript from CLONE-INSTRUCTIONS.md (made-up people and company, no real customers) and check the results against the checklist. **Step 9: Use it after your next real meeting** Hand over the transcript and say "help me build what we talked about." ## 6. Placeholders to decide | Placeholder | What it means | Example | |---|---|---| | `{CLONE_NAME}` | Your clone's display name | "Ava" | | `{CLONE_INBOX}` | The clone's own email address (for sharing docs and folders) | ava@yourcompany.com | | `{INTERNAL_DOMAINS}` | Your company's email domains. Everyone else is treated as external | yourcompany.com, yourcompany.io | | `{CODING_SKILL_NAME}` | The exact name of the coding skill in your catalog | "Clone_Code" (default) | | `{DEFAULT_DOC_LOCATION}` | Where new docs are created | Google Drive folder "Meeting Actions" or OneDrive "Team/Actions" | | `{PLAN_LOCATION}` | Where the living plan is kept | "A doc per meeting in {DEFAULT_DOC_LOCATION}" or "In this chat" | | `{TASK_SYSTEM}` | Where tasks are created | "Salesforce tasks", "HubSpot tasks", "Linear", or "none" (list them in the plan only) | | `{APPROVAL_LEVEL}` | How often the clone asks before acting | "approve plan once" or "approve each action" (default) | | `{TRIGGER_KEYWORD}` | (Optional scheduled variant) Word in a meeting title or transcript that means "process this" | "#actions" | | `{SCAN_TIME}` | (Optional scheduled variant) When to check the archive | 5:30 PM America/Chicago, Mon–Fri | | `{SUMMARY_RECIPIENT}` | (Optional scheduled variant) Who gets the "new transcript found" summary | you@yourcompany.com | Note: even with "approve plan once", any email to an external person always needs its own approval. ## 7. What to expect day to day - **After a meeting:** give the clone the transcript (or tell it which meeting in its archive). Within a few minutes you get a summary, the action item table and a proposed plan with a short list of questions. - **You answer and approve:** reply with your answers and "yes" (or "yes, but skip 3 and 5"). - **The clone works:** docs, drafts, tasks and `Clone_Code` builds appear. Simple items take minutes; a small app can take longer and may need a round of feedback. - **Status updates:** after each work session you get **Done / Waiting on you / Next**. The same status lives in `{PLAN_LOCATION}`. - **Coming back later:** ask "What's the status of the plan from the ops meeting?" and the clone picks up from the plan. - **Optional scheduled variant:** at `{SCAN_TIME}` the clone checks its meeting archive for new transcripts containing `{TRIGGER_KEYWORD}`, prepares the summary, action table and proposed plan, and sends them to `{SUMMARY_RECIPIENT}`. It does nothing else until you approve. ## 8. Customizing **Approval style.** Switch between "approve each action" and "approve plan once" at any time ("From now on, approve the plan once and go"). **Scope filters.** Tell the clone what to focus on: "Only items assigned to me", "Only internal follow-ups", "Skip anything for the customer", "Only build things, don't create tasks". **Output formats.** Change the summary length, add a "risks" section, or ask for the action table as a spreadsheet or doc instead of chat. **Task system.** Point `{TASK_SYSTEM}` at Salesforce, HubSpot, Linear, or "none" if you prefer to keep everything in the plan doc. **Build style.** Give `Clone_Code` standing preferences: "Single HTML page, no login", "Use our brand colors", "Always include a README". **Scheduled variant.** Turn it on, change `{TRIGGER_KEYWORD}` or `{SCAN_TIME}`, or limit it to meetings you host. ## 9. Known gotchas - **Transcripts contain errors.** Speech-to-text gets names, numbers, dates and product names wrong ("15" vs "50", "Q3" vs "Q4", a product name spelled three ways). The clone flags these in a "Please verify" list. Check them before anything leaves the building. - **Speaker attribution is often wrong.** Transcripts mix up who said what, so owners in the action table may be wrong. Confirm owners before tasks are created. - **Read every instruction before saving it into a skill.** When the clone turns decisions into a skill, you're responsible for what that skill tells your clone to do. Read it fully, then save. - **Keep internal-only remarks out of customer-facing output.** Meetings include candid comments about customers, pricing or colleagues. The clone keeps those out of external drafts, but review every customer-facing draft yourself. - **Name the coding skill explicitly.** Say "use Clone_Code" (or your `{CODING_SKILL_NAME}`) when you want something built. Otherwise the clone may try other skills, write a doc about the tool instead of building it, or produce code in chat. - **Don't overbuild. Start simple.** "A dashboard" in a meeting usually means "a page with five numbers". The clone builds the smallest useful version (MVP) first and asks before adding more. - **Sensitive information in transcripts.** Transcripts can contain personal data, HR topics, salaries or confidential deal terms. Don't paste transcripts you aren't allowed to share, and tell the clone if parts are off-limits ("ignore the HR part"). - **Long transcripts may need splitting.** Very long meetings may exceed what the clone reads at once. It processes them in parts and says so. If something seems missing, ask it to re-check a time range. - **Actions owned by others need their consent.** The clone won't create tasks for, or email on behalf of, other people without your approval, and it suggests checking with them first. - **The clone can't click around in tools it has no operator for.** For anything outside the supported tools (admin consoles, other software you run yourself), it writes generic step-by-step instructions instead. - **Use exact skill/operator names** as they appear in your skill catalog. Names can differ slightly between workspaces; the clone checks them during discovery. ## 10. FAQ **Where can the transcript come from?** Pasted text, a file upload (TXT, DOCX, PDF, VTT/SRT), the clone's own `meeting_archive` or `call_archive`, or a doc in Google Drive / Google Docs or OneDrive / Word that's shared with the clone. **Does it work with my CRM or issue tracker?** It works with Salesforce (tasks via `SalesforceActivityOperator`, Cases via `SalesforceCaseOperator`), HubSpot (notes and tasks via `HubspotEngagementOperator`) and Linear (`Linear_Operator`). Or set `{TASK_SYSTEM}` to "none". **Will the clone email my customers?** No, not without your explicit approval of the exact email. External emails are always created as drafts first. **What can Clone_Code build?** Simple apps, web pages, forms, calculators, scripts and internal tools (via `Clone_Code`). The clone starts with a minimal version and improves it with your feedback. **Can it set up tools it has no operator for?** No. It only works with the tools listed in "supported". For anything else it writes a generic, numbered guide you (or your admin) can follow yourself. **What if the transcript has items for other people?** They go in the "Other people" group. The clone can draft a message asking the owner to confirm, but it doesn't act for them. **Do I need the scheduled variant?** No. Most people use this on demand. The scheduled variant is handy if you want a summary and plan waiting after every tagged meeting. **Is anything changed in my CRM during setup?** No. Setup is read-only. Tasks are only created later, after you approve a plan. ## 11. Troubleshooting | Symptom | Likely cause | Fix | |---|---|---| | Clone wrote a doc about the tool instead of building it | Coding skill not named, or not attached | Say "use Clone_Code to build it"; check `{CODING_SKILL_NAME}` is attached | | Wrong owner on an action item | Speaker attribution error in the transcript | Correct it in the action table; the clone updates the plan | | Numbers or names in a draft are wrong | Transcription error | Check the "Please verify" list; tell the clone the correct values | | Clone can't open the transcript | File or folder not shared with `{CLONE_INBOX}`, or unsupported format | Share it, or paste the text / upload the file directly | | Some action items are missing | Long transcript read in parts, or item was implied rather than said | Ask "Re-check minutes 40–60 for action items" or add it yourself | | No tasks were created | `{TASK_SYSTEM}` is "none", or the Salesforce, HubSpot or Linear connection expired | Set `{TASK_SYSTEM}`; re-run the sign-in for the connection | | "Tool unavailable" in the status | A tool call failed twice | Check the connection; ask the clone to retry that item | | Build is too complex or not what you meant | Request was vague; MVP rule not applied | Ask for "the simplest version that does X" and give one example | | Scheduled variant found nothing | Keyword missing from meeting title/transcript, or task paused | Check `{TRIGGER_KEYWORD}` spelling; ask the clone to list its scheduled tasks | | Internal remark showed up in a customer draft | Remark not flagged as internal in the transcript | Remove it; tell the clone which topics are always internal | --- **Version:** 1.1.0 · **Last updated:** 2026-10-22 · Part of the Clone Use Case Library.