Skip to main content

Build a Choose‑Your‑Own‑Adventure Playlist with your AI assistant (Walnut MCP)

Ask Claude, ChatGPT, Codex, or Copilot Studio to assemble a CYOA Playlist from your library Demos and files, approve the outline, and get an unpublished draft.

Updated Nov 18, 2026

Build a Choose‑Your‑Own‑Adventure Playlist with your AI assistant (Walnut MCP)

Ask your AI assistant for a Playlist in plain words, and it builds a Choose‑Your‑Own‑Adventure (CYOA) Playlist with you in the chat, from Demos and files already in your library. You describe the buyer and how the Playlist will be used, settle a few answers, approve a short outline, and Walnut assembles an unpublished Playlist you can open, review, and share.

This works in any assistant connected to the Walnut MCP: Claude, ChatGPT, Codex, or Microsoft Copilot Studio. Only CYOA Playlists are built this way — Sales Hub and Customer Hub Playlists are built in the Playlist editor, not from the chat.

Before you start​

  • Connect the Walnut MCP with Full access. Building a Playlist writes to your account, so Read-only access isn't enough. See Connect Walnut to Claude, ChatGPT, Codex, or Copilot.
  • Have library content to assemble from. The Playlist is built from the Demos and Resource Hub files you can already see in Walnut. If your library has no match for a section, your assistant will tell you and offer ways to settle it.
  • Optional: a workspace brand theme. If your workspace has brand themes, you can name one — including Prospect branding when you've given a prospect website — and your assistant will set it on the Playlist.

Build a CYOA Playlist​

1. Ask for a Playlist​

Say what you need in your own words. The more you say about the buyer and the use, the fewer questions your assistant asks.

Build a CYOA Playlist for Acme's RevOps team to review after our discovery call.

I need a leave-behind Playlist that covers reporting, integrations, and security for an IT buyer.

2. Answer the setup questions​

Your assistant asks whatever the request didn't already answer. Each question has a few suggested answers you can pick, or you can reply in your own words.

  • How will it be used? Outbound, live call, leave-behind, customer review (QBR), or something else.
  • Who is it for? The audience — a role, a team, or free text.
  • Which company is it for? The prospect's name, and its website when you have it. The company names the Playlist, and the website is used to look up a logo. People's names, emails, and phone numbers are not accepted here.
  • Which theme? A workspace theme by name, or Prospect branding to style the Playlist in the prospect's colours and logo. Prospect branding needs a prospect website.
  • What should it showcase? For a CYOA Playlist, your assistant asks which shape to take:
    • Product introduction — a broad tour of your product.
    • Top capabilities — the capabilities you lead with.
    • Latest features — a recent-release Playlist. Your assistant also asks which features to include.
    • Custom — your own topics, typed as a comma-separated list. Your words are used verbatim as the topic list.
  • Which entry screen? Intent Survey, a welcome page, or none. See Buyer-guided discovery with an Intent Survey.

You can also say up-front that something must be in the Playlist — a specific Demo, a Resource Hub file by name, or a video URL (YouTube, Vimeo, or a Walnut-hosted link). Your assistant pins each one to the outline.

3. Walnut scans your library​

Once the answers are settled, your assistant scans your library and comes back with a coverage report, one row per candidate topic: how many Demos match, how many Resource Hub files match, and whether the topic is well covered, partly covered, or a gap.

Coverage is read-only — nothing is saved yet. Topics with no library match at all are dropped from the outline (unless you listed them yourself under Custom, in which case they stay as gaps for you to settle).

4. Approve the outline​

Your assistant drafts a short outline — one section per topic, in order — plus a page title and subtitle for the Playlist. Each section carries:

  • A name, and a one-line description that appears on the page.
  • The library content picked for it, by name.
  • A warning sign on any section the library can't fill.

Approve the outline, or ask for changes:

  • Reword a section, the title, the subtitle, or a section's line.
  • Reorder, add, remove, or swap a section.
  • Change the theme, the entry screen, or the Showcase. A different Showcase picks the topics again from scratch.
  • Add a must-have — a Demo, file, or video URL to pin in.
  • Change the prospect, its website, or its logo. Sending the logo back approves the one Walnut found; sending a blank value clears it; sending your own https image link overrides it.

Each change produces a new outline revision to approve.

:::info The narrowing question If you ask for a third free-form change on the same outline, your assistant pauses and asks one narrowing question first — whether the problem is the product area, the depth, or the content type — so the next revision lands closer to what you want. :::

5. Settle any gaps​

When the library doesn't hold something a section needs, your assistant offers a few ways to settle it:

  • Closest match — use the nearest thing the library has.
  • Video URL — your own YouTube, Vimeo, or Walnut-hosted video link.
  • File — a Resource Hub file by name, with an optional folder and file kind (image, video, or document).
  • Upload a file — your assistant tells you to upload one to the Resource Hub and come back.
  • Leave out — drop the section from the Playlist.

Settling a gap isn't counted as a round of change, so you can resolve as many gaps as you need without triggering the narrowing question.

6. Build it​

Say the outline looks good. Walnut queues the build and your assistant follows it for you, checking back every few seconds. When it's done you get:

  • The Playlist's name, taken from the prospect when you gave one.
  • An editor link, to open the Playlist in Walnut.
  • Any section the build couldn't finish, and the reason.

The Playlist is built unpublished, so you can open it, tweak anything you want in the editor, and then publish and share it from Walnut when you're ready. If a Demo an approved step depended on was removed between approval and the build, the plan is sent back to the outline so you can swap it; nothing is published silently.

What the Playlist includes​

  • Sections, in the order you approved, each holding the Demos, files, or videos the outline picked.
  • A page title and subtitle your assistant wrote, which you can edit at any step.
  • The entry screen you chose — an Intent Survey, a welcome page, or none.
  • Your theme — a workspace theme or Prospect branding — including the prospect's logo when one was found or supplied.

More prompts to try​

Build a CYOA Playlist for a security-minded IT buyer at Globex — Top capabilities, Prospect branding, with an Intent Survey at the start.

Make it a Latest features Playlist covering the new approvals workflow, SSO, and audit log. Must include the recorded webinar at https://vimeo.com/....

Swap the reporting section for the admin settings one, and drop the integrations section — nothing in the library fits it.

That section about pricing is a gap. Use the "Pricing one-pager" file from the Resource Hub.

For more ideas, see the MCP prompt library.

Was this helpful?