Skip to content
View packages

GoSeedly Short-Term Rental Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

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.

02

Run guided setup.

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.

03

Build and connect.

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.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. The included original short-term rental helper is required for connected creation, editing and starter setup. It checks the active account and native permissions, re-applies every domain rule, compares both the record timestamp and a server-managed revision, preserves unrelated custom fields and unknown child-row values, and then calls the native Seedly mutations in the same transaction. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers New owner onboarding, Unit turnovers, Guest issues, Owner renewals. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

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 sample mode.

Explore eight fictional units across three owner labels and two cleaner labels, with thirteen recorded stays plus one archived stay, six recorded turns and three recorded guest issues. Example edits stay in the current page memory and reset on navigation or reload; sample units are never inserted into your CRM. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-short-term-rental/config.ts to set company 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.

Starter removal, updates, and rollback

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.

What the workspace records

One unit under management is a native contact-linked opportunity. Its namespace records the address, bedrooms, bathrooms and sleeps, owner and cleaner labels, check-in and check-out times, channel labels, an optional monthly management fee, an optional owner report month, and three collections of child rows with stable IDs: stays, turns and guest issues. Other custom fields are preserved.

The domain rules are enforced on the server, not only in the editor. A stay occupies its check-in date through the night before check-out, and two recorded stays may not share a night on one unit. A turn is recorded on a change-over day and never in the middle of a stay, and two turns may not share a day. An assigned or completed turn needs a recorded cleaner label while an unassigned one records none. A guest issue falls inside a recorded stay, and a stay may only use a channel label its unit records. Night counts, change-over slots and the owner report are derived on every read rather than stored. There is no channel manager or booking platform sync, pricing engine, smart lock integration, guest messaging, payment processing, payouts, accounting, or cleaner scheduling engine. A channel label is a typed word, a recorded cleaner label assigns and notifies nobody, and a recorded payout reference is a number copied from a statement you already received.

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 Short-Term Rental Kit