4 ms·
Clever, but I wonder who the target demographic is. We're lucky to be in an era that has too many options for backend integration, both self-hosted and cloud,
by peteforde 7y ago
Clever, but I wonder who the target demographic is.
We're lucky to be in an era that has too many options for backend integration, both self-hosted and cloud, "monolith" and microservice.
I can't help but feel that anyone who can set up something to receive webhook notifications would likely just cut out the middleman.
People who don't know what a webhook is have SurveyMonkey and Google Forms.
What am I missing?
- icebraining 7y agoIf this lets you configure how the webhook is sent, you might not need to set anything up. Example: form is posted to Formcake, which then sends a webhook to Twilio that sends an SMS to the inserted number (for validation). The Zapier integration, on the other hand, is even more flexible. Using a similar service, I built a fully static website for a Mother's Day campaign, where the form was processed by a Zapier action that added the info as a row to a Google Sheet. No custom backend at all.