Build a No-Code Task Intake Automation

Create a form that stores task requests and emails you alerts with Zapier.

Introduction

30 Second Summary

Requests often arrive through scattered messages. A task can be saved in a list but still go unnoticed when nobody checks it.

In this project, you will build a no-code task intake automation with Zapier. Each browser submission will become a stored record before a Gmail alert reaches your inbox.

What You'll Build

A realistic request will travel from your browser form to a reviewable table before arriving in your inbox as a matching email.

By the end of this project, you'll have:

A shareable task-intake form in Zapier Forms where people can submit a task title, details, requester name, and priority.
A reviewable request table in Zapier Tables where every submission appears as a structured record.
A published automation that sends a Gmail alert for each new request. Its visible run history proves the workflow processed the request.
Secret Mission: Personalize the email subject with the submitted priority and task title.

Are there any prerequisites?

You'll need a Windows computer with internet access plus a Google account with Gmail. No coding experience is required.

Before We Start

Before you touch the tools, choose a real kind of request for your task-intake system to collect. This gives every form field a clear purpose and defines which submitted details need to reach your Gmail notification.

Set Up Zapier and Connect Gmail

Your task-intake system needs a reliable browser session before any form or workflow can exist. Microsoft Edge gives you access to Zapier on your Windows computer.

Gmail must authorize Zapier before the automation can send task alerts from your chosen account. This step establishes that permission.

In this step, get ready to:

Open Zapier in Microsoft Edge.
Access an existing Zapier account or create one.
Authorize your chosen Gmail account for Zapier actions.

Open Zapier in Microsoft Edge

Zapier runs in your browser. First, you need to confirm that Microsoft Edge is available on your computer.

Select Start on the Windows taskbar.
Type Microsoft Edge into the search box.
Choose the tab that matches your search result.

✔️ Microsoft Edge appears

Select Microsoft Edge from the search results.
Enter https://zapier.com/sign-up into the address bar.
Press Enter.

ⓧ Microsoft Edge is missing

Visit the official Microsoft Edge download page.
Install Microsoft Edge by following the instructions on the download page.
Press the Windows key to reopen search.
Type Microsoft Edge into the search box.
Select Microsoft Edge from the search results.
Enter https://zapier.com/sign-up into the address bar.
Press Enter.

You'll see Zapier's signup page or your existing Zapier account. Either view proves that Microsoft Edge can reach Zapier.

Can't reach Zapier in Edge?

Check that your Windows computer has an active internet connection.
Enter https://zapier.com/sign-up into the address bar again.
Restart Microsoft Edge if the page remains blank.

Help me troubleshoot why Zapier is not opening in Microsoft Edge. You can also ask the Zapier Community.

Access your Zapier account

Your Google email may already belong to a Zapier account. The signup page will either open that account or guide you through creating one.

Use your Google email address to continue from the signup page.
Choose the tab that matches what Zapier shows next.

✔️ My Zapier account opens

Sign in with your Google account if Zapier asks you to authenticate.
Continue until your Zapier workspace opens.

ⓧ I need to create an account

Create your Zapier account with your Google email address.
Complete any account verification prompt shown by Zapier.
Continue until your Zapier workspace opens.

Your Zapier workspace is now accessible in Microsoft Edge. That gives the rest of the project a stable place to build.

What happens after the trial?

A new Zapier signup starts with a 14-day trial of premium features. Those premium features stop being available if you do not upgrade.

This project uses one trigger plus one action. That two-step workflow shape is supported by Zapier's Free plan.

Connect your Gmail account

An app connection gives Zapier permission to use another service. For this project, the Gmail connection provides permission to send your task notifications.

Select Apps from Zapier's navigation.
Select + Add connection.
Search for Gmail.
Select Gmail from the search results.
Select Add connection.

The permission screen can feel sensitive because it gives Zapier access to send the Gmail alerts you configure.

Confirm that the Google sign-in screen shows your chosen Gmail account.
Sign in to that Gmail account if prompted.
Grant the requested permission to Zapier.

Before you check, where do you expect the newly authorized app to appear in Zapier?

Return to the Apps page in Zapier.
Locate Gmail among your connected app accounts.

You'll see Gmail listed as a connected app account. You've cleared the authorization hurdle that lets your future workflow send email.

Gmail connection not appearing?

Allow the Google sign-in pop-up in Microsoft Edge.
Repeat the connection from + Add connection.
Check that the permission screen shows your chosen Gmail account before granting access.

Help me troubleshoot my Gmail connection in Zapier. You can also ask the Zapier Community.

Your Gmail connection is ready. Next, you'll build the form that captures each new task request.

Build the Task Intake Form

Your Gmail connection is ready inside Zapier. The automation still needs structured request data before it can send a useful alert.

A visible form plus a stored test record gives you a working first version of the system. This proves the intake path before any automation is added.

In this step, get ready to:

Create a blank form project named Task Intake.
Connect the form to a table named Task Requests.
Submit a sample request to verify that form responses reach the table.

Create a blank form project

Zapier Forms gives you a browser-based page for collecting requests. A blank project starts with a placeholder form that you can shape around your use case.

Switch back to Microsoft Edge.
Use Zapier's left navigation to open Zapier Forms.
Select + Create.
Choose Blank form.

You'll see a new project with a placeholder form on the canvas.

Select the project title at the top of the canvas.
Enter Task Intake as the project name.

You'll see Task Intake as the project title above the form canvas.

Why Zapier Forms?

Zapier Forms keeps the request page in the same browser workspace as its stored data. That creates a short path from submission to stored row.

This browser-based approach avoids local infrastructure. You can focus on the data flow behind the automation.

Add request fields and connect storage

Each field gives one part of a request a consistent label. A connected Zapier Tables table stores every submission as a record.

Select the Form component on the canvas.
Select Fields in the editor panel.
Add a field named Task Title with + Add field.
Add a field named Details with + Add field.

The form canvas now shows fields for the task name plus its supporting details.

Add a field named Requested By with + Add field.
Add a field named Priority with + Add field.

Your form now presents all four request fields in one place.

Open the Data tab in the Form component's editor panel.
Select Create Table.
Enter Task Requests when Zapier asks for the table name.

You'll see Task Requests listed as the connected table for the form. Each future submission now has a storage destination.

Table not connected?

Return to the Form component in Task Intake.
Open Data to confirm that Task Requests is listed.
Select Create Table again if no connected table is listed.

Help me fix the connection between my Zapier form and table.

Submit and verify a sample request

Testing uses one realistic submission to prove that every field reaches storage. This gives you a known-good record before a workflow uses the data.

Select the form link at the top right of the Task Intake project.
Enter Prepare weekly report in the Task Title field.
Enter Summarize this week's progress for Friday in the Details field.

Your sample now has a clear task plus the context needed to complete it.

Enter Alex in the Requested By field.
Enter Medium in the Priority field.

Before you submit, do you expect these four values to arrive in one table row? Keep that prediction in mind.

Submit the form.

You'll see a confirmation that Zapier received the response.

Return to the Task Intake editor tab in Microsoft Edge.
Select the Form component.
Open the Data tab.
Open the connected Task Requests table.

You'll see a new row containing Prepare weekly report, Summarize this week's progress for Friday, Alex, plus Medium.

Sample row missing?

Refresh the Task Requests table.
Confirm that the submitted form belongs to the Task Intake project.
Reopen the form link if the submission did not complete.
Submit the sample request again after all four fields contain values.

Help me find why my Zapier Forms submission is missing from Task Requests.

The stored row proves that the intake path works. The shareable form link is the reusable entry point for future requests.

Return to the Task Intake form project tab.
Select Share at the top right.
Store the shareable form link here for later tests: your Task Intake form link.

Before your final check, do you expect the newest table row to match every value from the form? Keep that prediction in mind.

Return to the connected Task Requests table through the Data tab.

You'll still see one sample record with the same task title, details, requester, plus priority that you submitted.

Your first intake loop works. Each browser submission now lands as a structured record in Task Requests.

Next, you'll test what happens when nobody is watching the table for new requests.

Confirm the Missing Alert

Your Zapier Forms project already turns each submission into a row in Zapier Tables. The form-to-table path captures requests reliably.

A stored request can still sit unnoticed. This step tests whether storage alone creates a Gmail alert.

In this step, get ready to:

Submit a second realistic task through Task Intake.
Confirm the request appears in Task Requests.
Check Gmail for a matching task alert.

Prepare a fresh test request

A second realistic submission gives you fresh data for this test. Specific values make the request easy to recognize in every destination.

Switch back to the Task Intake form tab in Microsoft Edge.
Enter Book dentist appointment in the Task Title field.
Enter Schedule an appointment for next month in the Details field.
Enter Alex Morgan in the Requested By field.
Enter Medium in the Priority field.
Submit the completed form.

You should see the form confirm that your response was submitted.

Form not confirming the submission?

Check that each of the four form fields contains a value.
Retry the submission after correcting any empty field.

Ask for help with the form submission.

Trace the request into Task Requests

A record is a structured set of values stored as one table row. Matching all four values proves the form preserved the request correctly.

Switch back to the Zapier tab that contains Task Requests.
Locate the newest row in Task Requests.
Compare its Task Title with Book dentist appointment.
Compare its Details with Schedule an appointment for next month.
Compare its Requested By value with Alex Morgan.
Compare its Priority with Medium.

Good checkpoint. The second request now exists in Task Requests with the same four values.

Cannot see the second record?

Confirm that you are viewing the Task Requests table.
Reload the table to request its latest records.
Return to Task Intake if the form did not confirm the submission.

Ask for help tracing the missing record.

Test whether storage sends an alert

Storage answers whether the request was captured. Notification answers whether the right person learns about it.

Before you check Gmail, predict whether storage alone has created a task alert.

Return to your signed-in Gmail account in Microsoft Edge.
Refresh your Gmail inbox.
Check the newest messages for an email about Book dentist appointment.

You should find no task alert for Book dentist appointment. The request exists only in Task Requests.

You found the exact gap this test was designed to expose. No notification Zap exists to send the stored record through a Gmail action.

Seeing a message that looks related?

Compare the message with the exact task title from your second submission. A general Gmail message does not count as a task alert from this project.

Ask for help identifying the message.

Your form captures requests reliably. Next, you will connect that working intake path to an automatic Gmail alert.

Automate Gmail Alerts

Your second request proved that the form stores data reliably. The missing email showed that someone still has to check the table manually.

Now you will build a Zap that connects a Zapier Forms submission trigger to a Gmail action. Each new form submission will create an inbox alert.

In this step, get ready to:

Create a Zap from the Task Intake form.
Configure a Gmail alert with mapped request details.
Prove the published workflow with a live submission.

Create the form trigger

The trigger decides which event starts the workflow. A new submission to Task Intake will start this Zap.

Return to the Task Intake project in Zapier.
Select the Form component.
Select Edit.
Open the Action tab.
Select + Add action.

You will see the settings that define which form event creates the workflow.

Confirm Task Intake is selected as the form.
Set the submission event to Form Submission Created.
Select Create Zap.

You will see the Zap editor with Zapier Forms configured as the trigger.

Enter Task Intake Gmail Alert in the Zap name field.

The editor now identifies the workflow as Task Intake Gmail Alert.

Select the Zapier Forms trigger step.
Start the trigger test.
Compare the returned values with the latest record in Task Requests.

You should see the stored values from your most recent form submission. The values should match the latest Task Requests record.

Why use a two-step Zap?

A Zap starts with a trigger. Each following action performs work with the trigger data.

This project uses one trigger plus one action. That shape fits the Free plan's two-step workflow limit.

Can't find your form data?

Confirm the trigger points to the Task Intake form.
Return to the shared form from earlier if the trigger has no recent sample data.
Submit another sample request before running the trigger test again.

Help me fix a Zapier Forms trigger that cannot find my recent Task Intake submission.

Configure the Gmail action

Field mapping carries values from the trigger into another step. Your Gmail action will use the submitted task details to build a readable message.

Select the Action step in the Zap editor.
Select Gmail as the app.

You will see the actions that Gmail can perform with your connected account.

Choose Send Email as the action.
Select the connected Gmail account from earlier.

The email configuration fields will appear below the connected account.

Enter your own Gmail address in the To field.
Enter New task request as the fixed subject.

The message now has a destination plus a subject that stays the same for every request.

Select the email body field.

The field picker lets you insert values returned by the Zapier Forms trigger.

Build the first email-body line as Task Title: followed by the mapped Task Title value.
Build the second email-body line as Details: followed by the mapped Details value.

The body now shows two labelled dynamic values from the trigger.

Build the third email-body line as Requested By: followed by the mapped Requested By value.
Build the fourth email-body line as Priority: followed by the mapped Priority value.

The email body now contains all four submitted values. Each new run can fill those lines with different trigger data.

Testing the action sends a real email to your own inbox. The test does not use one of your monthly tasks.

Before you test the action, which values do you expect the email to copy from the selected form record?

Select Test step.

You should see the action result under Data out.

Switch back to Gmail in Microsoft Edge.
Open the newest message with the subject New task request.

The email body should contain the four values from the trigger test. You have now proved that the Gmail action can send mapped request details.

Didn't receive the test email?

Confirm the connected Gmail account is still selected in the action.
Check that the To field contains your complete Gmail address.
Confirm each email-body line contains a mapped trigger value.

Help me troubleshoot a Zapier Gmail Send Email test that did not reach my inbox.

Publish and verify the automation

Publishing activates the Zap for new data created after publication. Its run history records how each submission moved through the workflow.

Select Publish in the Zap editor.

Zapier will confirm that the workflow is published. The Zap is now ready to process a new form submission.

Before you submit a fresh request, do you expect the same task details to appear in the table, the inbox, and Zap History?

Return to the shared Task Intake form from earlier.
Enter Send project update in the Task Title field.
Enter Email the weekly progress summary in the Details field.
Enter Alex in the Requested By field.
Enter Medium in the Priority field.
Submit the form.

Return to the Task Requests table.
Find the row whose task title is Send project update.

You should see a fresh row whose values match the request you just submitted.

Return to Gmail in Microsoft Edge.
Open the newest message with the subject New task request.

You should see the fixed subject New task request. The body should show the four values from your fresh submission.

Return to Zapier in Microsoft Edge.
Open Zap History.
Select the newest run for Task Intake Gmail Alert.

You should see that the newest run completed successfully. Its details should show the fresh trigger values reaching the Gmail Send Email action.

Missing the live Gmail alert?

Confirm the Zap remains published.
Check the Task Requests table for the fresh record.
Inspect the newest Zap History run to locate the step that stopped processing.

Help me diagnose why my published Task Intake Gmail Alert Zap did not send a live email.

That is the missing loop closed. A new request now creates a table record, sends a matching Gmail alert, and leaves proof in Zap History.

Secret mission

Put Priority in the Email Subject

A fixed subject hides the urgency of a request until you open the message. Update your live workflow so every Gmail subject shows the submitted priority beside the exact task title.

Clean Up Your Resources

Choose whether to keep your Zapier resources active, pause the notification workflow, or delete the project assets. This one-trigger, one-action workflow can remain on the Free plan after the 14-day premium trial while your usage stays within the plan limits.

Resources you used:

A shareable Zapier Forms project named Task Intake.
A connected Zapier Tables table named Task Requests.
A published two-step Zap named Task Intake Gmail Alert.
A connected Gmail account authorized for the automation.

Keep everything running

No action needed. Choose this if you are still using the task-intake system to collect requests and send alerts.

Leave Task Intake Gmail Alert published.
Continue sharing Task Intake when you want to collect new requests.
Keep each new submission available in Task Requests.

Pause - I'll come back to this later

Turn off the published Zap to pause Gmail alerts while keeping the form and its stored records available.

Return to the Zapier Assets page in Microsoft Edge.
Locate the Zap named Task Intake Gmail Alert.
Use the Zap status toggle to turn it off.
Confirm that the status toggle shows the Zap is off.

New form submissions still appear in Task Requests. Gmail alerts remain paused until you turn the Zap on again.

Delete - I don't want to use this again

It is worth slowing down here because deleting the form project and table is permanent. The deleted Zap moves to Trash.

Return to the Zapier Assets page in Microsoft Edge.
Use the asset controls to delete the Zap named Task Intake Gmail Alert.
Confirm that the deleted Zap appears in Trash.
Use the asset controls to delete the Zapier Forms project named Task Intake.
Use the asset controls to delete the Zapier Table named Task Requests.

Your Gmail connection may support other automations in Zapier. Check for another dependency before removing its authorization.

Return to the Zapier Apps page.
Check whether another Zap uses your connected Gmail account.
Remove the Gmail connection with its connection controls if this project is its only use.

You should no longer see Task Intake Gmail Alert, Task Intake, or Task Requests among your active assets. The Gmail account should no longer appear as connected if you removed its authorization.

Nice Work!

Excellent work! You built a browser-based task intake system in Zapier that stores every request before sending a matching Gmail alert.

What you learned:

Built a shareable task intake experience in Zapier Forms that turns every submission into a structured record in Zapier Tables.
Observed how a stored request can remain unnoticed without automation. Connected a form-submission trigger to a Gmail action. Mapped every submitted field into a readable email alert.
Tested the Zap with saved form data before publishing it. Traced a live submission through the table. Found its matching email in Gmail. Reviewed the successful run in Zap History.
Secret Mission: Personalized the Gmail subject with mapped Priority plus Task Title values. The inbox now reveals each request's urgency before you open the message.

Ready to quiz yourself?