If a PolySaaS user is interacting with an external application, PolySniffer will record all of that traffic.
Along with logging login flows, API interactions, downloaded resources, complete GET/POST data (headers, payloads, arguments), and more, it does a lot more.

This comprehensive visibility enables us to accurately delineate the external application’s behavior, facilitating seamless accessibility to atomic services, dynamic orchestration, and workflows—without the need for custom code or dependence on vendor APIs.

The obtained output is automatically inputted into our AI engine, which produces a customized handle class for the endpoint.
This class provides distinct interaction points for users to inject and execute atomic services on incoming or exiting data, facilitating robust, configurable automation inside the PolySaaS ecosystem.

This is just one page of the details captured and used by PolySniffer.

PolySniffer provides users with the necessary details to capture, process, and transmit information to the relevant applications. Having operated across various applications, PolySniffer is aware of the required details, including headers, tokens, cookies, protocols, and data schemas. PolySniffer serves as the facilitator for all those functions.

PolySniffer continuously monitors a user’s connection to the target SaaS application, capturing every detail and transmitting it to our AI, which generates a “Handler.” This Handler is utilized whenever the user connects to the target SaaS application, facilitating the use of events such as GET and POST to orchestrate Atomic Services for task execution.

When a Tenant incorporates an External Application and executes PolySniffer, they receive all the necessary details for integration with that application without the need to write any code; even the atomic Services capable of reading from and writing to multiple endpoints are automatically built.