How to Build a Simple Zapier Automation

How do you build a simple Zapier automation for a small business? Build one Zap, Zapier’s name for a single automated workflow. Pick a trigger, such as a new website form submission. Add one action, such as creating a contact in your CRM. Add a second action that alerts your team. Test each step with a real submission, then publish the Zap. Every new lead then lands in the right place within minutes, with no copying by hand and no code.

What is a Zap, in plain terms?

A Zap has two parts. The trigger is the event that starts it, such as a form submission or a new payment. The action is what Zapier does next, such as create a contact, add a spreadsheet row, or send a message.

Each completed action counts as one task on your Zapier plan. Zapier connects with more than 9,000 apps, so the tools a small business already uses are very likely on the list.

Which automation should you build first?

Build the new lead Zap. It happens often, so you see results in the first week. Its steps are easy to check, because you can see the contact and the alert yourself. And a missed lead costs real money, while a missed spreadsheet row usually does not.

Here is the concrete example used below. It is an illustration, not a case study. A small plumbing company takes quote requests through its website form. Today the owner checks the form inbox twice a day and types each lead into a spreadsheet in the evening. The Zap replaces that routine: form submission, then a contact in the CRM, then an alert with the lead’s name, phone number, and the job they described.

How do you build it, step by step?

Step 1: Create the Zap and choose the trigger

Sign in to Zapier and choose Create, then Zap. In the trigger step, search for your form tool, such as Google Forms or Typeform. Choose the new submission event, connect your account once, and select the exact form.

Step 2: Test the trigger with a real submission

Fill in your own form first, with a note that says test. Zapier pulls that submission in as sample data. Build everything from this real record. Mapping from guessed field names can leave you with empty contacts.

Step 3: Add the first action, create the record

Add an action and choose your CRM, or Google Sheets if you do not use a CRM yet. Choose create contact, or add row. Then map the fields: put the form’s name value into the contact name field, the form’s email value into the email field, and so on. Mapping means clicking a field and picking the matching data from the trigger. Type static text only where every lead gets the same value, such as a source field set to website form.

Step 4: Add the second action, alert your team

Add one more action that sends a message where your team actually looks, such as email, Slack, or a text. Write the alert from the mapped data: the person’s name, phone number, and what they asked for. An alert with those facts can be acted on at once. One that only says new submission cannot.

Step 5: Test every step, then publish

Use the test button on each action and check the result in the destination app, not only inside Zapier. Confirm the contact exists, the fields are right, and the alert arrived. Then publish the Zap and submit the form once more, as a customer would.

How do you keep this Zap inside the free plan?

Zapier’s free plan costs $0 and includes 100 tasks per month, with unlimited two-step Zaps. The lead Zap above fits that shape. At 30 leads a month, with one contact and one alert per run, you use about 60 tasks, inside the free limit.

Multi-step Zaps and premium apps sit on paid plans. Professional starts at $19.99 per month billed annually, with 750 tasks per month. Built-in logic steps such as filters and paths do not count as tasks. Start free, count your tasks after one month, and upgrade only when the count tells you to.

What are the common mistakes with a first Zap?

• Automating a messy process. If nobody knows who should call a new lead, a faster alert only creates faster confusion. Decide the owner first.
• Skipping the test submission. Most broken Zaps were mapped from guessed field names. One real test record prevents that.
• Building five Zaps on day one. Run one Zap for two weeks, check its history for errors, then copy the pattern.
• No alert. A record created quietly in a CRM still waits until someone looks. The alert turns it into a faster reply.

What this means for your business

A first Zap is not a technology project. It is one routine, form to record to alert, that stops depending on someone remembering to check an inbox. For the plumbing company in the example, the gain is not the minutes saved on typing. It is that every lead gets a call while they are still comparing quotes, including leads that arrive in the evening and on weekends.

When this Zap has run cleanly for two weeks, pick the next daily routine, such as saving invoice emails to a folder, and build it the same way.

Keep Reading

Frequently Asked Questions

How much does Zapier cost for a first automation?

The free plan costs $0 and includes 100 tasks per month, which is enough for one simple lead Zap in most small businesses. Paid plans start with Professional at $19.99 per month billed annually, with 750 tasks per month.

What is the difference between a trigger and an action in Zapier?

The trigger is the event that starts the Zap, such as a new form submission. An action is a step Zapier completes after that, such as creating a CRM contact or sending a team alert. Each completed action counts as one task.

Do I need to know how to code to build a Zap?

No. You pick apps and events from lists, connect your accounts, and map fields by clicking the data you want to move. The whole first Zap in this article uses no code at any step.

What should I automate first with Zapier?

Start with new lead handling: a form submission that creates a CRM contact or spreadsheet row and sends your team an alert with the lead’s name, phone number, and request. It happens often, it is easy to test, and a slow reply is easy to measure.

How do I know if my Zap is working?

Submit your form as a customer would and check that the contact and the alert both appear. After that, open the Zap’s history in Zapier once a week for the first month. It shows every run and flags any step that failed.