bridge-lead-pooling

bridge-lead-pooling is a production webhook poller that keeps a rolling daily pool of sales leads from MogulBridge. It runs collect cycles on any schedule you want (typically hourly), fetches new webhook requests since the last cursor, deduplicates by request ID, and appends only the leads from your configured partner list to that day's pool. At the end of the working day (configurable hour, defaults to 17:00 Pacific), it publishes: a CSV export written to disk and an adaptive card POST to a Microsoft Teams Power Automate webhook with totals, top campaigns/events, and a preview of the first 8 leads.

The core logic is split into commands. collect always fetches new records and updates the cursor; publish builds the CSV and notifies Teams; tick chains them safely for scheduled runs—always collects, publishes only once per local-zone day at/after PUBLISH_HOUR, and is safe to fire on any cadence. Windows Task Scheduler integration (install-task) walks you through registering a scheduled task with natural-language interval parsing ("every 2 hours", "1h30m", "5 times a day" all work). On Linux or macOS, a standard cron entry runs the same tick command.

The implementation handles timezone-aware day boundaries (IANA timezone string), stores state and pools as JSON files on disk to survive process restarts, and provides defensive partner filtering both server-side (API query param) and client-side (drops mismatched records with a warning). The adaptive card payload stays compact intentionally—Power Automate's card renderer hits size limits around 28 KB—so the full CSV is always saved locally; Teams just gets the summary and a path to where the file was written.