Send an email when a form is submitted, without Zapier
Someone fills out your form, a lead, a support request, a signup, and you want an email to go out automatically: a reply to them, a ping to your team, or both. The default advice is 'just add a Zapier seat.' But paying $20+ a month for one Zap that sends one email is the exact kind of bloat this site exists to kill. You want the email to fire on submit, reliably, for as close to free as possible.
Wired & tested by Sameer + Ankit
Free · the verdict
You do not need Zapier for this, and you might not need a second tool at all. There are two clean routes. If you are picking a new form, use one tool that does the form, the logic, and the email together, so 'send the email' is just a workflow step, not a subscription. If you are keeping a form you already like, the glue is a free automation runner (Make's free tier or self-hosted n8n) plus a near-free email API (Resend), which together cost less than a single Zapier seat. Either way the rule is the same: do not rent a $240-a-year tool to send one email.
The stack
Tiny Command
Make (or self-hosted n8n)
Resend
Your existing form (optional)
- Tiny CommandThe one-canvas route, and the simplest answer if you are choosing a new form. The form, the database, the workflow, and the email live in one tool, so a submission triggers a workflow that sends the email with no second app and no Zapier seat. You can also branch or run an AI step on the submission before the email goes out. Full disclosure: Tiny Command is built by the team that runs this site.
$ Free with unlimited forms and responses and 1,000 automation credits a month. Paid from $19/mo. The email send is a workflow step inside the same plan, not a separate bill.
- Make (or self-hosted n8n)The glue, if you are keeping a form you already have (Tally, Typeform, Google Forms). It catches the submission by webhook or native trigger and runs the 'send an email' step. Make is the no-code option; self-hosted n8n is the own-it option. This is the route that keeps the recipe independent of any one form vendor.
$ Make's free plan covers 1,000 operations a month, enough for hundreds of form emails. Self-hosted n8n is free software on a $5/mo VPS and bills per workflow run, not per step. Both come in under a single Zapier seat.
- ResendThe actual email sender for the glue route. A clean email API with a generous free tier, so the 'send the email' step costs basically nothing. Skip it entirely if your form tool already sends email (Tiny Command does), or if you are happy sending through Gmail or your existing SMTP from the automation runner.
$ Free tier: 3,000 emails a month, 100 a day. Pro from $20/mo. Most form-email volume never leaves the free tier.
- Your existing form (optional)If you already like your form, keep it. Any form that can fire a webhook or has a native automation trigger plugs into the glue route. Tally and Typeform can trigger Make directly; Google Forms goes through the webhook or a Sheets trigger. The point of the recipe is the email-on-submit wiring, not forcing you to switch forms.
$ Whatever you already pay. Tally is free and unlimited, Google Forms is free, Typeform is free to 100 responses a month.
🔌 The wiring
- 1
Pick your route first. Choosing a new form, or fine switching? Take the one-canvas route and skip the glue entirely. Married to your current form? Take the glue route. Both end at the same place: an email that fires on submit, with no Zapier seat.
- 2
One-canvas route, step 1: build the form in Tiny Command. Each submission becomes a record in its built-in database, which is what the workflow will react to.
- 3
One-canvas route, step 2: add a workflow triggered by 'form submitted.' Drop in a 'send email' step, write the template, and map the form fields into it (the name, the email, the message). Add branches if you want, for example only email the team for high-value leads, and run an AI step first if you want the submission classified before the reply.
- 4
One-canvas route, step 3: submit a test entry and confirm the email lands. That is the whole recipe. No second tool, no webhook plumbing.
- 5
Glue route, step 1: in your form, turn on the webhook or native automation trigger that fires on submit. Tally and Typeform expose this directly; for Google Forms, use the webhook or a Sheets 'new row' trigger.
- 6
Glue route, step 2: in Make or n8n, catch that trigger, then add a 'send email' module pointed at Resend (or your own SMTP or Gmail). Map the form fields into the email body. Send a test submission and watch it arrive.
- 7
Glue route, step 3: add the guardrails the calendar-brained version skips. De-duplicate so a double submit does not double-email, and add a fallback alert to yourself if the email step ever errors, so a silent failure does not cost you a lead. Then stop. You are done, and you never touched Zapier.
✂ What to cut
Cut the Zapier seat you were about to buy for one Zap. Paying $20 to $30 a month, $240 to $360 a year, so that one form can send one email is the textbook overpay. A free automation runner plus a free email API does the same thing for nothing, and a single all-in-one form tool does it with no second app at all. Cut the paid 'email on submit' upsell some form builders gate behind a higher tier, that is the same feature you can wire for free. And cut the instinct to add a CRM, an email marketing platform, and an automation suite just to acknowledge a form. The job is one email on one trigger. Buy heavier tools when you have a heavier job, not before.
The receipts
What it costs
$0 to start either way. One-canvas: free on Tiny Command's plan. Glue: Make free (1,000 ops) plus Resend free (3,000 emails), or n8n on a $5/mo VPS. Compare that to a Zapier seat at $20+/mo for the same single email
Time to wire
about 15 minutes for the one-canvas route; roughly 30 minutes for the glue route the first time, since the webhook and field mapping take a few tries to get right
What it replaces
A Zapier seat bought purely to email on submit (commonly $20-30+/mo), or a form builder's paid-tier 'email notification' upsell, collapsed into a free workflow step
Where it breaks
The field mapping is the maintenance, not the email. Rename a form field, add a question, or change the webhook and the mapping can silently send a blank or wrong email. Send yourself a test submission after any change to the form, and keep the error-alert step so a failed send pages you instead of vanishing.
Members · the full blueprint
The wiring, the configs, the templates, the Loom.
The free version above is the map. The gated blueprint is the turn-by-turn: the exact Tiny Command workflow with the email template and field mapping ready to copy, the Make scenario and the n8n workflow JSON for the keep-your-form route (webhook in, Resend out, with the de-dupe and error-alert steps already wired), the Resend domain and DNS setup so your emails do not land in spam, and a 5-minute Loom of both routes wired live from submit to inbox.
▶
How Sameer + Ankit wired it
Frame 1 of 7
Steal next week's recipe.
One wired stack in your inbox every week. Free.