trigger-event-scout
Continuous, entity-seeded buying-signal detection. Each cycle scans configured sources for events matching named signal definitions — each with positive/negative/edge-case examples — resolves the entities involved against a curated watchlist, scores fit and confidence separately, and emits qualifying hits as standard `type: lead` notes plus an inbox digest.
Nodig
- signal-records — Prior signal records — dedupe and trend base.
- config_id — Watchlist config to run
- since — Only consider signals after this date
- signal-config — Signal config (signals, entities, sources, thresholds)
- seen-log — Previously emitted signal hits (dedupe state)
- client_id — Restrict the sweep to one client's watchlists
- entities — Organizations to watch
- signal_types — Buying-signal events that count — tenders, launches, exhibitions
- sources — Where to look; defaults to the standard source set
- config_id — Config whose scoring or sources need adjusting
- false_positives — Signals that scored high but were not real buying windows
Zo vraag je het
- Monitor buying signals
- Watch for leads
- Run a signal cycle
Oplevert
- (client-scoped config) or (own-company config)
- combined-digest (markdown)
- cycle-log (markdown)
- digest (markdown)
- lead-notes (markdown)
- signal-config (markdown)
- updated-config (markdown)
Niveauadvanced
Invoerconversation
Uitvoerdocument
Vereist[api-key]
Rollen[]