DATA OPS
Self-serve BigQuery export from a Slack slash command with masked delivery
Lets teammates request a data export by typing a Slack slash command; runs the query against an allowlist, masks PII, and DMs back a private Dropbox link.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command invokedSlack
- LogicValidate report against approved allowlist
- ActionRun matched query in BigQueryBigQuery
- LogicMask PII columns for the report
- ActionUpload masked file to DropboxDropbox
- OutputDM Dropbox link to requester in SlackSlack
What it does
Gives non-technical teammates a self-serve export without warehouse access. They invoke a Slack slash command naming an approved report and date range. The workflow validates the request against an allowlist of safe queries, runs it in BigQuery, masks PII columns, uploads to Dropbox, and DMs the requester a link.
When to use it
Use it when many people need routine exports of a small set of approved reports and you want to keep them out of the BigQuery console. The allowlist prevents arbitrary queries while still letting people self-serve.
How it works
- 1A Slack slash command triggers the workflow with the report name and parameters.
- 2A logic step checks the requested report against the approved allowlist; unknown requests are rejected with a Slack reply.
- 3BigQuery runs the matched, parameterized query.
- 4A masking step redacts PII columns for that report.
- 5The masked file is uploaded to Dropbox.
- 6Slack DMs the requester the private Dropbox link.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect DropboxFiles and folders.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.