From fa52cef7e3be1c1ba3824b8beae6b9a12f14bdda Mon Sep 17 00:00:00 2001 From: rsindall Date: Tue, 4 Aug 2026 01:46:36 +0100 Subject: [PATCH] adr: request FullEnrich connector Product ask for first-class FullEnrich enrichment tooling in QM. --- adrs/fullenrich-connector.txt | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 adrs/fullenrich-connector.txt diff --git a/adrs/fullenrich-connector.txt b/adrs/fullenrich-connector.txt new file mode 100644 index 0000000..641447d --- /dev/null +++ b/adrs/fullenrich-connector.txt @@ -0,0 +1,26 @@ +fullenrich connector + +It would be really useful if QM had first-class FullEnrich support for agents — +people / company enrichment as an Admin-configured connector (or MCP-shaped +tool surface), so orgs don't have to hand-roll sandbox CLIs and API keys. + +What we'd want, roughly: +- Admin can register a FullEnrich API key (org-shared) with clear spend limits +- agent can run common enrichment reads first: person lookup, company lookup, + bulk enrich where that fits +- writes back into CRM optional later and clearly gated +- works from agent turns without requiring a custom sandbox image just for + FullEnrich + +Why this belongs in QM: commercial agents spend a lot of turns on contact and +account enrichment. Today this can be approximated with a FullEnrich CLI or +HTTP calls from the sandbox plus a skill, but a supported connector would +match how other SaaS tools show up under Admin → Connectors and be much +cleaner for company rollouts. + +Happy for you to shape this as: +- a first-class HTTP/API connector with built-in FullEnrich tools, or +- a first-class MCP connector recipe for FullEnrich, or +- both + +Not a security report — just a product ask.