GitHub Webhook to Azure Synapse Integration

How Datrise loads GitHub Webhook into Azure Synapse

Datrise syncs GitHub Webhook's push events, pull requests, issues, releases, commits, and workflow runs into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

GitHub Webhook: Repository event stream delivered by webhook.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How GitHub Webhook entities map to Azure Synapse

GitHub Webhook entity	Azure Synapse object	Notes
push events	`github_webhook_push_events`	datetime2 events
pull requests	`github_webhook_pull_requests`	id PK · linked to github_webhook_push_events
issues	`github_webhook_issues`	id PK · linked to github_webhook_push_events
releases	`github_webhook_releases`	id PK · linked to github_webhook_push_events

FAQ

How does Datrise handle GitHub Webhook's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the GitHub Webhook to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect GitHub Webhook to Azure Synapse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.