Live and supported
Reserved for a verified production integration with defined delivery and support ownership.
Integration Directory
Check the status before assuming compatibility.
A named system belongs in this directory only after Heritage confirms its delivery status, capabilities, requirements, limitations, and support relationship. An evaluation is not the same as a live or supported integration.
Compatibility checklist · not a resultA complete evaluation
- Status and category
- Capabilities and requirements
- Known limitations
- Delivery and support ownership
A vendor name or logo alone does not establish compatibility, availability, or support.
Classification model
Five statuses, each with a different meaning.
These definitions are the directory framework. They do not state that an integration currently exists in any category.
Configurable Heritage integration
A verified repeatable pattern that still requires customer-specific configuration and authorization.
Custom integration available with API access
A scoped build may be available when usable documentation, required functions, and customer-authorized access are confirmed.
Evaluation required
The required access, data, actions, limits, ownership, and operating fit have not yet been confirmed.
Not currently feasible
The required access, data, action, or operating condition is unavailable based on the recorded evaluation.
Terminology boundary: Heritage does not label an integration “native” unless the underlying product actually supplies and supports it natively.
Integration listings
Current verified directory
Integration evaluation
Looking for a specific business system?
No named integrations are listed today. Heritage can evaluate a defined workflow when the target system provides usable API documentation and customer-authorized access.
Request an integration evaluationEvaluation path
A missing entry does not mean “compatible” or “impossible.”
Heritage can evaluate a system when the intended workflow is defined and the target provides usable API documentation and customer-authorized access. The necessary data and actions must actually be available.
- 01
Name the software and result
Describe the event, desired action, people involved, and exception path.
- 02
Provide public documentation context
Share the vendor documentation URL and known account requirements, but not credentials.
- 03
Evaluate access and limits
Heritage reviews authorization, functions, data, identifiers, stability, rate limits, and vendor rules.
- 04
Define the supported scope
Document the capabilities, requirements, limitations, ownership, and maintenance model.
Credential boundary
Describe the workflow. Do not send access secrets.
The general contact form is for the software name, documentation link, desired result, and business context. Do not submit passwords, API keys, tokens, customer records, recordings, transcripts, or other sensitive data.