Beginner guide / Forms & automation

Get an email when someone submits a Tally form

Build a client inquiry form in Tally and send yourself an email through Make and Resend. The only email credential Make needs is a Resend key with sending access.

Before you start

Use accounts on Tally, Make and Resend. For the first test, use the email address associated with your Resend account. Gmail can receive the message like any other email. This workflow needs no Gmail connection or inbox permissions.

Tally → Make → Resend → Your inbox
24-second demo

Watch a form submission turn into an email

Follow the sample submission from Tally to the delivered email. The video includes English narration and on-screen captions.

Make starter template

Start with the ready-made scenario

Download the Make blueprint (.json)

  1. Open a new scenario in Make. From the More menu, choose Import blueprint and select the downloaded JSON file.
  2. Open Tally → Watch New Responses and create a webhook for your own form. Follow steps 1 and 2 below. Use the exact field labels Name, Email and Request, or remap them in the Resend module.
  3. Open Resend → Send an Email and add your own send-only connection and a fixed recipient as shown in step 3. The blueprint already maps the three answers to Text Content.
  4. Save the scenario and use Run once to test a fresh submission before switching it on.

The download contains the two modules and their field mappings. You supply your own webhook, API key and recipient.

Step 01

Create the form in Tally

  1. Create a new form called Client Inquiry.
  2. Add a short-answer field for Name, an email field for Email and a long-answer field for Request. Mark all three as required.
  3. Publish the form and open its share link. Try to submit with a required field blank. Confirm that Tally asks you to fill it in.

Checkpoint · The share link opens and incomplete submissions are blocked.

Step 02

Connect Tally to Make

  1. In Make, create a new scenario. Add Tally → Watch New Responses as the first module.
  2. Create a webhook. When Make asks for a connection, choose Tally OAuth, sign in and review the requested access before authorizing it.
  3. Select Client Inquiry as the form and save the module.
  4. Click Run once. Submit the sample below through the published form, then open the output bubble above the Tally module. Check that the three answers are present.
Sample submission
Name: Alex Example
Email: [email protected]
Request: Please send me your workshop schedule.

Checkpoint · Make shows one captured submission. This first run gives you sample fields to map in the next step.

Step 03

Connect Resend with a send-only key

  1. Open API Keys in Resend and choose Add API Key. Name it Make form notifications and select Sending access under Permission. For a production sender on your own verified domain, you can restrict the key to that domain.
  2. Click Add and copy the new key. Resend shows the full key only when you create it. Keep it private and paste it directly into the Make connection.
  3. In Make, add Resend → Send an Email directly after Tally. Next to Connection, click Add. Give the connection a name, paste the key into API Key and click Save.

Configure the first notification

  • From · [email protected]
  • To · Click Add item and enter the email address associated with your Resend account. Keep this fixed so form visitors cannot choose the recipient.
  • Subject · New Tally submission — test
  • Send Email As · Choose Plain Text. In Text Content, enter A new Tally submission triggered this test email.

Save the module and the scenario. The test sender can send only to your Resend account email. To send to other addresses, verify a domain in Resend and use a sender address on that domain.

Step 04

Test from form to inbox

  1. Click Run once. If Make shows items already in the webhook queue, choose Wait for new data.
  2. Submit the published Tally form again with sample data. In Make, confirm that both the Tally and Resend modules completed.
  3. Open Emails → Sending in Resend and look for the test subject. Delivered means the receiving mail server accepted it. Check your inbox and spam folder to confirm where it landed.
What BuildApp.blog tested

A fresh Tally submission triggered a manual Make run. Resend recorded the notification as Delivered to Gmail, and its message preview showed the submitted name, email and request. We also checked that the downloadable blueprint imports into a blank Make scenario.

Include answers in future notifications

After the basic delivery test, use Make’s mapping panel in Text Content to insert each answer from Tally. Save and run a fresh test to check the mapped values.

Example message layout
Name: [map the Name answer]
Email: [map the Email answer]
Request: [map the Request answer]

Troubleshooting

  • Tally never fires. Check that the webhook points to the published form you opened. Start Run once before submitting.
  • Resend rejects the recipient. Check that the test sender is paired with the email address associated with your Resend account.
  • Resend rejects the key. Check that you saved the intended connection and that its sending key is active and allowed to use the sender domain.
Step 05

Turn the automation on

After the manual test, activate the scenario with Immediately as data arrives. Submit a new sample and check Make’s History and Resend’s delivery status. One submission should produce one notification without pressing Run once.

Want help with your setup?

Tell us what your form should do and where the email should go. We’ll reply by email about setting up the workflow for you.

Get help setting this up

Official references

← Explore the tool directory