Automated Confluent Schema Change Digest
Every morning, WebRun opens Confluent Cloud, lists the schema subjects with a version registered since yesterday, reads each one's compatibility setting and the topics that carry it, posts a digest to Microsoft Teams, and messages the platform owner on Telegram when a change lands on a subject set to no compatibility checking.
How do I track which Kafka schemas changed overnight?
Every morning WebRun opens Confluent Cloud, lists the schema subjects with a version registered since yesterday, and reads each one's compatibility setting and the topics that use it. It posts the digest to Microsoft Teams and messages the platform owner on Telegram about risky changes, so downstream breaks are caught at review time.
- Schema changes are known at review time rather than at run time
- Every change arrives with the topics that consume it named
- Versions landing on subjects with checking switched off are escalated immediately
Built for data platform teams · streaming engineers · analytics engineers · SRE teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
confluent.cloudin a real browser with your saved login - no setup, no API keys. -
1
Confluent - read new schema versions
confluent.io
WebRun opens Confluent to read new schema versions. - Open Confluent Cloud and go to the schema registry for each environment you watch
- List the subjects with a new version registered since yesterday, with the version number and the time
- Read each subject's compatibility setting and note which topics use it
Done when Every schema version registered yesterday is listed with its subject and topics.
-
2
Microsoft Teams - post the change digest
microsoft.com
WebRun opens Microsoft Teams to post the change digest. - Post one line per changed subject with the new version, the environment and the compatibility setting
- Name the topics that carry the subject so consumers know whether it touches them
- Put changes on production environments above changes on staging
Done when The data team can see yesterday's schema changes in Teams.
-
3
Telegram - flag the risky changes
telegram.org
WebRun opens Telegram to flag the risky changes. - Message the platform owner when a new version lands on a subject with compatibility checking switched off
- Include the subject, the environment and the consuming topics
- Keep it internal. WebRun never registers, edits, or deletes a schema
Done when Risky schema changes have reached the platform owner.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change schemas or compatibility settings?
No. WebRun reads the registry only. Registering a version, editing a subject and changing a compatibility mode all stay with your engineers.
Does it read the message data on the topics?
No. It reads schema metadata: subjects, versions, compatibility settings and which topics use them. It never consumes records from a topic.
What if nothing changed overnight?
It stays quiet on Telegram and posts a short no-changes line in Teams, so the channel confirms the check ran without adding noise.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.