I haven’t implemented it myself (yet), but you gave me an idea with the event triggered functions bullet point! It may make for a great article on the Netlify blog as well.
In theory, a user could utilize an event triggered function to handle some conditional logic behind the scenes when a form is submitted.
In combination with the Netlify Email integration, an email could be fired off to a certain individual or group based on data in the form.
For example:
If the user selected “Sales” in a dropdown, send the form submission to sales@domain.com
If the user selected “Customer Support”, then send it off to support@domain.com
This could be taken one step further by bringing Supabase into the mix or another database tool. Allowing you to pull any existing information you have on the form submitter and adding it to the internal email.
If you want to take it even further, you could use the Netlify Edge Function and the HTMLRewriter to store information on the form submitter in hidden form input fields. For example - their country, referrer, etc. This would be great immediate context for logging submissions in a CRM. While this can be achieved with clientside Javascript, it is not always 100% accurate, and it wouldn’t work for users who have JS disabled as well.
Another use-case for the event triggered function could be using the OpenAI Moderation API to automatically delete a submission if it triggers a red flag. This would be useful for a blog post comment submission form or customer feedback form. This could also be achieved using no-code, through Netlify’s Zapier integration and OpenAI’s Zapier integration.
Aside from form submissions, the event triggered functions could also be used in tandem with a tool like LogSnag when a site deploy fails. You can use LogSnag to track the number of times a site deploy has failed and even have it send a push notification to your desktop or mobile device.
Scheduled functions could be used to have your “own” uptime monitoring configuration as well. You can have one check if your site is still live on an hourly basis and when an error code is returned, notify the respective individual(s) using the Netlify Email Integration.
Alternatively, you could use a third-party uptime monitoring tool and still combine it with a Netlify function. Most, if not all, tools allow you to specify a webhook URL when your site goes down. You could add your Netlify function endpoint here and then essentially extend the functionality of that tool. If they don’t for example, support sending you a Slack message, you can have the Netlify function handle that.
Or you could (again) use the Netlify Email Integration to notify your customers about the downtime, with an entirely custom-branded email sent from your email address. As opposed to being restricted by the style customization limitations offered by the tool with their email notifications.
If you want to really have some fun, you could have a button added to the Slack message or an internal email that lets you roll back a site deploy using the Netlify API. You can have the button link to a Netlify function endpoint and when it’s done running, have it send you to your site or the Netlify dashboard. This way, if you make a change that breaks your site, you can rectify it immediately.
