Google BigQuery

Runs on its own 9

Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.

• List projects Tier 0 · Read Outside content

  Google Cloud projects these credentials can use with BigQuery, with their IDs and names.

• List datasets Tier 0 · Read Outside content

  Datasets in a project with their location and labels. project_id defaults to the connected project; use another, such as bigquery-public-data, to browse shared data.

• List tables Tier 0 · Read Outside content

  Tables, views and materialized views in a dataset, with type, partitioning and creation time.

• Describe a table Tier 0 · Read Outside content

  A table's or view's columns (name, type, mode, description, nested fields), row count, size in bytes, partitioning and clustering, and whether queries must filter on the partition column. Read this before writing SQL.

• Preview rows Tier 0 · Read Outside content

  Read rows straight from a table without running a query: free and quota-light, but unfiltered and in storage order. Values come back as rows[].f[].v in column order (or in the order of columns when given); get_table gives the names. Does not work on views.

• Estimate a query's cost Tier 0 · Read Outside content

  Validate a GoogleSQL query and report how many bytes it would scan, without running it or paying for it. On-demand pricing is $6.25 per TiB after the first free TiB each month.

• Run a SQL query Tier 0 · Read Outside content

  Run a read-only GoogleSQL query (SELECT, or WITH ... SELECT) and get column names and up to max_rows rows as objects. Name tables as `project.dataset.table`, select only the columns you need and filter on the partition column: billing counts every byte of each column read, and LIMIT does not reduce it. Queries that would scan more than the connection's limit are refused without charge; other statements (INSERT, UPDATE, DELETE, CREATE...) are refused.

• Get more query results Tier 0 · Read Outside content

  Fetch further pages, or the finished results, of a query that run_query returned with a job_id (large results or a query still running). Values come back as rows[].f[].v in the order of schema.fields.

• Append rows to a table Tier 2 · Reversible Outside content

  Stream new rows into an existing table, for example to log results or decisions. Each row is {"json": {column: value}} and may carry an insertId so retries within a minute are not duplicated. Rows that fail are listed in insertErrors even when the call succeeds.