How to set up a Zapier automation from scratch

Zapier connects apps by watching for events in one app (the trigger) and performing actions in another when that event happens. No code required for the majority of use cases.

Use Zapier when:

• You need to move data between two apps that have Zapier integrations
• The workflow is linear: one trigger leads to one or more predictable actions
• The volume is moderate (under ~100k tasks/month on a reasonable plan)
• The client or team needs to be able to understand and edit the automation without developer help

Consider a code-based solution instead when:

• You need complex branching logic across many conditions
• You need to process large data volumes or do heavy transformations
• The tools involved don't have Zapier integrations (or require custom API calls)

For most small business automation — form to CRM, email to spreadsheet, notification triggers — Zapier is the right tool.

Go to zapier.com/sign-up and create a free account. The free plan includes 5 Zaps and 100 tasks per month — enough to build and test.

Once logged in:

• The left sidebar shows My Zaps (your automations), Zap history, and Apps (connected accounts)
• The center is your Zap editor
• A Zap is one automation: one trigger + one or more actions

To create your first Zap, click Create Zap in the top left. You'll land in the Zap editor, which has two sections: Trigger and Action.

The trigger is the event that starts your automation. It must happen in a specific app.

To configure the trigger:

1. Click the Trigger box in the editor
2. Search for and select your source app (e.g., "Google Forms", "Typeform", "Gmail")
3. Select the trigger event — this is the specific thing that starts the Zap. For Google Sheets, events include "New Spreadsheet Row," "New or Updated Spreadsheet Row," etc. Choose the most specific one.
4. Connect your account. Zapier will ask you to sign in to the source app to authorize the connection. Do this once per app — the connection is saved.
5. Configure the trigger settings. For most triggers, this means selecting which specific form, spreadsheet, inbox, or folder to watch.
6. Click Test trigger to pull in a sample record. This sample data will be used to set up your action steps.

Important: If Test trigger returns no results, it means there are no recent records in the source. Add a test record (submit the form, add a spreadsheet row) and try again. The test trigger only pulls existing records — it does not create one.

An action is what happens after the trigger fires. Click + below the trigger to add one.

To configure an action:

1. Search for and select the destination app (e.g., "HubSpot", "Slack", "Google Sheets")
2. Select the action event — the specific thing to do. "Create Contact" in HubSpot, "Send Channel Message" in Slack, "Create Spreadsheet Row" in Google Sheets.
3. Connect the destination app account.
4. Map the fields. This is the core of the Zap. Each field in the destination app needs a value. You can either type a static value or click the field to insert data from your trigger. For example, the "First Name" field in HubSpot would map to the "First Name" field from your form submission.

Field mapping tips:

• Use the field picker (the + icon inside each field) to insert dynamic data from previous steps
• You can combine static text and dynamic fields: "New lead: " + {{First Name}}
• If a required destination field has no matching source field, you'll need to either add it to your form or use a static default value

Filters let you run the action only when specific conditions are met. Without filters, your Zap runs on every trigger — including test submissions, spam entries, and incomplete records.

To add a filter:

1. Click + between your trigger and action steps
2. Select Filter
3. Set your condition: choose a field, choose an operator (contains, equals, exists, etc.), and set the value
4. You can add multiple conditions with AND / OR logic

Common filter use cases:

• Only process rows where "Status" column = "Approved"
• Only process form submissions where email is not empty
• Only process records created after a specific date
• Skip records where a field contains "test"

Alternative: Use Zapier's built-in "Only continue if" step — same result, cleaner editor interface in newer Zapier UI versions.

Before activating your Zap, test it with a real record.

Testing process:

1. Click Test on each step individually to confirm the mapping is correct
2. At the action step, click Test step — this will actually perform the action (create the record, send the message) using your test data. Check the destination app to confirm it worked.
3. If the test fails, read the error message carefully. Common issues: required field missing, wrong data format (date formatting, phone number format), permission scope too narrow on the connected account.

Once testing passes:

• Click Publish Zap (or Turn on Zap depending on UI version)
• The Zap is now live and will run automatically

After going live:

• Go to Zap History (left sidebar) to monitor runs
• Each run shows: timestamp, status (success/error), and the data that flowed through
• Set up error notifications: under the Zap settings, enable email alerts for failed runs