GoSeedly Communications Church CRM 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 requests, the channels record, the form inbox, households, the church lists, linked contacts and setup. The shared church lists fit one to three weekly services; a church with four or more should keep its roster and headcounts elsewhere for now. They preserve native account permissions, unrelated custom fields and row history, keep requests, channels, households, people and money apart, refuse image and video file names, links to shared photo albums, folders, file transfers and video pages, stream keys, door and alarm codes, children's ages and names lists, allergy and custody notes, health details, logins, card and bank numbers and Social Security numbers as a guard against accidental entry rather than a guarantee, refuse photos or video of children from a household without a recorded yes while the request still runs, refuse dates still ahead for things that already happened, and check revisions before saving. Deploy them from the authoritative backend source before you build and deploy the web app. To update, remove the earlier release and install this one in the Seedly working tree with no deploy or build between the two, then deploy the backend, then build and deploy the web app: every helper an earlier release's page calls keeps its arguments and answers, so the page in use keeps working until the new one ships. Pipelines, drafts, forms, documents and the campaign draft are optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.
Starter setup offers Guest follow-up, Serving teams, Group leaders, Care requests, Communication requests. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.
All 15 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. The message drafts’ text and email steps ship switched off and send only after your office turns them on.
Explore Ninebark Community Church, a fictional church with six channels and 17 requests from its ministries: a fall sermon series, a newcomer lunch, a kids club, a youth retreat, a grief support group and more, with a stage announcement over capacity on Sunday, a women's retreat request waiting eight days, a due date passed without being scheduled, a request whose board is a stage behind and a youth retreat slideshow flagged red because a family in it now says no, plus six weeks of sermon media with clips still to post, two form submissions waiting to be recorded, and 14 households with children recorded as a first name and an age band, first-time guests, groups, a two-service roster, events, care requests and 41 recorded gifts. 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-church-communications/config.ts to set business name, descriptor, default pipeline name and message mode, 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.
Each request is an opportunity in Communication requests, linked to the requester's contact, holding the title, kind, ministry and requester, the first service day it runs and for how many weeks, the materials due date, the channels asked for and the channels approved, whether it needs a graphic, video or copy, the event it promotes, whether its photos or video show children and from which households, or that the ministry is not sure yet, the status and the dates it came in and was decided, and the form submission it was recorded from. Channels and the weekly sermon media live in their own account record. Households keep the shared church record: adults linked to Seedly contacts, children as a first name and an age band only, a photo and video answer for the children as yes or no with the date the office recorded it and who recorded it, groups and teams, attendance, sign-ups, gifts as recorded by fund and care requests as category labels.
Tidings records what the office decided. It creates each request's opportunity at the stage that matches its status and never moves it afterward; the office drags it in Seedly. A stage draft runs only when a request is dragged into its stage on the Seedly board, not when Tidings records a request at a later stage, and the Requests view marks a board that is behind. A request counts against a channel only once the office approves that channel. While any of its run dates is today or ahead, a request using photos or video of children is refused, and flagged red as Children shown without a current yes, unless every household named has a yes recorded; a ministry's "Not sure" stays not sure until the office answers. Tidings reads every open request and every open household with its own queries, past Seedly's 1,000-opportunity board limit; the card inbox, prayer topics, the form inbox and the consent counts read within Convex's per-query limit on any size of pipeline and say how far they got, even when someone sends very large form answers; and today, the sample's day and every card, prayer and form request day follow the church time zone. Names lists after a child or youth word ("Kids pictured: Leo, Ava and Sam", "Youth: Leo, Ava, Sam") are refused in every field, and so is a names list after a photo or video word with a child word after it ("Photos of Leo, Ava and Sam from kids camp"), while ordinary list-shaped requests such as "Video of baptisms, Easter and VBS" pass. It never publishes, posts or sends anything and never creates a social post. Tidings has no field for an image, video, file or link. The guard refuses image and video file names, inline images and links to shared photo albums, folders, file transfers and video pages; a link to any other page passes. It claims no rights, licensing or consent beyond the answer the office recorded and makes no reach or engagement claim. The Weekly church email campaign draft stays a draft until the office sends it from Seedly: read and edit it first, and when it is sent, Seedly skips anyone who opted out of email or of the list and adds its own unsubscribe link. The three message drafts hold real texts and emails with every send step off, each text behind recorded text consent and each email behind not opted out, every text ending "Reply STOP to opt out.", each draft holding the send window it was added with in the church time zone, and a paused consent check ends the run. A matching Seedly church website template is available separately.
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 Communications Church CRM 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.