Snapdiff
The easiest way to monitor websites ⚡️
When a monitor change is detected, Snapdiff is now triggering webhooks. This implementation is still on early stages, but this already allows users to integrate Snapdiff with their own systems.
The next steps for webhooks will be to add a report system in the UI and allow users to retry events manually (or through a future public API)
Once a monitor is added and ran for the first time, the registered e-mails are notified. Besides, it not only sent e-mail alerts on changes, but it includes a small diff of what changed on the desired website.
There are always some lessons around third-party integrations. For this e-mail integration, template rendering quirks and error debugging were quite a tricky.
-
1
Let me try this scripts for my review blog that hosted on WordPress. I'm running a project of telecomando universale.
-
1
Sorry, I discontinued Snapdiff. There are some tools in the market that do similar things though 😉
-
Released an alpha version of the web app, together with the first version of our website differ algorithm.
I guess the hardest bits were setting up infrastructure, metrics and alerts and so on. These usually come as guaranteed when working as an employee, but is a bit different when you are bootstrapping a project.
The landing page contains a "Sign-up for early access" CLA which sends the access to the web app. Hopefully will get some feedbacks from it.
3 Comments
Nice job! Coincidentally, I am working on a v2 version of web hooks on StatusGator today. We've had requests for more sophistication so I'm trying to get something simple up and running on this rainy Sunday.
One thing I would recommend is having a Test button in the web UI so people can trigger a test after they configure it. You will also need to have versions eventually with something like a drop down in the UI to choose. This is what I am adding right now. I don't want to change the format of the web hook suddenly on all the people who have been using it as-is for the last 5 years.
Funny that I was preparing a backlog of technical tickets I want to focus on next and one of them was exactly a Test button for my monitors and for the webhooks 😅
What you mean by "You will also need to have versions eventually with something like a drop down in the UI to choose. "?
Again, thanks for the feedback 😉
If you ever change the format of the web hook, IE: the payload JSON changes or something similar, then you will want your users' integrations to keep working. So you will need to allow them to choose a version. That's what I just today in my project:
Then I added a drop down in our configuration UI so that each user can choose what version of the web hook they want. Everyone who is already using web hooks will have version 1, the old version. Everyone who starts using web hooks today will default to version 2. That way, nobody breaks.
You wouldn't technically need to implement this until some time in the future if and when you ever change the web hook payload.