Every Way Querri Connects

Esta página aún no está disponible en español. Se muestra la versión en inglés.

Querri connects to the rest of your systems in four directions. It reads data in from the tools you already use, sends results and tables back out, runs inside your own product, and takes instructions from your scripts and AI assistants. This page lists each way, what it’s for, and where its full instructions are.

Anything marked Beta or Early access is turned on one organization at a time. To try it, contact us at support@querri.com.

Bring data into Querri

Way in	What it does	Notes
Connectors	Pick a system from the catalog and sign in, or enter its connection details. Each table it loads becomes a source in your Library.	Querri syncs a copy, on a schedule or by hand.
Databases and warehouses	PostgreSQL, MySQL, SQL Server, Amazon Redshift, BigQuery, Snowflake and Databricks.	Use a read-only user. PostgreSQL, MySQL, SQL Server and Redshift can connect over a VPN.
Live tables	Leave a Snowflake or Databricks table in your warehouse and query it there, instead of copying it.	Scale plans.
Business apps	CRM, accounting, payments, marketing, support and analytics apps, such as Salesforce, HubSpot, QuickBooks, NetSuite and Stripe.	Most sign in with the app, so Querri never gets its password.
Google Drive	Add the CSV, Excel, JSON, Parquet and Google Sheets files you pick in Google’s file picker.	Querri can open only the files you pick.
File uploads	Drop CSV, Excel, JSON and Parquet files into the app.	No connector to set up.
Connector Agent	An assistant beside the Connectors page that finds, connects, tests and fixes connectors with you.	It never sees your passwords or keys, and waits for your approval before it creates or loads anything.
REST APIs and OData feeds	Have the Connector Agent build a connector for a JSON REST API or an OData feed, or start from a public data template.	Early access. Organization admins only.
Data API	Push rows into Querri from your own code: create a source, append rows, or replace its data.	Needs an API key with `data:write`.
Airbyte destination	Send any Airbyte source’s streams into Querri as sources.	Open source on GitHub. See below.

To choose where to start, see Decide What to Connect First. To keep it current, see Sync Scheduling.

Send data and results out

Way out	What it does	Notes
Downloads	Download any result: tables as CSV, Excel, Parquet or Markdown, charts as PNG or SVG.	From the result card.
Excel Export	Build a formatted Excel workbook from a project’s steps, with a sheet for each and formulas when you ask.	A step over 100,000 rows is cut to its first 100,000.
Deliver	Email results with a workbook, CSV file or chart attached, by hand or every time the project runs on a schedule.	Previews until you send it.
Message delivery	Send Deliver emails from your organization’s own address, through your own SMTP server.	Admins only.
Monitor alerts	Email a monitor’s alerts to up to 25 people when a number it watches moves.	The email carries the summary and chart, never rows of data.
Dashboard links	Publish a dashboard as a page anyone with the link can open, with an optional password and expiry.	Plan limits apply.
External drives	Copy clean tables from a workspace or a project into an S3 bucket you own, as Delta Lake, Apache Iceberg or Parquet, for Databricks, Snowflake, Microsoft Fabric or any tool that reads them.	Beta. Admins only.
Data API	Read your sources’ rows from your own code, or run a SQL query on one.	Needs an API key with `data:read`.
Airbyte source	Read your Querri sources into Airbyte, and from there into any destination Airbyte supports.	Open source on GitHub. See below.
Outbound webhooks	Send signed events to an endpoint you run: usage thresholds, plan changes and billing failures.	Admins only. Account events, not your data.

Put Querri inside your product

Way in	What it does	Notes
Embed SDK	Show dashboards, projects and the Library inside your own web app, for your own users.	`@querri-inc/embed`, for the browser and Node.js.
PHP SDK and Python SDK	Create your users, their access policies and their embed sessions from a PHP or Python backend.	Access policies keep each user to their own rows.
Widget embeds	Publish a single dashboard widget, with its own URL and embed HTML, on a website or in another tool.	No code.
Embed domains	Limit which websites can show embedded Querri.	Until you add a domain, any site can.

Drive Querri from your own tools

Tool	What it does	Notes
MCP server	Connect an AI assistant such as Claude or ChatGPT, then ask about your data, start a project, and look at sources, views and dashboards from inside the assistant.	The assistant acts as you and sees only what you can see.
CLI	Upload files, run projects and chats, query sources, and manage users, keys and policies from a terminal or a script.	`pip install "querri[cli]"`. Add `--json` for scripts and coding agents.
Python SDK	Do the same from Python, with sync and async clients.	`pip install querri`.
REST API	Every endpoint the SDK and CLI use, for any other language.	See Authentication.
API keys	Give a script, integration or embed its own key, with its own scopes, rate limit, expiry and optional IP allowlist.	Admins create keys in Settings.

The Airbyte connectors

If your team already moves data with Airbyte, Querri has two open-source Airbyte connectors on GitHub: Querri-inc/airbyte-querri-connectors.

Destination (destination-querri): writes Airbyte streams into Querri. Each stream becomes a source in your Library. Choose Overwrite to replace a source’s rows on each sync, or Append to add to them.
Source (source-querri): reads your Querri sources into Airbyte. Each source becomes a stream, with full refresh or incremental syncs.

Both use the Data API with an API key. The destination needs the data:read and data:write scopes, and the source needs data:read.

Data Connectors Overview: how connectors sync, and the full list
Sources and connectors: the ideas behind bringing data in
Security & Governance: who can see what, wherever the data goes