Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 36 ยท Getting Started

Build Your First Zap: A Step-by-Step Walkthrough

Build a classic first Zap in words: new form response to spreadsheet row plus chat alert. Covers testing, turning on, checking history, and a runnable stand-in simulator.

Time to build. Our first Zap is the classic one: when someone submits a form, add a row to a spreadsheet and send a team message. You can use any form app, spreadsheet app and chat app that Zapier supports; the steps are the same. We describe each click in words because Zapier's screens change, and we never show output we cannot guarantee.

Zapier cannot run on this site. The steps below are a guide for your own account. The Python blocks are labelled stand-ins that simulate the logic so you can see why each stage matters.

Before you start

You need three things: an app that produces events (a form), an app that stores data (a spreadsheet with a header row such as Name, Email, Message), and an app to notify (a chat channel). Create a test form with three questions and submit one response by hand, because Zapier needs a real example to learn the data shape.

Step 1: Create the Zap and name it

From the dashboard choose to create a new Zap. Click the title and name it "Form response to Sheet and chat". Put it in a folder if you like.

Step 2: Set up the trigger

  1. Click the trigger step and search for your form app.
  2. Choose the event, usually named like New Form Response or New Submission.
  3. Choose the account: connect your form app if you have not yet (you will log in and approve access).
  4. Configure: select the form to watch.
  5. Click Test trigger. Zapier fetches a recent response and shows its fields. If it finds none, submit the form again and re-test.

You should now see sample data with the Name, Email and Message fields. Read it: this is exactly what later steps can use.

Step 3: Add the spreadsheet action

  1. Add an action step, search for your spreadsheet app, and choose an event like Create Spreadsheet Row.
  2. Pick the connection, then the spreadsheet and the worksheet. Zapier loads the header row and shows one input per column.
  3. Map each column: click the field and choose the matching value from the trigger (Name into the Name column, and so on).
  4. Click Test action. A new row should appear in your spreadsheet. Open the sheet and look.

Testing an action really performs it. A test of "Create Row" adds a real row, and a test of "Send Message" posts a real message. Use a test sheet or channel while you learn.

Step 4: Add the chat alert

Add another action for your chat app, with the event Send Channel Message. Choose the channel and compose the text, mixing typed words and mapped fields:

Text
New lead from the website: <Name> (<Email>)
Message: <Message>

In the editor you insert the angle-bracket parts with the data picker. Test it and check that the message appears.

Step 5: Turn it on

When all steps have a green status, switch the Zap on (or publish it). From then on, new form responses start runs. Submit your form once more and wait. Depending on how the trigger works, the run starts instantly or within a polling interval; see polling vs instant triggers.

Step 6: Check Zap History

Open the Zap's run history. You should see the new run with a status such as success, and you can open it to see the data each step received and sent. This is your main debugging tool; the lesson on Zap history and replay explains it in depth.

A simulator for the whole flow

The stand-in below models a run: a response arrives, each action's fields are mapped, and the result of every step is logged. It also deliberately breaks one mapping so you can see how an error stops the rest of the Zap.

Python Stand-in: simulate the first Zap

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

In a real Zap, a failing step normally halts the run and marks it as errored, which is why you must watch your error notifications.

Why your first Zap might not fire

A short checklist that solves most beginner problems:

  • The Zap is still off or unpublished.
  • The trigger found no new data since the last check (polling takes time).
  • The trigger watches the wrong form, sheet or folder.
  • An account connection expired and needs reconnecting.
  • You are testing with old sample data and expecting a new run.
  • A filter step (filters) is stopping the run.

Make it better

Once it works, improve it: add a filter so only messages containing a keyword reach the chat, use Formatter to tidy names, or split work with Paths.

Test the thinking

A tiny exercise: the stand-in below checks whether a Zap is "healthy" using the checklist above.

Python Stand-in: first-Zap health checklist

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why should you submit a real test response before testing the trigger?

    The trigger test loads a recent example; without one, there is no sample data to map.
  2. 2. What happens when you test an action step such as Create Row?

    Tests perform the real action, so use test sheets and channels.
  3. 3. A Zap is built and tested but nothing happens when new responses arrive. First check:

    An off or unpublished Zap never runs, regardless of how well its steps tested.
  4. 4. Where do you see what data each step received in a past run?

    Zap History shows each run and step-level data.

Summary

  • A first Zap: trigger on a form, an action to add a sheet row, an action to message a channel.
  • Name the Zap, test each step with real data, then turn it on.
  • Action tests are real: they create rows and send messages.
  • Zap History shows what happened; use it to debug.
  • Most "it did not run" problems are off switches, polling delays, wrong sources, expired connections or filters.

Next: Plans, Tasks and Limits