Name the source. Preserve its boundary.
A useful source connection has a defined purpose, permission model and processing boundary. BotXpose supports the sources below; exact access, synchronization and deployment details are confirmed for each customer environment.
- 01Discover
- 02Correlate
- 03Validate
- 04Prioritize
- 05Guide remediation
Inputs must carry their boundaries with them.
Each input is shown with its intended purpose and a support state. The page does not turn an architecture subject into a production claim.
Swagger / OpenAPI + Postman
Customer-supplied API inventory and definition context.
GitHub + SharePoint
Credential and secret exposure discovery within approved boundaries.
ServiceNow
Service and workflow context within the approved deployment.
External + internal discovery
Exposure signals from customer-approved discovery boundaries.
DECISION MODEL
The graph should answer a question.
- 01
What business question requires this source?
- 02
Which permissions and records are actually needed?
- 03
How are updates, errors and deletion handled?
- 04
Where does the resulting action need to go?
Evidence enters.
An owned action leaves.
- 01Documented source purpose and owner
- 02Minimum required permission and data boundary
- 03Declared support status and delivery dependency
- 04Observable sync and downstream action workflow
What this page does not claim.
- A named source does not imply every access or synchronization mode.
- Logos and vendor marks should not be added without permission.
- Authentication, rate, retention and residency vary by customer deployment.
- BotXpose guides remediation; it does not autonomously change customer systems.
Confirm the use case before promising the connector.
We will establish the exposure question, approved sources, data boundary and current support status before representing a deployment path.