Integrations

OneQuery integrations become named sources. Each source has a provider, a local name, credential metadata, and one or more interfaces.

Databases PostgreSQL, Supabase, MySQL, and MongoDB setup patterns.

Warehouses Snowflake, BigQuery, AWS Athena Connector, and MotherDuck setup patterns.

Observability Sentry, Laminar, and Cloudflare Workers Observability for incident evidence.

Developer tools GitHub, Linear, Jira, Confluence, Vercel, and Discord access patterns.

Product analytics Google Analytics, Amplitude, Mixpanel, PostHog, Clarity, and Cloudflare Web Analytics.

Marketing and productivity Airtable, Cal.com, Granola, Amazon Ads, LinkedIn Ads, TikTok Marketing, SendGrid, and Search Console.

Interfaces

OneQuery sources commonly expose one of two access patterns.

Interface	Use it for
Query	SQL-oriented sources such as databases and warehouses.
Source API	Provider APIs such as GitHub pull requests, Sentry issues, or product analytics endpoints.

Some provider credentials can be used from the dashboard and the CLI. Others are CLI-first because their setup or workflow is more specialized.

Run a provider guide command before connecting a new source:

onequery source connect --source postgres

Replace postgres with the provider ID you plan to connect. The provider guide shows the expected credential shape and an example input payload.

Use source identifiers in agent instructions and runbooks after a source is connected.