Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions adrs/fullenrich-connector.txt
Original file line number Diff line number Diff line change
@@ -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.