How to Set Up Zapier: Build Your First Zap Step by Step

If you want to know how to set up Zapier properly, the process is: create an account, plan one workflow on paper, connect the apps involved, build a Zap with a trigger and an action, map your fields, test with real data, then name and publish it. The editor itself is friendly. The parts people skip, planning and testing, are what decide whether the Zap still works in three months.

This guide on how to set up Zapier walks through each step in order, with the checks we use when we build Zaps for clients. If you are still deciding whether Zapier is the right tool at all, start with our explainer on what Zapier is and how it works, then come back here.

Step 1: Pick one workflow and write it down

Before you open Zapier, choose a single, repetitive task. Good first candidates are small and frequent: a website form that someone copies into a CRM, or new orders that someone posts to a team channel.

Write the workflow as a sentence and a short list:

• The sentence: “When someone submits the contact form, create a contact in the CRM and alert the sales channel.”
• The trigger app and event: which app, and which exact event starts it.
• The action apps and events: what should happen, in order.
• The data you need: every field that has to travel, such as name, email, company and message.
• The exceptions: what should happen if the email is missing, or the contact already exists.

This takes ten minutes and saves hours. It also gives you something to hand to the next person who has to maintain the Zap.

Step 2: Create your account and set up the basics

Sign up at zapier.com. During signup Zapier may ask about your role and the apps you use; this only shapes suggestions, so don’t worry about the answers.

Then handle two decisions that are hard to change later:

• Which email owns the account: use a business address that won’t disappear when one person leaves, or set up a team account where several people can manage Zaps.
• Which plan you need: the free plan is fine for learning, but features like multi-step Zaps, Paths and webhooks sit on paid plans. Check Zapier’s pricing page for what each plan includes today, because it changes.

Step 3: Connect your apps

Zapier calls a saved login to an app a connection. You can add connections while building a Zap, but adding them first from the Apps or connections area of your account keeps things tidy.

For each app in your workflow:

1. Search for the app and choose to add a connection.
2. Sign in and approve the permissions Zapier asks for.
3. Give the connection a clear label, such as “CRM: sales shared account”, so you can tell connections apart later.

Use the same rule as before: connect with an account that belongs to the business, not to an individual. If an app offers API keys instead of a login, store a copy of the key in your password manager, not in a note.

Step 4: Build the trigger

Create a new Zap. In the editor, the first step is always the trigger.

1. Choose the trigger app, for example your form tool.
2. Choose the trigger event, for example “New Form Submission”. Read the event descriptions; similar names can behave differently, such as “New Entry” versus “New or Updated Entry”.
3. Select the connection you set up in Step 3.
4. Fill in any trigger options, such as which form or which spreadsheet tab to watch.
5. Test the trigger. Zapier will pull in a recent sample record.

If the test finds nothing, submit a real test entry in the source app and test again. Pick a sample that looks like a real customer record, with every field filled in, so you can map fields properly in the next step.

Step 5: Add actions and map the fields

Now add the first action.

1. Choose the action app, for example your CRM.
2. Choose the action event, for example “Create Contact” or, if available, “Create or Update Contact” to avoid duplicates.
3. Select the connection.
4. Map each field. Click into a field and choose the matching value from the trigger data. Zapier shows the sample values next to each option, which helps you pick the right one.

A few mapping habits prevent most errors:

• Map the field with the right value, not just the right label. Two fields called “Name” can hold different things.
• Fill in required fields, which the editor marks, but also check optional fields you care about, such as lead source.
• Use fixed text where it helps. Typing “Website form” into a lead source field tells your team where the contact came from.
• If data needs cleaning first (a full name split into first and last, a date in the wrong format), add a Formatter step before the action. Our guide on using Formatter by Zapier covers the common fixes.

Add further actions the same way. Each new step can use data from any earlier step, including IDs created by previous actions, such as the new contact’s ID.

Step 6: Test every step with realistic data

Test each action from inside the editor. Zapier will run the step using your sample data and show the result. Then go into the destination app and look at what was created. Check:

• Did the record land in the right place, with the right owner?
• Are names, emails and phone numbers formatted correctly?
• Did empty fields cause an error or a blank value that will confuse your team?
• If you ran the test twice, did you get two records? If so, you may need a “find or create” step or a filter.

Delete your test records afterward so they don’t pollute your reports.

Then run one more test the way your customer would: submit the real form from your website after the Zap is on and follow the record all the way through.

Step 7: Add guardrails before you publish

These small additions make a Zap far more reliable:

• Filters: stop the Zap when data is missing or irrelevant, such as test submissions from your own team or entries without an email.
• Find steps: search for an existing record before creating a new one.
• Error notifications: in your account settings, make sure error emails go to someone who reads them.
• A clear name: rename the Zap from “Untitled Zap” to what it does, such as “Contact form to CRM and sales alert”.
• A folder: group Zaps by team or process so they are easy to find.

Step 8: Publish and monitor

Publish the Zap to turn it on. From then on, every run appears in Zap history, with each step’s input and output. Check the history daily for the first week, then weekly.

When something fails, the history shows which step broke and why. Typical causes are an expired connection, a renamed field in the source app, or a value the destination app rejects. Fix the cause, then replay the failed run if the option is available for that run.

Set a reminder to review all your Zaps every few months. Apps change their fields, people leave, and processes evolve. A short review catches problems before a customer notices them.

How to set up Zapier without the common mistakes

• Building three Zaps on day one instead of getting one working end to end.
• Testing with a half-empty sample record, then discovering the mapping is wrong when real data arrives.
• Using “New or Updated” triggers when you only want new records, which causes repeat actions.
• Letting the person who built the Zap be the only one who knows it exists.
• Creating a Zap that updates the same app that triggers it, which can cause a loop.

When setup becomes a project

The steps above are enough for straightforward workflows. When a process spans several teams, needs branching logic, touches payment data, or depends on apps without a standard integration, setup turns into a design job. That is the point where it often makes sense to bring in a Zapier expert to map the whole system before building, so the Zaps fit together instead of competing. You can also email support@growthscribe.com with the workflow you want to automate.

Whichever route you take, keep the habit from Step 1: write the workflow down first. Knowing how to set up Zapier is mostly knowing what you want it to do.

FAQ

How long does it take to set up a first Zap?

A simple two-step Zap can be built in one sitting once you know which apps and fields you need. Most of the time goes into planning the workflow and testing it with realistic data, not into clicking through the editor.

Should I connect apps with my personal account or a shared account?

Use a shared or role-based account wherever your apps allow it. Zaps built on one person’s login stop working when that person changes their password, loses access or leaves the business.

Why is my Zap not triggering?

The most common reasons are that the Zap is still off, the trigger is waiting for a genuinely new record rather than an old one, the app connection has expired, or a filter is stopping the run. Check the Zap’s status, then its Zap history, then the app connection.

Can I edit a Zap after it is published?

Yes. You can open the Zap, make changes and publish again. Test the edited steps before publishing, because changes apply to every future run.