21 lines
989 B
Markdown
21 lines
989 B
Markdown
|
# Research Questions
|
||
|
|
|
||
|
|
Open questions surfaced during exploration, not yet investigated. Pull into the
|
||
|
|
relevant phase's research step when picked up.
|
||
|
|
|
||
|
|
## RESEARCH-pax8-company-identifiers
|
||
|
|
|
||
|
|
**Raised:** 2026-07-10, during exploration of [[SEED-002]] (PAX8 Integration)
|
||
|
|
|
||
|
|
**Question:** Does the PAX8 API expose a stable identifier for companies beyond
|
||
|
|
name — a domain, external/tenant ID, or similar — that could serve as a more
|
||
|
|
reliable join key to Autotask companies than fuzzy name matching?
|
||
|
|
|
||
|
|
**Why it matters:** The PAX8 integration scope defaulted to "fuzzy name match at
|
||
|
|
sync time, flag unmatched/ambiguous for manual review" for mapping PAX8
|
||
|
|
companies to Autotask companies. That's a reasonable starting point, but if the
|
||
|
|
API exposes something like a primary domain, it would be materially more
|
||
|
|
reliable and worth using instead (or as a tiebreaker for ambiguous name
|
||
|
|
matches). Check the PAX8 API docs (`companies` endpoint) before committing to
|
||
|
|
fuzzy-name as the permanent strategy.
|