Integrations

Use DocQuery from n8n, Zapier, Make, Claude, and Cursor.

Every workspace is a plain HTTPS API with a bearer key, plus a hosted MCP server. There are no custom nodes or apps to install: any tool that can make an HTTP request can read your linked spreadsheet and document tables.

The request every tool makes

GET a table's rows, filter with ?column=value, page with limit and offset, and embed linked rows with include=.

GET https://docquery.io/api/v1/tables/invoices/rows?status=unpaid&include=customer_id&limit=100
Authorization: Bearer YOUR_API_KEY

Try a real call now, no signup. This uses the public read-only demo key (example customers and invoices):

curl -H "Authorization: Bearer dq_demo_readonly" \
  "https://docquery.io/api/v1/tables/example_invoices/rows?status=due&include=customer_id"

Your table slugs, columns, and an OpenAPI spec are on the API docs page after you sign up.

Tool by tool

1

n8n

Add an HTTP Request node: method GET, the URL above, and a header Authorization: Bearer YOUR_API_KEY (or a Header Auth credential). The rows arrive as JSON under data.
2

Zapier

Use Webhooks by Zapier with a GET request to the same URL and the Authorization header. Use it as a lookup step before the action that needs the data.
3

Make

Use the HTTP module's "Make a request" with the URL and the Authorization header, and turn on response parsing.
4

Claude and Cursor

Connect the hosted MCP server so the agent can list tables and follow relations itself. Setup is on the MCP server page.

Prefer GraphQL? The same workspace serves a GraphQL endpoint; see the API docs after signing up.

Where the data comes from

An Excel workbook, an Airtable base, and the PDFs that go with them, linked by foreign keys.