Have access to Tally, Make and a Gmail account you can use to send a test email. You’ll need permission to connect Tally and Gmail to Make. Use sample data while you set up the automation.
Create the form in Tally
- Create a new form called Client Inquiry.
- Add a short-answer field for Name, an email field for Email and a long-answer field for Request. Mark all three as required.
- 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.
Connect Tally to Make
- In Make, create a new scenario. Add Tally → Watch New Responses as the first module.
- Create a webhook. When Make asks for a connection, choose Tally OAuth, sign in and review the requested access before authorizing it.
- Select Client Inquiry as the form and save the module.
- 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.
Name: Alex Example Email: alex@example.com 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.
Send the details to your inbox
- Add Gmail → Send an email after Tally. Connect the Gmail account you want to send from and review the access Make requests.
- In To, enter an email address you control. Use a fixed address so this scenario sends an internal notification to you.
- Set the subject to New client inquiry. Choose Collection of contents for the body and add a text item.
- Type the three labels below. After each label, use Make’s mapping panel to insert the matching answer from the Tally module. Save the module and the scenario.
Name: [map the Name answer] Email: [map the Email answer] Request: [map the Request answer]
Checkpoint · The body contains mapped fields from Tally. The recipient is your fixed inbox.
Run an end-to-end test
- Click Run once again. Send a fresh submission and change the request to BuildApp test 002 so you can distinguish it from the first run.
- Check the output of both modules in Make. Then check your inbox for one email with the new request text, the name and the email address.
- Try one more submission with a required field blank. The form should block it and your inbox should receive no new notification for that attempt.
- Tally never fires. Check that the selected form matches the share link you opened, then start Run once before submitting.
- The email arrives with blank fields. Inspect the Tally output and remap each field to its answer value.
- Make reports a Gmail error. Open the failed run and read the module error. Check the connection and the recipient, then send a fresh test.
- Make succeeds but you see no email. Check Spam, your Gmail Sent folder and the exact recipient address.
Turn the automation on
Once the manual test passes, activate the scenario. For this webhook trigger, use Immediately as data arrives if Make asks for a schedule. Submit one last sample with the scenario on, then confirm it appears in History and reaches your inbox without pressing Run once.
You’re done when · One valid submission sends one email with the correct details while the scenario is active.
Verification · Steps reviewed against official documentation. Live delivery through a connected Gmail account has yet to be independently tested by BuildApp.blog.