Navigating the Zap Editor

While each app has different options, the structure never changes. Every Zap step follows the same flow. Learn it once and you can work with any Zapier app.

Setup → Configure → Test

The Three-Tab Structure

This structure applies to all triggers and all actions.

The Setup Tab

The Setup tab defines the basics of a Zap step. First, you choose which app the step uses and which event it should run, for triggers this means what starts the Zap, and for actions this means what the Zap does, like New Email in Gmail or Create Spreadsheet Row in Google Sheets.

Finally, you select which account Zapier should use. You can connect multiple accounts for the same app and decide per Zap which one runs the automation, keeping each workflow clean and flexible.

Configure Tab

This is where you customize how the step behaves. The fields here depend entirely on the selected app and event. Typical configuration includes:

• Selecting specific resources (labels, files, sheets, folders);
• Setting options and parameters;
• Mapping data from earlier steps.

Fields can accept data from previous steps. Outputs from earlier steps become inputs for later ones. This is how data flows through a Zapier.

The Test Tab

The Test tab confirms the step works correctly.

What Testing Does

• Triggers: Finds recent data that matches the trigger;

• Actions: Executes the action using test data.

Data In vs. Data Out

• Data In: What this step received;

• Data Out: What this step produced for later steps.

This distinction is key for troubleshooting.