{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/project-management.watch-for-changes/",
    "json": "https://www.anchorterminal.com/niches/project-management.watch-for-changes/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/project-management.watch-for-changes/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/project-management.watch-for-changes/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 16 | 15 | 6 | 3 |\n\n## What counts as done\n\nA change or comment made in the web app reaches the agent as an event, with the task id and the changed field, and missed events can be replayed or re-synced.\n\nMeasured, for our own tests: the event arrives within a minute.\n\nHow agents ask for it: tell me when the client replies on the ticket; pick up work when someone moves a card to Ready; keep my index in sync with the board\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Taiga (Taiga Cloud Services, S.L.)**: Webhooks fire on create, change and delete with a change diff, and /webhooklogs lists deliveries with a resend endpoint, so missed events can be replayed; the setup is per project.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Asana (Asana, Inc.)**: REST webhooks deliver task and comment changes, on average within a minute, but delivery is at-most-once with no replay, MCP has no event route, and task changed events stopped for a week in acc-43.\n- **Basecamp (37signals LLC)**: Webhooks fire for to-do, comment and other recording events with up to 10 attempts and inspectable delivery records, and basecamp connect watches for an agent's work, but no replay or sync-token route is documented.\n- **ClickUp (Mango Technologies, Inc. DBA ClickUp)**: REST webhooks cover task and comment events with five retries per event, after which the event is dropped and fail_count rises; no replay is documented and MCP has no event route.\n- **monday.com (monday.com Ltd.)**: GraphQL webhooks fire on column changes, status changes, item moves and new updates, retrying once a minute for 30 minutes; no replay is documented and MCP has no event tool.\n- **ONES (The Beautiful ONES Technology PTE. LTD.)**: Plugin apps can subscribe to issue created, updated, status-changed and deleted events by HTTP callback, but replay or missed-event recovery isn't stated in the index and MCP has no event route.\n- **OpenProject (OpenProject GmbH)**: Admin-configured webhooks fire on work package, comment, project, time entry and attachment create and update, per project, but no retry, replay or missed-event guidance is documented.\n- **Plane (Plane Software, Inc.)**: v2 webhooks carry event_id, previous_attributes diffs and PQL filters, with retries over five attempts, but there is no manual retry or replay and events aren't queued while disabled.\n- **Redmine (Redmine project)**: Redmine 7 sends issue webhooks with the update's journal, but WebhookJob calls the hook once with no retry or replay found in the source, and the wiki API page doesn't document them.\n- **Roma (Milo Mode Inc.)**: list_items changedSince is a changes feed including trashed items, and wait_for_item holds up to 25 seconds for news on one item, but this is polling, not a push event with the changed field.\n- **Shortcut (Shortcut Software Company)**: Outgoing webhooks send story changes with the changed fields, and story history is readable through /stories/\u003cid\u003e/history for re-sync, but no retry or replay policy is documented and an incident delayed webhooks on 19 October 2026.\n- **Taskade (Taskcade Inc.)**: Signed webhooks cover six events (task.due, task.assigned, comment.created and three project events), so completions and field edits need automation triggers; no retry or replay is documented.\n- **Teamwork.com (Teamwork Crew Limited)**: Webhooks can be set at site or project level on paid plans, but the setup guide states no retry, replay or missed-event recovery, and the MCP has no event route.\n- **Todoist (Todoist Inc.)**: Webhooks send item and note events with the changed entity and a delivery id, retried up to three times 15 minutes apart, and the Sync API's sync_token re-syncs missed changes, but delivery can be 45 minutes late, past the one-minute bar.\n- **Trello (Trello, Inc.)**: Webhooks fire per model on card updates and comments with the action data, retrying three times with backoff, but there is no replay; acc-56 dropped Trello because replies needed manual refresh.\n- **Wrike (Wrike, Inc.)**: Webhooks send events such as TaskStatusChanged with old and new values and CommentAdded, and can be suspended or resumed, but no retry or replay of missed events is described.\n- **YouTrack (JetBrains s.r.o.)**: There are no native webhooks; an administrator writes an on-change workflow rule that makes outbound HTTP requests, with no replay, and MCP has no event route.\n\n- not this job: Financial Cents MCP (Financial Cents LLC): No webhook, event or changed-since tool appears among the 40 MCP tools in the guide.\n\n## What stops agents finishing\n\n- task-level changed events stop silently while story events still arrive\n- no event stream, so the agent polls and misses human edits\n\n## Around it\n\nBefore: project-management.coding-agent-ticket-loop. After: project-management.update-tasks, notifications.push.\n\n## Where this comes from\n\nWeight 6 of 100 in Project \u0026 task management: 3 of 58 accounts (an Asana change-event outage, a ClickUp user indexing via webhooks, a builder who dropped in-ticket conversation because issues needed refreshing); weight lifted above its count because change events are a buyer check.\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/project-management.watch-for-changes.json, or the MCP tool get_use_case with id project-management.watch-for-changes. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Notice when a human comments or changes a task the agent owns",
        "url": ""
      }
    ],
    "description": "Notice when a human comments or changes a task the agent owns: 1 companies fully do it, 16 with a limit, 15 carry the tag. Every listing in Project \u0026 task management with the reason and a source.",
    "facts": null,
    "h1": "Notice when a human comments or changes a task the agent owns",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/project-management.watch-for-changes/",
    "published": "",
    "section": "agents",
    "title": "Notice when a human comments or changes a task the agent owns |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/project-management.watch-for-changes/"
  },
  "tokens": {
    "markdown": 1600,
    "slim": 380
  },
  "version": 1
}
