How to Build a slide deck that build itself from your data

### Using the Agent Native Slides connector This is the prompt and setup from the livestream session. Copy the prompt, point it at your own data, and see what it produces. --- ## What this does You hand Claude one prompt plus the **Agent Native Slides** connector. Claude pulls from the sources you point it at, a CSV of booked meetings, a Slack channel, a Gong account set, a Granola transcript, does the analysis and synthesis, and outputs a finished deck matched to your branding. No template to fill in afterward. The pulling, the synthesis, and the design all happen inside the run. ## Setup ### 1. Add the Agent Native Slides connector 1. Go to the connector directory: [claude.ai/directory/agent-native-slides](http://claude.ai/directory/agent-native-slides) 2. Click Connect and complete the authentication flow. 3. Confirm it's on for your chat — you'll see *Agent Native Slides* in the connectors list. ### 2. Connect the data sources your prompt reaches into The session prompt pulls from four sources. Enable whichever ones your version of the prompt uses: - **Google Drive** — for the CSV of booked meetings (or attach the CSV directly). - **Slack** — for the strategic-account channel and its most recent thread. - **Gong** — for cross-account call signal. Its `ask_account` tool accepts CRM IDs directly. - **Granola** — for the meeting transcript, or paste/attach the transcript in-chat. Each connector is added the same way as above: find it in [claude.ai/directory](http://claude.ai/directory), connect, authenticate. ## The prompt This is the full session prompt, cleaned up for reuse. Paste it into Claude with the Agent Native Slides connector on, attach your reference deck and CSV, and run it. Edit the *bracketed details* to match your own data. ``` Build a leadership update deck as a PowerPoint (.pptx) I can import into Google Slides, matching the branding of the attached reference deck (dark background, cyan/pink/orange accents, same fonts and layout patterns).

Include these sections:

1. NBM MEETINGS BOOKED THIS FISCAL QUARTER (our fiscal quarter starts 8/1). Pull from the attached CSV. Break it out by rep (Activity created by / Owner), showing meeting counts and any notable patterns — meeting type, or a rep's meetings clustering on one account.

2. WEEKLY STRATEGIC ACCOUNT FOCUS. Pull the account list from our Slack channel #strategic-account-focus-group (most recent week's thread). I'll attach the Granola transcript from that session — use it for account status, blockers, next steps, and owners per account. DO NOT NAME CUSTOMERS — this is a live demo.

3. CROSS-CUSTOMER THEMES FROM GONG (the most important section). Don't limit this to the strategic accounts. Pull signal from Gong across as many active accounts as you can reach this week (use company IDs from the meetings CSV as accounts to query — Gong's ask_account tool accepts CRM IDs directly). For each account ask a variant of: "What are the key themes, concerns, or updates from calls in the past week?" Then synthesize into 3-5 CROSS-CUTTING THEMES that show up across multiple unrelated accounts — a shared objection, use case, blocker, or buying signal. Give each theme its own callout with 2-3 supporting examples. Synthesis is the deliverable — don't just list accounts. DO NOT NAME CUSTOMERS.

4. Close with a brief thank-you slide matching the branding.

Rules: - If any Gong query fails or times out, skip it and note it — don't block. - If Slack or Granola content is ambiguous or missing, ask me before guessing. - Validate the final file and visually QA each slide (render to images, check for overflow/misalignment) before sharing. ``` ## Adapting it to your own data ### Swap in your sources - **The CSV.** Point the meetings section at your own export. Tell Claude which columns identify the rep (e.g. "Activity created by" / "Owner") and your fiscal-quarter start date so the counts are scoped correctly. - **The Slack channel.** Replace the channel name with yours and tell Claude to find the most recent week's thread or summary. - **The Gong accounts.** If you don't have account names, hand Claude the company IDs from your CSV — Gong queries by CRM ID. Ask it to reach as many active accounts as it can that week. - **The transcript.** Attach a Granola transcript or paste the notes. If it's missing or ambiguous, the prompt tells Claude to ask before guessing. ### Keep the guardrails - **"Don't name customers."** If the deck is going on screen in a live demo, keep this line in — Claude will anonymize accounts throughout. - **"Skip and note, don't block."** Any single Gong query can time out. This line keeps one failed account from stalling the whole deck. - **"QA each slide."** The prompt asks Claude to render the finished slides to images and check for overflow and misalignment before handing it over. Keep it — it's the difference between a deck you can present and one you have to fix. ## The part that makes it worth it The Gong section isn't an account-by-account readout — it's **synthesis**. One account raising an objection is noise. The same objection showing up across five unrelated accounts is signal. The prompt asks Claude to query each account, then roll the individual findings up into 3–5 cross-cutting themes, each with a couple of supporting examples. That roll-up is the deliverable. When you adapt the prompt, protect that instruction — it's easy to water down into a list, and the list is the least useful version. --- Connector: [claude.ai/directory/agent-native-slides](http://claude.ai/directory/agent-native-slides)