GoSeedly Cabinet & Millwork Shop 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 record creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, check revisions before saving, and enforce the drawing gate and every cross-field rule on the server. 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 Cabinet and millwork jobs, Commercial millwork, Built-ins and casework, Builder accounts. 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 nine fictional cabinet and millwork jobs carrying thirty-one traveler tickets across all six stations, three rows held by the drawing gate, one of them waiting on an approval for a newer revision letter, four tickets past their recorded due date, seven hardware or finish lines not received and five open punch items. 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-cabinet-millwork/config.ts to set business name, descriptor and default pipeline name, 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 job holds the site label, the designer or builder, the drawing revision letter, the sent and approval dates, the revision letter the approval was recorded for, the install date and crew label, plus traveler tickets, hardware and finish lines, punch items and an editable checklist.
The drawing gate is enforced in the shared record model, so the included backend helper refuses a ticket past cut while the drawings are not approved. An approval belongs to the revision letter it was recorded for, so changing the letter closes the gate until an approval is recorded for the new one, and a job with tickets past cut cannot change its revision letter without either recording that approval or returning the tickets to cut. Approval is a fact a staff member records with a date and a revision letter; the kit collects no signature. It does not produce CAD, CNC output or cut lists, does not nest or optimize material, holds no inventory, places no supplier orders, and is not a scheduling engine, a payment system or a messaging tool.
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 Cabinet & Millwork Shop 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.