How to Send Email When a Form Is Submitted

You’ve built a form into your site with Claude Code. Maybe it collects quote requests, event sign-ups or feedback. People are filling it in, but you’d rather see each entry arrive in your inbox the moment it comes in.

This guide shows how to send email when a form is submitted, using Claude Code and SimpleSends. You’ll get the exact message to send Claude Code, what each email should include, two sample emails, and a way to test everything before real people use the form.

If your form is a contact form, our guide to making your contact form send emails covers the details specific to contact pages.

Why doesn’t your form send email on its own?

A form can’t send email by itself. When someone presses Submit, their browser packages up what they typed and sends it to your site, and something there has to decide what happens next. Sending an email is one option, but it needs two things your site doesn’t come with:

• An email service: a company that delivers your emails and keeps a record of what was sent.
• Sending code: a small piece of code in your project that runs every time the form is submitted.

Claude Code writes the sending code. The email service is what you choose. SimpleSends is a transactional email service built for people who build with Claude Code but don’t write code. Transactional emails are the ones your site sends automatically because someone did something, like submitting a form.

Email to you vs a confirmation to the person: which do you need?

Most forms need an email to you, and most benefit from a confirmation to the person too.

The last row matters. Every email can carry a reply-to address, which tells the inbox where replies should go. Set it to the person’s address on your copy, and pressing Reply writes straight back to them. On their confirmation, set it to an inbox you read, such as hello@yourcompany.com, so their questions reach you.

What should you tell Claude Code to send email when a form is submitted?

Connect SimpleSends once, then describe the emails the way you’d brief a person.

1. Sign up on the SimpleSends website and follow the steps there to set up the email address you’ll send from. To send from your own domain, this includes adding a few DNS records where your domain is registered. DNS records are settings that tell the internet which services can send email for your domain. Our guide to choosing a sending domain and from address helps you pick.
2. In Claude Code, open Customize, then Connectors, choose Add, then Add custom connector, and fill in the details in the table below.
3. When Claude prompts you to connect, log in to SimpleSends.
4. Back in the Claude Code chat, tell Claude Code: “I’ve connected SimpleSends for all transactional email.” It takes it from there, including adding what your project needs to send email.

The connector is an MCP server, a standard way for Claude Code to work with another service while you build. Once your site is live, form emails don’t go through the chat. Your site sends them through SimpleSends using its sending code and a secret key, known as an API key, that proves the request comes from you.

Now brief Claude Code:

I’d like an email every time someone submits the quote request form on my site. Send it to hello@yourcompany.com with everything they filled in, and set the reply-to to their email address so I can reply directly. Also send them a short, friendly confirmation that thanks them, repeats what they asked for, and says we’ll reply within one business day. Check what people type in before anything is sent. Show me both emails before you build anything.

Claude Code shows you drafts of both emails, then builds them once you approve. If something isn’t right, say so in plain words:

The confirmation feels a bit formal. Make it warmer, and put the summary of their request in a list.

What should each email include?

Your copy should be quick to act on. Their confirmation should reassure them that it worked.

Keep the confirmation about their request. Anything promotional belongs in a separate email they’ve chosen to receive.

(your copy) Subject: New quote request from Maria Lopez

New entry from the quote request form, received Monday, October 5, 2026 at 2:14pm.

Name: Maria Lopez Email: maria@yourcompany.com Company size: 11–50 people What they need: A monthly plan for three teams, starting in November

Press Reply to answer Maria directly.

(their confirmation) Subject: We’ve got your quote request

Hi Maria,

Thanks for getting in touch. Here’s what you sent us:

• Company size: 11–50 people
• What you need: A monthly plan for three teams, starting in November

We’ll reply within one business day. If anything changes before then, reply to this email and it comes straight to our team.

The YourCompany team

How do you test it before real people use it?

Send test emails to yourself first, then submit the live form and check both inboxes.

1. Ask Claude Code for test versions of both emails.

   Send me test versions of both form emails at my own address, filled in with realistic sample answers.

2. Check the names, labels and layout on your phone and your computer.
3. Submit the live form yourself, using a second address you can read.
4. Press Reply on your copy and check the reply goes to that second address.
5. If an email doesn’t arrive, ask Claude Code. It can read SimpleSends send logs and delivery status, so it can tell you whether the email went out and help work out why one didn’t.

   I submitted the quote form at 2:15pm but no email arrived. Can you check whether it was sent?

For a fuller checklist, see our guides to testing your emails before users see them and checking whether an email actually sent. Form emails are one of the transactional emails every SaaS needs, and Claude Code can set the others up the same way.