SaveForm.io
Collect form submissions without a backend | saveform.io
Start new thread
Marco Ruch

SaveForm.io - Automated form tracking and e-mail notifications & webhooks

by
SaveForm.io
•
SaveForm removes the need for backend form handling with no server and no setup required. Unlike traditional solutions, it is plug and play with instant submissions to your dashboard. Built in automated emails, real time notifications, and webhook integrations like n8n, Zapier, and Discord come standard. A generous free tier of 100 submissions per month makes it ideal for simple sites without complexity.

Add a comment

Replies

Best
Marco Ruch
Maker
đź“Ś
I kept running into the same issue: building simple websites that didn’t need a backend… except for one thing, forms. Whether it was a small SaaS, a personal project, or a client site like a flower shop, everything could be static, but you still need a clean way for users to reach out. Setting up a backend just for that always felt like overkill. That’s why I built SaveForm. It lets you handle form submissions with just HTML or simple frontend JavaScript. No server, no setup. You still get a clean dashboard, email notifications, auto replies to users, and webhook integrations like Discord, n8n, or Zapier to automate workflows. Curious how others are currently handling forms on simple or static sites.
Curious Kitty
Webhooks are where simple form backends become workflow infrastructure: how do you handle webhook auth (signatures/tokens), retries, and per-destination delivery logs—especially when receivers are slow or flaky—and how does that compare to what you found lacking in tools like Formspree/Basin/Getform?
Marco Ruch
Maker

@curiouskittyWe've been pretty intentional about not going all the way down the complexity rabbit hole yet that the other tools lean into.

The core idea (for now) remains that it should be dead simple to use, use saveform.io if you are happy to receive an E-Mail notification or a discord/slack ping. n8n, zapier, slack workflows are optional upgrades which were requested by some users, they're as of now very minimal with a retry mechanism and are by design optional opt-ins and not required.

Deliverability you can see directly in your dashboard. Should a webhook fail, as you can aswell see the spam-protection etc.

In regards to signature and tokens, You can indeed add in headers, that's configurable on a per form basis. But we're intentionally avoiding heavy signature schemes because most users don't actually need that complexity on day one and generally yet.

That said, there's features on the roadmap to do, such as templates for forms and more. But we're trying to stay very minimalistic as of now - drop in URL is the main thing we are trying to help with.

Hope that explains your question :).

BRICE EKUKA

The 'everything could be static except forms' problem is one of those things every developer hits and then builds a workaround for that they are not proud of. I ran into the exact same thing building DocMetrics — you just want a contact form or a waitlist signup and suddenly you are spinning up a whole backend for one endpoint. The flower shop example is perfect because it describes 80 percent of real client projects. The webhook integrations with n8n and Zapier are what make this production ready rather than just a toy. Congrats on shipping something genuinely useful. To answer your question — before finding proper solutions I was using Google Forms embedded in pages which works but feels wrong every single time.