A newsletter signup that emails you each subscriber

When you want this form

Readers who finish a post are the ones most likely to want the next one. A small subscribe box right where the content ends — or always present in the footer or sidebar — catches them at that moment, and one email field is all it takes.

If your blog is static — plain HTML on any host — it can't receive the form POST itself. Form2Email receives it and emails you the address, and you add it to whatever tool actually sends your newsletter.

The form

Paste this into your page and replace your-token with the token from your endpoint (setup below):

<form action="https://form2email.terragohan.com/f/your-token" method="post">
  <label for="email">Get new posts by email</label>
  <input id="email" name="email" type="email" required>

  <!-- optional: your own thank-you page after submit -->
  <input type="hidden" name="_redirect" value="https://yoursite.com/thanks">

  <button type="submit">Subscribe</button>
</form>

That's the whole integration — small enough to sit in a sidebar or footer partial. Only the action, method="post", and the input name attributes matter to Form2Email; style it to match your site.

Set it up

1. Create the endpoint

   Use the tool on the homepage — or POST https://form2email.terragohan.com/api/endpoints — with the email that receives submissions and the exact domain this form lives on.

2. Verify the email

   We send a verification link to the destination address — single-use, valid 24 hours. Nothing is accepted until a human clicks it. Add form2email@terragohan.com to your trusted senders.

3. Point the form at it

   Put your public URL in the form's action. Submissions are only accepted from the domain you registered — exact hostname match, subdomains need their own endpoint.

4. Keep it alive

   Endpoints stay active for 7 days after verification. Extend for free (+7 days, as often as you like) from your manage page — extending also revives an expired endpoint.

What lands in your inbox

Each submission becomes one email to your destination address:

• Reply-To is the subscriber's email, so you can reply to them directly.
• The address also appears in the body, ready to copy into your newsletter tool.
• Any other fields you add (a first name, a topic checkbox, anything) are listed as additional fields.

With _redirect set, the subscriber's browser is sent to your thank-you page after a successful submit — a 303 redirect. Without it they get a small JSON response — fine for JavaScript-driven forms, less friendly for plain HTML.

Tips

• Keep it to one field. Email only — every extra field costs you subscribers, and you can ask for a name later.
• Put the box where readers finish content: the end of each post, the footer, or the sidebar — not a popup the moment they arrive.
• Make the button say what happens: "Subscribe" or "Get new posts by email", not "Submit".
• Use _redirect to send subscribers to a thank-you page that tells them what to expect and how often you write.
• Add form2email@terragohan.com to your contacts so the verification and signup emails don't land in spam.

Limitations

• Form2Email is not a newsletter service: no double opt-in, no list management, no sending campaigns. You get one email per signup and add the address to your newsletter tool yourself — check that tool's consent requirements before importing.
• Subscribers get no confirmation email — Form2Email only ever emails you, the endpoint owner. Your thank-you page is where you set expectations.
• The endpoint expires 7 days after verification — extend it for free from your manage page as often as you like (extending also revives an expired endpoint), or ask the operator for a permanent endpoint.
• Submissions are accepted only from the exact domain you registered. If your blog answers on both yoursite.com and www.yoursite.com, register the one your form is served from (or create one endpoint per hostname).
• Spam protection is origin checks plus per-IP rate limits (30 submissions a minute, with exponential backoff) — there is no CAPTCHA or honeypot, so skim the addresses before you import them.

Keep reading

• Waitlist form — the same single email field, for a coming-soon or pre-launch page.
• Feedback form — when you want ratings and comments, not just an address.
• How it works — the endpoint lifecycle and security model in detail.