SkillFoxx

Bitrix24 overdue task watcher skill

task-overdue-watcher

A skill and script that check overdue Bitrix24 tasks twice a week, ping assignees and send a summary to the owner

  • 0 ★ on the repository
  • Last commit
Skill

Extended access

Why this level

  • Sends notifications to assignees and a summary to the webhook owner on the system's behalf
  • Keeps overdue-task history state in state.json
All reasons and checks
Russian stack

hemonc-team/task-overdue-watcherAuthor:hemonc-team

Install

Services

Manual install

git clone https://github.com/hemonc-team/task-overdue-watcher.git && cd task-overdue-watcher && python3 overdue_watcher.py --dry

A local read-only run, requires a filled-in .env with BITRIX24_WEBHOOK_URL.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Sends notifications to assignees and a summary to the webhook owner on the system's behalf
  • Keeps overdue-task history state in state.json

This is third-party code. Review the repository files before installing.

What it does

The overdue_watcher.py script runs on a schedule (by default Monday and Thursday mornings, Moscow time), reads Bitrix24 tasks via the inbound webhook REST API, finds overdue ones, pings the assignees and sends a summary to the webhook owner. State between runs is kept in state.json, which can be synced via Bitrix Disk through the state_disk.py module for cloud runs, so history is not lost when moving off a local run. There is a SKILL.md with instructions for Cursor Automations and Claude Code, and a separate step-by-step guide for setting up the automation in Cursor. A --dry mode runs the check without writing to the portal.

Who it is for. For small team leads on Bitrix24 who want a regular reminder about overdue tasks without manually checking them.

Good fit when

  • You need a regular (twice-weekly) check of overdue tasks without manually opening Bitrix24
  • You need a summary for the webhook owner and pings to specific assignees
  • You need to migrate the watcher's state from a local run to the cloud without a duplicate notification wave

Not a fit when

  • You need checks more often than twice a week or on a custom schedule: the cron expression needs changing
  • You do not use Cursor Automations or Claude Code, which the SKILL.md targets

Example request

Check, without writing anything, which Bitrix24 tasks are currently overdue

Limitations

The default schedule is hardcoded to Monday and Thursday; anything else requires manually editing the cron expression. Running it fresh without migrating the old state.json triggers a repeat seed and resends every notification, which is why state migration is documented as a required step. The script is written for one specific portal and webhook, with no reusable package release.

How to disable. Remove the Automation in Cursor or the cron job, stop the script and revoke the Bitrix24 webhook.

FAQ

What do I do when migrating from an old run?

Copy the old state.json with seeded true, upload it to Bitrix Disk, get a BITRIX_DISK_STATE_FILE_ID, and on the first cloud run download the state via state_disk.py before running --dry and then live.

Can I check without actually sending notifications?

Yes, the --dry flag runs the check without writing to the portal or pinging assignees.

Discussion

No questions or reviews yet.

All Bitrix24 tools
Russian stack

A Bitrix24 MCP server for task planning: subtasks, scrum epics, story points and kanban stages, from a PyPI package

MCP serverBroad access1
Russian stack

A Bitrix24 REST skill split into capability packs with a method allowlist, risk confirmations and an audit log

SkillBroad access26
Russian stack

Bitrix24 as mission control for AI dev agents: a kanban task conveyor, shared memory and one-button phone acceptance

SkillBroad access1
Russian stack

A React Ink terminal client for Bitrix24: tasks, comments, time tracking and kanban from the command line

CLIExtended access2
Russian stack

An article snapshot of the b24-ai-starter kit with four added CRM robot handlers on the Python backend: overdue tasks, phone, full name, deal sum

SkillExtended access2

README in short

The README describes the watcher's purpose and schedule, gives a table of project files (the main script, Bitrix Disk state sync, SKILL.md, a Cursor Automations guide, a state template), a quick start with the --dry flag, a short Cursor Automations guide, a state-migration section from old Dropbox storage to avoid a duplicate notification wave, and links to the team's related repositories.

README badge

Report a problem