Connectors
Connect authorised systems. Build the private relationship layer.
KynticAI is built to inject approved records and source structure inside the customer-owned data plane, including connectors and customer-approved one-off imports. Free open-source Scout stores data items as attribution paths and relationship sets, then hands the model top-example JSON without sending raw operational data into KynticAI product operations.
Buyer spark
The magic is not the connector. The magic is the moment the source field becomes a decision.
A CRM stage, a support ticket, a cookie, an email address, a product view, or a CSV import stops being scattered noise and becomes a relationship fact the engine can compare.
The buyer sees their own systems staying in place instead of another rip-and-replace platform.
The data team sees a controlled source path, not a vague prompt dump.
The revenue team sees a task: follow up, register, recover, escalate, or retain.
Data Source Connectors
The goal is simple: let each source keep doing its job while the KynticAI relationship layer stores exact authorised data items privately, preserves attribution paths, compares relationship sets, and creates model-ready JSON for a decision, workflow, or task.
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
Connector example
Source fields become top-example JSON.
Illustrative sample data only. A real connector pilot agrees source access, credential handling, role/purpose controls, and audit boundaries before any operational data is used.
01 / Sources
Existing systems and imports stay controlled
Salesforce.stage = renewal
Zendesk.open_tickets = 5
PostgreSQL.login_drop_pct = 31
OneOffImport.source = customer-approved import pack
02 / Relationships
KynticAI stores attribution paths
attributionPath = CRM -> support -> usage_drop
relationshipStrength = high
similarPattern = won after support fix
confidence = medium-high
03 / Action
The model gets top-example JSON
topExample = won after support fix
recommend = send support-resolution note
include source trail
route = customer-success owner
Fortress model handoff and proposed Elite walkthrough
Fortress sends governed top-example JSON to the customer's own LLM or approved internal workflow. The proposed Elite path shows how Discovery MCP, synthetic demo, Fortress pilot scope, approved model boundary, and outcome review fit together.
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
Deployment-specific · Future or optional model API
Private model gateway
Customer-approved endpoint · Optional model API
Human and AI workflows
Customer workflow · Action layer
Evidence Results
Connectors in action.
What happens when source systems produce relationship analysis instead of another raw-data copy.
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 Connector We Have Not Listed Yet?
Tell us which systems matter and what next-best task you want to support. Enterprise pilots can prioritise the connector path around a concrete relationship-analysis workflow.