Breaking Change → Slack #engineering
When breaking_changes > 0, post a message to Slack with the affected tables and a link to review the diff. Tag the on-call engineer.
Every time you run a schema diff in SchemaLens, automatically send the results to Slack, email, Jira, Notion, Google Sheets, or any of 5,000+ apps via Zapier. No code required — just paste a webhook URL and flip a switch.
Works with Pro and Team plans. Free plan can test with manual webhook sends.
Turn every schema diff into a trigger for your team's workflow.
Instantly notify your team in Slack when a diff contains breaking changes. Include severity, affected tables, and a link to review the full diff.
Send formatted diff summaries to PMs, QA, or compliance teams after every schema review. No need to copy-paste screenshots.
Auto-create Jira issues for each breaking change detected. Assign to the engineer who opened the PR and link back to the diff report.
Append every schema diff to a Notion database. Build a searchable changelog of every table change across your organization's history.
Log every schema change to a shared Google Sheet. Track who changed what, when, and the risk score over time for compliance audits.
Every webhook includes an optional HMAC-SHA256 signature. Verify the payload came from SchemaLens, not an attacker, before acting on it.
Connect SchemaLens to Zapier in three steps.
In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger. Select Catch Hook and copy the webhook URL.
https://hooks.zapier.com/hooks/catch/123456/abcdef/)Open SchemaLens, run any diff, then open Settings → Webhooks and paste your Zapier webhook URL.
Back in Zapier, add any action app as the next step. Use the diff payload fields to customize your message, ticket, or record.
summary.breaking_count, summary.tables_modified, and migration_sql_previewEvery webhook sends a JSON payload you can map to any Zapier action.
{
"event": "diff_completed",
"dialect": "postgres",
"timestamp": "2026-04-28T14:32:00.000Z",
"url": "https://schemalens.tech/app.html",
"summary": {
"tables_old": 12,
"tables_new": 14,
"tables_added": 2,
"tables_removed": 0,
"tables_modified": 3,
"breaking_changes": 1,
"risk_score": 42
},
"breaking_changes": [
{
"severity": "high",
"table": "users",
"change": "Dropped column 'email'"
}
],
"migration_sql_preview": "ALTER TABLE users DROP COLUMN email;\nCREATE TABLE orders (...)"
}Number of breaking changes. Use this to conditionally alert only when > 0.
0–100 risk score. Use this to route low-risk diffs to a log and high-risk diffs to Slack.
First 2,000 characters of generated SQL. Use this to include a preview in emails or tickets.
Array of individual breaking changes with severity, table, and description.
Copy these recipes for common schema diff automations.
When breaking_changes > 0, post a message to Slack with the affected tables and a link to review the diff. Tag the on-call engineer.
Log timestamp, dialect, risk score, and table counts to a shared Google Sheet. Build charts showing schema churn over time.
When risk_score > 70, create a Jira ticket in the "Database Review" project with the migration SQL attached.
Add a secret key in SchemaLens Settings. Every webhook includes an X-Webhook-Signature header. Verify it in Zapier with a Code step to prove the payload came from SchemaLens.
SchemaLens never stores your webhook payloads. They are forwarded directly from your browser to your endpoint. Stateless and private.
If your webhook server is down or Zapier errors, your diff still completes normally. Webhooks are fire-and-forget — they never block your workflow.
Generate schema diffs programmatically with curl, JavaScript, Python, and Go examples.
Run schema diffs in GitHub Actions, GitLab CI, and Bitbucket Pipelines. Catch breaking changes before they merge.
Learn what triggers a breaking change alert and how to prevent production incidents.
Set up your first Zapier webhook in under 5 minutes. Connect SchemaLens to the tools your team already uses and never miss a breaking change again.
Open SchemaLensNo signup required. Webhook settings are in the app toolbar.