Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 36 ยท Getting Started

Your Zapier Account and the Zap Editor

Tour the Zapier dashboard and Zap editor: creating an account, folders, the step list, setup versus test tabs, naming, and a runnable stand-in for step validation.

Before you build, you should know your way around. This lesson describes the parts of the Zapier web app you will use every day: the dashboard, the Zap editor, the step panel and the test controls. Zapier changes its interface from time to time, so we describe concepts and typical locations rather than pixel positions. If a label differs slightly in your account, look for the same idea nearby.

Zapier cannot run on this site. This lesson is a written tour. The only runnable code is a labelled stand-in that models how the editor decides whether a step is ready.

Creating an account

You sign up on Zapier's website with an email address and a password, or with a Google or Microsoft sign-in. New accounts start on a free plan, which is enough to learn with. When you sign up, Zapier may ask about your role and goals; you can answer briefly or skip. Use an email you will keep. If you work for a company, check whether your organization already has a Zapier team before creating your own, because shared work belongs in a team workspace (governance comes later in the course).

Turn on two-factor authentication in your account security settings as soon as you can. Your Zapier account holds logins to many other apps.

The dashboard

After signing in you land on a home or dashboard area. Its main parts are:

  • Create / New Zap button: opens the editor with an empty Zap.
  • Zaps list: every Zap you can access, with its name, apps, on/off switch, last-modified time and folder.
  • Folders: a way to group Zaps, for example one folder per project or department.
  • Zap History: a log of runs, with their status and data. See Zap history, errors and replay.
  • Connections (sometimes under "My Apps"): your saved logins to other apps.
  • Tables and Interfaces: Zapier's own data and app-building products, covered in chapter 6.
  • Settings, plan and billing, and usage: account details and task consumption.

The Zap editor

The editor is a vertical (or flow) list of steps. The first step is the trigger; below it are actions. Click a step to open its settings panel. The panel for most steps has the same tabs or sections:

  1. App & event: choose the app and what the step does (for a trigger, which event starts the Zap; for an action, which operation to run).
  2. Account: choose the saved connection to use, or connect a new account.
  3. Configure / Setup: fill in the fields. Some fields are fixed values you type; others are mapped from earlier steps (chosen from a data picker).
  4. Test: run the step with real or sample data to confirm it works.
flowchart TD
  A["Pick app and event"] --> B["Choose account"]
  B --> C["Configure fields"]
  C --> D["Test step"]
  D -->|"works"| E["Next step"]
  D -->|"error"| C

Each step walks through the same four stages. You fix and re-test until the step succeeds, then add the next one.

Data picker and sample data

When you configure an action, clicking a field usually opens a data picker listing values from previous steps, such as "Name" from the form trigger. Zapier fills these with sample data fetched when you tested the trigger, so you can see what a real value looks like. Pick the field you need, and Zapier inserts a placeholder that is replaced by the real value at run time.

Typing text around a placeholder is fine. For example, a chat message field could contain "New lead: " followed by the Name placeholder.

On and off, drafts and publishing

A Zap only runs when it is turned on. While you build, it stays off (a draft). Newer editors may also use a publish step: changes to a Zap that is already on are not live until you publish them. Check the top of the editor for the Zap's status before you assume a change is running. Tests in the editor use sample or real data but do not make the Zap live.

Naming and organizing

Give every Zap a clear name that says trigger, action and purpose, for example "Typeform lead to Sheet and Slack alert". Put it in a folder. Six months later you will not remember what "Zap 14" does. Good names also make Zap History searchable.

A stand-in: when is a step ready?

A step is "ready to test" only when every required field is filled. The stand-in below mimics that check. It is not the real editor.

Python Stand-in: step readiness check

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.

A stand-in: placeholders and sample data

This one shows how a data picker placeholder becomes a real value. It substitutes {{name}} style tokens, and flags a token that has no data, a common mistake when a field name changes.

Python Stand-in: filling placeholders

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.

The missing phone field reminds you that if the trigger's data does not include a field, no placeholder can supply it.

Habits worth building from day one

  • Always test every step, and read the returned data, not just the green tick.
  • Rename steps (for example "Create lead row") so the run log is readable.
  • Keep each Zap small and focused.
  • Turn on error notifications so failures reach you (error handling).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the data picker do?

    The data picker inserts placeholders for data produced by previous steps.
  2. 2. A Zap under construction is usually:

    Zaps run only when on. Tests in the editor do not make a Zap live.
  3. 3. Why give Zaps clear names and folders?

    Names and folders make a growing list of Zaps maintainable and searchable.
  4. 4. Which is NOT one of the usual four stages of a step?

    Steps are not compiled; you choose the app/event, account, configure fields, and test.

Summary

  • The dashboard lists Zaps, folders, history, connections and usage.
  • The editor is a list of steps; every step goes through app/event, account, configure and test.
  • The data picker inserts placeholders that become real values at run time.
  • A Zap runs only when it is on or published; tests do not make it live.
  • Name, organize and test each step from the start.

Next: Build Your First Zap