Does it work with the tools we already use?

There is no list of supported platforms, because there is no per-platform code in the product. An integration is written for your workflow, during the interview, against whatever API the service publishes.

You name the system while you are describing the job, and you connect it in the same conversation: either by handing over a key you already have, or by signing in through a browser the agent opens for you, two-factor prompts included. The interview agent then reads the service's documentation and writes the small piece of code the workflow needs. That code runs in a sandbox that starts from an empty environment and only ever receives the credentials that workflow declared.

We used to keep a handful of built-in integrations and retired them, because a catalogue means "does it work with our system" has an answer that sometimes depends on our backlog. The difference shows up on the unglamorous systems: the niche vendor portal, the internal API, the regional accounting tool nobody builds connectors for. Those are now reached exactly the same way a well known platform is.

The trade is real and worth saying out loud. A hand written integration for a big platform would be more polished than one authored on demand, and each integration now costs interview turns instead of a menu click. Publishing is where it gets checked: a workflow cannot go live while a system it declared is still unconnected.