Triggers — what can start a workflow

Every workflow starts with exactly one trigger. The list below is what Carerealm currently emits — only triggers from this list will actually fire a workflow.

Diary

• diary.entry_created — a new diary entry was added.

• diary.entry_updated — a diary entry was revised.

• diary.entry_locked — a diary entry was locked.

• diary.no_entry_for_days — N days have passed with no diary entry in an area.

Forms

• forms.entry_submitted — a form was completed.

• forms.entry_locked / forms.entry_commented — moderator actions.

• forms.no_submission_for_days — N days without a submission of a specific template.

• forms.queue_overdue — a queued form passed its deadline.

eMAR

• emar.dose_recorded — a positive administration was recorded.

• emar.dose_missed — buffer expired and the dose flipped to Missed.

• emar.dose_refused — outcome 3 recorded.

• emar.controlled_drug_administered — a CD-flagged medication was given.

• emar.incident_reported — a medication incident was logged.

About + Policies

• about.section_created, about.section_updated, about.section_read, about.section_read_completed

• about.section_unread_for_days — a user hasn't marked the latest revision read after N days.

• about.revision_stale_for_days — the latest revision is older than N days.

• Mirror set for policy.*: created, updated, read, read_completed, unread_for_days, revision_stale_for_days.

Admin & users

• admin.user_signed_in / admin.user_signed_out / admin.user_invited.

• area.archived, area.access_granted, area.access_revoked.

Files & webhook

• files.uploaded — a file was uploaded.

• webhook.received — receive an arbitrary HTTP POST at /api/workflows/webhook/<slug> (rate-limited 60/min) and fire the workflow.

Heads up — files.shared appears in the registry but has no emitter today — it won't fire any workflow yet. Don't build against it.