Point the action at an Etariosk Form endpoint and every submission lands in your inbox — stored, spam-filtered and searchable. No server to run, no SMTP account to configure, no database to back up.
Free while it’s small: 300 emails a month, every submission stored.
<form action="https://forms.etariosk.com/f/a1b2c3" method="POST"> <input name="email" type="email" required> <textarea name="message"></textarea> <input type="hidden" name="_key" value="ef_live_••••••••"> <button type="submit">Send</button> </form>
It accepts multipart/form-data, urlencoded and JSON, so the transport is your choice.
<form action="https://forms.etariosk.com/f/a1b2c3" method="POST"> <input name="email" type="email" required> <textarea name="message"></textarea> <input type="hidden" name="_key" value="ef_live_••••••••"> <input type="hidden" name="_redirect" value="https://yoursite.com/thanks"> <button type="submit">Send</button> </form>
No form builder, no analytics, no CRM. What it does do, it does properly.
Every form gets its own URL and API key. Rotate a key without touching the others; retire a form and its endpoint stops accepting anything.
An address receives nothing until its owner clicks a confirmation link. That's what stops the sending domain being aimed at a stranger's inbox.
Invite people as admins or viewers. Viewers read forms and submissions; they never see an API key or a button that would only fail.
Honeypot fields and per-IP flood detection as standard; strict adds link and language heuristics. Spam is stored and labelled, never silently dropped.
Pin a form to the domains you actually publish it on, and a key lifted from your HTML is useless anywhere else.
Every submission is stored with its payload, origin, delivery status and message ID — searchable, filterable, and readable long after the email is buried.
Add _redirect and the browser lands on your thank-you page; leave it off and you get JSON back. Same endpoint either way.
A machine-readable guide at /llms.txt and a copyable prompt pre-filled with your endpoint, so an AI coding agent can wire it up unattended.
Your Google address becomes the first delivery address, already confirmed. Nothing else to configure.
Every account is reviewed by hand — usually inside a day. It's what keeps the endpoints from becoming a spam relay.
Your workspace starts with one form, one URL and one key. Add more forms whenever you need them.
Any HTML form works — static sites, landing pages, docs. Submissions arrive as email and appear in your dashboard.
Stored first, always — before any spam check or quota maths runs.
Honeypot, flood detection and, on strict, link and language heuristics.
Emailed to every confirmed address. One submission costs one email, however many addresses that is.
Delivery status, message ID and any error land on the submission, so a failure is visible rather than lost.
Jekyll, Astro, Hugo, a hand-written index.html on GitHub Pages — no build step, no JavaScript.
Waitlists and enquiry forms that need to work the hour they go up, not after a backend exists.
“Was this helpful?” and feedback boxes, without wiring a docs generator to a database.
Hand a site over with a working contact form and no server for anyone to maintain afterwards.
Small request and intake forms where standing up a service would cost more than the form is worth.
A generated app can be wired to a real, live inbox in the same pass that writes the markup.
There’s a monthly email quota, and this is exactly what it does.
Per organization, not per form. Ask for more from the dashboard and it's raised by hand — there's no plan to upgrade to, because there are no plans.
Fanning out to five confirmed addresses still costs one. The quota counts submissions forwarded, not messages sent.
Storage isn't metered and isn't gated. Past the email quota the endpoint still returns 200 and still records everything — only the forwarding pauses.
The endpoint never returns 429. A form on your live site should not start failing because a month was busy.
Pasting this prompt into Claude Code, Cursor, or similar hands an agent everything it needs to integrate Etariosk Form — no hand-holding.
Add Etariosk Form to the form(s) in this project so submissions arrive as email. Read the integration guide at https://forms.etariosk.com/llms.txt and follow it exactly — reuse my existing form markup where one already exists rather than replacing it, or create a minimal new one per the guide if there isn't one yet. My endpoint: <your-endpoint> My API key: <your-api-key>
Sign in and get approved first — this exact prompt is pre-filled with your real endpoint and key on your . Agents can also read the guide directly at forms.etariosk.com/llms.txt.
An open form-to-email service is a spam relay with extra steps. Reviewing accounts is the cheapest thing that stops that, and it usually takes under a day. If someone invites you to their organization, you skip the queue entirely.
No passwords to store, leak or reset, and the address you sign in with is one Google has already verified — which is why it becomes your first delivery address without a confirmation email.
Submissions keep arriving and keep being stored; the forwarding email pauses. The endpoint still returns 200, so nothing on your site breaks, and the dashboard shows exactly what wasn't delivered and why.
Not today. Mail goes out from the Etariosk Form sending domain with the submitter's address as reply-to, so hitting reply in your inbox answers the person who filled in the form.
Yes — every field, exactly as posted, so you can go back to it long after the email is buried. You can delete any submission from the dashboard, and retiring a form stops new ones at the endpoint.
The submission is already stored by then; the failure is recorded on it and shown in the dashboard. That ordering is deliberate — a bounced email should never be the same thing as a lost enquiry.
No. Keys are stored hashed, so a key is shown once, when it's created or rotated. Lost it, rotate it — the old one stops working immediately.
That's the main thing it's for. A plain HTML form on GitHub Pages, Netlify, Vercel or an S3 bucket needs no JavaScript and no build step to use this.
Sign in with Google, wait for approval, paste the endpoint. Nothing to install, and nothing to keep running afterwards.