Webhooks

When you transform outside Weld (Other / directly in my warehouse under Settings → Transform), Weld can still run your jobs as steps in an orchestration. A webhook step triggers the tool's job when the steps before it have finished, so your models rebuild on fresh data, right after the syncs they depend on.

Webhook steps are added on an orchestration's Webhooks tab, with Create webhook.

Supported tools

• Cube: a direct Cube webhook triggers your Cube job from the orchestration.
• SQLMesh: the orchestration triggers your SQLMesh job by webhook.

For dbt, see dbt Cloud and dbt Core.

How it fits an orchestration

An orchestration runs ELT syncs, models and reverse ETL together, in order, on one schedule. With a webhook step:

1. Weld syncs your sources into your warehouse.
2. The webhook step triggers the Cube or SQLMesh job.
3. Reverse ETL syncs in the same orchestration can run after it, on the updated models.