Workflow · Productivity
Overdue alerts
A daily check over any table with a due date and a status: tasks, jobs, invoices, orders. A row whose due date has passed and isn't done gets an overdue_since stamp, the assigned person gets a notification (when you name an assignee field), and the role you choose gets one notification listing everything overdue. Marking a row done clears the stamp.
use_template { slug: "overdue-alerts" } adds
- Fields
- ‹entity›.overdue_since
- Workflows
- overdue-check, overdue-clear
What it adds to your app
Field overdue_since on your table. A daily 09:00 check that stamps and announces overdue rows. A workflow that clears the stamp when a row is done.
Fields added to your tables
‹entity›.overdue_since
Workflows
overdue-checkFlag and announce overdue ‹entity› rows. On schedule daily 09:00 over ‹entity›overdue-clearClear the overdue flag when a ‹entity› is done. On ‹entity› updated
Where it attaches
Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.
| Param | What it is | Example |
|---|---|---|
entity | The table of things that can be late (tasks, jobs, invoices). Optional. | task |
due_field | The date or timestamp field holding when it is due. Optional. | due_on |
status_field | The enum field that says whether it is finished. Optional. | status |
done_value | The status value that means finished (never overdue). Optional. | done |
assignee_ref | Optional: the ref field naming the person responsible, so they are told directly. Leave it out to tell only the team. Optional. | assignee_id |
notify_role | The role that gets the daily list of overdue rows. Optional. | staff |
Use with your coding agent
- Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
- Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
- It applies to dev. Check it, then deploy when you are happy.
Add the Overdue alerts template (slug "overdue-alerts") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (entity: table with due dates; due_field: due date field; status_field: status field; done_value: done value; assignee_ref: assigned person; notify_role: team to tell).{
"tool": "use_template",
"arguments": {
"slug": "overdue-alerts",
"project_id": "<your project id>",
"params": {
"entity": "task",
"due_field": "due_on",
"status_field": "status",
"done_value": "done",
"assignee_ref": "assignee_id",
"notify_role": "staff"
},
"dry_run": true
}
}appbricx templates use overdue-alerts --param entity=task --param due_field=due_on --param status_field=status --param done_value=done --param assignee_ref=assignee_id --param notify_role=staff --dry-runGoes well with
Kanbo
App. Team project board with drag-and-drop cards, checklists, comments and my work.
managermemberprojectcardchecklist_itemWelcome email
Workflow. Emails every new person a short, friendly welcome the moment they sign up.
welcome-emailSlack message on signup
Workflow. Posts to a Slack channel whenever someone new signs up, with their name and email.
slack-on-signup