Workflow Automation

Bahá'í Feast Announcement Workflow

The Bahá'í Feast Announcement workflow automates the full announcement cycle for each of the 19 Bahá'í months and all upcoming Holy Days and significant dates. It works for communities of any size — from a single gathering place to multiple areas each with their own coordinator — and handles community-wide occasions and per-area collection in the same workflow. Once configured and activated, it runs without any manual steps.

Community size and structure

The workflow adapts to how your community is organized:

  • Single gathering — configure one area with one coordinator, or use the community-wide setting so no collection is needed at all and the announcement goes out with a fixed location every month.
  • Multiple areas — each area has its own primary (and optional secondary) coordinator. Request, reminder, and escalation emails go to each area independently.
  • Mixed — some months or Holy Days can be community-wide while others are per-area. Riḍván Day 1 at the Bahá'í Center, Days 9 and 12 per-area — all handled in the same workflow.
You can change how any month or Holy Day is handled at any time from the workflow edit page, before the coordinator requests go out.

How the cycle works

Each Bahá'í month is one cycle. The workflow announces the upcoming feast during the current month — so while the community is in the month of Núr, the workflow is collecting information and sending announcements for the feast of Raḥmat.

The engine computes all trigger dates automatically based on the Bahá'í calendar and your timing settings. A typical cycle looks like this:

  • Day 7 of the current month — information request emails sent to each area coordinator
  • Day 9 — reminder sent to coordinators who have not yet responded
  • Day 11 — admin escalation if any areas are still missing
  • 7 days before cycle end — community announcement sent to distribution list
  • 3 days before cycle end — community reminder sent
Exact dates depend on your timing settings. The defaults above reflect a standard configuration with a 2-day reminder window and 2-day escalation window.

Area coordinators

Each area has a primary contact and optionally a secondary. When the workflow fires, each coordinator receives a personalized email with a secure link to submit their area's hosting details — date, time, host name, location, and notes. No login is required; the link is unique to each coordinator and expires automatically.

If a coordinator does not respond before the reminder date, they receive an automatic follow-up. If they still do not respond, the admin receives an escalation alert with a link to enter the information manually.

Volunteer host integration

If a community member has signed up as a volunteer host for a given area and feast month, the workflow detects this automatically. Instead of sending an information request to the area coordinator, it uses the volunteer's details directly and notifies the coordinator that a volunteer has been confirmed. No action is needed from the coordinator.

The admin status report will show a Volunteer hosts section listing any areas filled by volunteers, along with the host name, date, and a confirmation that the coordinator was notified.

Admin status emails

The admin receives three routine digest emails per cycle, plus a delay notice if any area is still missing when the announcement is due:

  • Status report — sent when coordinator request emails go out, listing all areas, contacts, any volunteer-filled areas, and the upcoming schedule
  • Heads up — sent just before reminder emails fire, showing which areas have responded and which are still pending
  • Reminders sent — sent after reminder emails go out, confirming which areas were reminded and when escalation will occur
  • Delay notice — sent only if the announcement must be postponed because one or more areas are still missing, listing those areas and the new send date

Manual override

At any point during a cycle, the admin can enter hosting information manually for any area from the run detail page. Click the pencil icon on any pending, waiting, or escalated collect step to open the override form.

Scheduling mode

When a new cycle starts with limited time before the feast, the engine automatically adjusts the schedule:

  • Normal — full timing as configured
  • Compressed — shortened windows when 4–9 days remain before the feast
  • Tight — initial request only, no reminder, escalation the next day, when fewer than 4 days remain

When information is missing

If any area has not submitted its details by the announcement date, the workflow delays rather than sending an incomplete announcement:

  • The announcement is pushed back by 2 days
  • The admin receives a delay notice listing the missing areas and the new send date
  • Each missing coordinator receives an urgent request with the deadline

This delay happens once per cycle. On the new date the announcement goes out with whatever has been collected — areas that never responded are simply omitted from the email. A single unresponsive coordinator never blocks the announcement indefinitely.

If no area has submitted anything and no community-wide feast is scheduled for the cycle, the announcement is not sent at all. An empty announcement is never mailed to your community. The workflow re-checks daily, so it will go out as soon as any area submits or you enter details manually. If the cycle ends with nothing collected, the run is marked cancelled with a note explaining why.

The community reminder always goes out at least 2 days after the announcement actually sent — so if the announcement was delayed, the reminder shifts with it rather than arriving on its heels.

Holy Days and significant dates

In addition to the 19 Bahá'í months, the workflow automatically creates a run for each upcoming Bahá'í Holy Day and significant date within a 30-day window. This includes the 9 Holy Days (on which work is suspended) as well as the Day of the Covenant and the Ascension of 'Abdu'l-Bahá.

By default, each Holy Day is handled per-area — the same pipeline as the Nineteen Day Feast. Each area coordinator is asked to submit gathering details, and the community announcement is sent 7 days before the occasion with a reminder 3 days before. The admin receives a one-time notice when a new Holy Day run is created, explaining this default and how to change it.

The email content is occasion-aware. Celebrations, Commemorations, and Observances each use appropriate wording — no Feast language appears in Holy Day emails.

Holy Day runs use a backward-planned schedule: coordinator requests go out 13 days before the occasion, escalation at day −9, announcement at day −7, and reminder at day −3. Even in the worst-case delay scenario, the announcement always reaches the community at least 2 days before the occasion.

Holy Day overrides

If your community observes a particular Holy Day differently from the per-area default, you can configure an override from the workflow's edit page under Holy Day Overrides. Three modes are available for each upcoming occasion:

  • Per-area (default) — each area is asked for its own gathering details, same as the Feast pipeline
  • Community-wide — all areas gather at one location; provide the location name, address, time, and optional notes. No coordinator requests are sent; the announcement goes directly to the community with the single location.
  • Skip — no emails are sent for this occasion and the run is immediately marked complete

Overrides apply to the specific occurrence being configured. Each year's occasions can be set independently as they approach.

Community feast

If a community-wide feast has been scheduled for a given Feast cycle, all collect steps are automatically skipped and the announcement is sent using the community feast details. No coordinator requests go out for that cycle. Community-wide Feast months are configured from the Community-Wide Feasts section of the workflow edit page.

Last updated: July 26, 2026