Trigger BigQuery Scheduled Queries
Trigger BigQuery scheduled queries by display name.CLI Command
Options
Recommended SetupFor security and convenience, set your GCP credentials as environment variables:
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Trigger Google BigQuery Data Transfer scheduled queries and list transfer configs from Paradime Bolt with real-time run monitoring in the paradime CLI.
paradime run gcp-bigquery-transfer-trigger
| Flag | Type | Description |
|---|---|---|
--service-account-key-file | Required, TEXT | Path to your GCP service account JSON key file. Can be set via GCP_SERVICE_ACCOUNT_KEY_FILE environment variable. |
--project | Required, TEXT | Your GCP project ID. Can be set via GCP_PROJECT_ID environment variable. |
--location | Optional, TEXT | BigQuery Data Transfer location (e.g. ‘us’, ‘eu’, ‘us-central1’). Default: us. Can be set via GCP_LOCATION environment variable. |
--scheduled-query-names | Required, TEXT | Comma-separated display name(s) of the scheduled query/queries to trigger. |
--wait / --no-wait | Optional, Flag | Wait for the scheduled query run to complete before returning. Default: --wait. Can be set via GCP_BIGQUERY_TRANSFER_TRIGGER_WAIT environment variable. |
--timeout | Optional, INTEGER | Maximum time to wait for completion (in minutes). Only used with --wait. Default: 1440 (24 hours). Can be set via GCP_BIGQUERY_TRANSFER_TRIGGER_TIMEOUT environment variable. |
--help | Optional, Flag | Show the help message and exit. |
GCP_SERVICE_ACCOUNT_KEY_FILE="/path/to/service-account-key.json"
GCP_PROJECT_ID="your-gcp-project-id"
GCP_LOCATION="us"
# Trigger a single scheduled query (using environment variables)
paradime run gcp-bigquery-transfer-trigger \
--scheduled-query-names "daily_revenue_rollup"
# Trigger multiple scheduled queries (comma-separated)
paradime run gcp-bigquery-transfer-trigger \
--scheduled-query-names "daily_revenue_rollup,marketing_attribution"
paradime run gcp-bigquery-transfer-list
| Flag | Type | Description |
|---|---|---|
--service-account-key-file | Required, TEXT | Path to your GCP service account JSON key file. Can be set via GCP_SERVICE_ACCOUNT_KEY_FILE environment variable. |
--project | Required, TEXT | Your GCP project ID. Can be set via GCP_PROJECT_ID environment variable. |
--location | Optional, TEXT | BigQuery Data Transfer location (e.g. ‘us’, ‘eu’, ‘us-central1’). Default: us. Can be set via GCP_LOCATION environment variable. |
--help | Optional, Flag | Show the help message and exit. |
# List all scheduled queries (using environment variables)
paradime run gcp-bigquery-transfer-list
# With explicit credentials
paradime run gcp-bigquery-transfer-list \
--service-account-key-file "/path/to/service-account-key.json" \
--project "your-gcp-project-id" \
--location "us"
| Environment Variable | Description |
|---|---|
GCP_SERVICE_ACCOUNT_KEY_FILE | Path to your GCP service account JSON key file |
GCP_PROJECT_ID | Your GCP project ID |
GCP_LOCATION | BigQuery Data Transfer location (e.g. ‘us’) |
GCP_BIGQUERY_TRANSFER_TRIGGER_WAIT | Whether to wait for query run completion |
GCP_BIGQUERY_TRANSFER_TRIGGER_TIMEOUT | Maximum time to wait for completion (minutes) |