Native connectors
Native connectors link Qontext to external tools like HubSpot or Google Drive and keep their data continuously synced into the context repository.
Category
Product feature
See all terms
What are native connectors?
Native connectors are prebuilt connections that link Qontext to external tools where company context already lives, tools like HubSpot, Google Drive, Notion, and Slack. Each connector pulls selected source data into the context repository and keeps it in continuous sync with minimal setup.
Why native connectors exist
Company context doesn't live in one place. It's split across a CRM, a drive, a wiki, and a chat tool, and every one of them changes constantly. Without a connector, someone has to export data by hand and re-import it whenever it changes, which means agents end up working from whatever was current on the day someone last remembered to update it. A native connector removes that manual step: once it's set up, the source data stays current in the context repository on its own.
How do native connectors work?
Setting up a connector links a source account to the workspace, and from there the sync runs on its own. An initial sync can take up to twelve hours for large datasets, since it has to pull in everything selected for the first time. After that, syncs only process what changed, which runs far faster.
Each source gets filters, so a workspace can choose exactly which data gets synced instead of pulling in everything the connected account has access to. Every source also keeps its own sync logs, showing when a sync started and finished, whether it succeeded, what was skipped, and what triggered it. If a tool doesn't have a native connector yet, the same data can still reach the context repository through MCP, the API, workflow tools like n8n or Make, or by requesting the connector directly. Once source data lands in the repository this way, it becomes part of the same context repository that context agents read from and users query.