Bitrix24 overdue task watcher

task-overdue-watcher

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

Skill

Medium risk

We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.

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

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/task-overdue-watcher

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a claude-code -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a cursor -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a github-copilot -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a codex -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a gemini-cli -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a cline -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a roo -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

A fork of Roo Code, same .roo folders.

Run in a terminal in the project folder

npx skills add hemonc-team/task-overdue-watcher --skill task-overdue-watcher -a opencode -y

The skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit ab704d8.

Text for your agent

Clone hemonc-team/task-overdue-watcher, fill in .env with your Bitrix24 webhook, run python3 overdue_watcher.py --dry to check without writing, then set up the Cursor Automation per docs/CURSOR_AUTOMATIONS.md with the 0 6 * * 1,4 schedule.

Other ways from the author
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.

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.

Security check

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

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.

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.

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483Repository stars
Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28Repository stars
Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh riskRussian stackNo VPN needed

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed
Foxx AIBitrix24 overdue task watcher

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.