GoSeedly Family Entertainment Center Kit / INSTALLATION
Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.
Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.
Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.
Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.
Frontend installation and optional account content are separate. The included original backend helpers are required for connected booking creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse a guest of honor's full name, children's details, access codes, logins, card, game card, bank, passport, license and ID numbers in recorded text and in booking, contact, group and host labels, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.
Starter setup offers Birthday parties, Group events, Company and private events, Schools, camps and churches outreach. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.
All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.
Explore 22 fictional bookings dated around today: 15 birthday parties and 7 group events from a parks and rec kids club, a middle school, a camp, a church youth group, a company, a scout troop and a youth soccer team. Eight bookings fill today's party grid across two party rooms, the arena, laser tag and the pavilion, with a double-booked party room, a short waiver count and two bookings without a host flagged in red. Sample edits stay in memory and reset on navigation or reload. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.
MORE OF THE WORKING DAY
Editable native forms and document templates give your team a practical starting point.
Choose forms individually in Setup & resources, then customize and publish them in the native form builder.
Open each template in Documents and complete it for the actual job or visit.
Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.
Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.
INSTALLING WITH AN AI AGENT?
Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.
Edit apps/web/components/devlaunch-family-entertainment-center/config.ts to set venue name, descriptor, default pipeline name, the rooms and areas on the party grid (with open play marked shared), the grid's opening and closing time and slot length, how many days ahead a booking without a host is flagged, and the packages, add-on items and party hosts offered in the booking editor, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.
Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.
Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.
For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.
One contact-linked booking holds the parent or organizer contact, whether it is a birthday party or a group event, the guest of honor as a first name with an age band or the group's name and type, how they heard about the venue, the inquiry and party dates, the status from inquiry to party held, the package and its price as recorded, the deposit as recorded, the head count and adults, the waivers recorded as a count and the party host, plus each room or area slot with its start and end time, add-ons as counts and an editable checklist.
Popslot records what the party desk typed. It makes no safety, insurance, health, capacity or waiver statement: waivers are a count, never collected, read or judged. It does not take payments or deposits, sell tickets or wristbands, run an online booking widget, schedule staff or send messages. Party guests are often children, so a guard against accidental entry refuses the common ways their details get typed: a guest of honor's full name, birth dates, an age tied to a name, lists of children's names, allergies, medical, injury, diet, custody and behavior details, while ordinary party wording such as "7th birthday party" and "turning 6 to 8" stays. It also refuses door, locker and alarm codes, party and play pass codes, passwords and logins, card, game card, bank, routing, Social Security, passport and driver license numbers, in recorded text and in the native form drafts. Form answers are capped at 250 characters, names at 80, and phone answers take a phone number only. It is a guard, not a guarantee. The search box and the alert filter narrow the lists, never the day's counts, and an open tab moves to the new day at midnight.
The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.
See the interface and everything included.
Back to GoSeedly Family Entertainment Center KitWe use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.
Read our Cookie Policy and Privacy Policy.