agent-data-monitor
Monitor data with agent-data
Build a recurring workflow that retrieves the right data, retains progress, and delivers the requested outcome. Agent-data supplies API access and notify; the released CLI has no recurring scheduler. Use the host's actual scheduling tools or an existing application scheduler.
Use agent-data-cli for authentication, typed calls, output capture, and notification mechanics. Follow current tool schemas and API docs for the selected environment.
1. Define the recurring outcome
Inspect existing workflow configuration and scheduler records first. Update the matching monitor when the user asks to change it; preserve its identity and state.
Record the user's objective, sources, inputs, qualifying changes, cadence, timezone, delivery destination, and first-run behavior. Translate broad requests into explicit criteria: products crossing a price threshold, new jobs matching stated preferences, new papers on specified topics, or competitor pages changing named facts. Define whether a report contains new records, changed records, or a fresh snapshot.
Use requirements already supplied. Ask for missing decisions that determine the result, such as which market to monitor or where alerts must go. For “watch for new changes,” establish the current state as the baseline and say when monitoring begins. For an initial report or backfill, retrieve the requested history before switching to incremental runs. Never label the entire baseline as newly discovered events without making that first-run behavior explicit.
2. Select and test the retrieval contract
Reuse a suitable selected API; otherwise use agent-data-search. Read current docs and call representative inputs. If required data is absent, carry the demonstrated gap to agent-data-extend or agent-data-build.
Choose retrieval based on the actual contract: