Connectors
Connect the systems you already use without moving everything into another platform.
KynticAI connects to approved company systems and imports the information needed for an agreed question. Scout can link those records and events inside the customer controlled environment, keep the order in which they happened and prepare a structured result for people, software or approved AI to use. Raw operational customer data does not need to be sent to the KynticAI cloud service.
Why the connection matters
A connector is only useful if it helps turn separate facts into a useful decision.
A CRM stage, support ticket, website visit, email address, product view or approved file can be part of the same business story. KynticAI connects those facts so they can be considered together.
Existing systems can stay in place.
Only approved information is used for the agreed purpose.
The result can become a task such as follow up, register, recover, escalate or retain.
Systems KynticAI can connect to
The aim is to take the useful information from approved systems, connect related records and events inside the customer environment and keep enough history to explain a later recommendation. The system of record can remain the system of record.
SQL Server
Database · Enterprise
PostgreSQL
Database · Enterprise
MySQL
Database · Enterprise
SQLite
Database · Free open source
Oracle DB
Database · Enterprise
Salesforce
CRM · Enterprise
HubSpot
CRM · Enterprise
Dynamics 365
CRM · Enterprise
SAP
ERP · Enterprise
REST API
Generic · Free open source
GraphQL
Generic · Free open source
CSV / Flat Files
File · Free open source
Email Engagement
Communication · Enterprise
SharePoint
Document · Enterprise
Azure Blob
Storage · Enterprise
AWS S3
Storage · Enterprise
Snowflake
Warehouse · Enterprise
BigQuery
Warehouse · Enterprise
A simple example
Three separate source records can become one useful recommendation.
The example uses synthetic information. In a real project we first agree which systems can be accessed, how credentials are handled, who is allowed to see which information, what the information may be used for and what must be recorded for audit.
01 / Information from existing systems
The systems keep doing the jobs they already do
Salesforce.stage = renewal
Zendesk.open_tickets = 5
PostgreSQL.login_drop_pct = 31
ApprovedImport.source = customer approved file
02 / Connect the history
KynticAI links the events and keeps their order
journey = CRM -> support -> usage_drop
relationship = strong
similar_success = won after support fix
confidence = medium to high
03 / Recommended action
Return a checked result that other software can use
best_example = won after support fix
recommend = send support resolution note
include = evidence sources
owner = customer success
Where the result can go
Fortress returns a structured result containing the action and evidence. That result can go to the customer's approved model, internal software or a person. The model is one possible way to explain or use the result, not the place where the underlying customer history has to live.
Llama
Local or private runtime · Open source model
Mistral
Local or private runtime · Open source model
Qwen
Local or private runtime · Open source model
Approved hosted adapter
Depends on the deployment · Optional model API
Private model gateway
Customer approved endpoint · Optional model API
Human and software workflows
Customer workflow · Action
Worked examples
Connectors in use.
Examples of what changes when information from separate systems is connected before a decision is made.
Synthetic 3PL scenario - WMS, transport, staffing, dock sensors
Connector evidence becomes an action
“Facility Birmingham is heading for an SLA miss. Tuesday night shift had three of eight pickers absent, creating a 340-unit backlog while dock doors 4-7 sat idle for 2.3 hours.”
Synthetic insurer operations scenario - policy, broker, claims trend
Expose the hidden policy pattern
“Flood Domestic claims in the North West show a 23% higher payout ratio through Broker Channel X, with wording variance in 68% of reviewed cases.”
Synthetic hotel scenario - booking journey, channel, POS
Revenue loss hiding in the journey
“RevPAR is down 12% despite flat occupancy. OTA bookings rose to 62% of mix because the direct booking path is three clicks slower than the OTA path.”
Need a system connection that is not listed here?
Tell us which system contains useful information and what business question you are trying to answer. A connector is worth building when it supports a real use case, not simply to make the list longer.