Every next step, written down and followed up.

Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected household creation and edits, the church lists, the pathway, linked contacts and setup. They preserve native account permissions, unrelated custom fields and row history, keep households, people, seats, positions and money apart, refuse children's ages and names lists, allergy and custody notes, health details, access codes, logins, card and bank numbers and Social Security numbers as a guard against accidental entry rather than a guarantee, refuse dates still ahead for things that already happened, and check revisions before saving. They also read the household pipeline page by page for the workspace (up to 10,100 open households, with a note beyond that), keep every long job within three quarters of Convex's read limit, and work in steps on a large account. To update from an earlier release, run the earlier release's setup remove and then this release's setup install in the Seedly working tree with nothing deployed or built between them, then deploy the backend (eight files), then build and deploy the web app; a page still open on the earlier release keeps working until it reloads, and on a very large account a long job it can no longer finish in one call is refused with nothing written and asks for a reload. Two of that page's calls can also be refused where the earlier release completed: Add as a contact for the household's primary adult while the household's own contact is still in Seedly (link that contact instead), and a save that adds or changes text the newer guard refuses (text already saved is marked and still saves unchanged). If remove refuses because a file carries your edits, keep a copy of your edits, put the file back exactly as the earlier release's installer wrote it (from your own commit made right after installing it, or by installing that release on a fresh copy of the same Seedly version and copying the file from there), remove and install, then re-apply your edits. Deploy them from the authoritative backend source. Pipelines, drafts, forms and documents are optional.

One contact-linked household record holds the household's status, the guest path, an office note, its adults linked to Seedly contacts, its children as a first name and an age band only, the groups and serving teams it joined, recorded attendance, event sign-ups, gifts as recorded by fund, care requests as category labels, a checklist and each adult's pathway steps with the class, date and sessions attended. The church's name, time zone, campuses, services, funds and teams with positions live in a small directory in the account's settings (large team lists move to a stored list of their own), and the lists that grow live on stored lists of their own in your Seedly database, one per roster week, headcount year and event year and one for the groups, so they keep growing without a ceiling. Sized for a church with two campuses and six weekly services: a full roster week of 180 people serving is about 53 KB of a 256 KB list, a year of headcounts at six services about 55 KB and a year of 120 events about 23 KB. Roster rows clear after eight weeks when the roster is saved, a year of events can be cleared once it ended more than a year ago, and household attendance older than three years and gifts older than seven fold into yearly counts, so nothing blocks a new entry. The pathway's steps and classes have their own stored list. Remove all church records in setup deletes the church lists, the stored lists and the pathway, because deleting a Seedly account does not. It leaves only a small marker with no church data, so a page left open from before can never save its old lists or pathway back over what the office enters next.

Waymark records what the office recorded. Saving a household keeps the church tags on its linked contacts and moves the guest follow-up opportunity forward a stage, never back. The three message drafts hold real texts and emails with every send step switched off, every text behind a check that the contact agreed to texts and every email behind one that they did not opt out, every text ending with the opt-out line, each draft added with a 10:00 to 19:30 church-time send window, and a paused check ending the run rather than sending; you add them only after ticking that you record consent, you can add them before your A2P campaign is approved, and nothing sends until your office reads each step and turns it on. Waymark has no child check-in and refuses children's exact ages, birthdays, names lists, allergy and custody notes and a child's baptism or dedication in notes. Care requests are category labels and health details are refused. Giving is only what the office typed in: Waymark never processes, imports or receipts gifts and makes no tax claim. Access codes, Wi-Fi passwords (including one written after the network name) and portal logins, card, bank and routing numbers and Social Security numbers are refused in recorded text, and so are lists of children's names, including after youth words and after a short phrase such as kids pictured or kids on the bus, while church text such as John 3:16, Room 204, Baptism class, a team roster of adults, Bible names in a lesson title and a youth band's instruments listed together is kept. That is a guard against accidental entry, not a guarantee, and the shapes it cannot tell from ordinary text are listed in the README. The public form drafts hold only names, email, phone and fixed choices, with children counted and never named, and the card inbox shows an answer only when it is one of that question's own choices. Today, the day a card or prayer request arrived and a form's upcoming events are read in the church's time zone. Households are read through the kit's own paged query, so the pathway does not stop at 1,000 households, and Giving, Groups and Care counts read every household while the search box narrows only the lists. A contact deleted in Seedly is never offered or newly linked and never gets a tag, and its household still saves; Add as a contact is refused only for the primary adult while the household's own contact is still in Seedly, and the household editor searches every contact by first name, email or company. Setup flags any QR code, value, snippet or draft whose form was deleted, adds and removes in steps on a large account, and shows how much of the account's record the kit uses. Install one church kit per Seedly installation. A matching Seedly church website template is available separately.

Six optional pipeline templates and 16 inactive workflow drafts. 20 fictional in-memory households.

Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.