# Page Not Found

The URL `article/fjkcbibhdv-configuring-direct-connection-to-google-bigquery` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Connecting to Google BigQuery](https://help.tellius.com/data/create-new-datasource/connecting-to-google-bigquery.md)
- [Steps to connect to a Google BigQuery database](https://help.tellius.com/data/create-new-datasource/connecting-to-google-bigquery/steps-to-connect-to-a-google-bigquery-database.md)
- [Connecting to Google cloud SQL](https://help.tellius.com/data/create-new-datasource/connecting-to-google-cloud-sql.md)
- [Alerts on the detection of anomalies](https://help.tellius.com/feed/alerts-on-the-detection-of-anomalies.md)
- [Connecting to Salesforce](https://help.tellius.com/data/create-new-datasource/connecting-to-salesforce.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://help.tellius.com/data/create-new-datasource/connecting-to-google-bigquery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://help.tellius.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://help.tellius.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/data/create-new-datasource/connecting-to-google-bigquery.md`).

You may also use `Accept: text/markdown` header for content negotiation.