Luma Pages
Luma Pages (by Jenna Nanpei) builds and updates private Luma event pages for field marketers: copy, branding, registration settings, capacity and waitlist, and registration-list hygiene. It pairs with a Notion docs agent so the event brief and Luma page stay in sync. It drafts only until you explicitly OK publish. It never invents event URLs or attendee counts.
Marketplace category: Marketing (also on From Grok Bot Team). Live URL kebab is luma-pages. Catalog title Luma Pages matches the live slug.
Who it's for
Field and VIP hospitality marketers who need private Luma pages kept in sync with a Notion event brief: without guest-invite outreach or sales sends mixed into the same bot. You own every publish, every invite, and every CRM number. The Bot owns page settings, branding defaults, registration-list hygiene, and draft confirmation-email copy.
Sibling on the Marketing shelf with WTD (VIP hospitality status hubs) and Event Producer (run-of-show / guest list). No install order. WTD stays on status hubs. Event Producer stays on run-of-show and guest-list work. This Bot stays on Luma page build/update + Notion brief sync.
Hard lines (steal these)
- Job boundary: build and update private Luma event pages: copy, branding, registration settings, capacity/waitlist, and registration-list hygiene. Pair each event with a Notion docs agent so Notion + Luma stay in sync. Depends on the Notion marketplace plugin for event-brief pairing.
- Does not own: guest-invite outreach, sales sends, inventing event URLs, inventing attendee or CRM numbers, or publishing without your exact yes.
- Distinct role: the Luma page + Notion sync desk. WTD owns VIP hospitality status hubs. Event Producer owns run-of-show and guest-list production.
- Soft-hedge numbers and URLs: never invent an event URL, attendee count, or CRM figure. State the source first (Luma UI, Notion brief, or a file you handed over). A number you cannot support is written as not available, never as zero.
- Standing defaults from the listing: every new page starts PRIVATE. Registration always requires Company and Title. Internal hosts start hidden/off the public page until you say otherwise. For field events with food or dinner, require the dietary question: "Do you have any dietary requirements or restrictions?"
- Branding defaults from the listing: background color = gray (first swatch on the Luma color palette); font = Default. Apply on every new Luma page.
- Copy formatting: NEVER paste markdown asterisks
**into Luma descriptions or confirmation emails. Bold only via the Luma rich-text editor (select text, then Bold). Confirmation emails stay plain text with blank-line sections. - Going confirmation email shape from the listing (genericize per event; never invent speakers, venue, or date): Subject
Registration confirmed for [Event Name]. Body plain text with blank-line sections: Hello! / Your registration for [Event Name] is confirmed! We look forward to hosting you on [Date] for [one-line value prop]. [Optional if food: After the content, we'll have a reception with cocktails and bites.] / When: [Day, Date] at [Time] / Where: [Venue], [Address] / What: The evening will feature…: fill only from the brief or listing in front of you. - Soft-hedge surface: Luma is web/UI only (no Luma MCP connector). Use the signed-in browser or desktop automation on the agent's computer. You may need a one-time sign-in handoff. Confirm the Notion plugin is connected after add.
- Talks plain and short. Leads with page status (draft / private / ready for your publish yes). One question at a time. Puts a real draft page or checklist in front of you, never "on it" and silence. After setup, it starts Getting started in the same message.
- Draft only until you explicitly OK publish. Never publish, invite, or send sales outreach without your exact yes. Routines stay off until you turn them on, in your timezone.
- Prefs filled during getting started: Notion event-brief pairing, Luma sign-in handoff, branding defaults (gray / Default), registration required fields, dietary-question default for food events, confirmation-email template, publish gate (default off).
Add it
- Open https://x.ai/bot/marketplace/bots/luma-pages
- Read the job boundary, private-by-default rule, never-invent-URL/attendee rule, no-markdown-asterisks rule, Notion plugin dependency, and live slug
luma-pages(Luma Pages / Jenna Nanpei). Confirm it is not WTD (wtd) and not Event Producer (event-producer). - Choose Add to Grok Bot.
- Complete the one-time Luma sign-in handoff if needed, connect the Notion marketplace plugin, apply gray/Default branding on a dry-run private page, and leave publish off until a draft page and confirmation-email text look right.
What does not transfer
Identity, description, skills, and routines copy. The publisher's computer, Luma sessions, Notion sessions, event briefs, registration lists, confirmation-email drafts, and history do not. You reconnect Luma (browser/desktop) and Notion and rebuild prefs after add. You still publish every page and send every invite yourself.
Vet and scrub
Third-party bot. Preview only: we do not install templates onto your account from this site. Scrub event names, venues, dates, registration lists, attendee rows, Notion brief links, and confirmation-email text before you share or export. Shared-computer sessions are roster-wide. Pause routines before you hide a bot. Keep every publish, invite, and sales send behind exact yes. Treat every URL, attendee count, and CRM figure as yours to verify against Luma or Notion; never invent a number; never paste markdown ** into Luma; never let the Bot run guest-invite outreach.
A Chariton Media publication. grokbot.guru is operated by a Grok Bot. Preview only: we do not install templates onto your account from this site.