Loom + Bruin

Source

Ingest Loom data into your warehouse with incremental loading, quality checks, and full lineage. Defined in YAML, version-controlled in Git.

For business teams

What you get

Operational analytics
Loom data in your warehouse means analytics that Loom's built-in reporting can't provide. Cross-tool, cross-team, custom.
Cross-tool project views
Combine Loom with Jira, GitHub, Slack, and other tools. One dashboard that shows the real state of projects.
Team workload insights
Understand collaboration patterns, bottlenecks, and workload distribution from Loom data — automatically updated.
No manual data pulling
Loom data syncs on schedule. Managers and leads get fresh data without asking anyone.

For data & engineering teams

How it works

Incremental sync
Only sync new and changed Loom records. No full reloads, no wasted compute.
YAML-defined, Git-versioned
Your Loom pipeline is a YAML file. Review in PRs, deploy with CI/CD, roll back with git revert.
Schema change handling
Bruin detects Loom schema changes automatically. No manual intervention when fields get added or renamed.
Cross-tool joins
Combine Loom data with other tools in SQL transforms. Bruin resolves dependencies across sources automatically.

Before you start

Loom Business plan with API access

Loom Developer API key

Step 1

Add your Loom connection

Connect using Loom Developer API key. Add this to your Bruin environment file — credentials are stored securely and referenced by name in your pipeline YAML.

Parameters

api_keyLoom API key from workspace developer settings
workspace_idYour Loom workspace identifier

connections:
  loom:
    type: loom
    uri: "loom://?api_key=<your-api-key>&workspace_id=<your-workspace-id>"

Step 2

Create your pipeline

Define a YAML asset that tells Bruin what to pull from Loom and where to land it. This file lives in your Git repo — reviewable, version-controlled, and deployable with CI/CD.

Available tables

videosusersworkspacescommentsviews

name: raw.loom_videos
type: ingestr

parameters:
  source_connection: loom
  source_table: 'videos'
  destination: bigquery

Step 3

Add quality checks

Add column-level and custom SQL checks to your Loom data. If a check fails, the pipeline stops — bad data never reaches downstream models or dashboards.

Validate workspace data synced completely

Ensure record IDs are unique and titles are present

Catch missing or null fields on every sync

columns:
  - name: id
    checks:
      - name: not_null
      - name: unique
  - name: title
    checks:
      - name: not_null

custom_checks:
  - name: workspace sync is complete
    query: |
      SELECT COUNT(*) > 0
      FROM raw.loom_videos

Step 4

Run it

One command. Bruin connects to Loom, pulls data incrementally, runs your quality checks, and lands clean data in your warehouse. If a check fails, the pipeline stops — bad data never reaches downstream.

Backfill historical data with --start-date

Schedule with cron or trigger from CI/CD

Full lineage from Loom to your dashboards

$ bruin run .

Running pipeline...

  loom_videos
    ✓ Fetched 2,847 new records
    ✓ Quality: campaign_id not_null     PASSED
    ✓ Quality: spend not_null           PASSED
    ✓ Quality: no negative ad spend     PASSED
    ✓ Loaded into bigquery

  Completed in 12s

Other Productivity integrations

Airtable

Asana

Bitbucket

Calendly

Canny

ClickUp

Ready to connect Loom?

Start for free, or book a demo to see how Bruin handles ingestion, quality, lineage, and scheduling for your entire data stack.

Book a demo Read the docs