# dbt integrations

> Call the dbt API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/dbt-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

dbt is a data transformation platform where analytics teams build, test and schedule SQL models in their data warehouse, with jobs run from the dbt platform. Tray.ai connects to dbt through the HTTP Connector, so your workflows can call the dbt API alongside the rest of your stack.

## Use cases

### Jobs

Read and create jobs in dbt from any Tray.ai workflow. The dbt API covers calls such as trigger a job run and get a run's status.

- Trigger a job run
- Get a run's status

### Webhook subscriptions

Read, create, update, and delete webhook subscriptions in dbt from any Tray.ai workflow. The dbt API covers calls such as list webhook subscriptions and get a webhook subscription.

- List webhook subscriptions
- Get a webhook subscription
- Create a webhook subscription

### dbt events

Start a Tray.ai workflow the moment something happens in dbt. dbt sends events such as job run started and job run completed to a Tray.ai webhook trigger.

- Job run started
- Job run completed
- Job run errored

## Challenges Tray.ai solves

### Keeping dbt credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store dbt credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the dbt API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the dbt API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to dbt?

Yes. Tray.ai connects to dbt through the HTTP Connector, which calls the dbt API directly. Any call the dbt API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with dbt?

The dbt API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated dbt connector?

dbt runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated dbt connector from the dbt API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/