Every announcement on the right channel, in the right week.

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

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.

Five optional pipeline templates and 15 inactive workflow drafts. 17 fictional in-memory requests.

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.