How we work
What we mean when an integration says “on request”
All but one of the integrations in our catalogue say On Request. That is not hedging. It is the difference between what is possible and what we have verified.
Our integrations page lists every connection we support and marks almost all of them On Request. Visitors reasonably ask whether that means they do not work.
What the labels actually mean
Available means we have a working configuration and a verification source recorded against it, with a date and a note of what was tested. Our content rules will not let a page claim Available without one, and the test suite enforces it. That is not a policy we can quietly relax; a build fails if someone tries.
On Request means the connection is technically supported and has not been verified for a published claim. It is not a no. It is a refusal to say yes on your behalf before we know.
Why we do it this way round
The alternative is the industry norm: list everything, mark it all as supported, and deal with the specifics during implementation. That produces a better-looking page and a worse conversation three weeks in, when it emerges that the connection works for one direction, or one document type, or not with the particular version you run.
We would rather lose the enquiry than win it on a claim we cannot stand behind.
What this means for you
Ask. The answer for your specific setup is usually concrete and quick, often yes with a caveat about scope, sometimes no. Either way you get a real answer rather than a green tick that meant nothing.
It also means the number of Available integrations will grow slowly and honestly, and each one that changes status will have a date and a source behind it.