Zapier in depth

How Zaps are built and billed: triggers and actions, field mapping, Filters and Paths, Formatter, Webhooks and Code steps, Tables and Forms, and tasks.

Zap

Also called Zap workflow, Zap history, multi-step Zap

What: A Zapier workflow: one trigger and one or more action steps. Every run is recorded in Zap history with the data each step received and returned.
Why: Zap history is where you debug and replay. The free plan allows two-step Zaps; multi-step Zaps, Paths and webhooks need a paid plan as of 2026-09.

Watch out

Turning a Zap on and never opening Zap history until a client reports missing data.

Field mapping and line items

Also called line items, Looping by Zapier, test step

What: Inserting fields from earlier steps into later ones, shown by step number and name. Arrays such as order products arrive as line items, which some actions accept and others need Looping or Formatter for.
Why: Mapping from a realistic test sample, and handling line items deliberately, prevents blank fields and lists crammed into one cell.

Watch out

Mapping a line-item field into an action that expects one value.

Filter

Also called Filter by Zapier, only continue if

What: A step that lets the Zap continue only when conditions are true, such as the email not containing "test".
Why: Filters stop irrelevant runs early, and the pricing page lists them as not counting as tasks.

Watch out

Placing the filter after the expensive action steps instead of before them.

Paths

Also called Paths by Zapier, branching

What: Branches inside a Zap, each with its own rules and steps, so one Zap can handle several cases such as new and returning customers.
Why: Paths replace several near-identical Zaps with one that is easier to maintain.

Watch out

Rules that overlap, so a record runs two paths, or leave a gap, so it runs none.

Formatter

Also called Formatter by Zapier, lookup table

What: Built-in steps to transform data: Text (trim, case, split, extract), Numbers (format, calculate), Date/Time (format, time zones, add days) and Utilities (line items, lookup tables).
Why: Most cleaning in Zapier is done with Formatter, which does not count as a task on the current pricing page.

Code

Formatter > Date/Time > Format
Input: (1) Created At
To Format: YYYY-MM-DD HH:mm
To Timezone: Africa/Lagos
From Timezone: UTC

Watch out

Leaving the time zone fields empty, so dates shift by hours.

Code by Zapier

Also called Code step, inputData, Webhooks by Zapier

What: A step that runs short JavaScript or Python. Mapped fields arrive in inputData, and you return an object whose keys later steps can map. Webhooks by Zapier catches or sends raw HTTP requests.
Why: Code and webhook steps cover logic Formatter cannot and apps with no Zapier integration. Both need a paid plan.

JavaScript

const email = (inputData.email || '').trim().toLowerCase();
const parts = (inputData.name || '').trim().split(' ');
const [first, ...rest] = parts;
return {
  email,
  firstName: first || 'there',
  lastName: rest.join(' '),
  valid: /^[^@\s]+@[^@\s]+\.[^@\s]+$/.test(email),
};

Watch out

Hard-coding an API key inside the code where every editor can read it.

Tables and Forms

Also called Zapier Tables, Zapier Forms, Interfaces

What: Tables is a built-in database for records Zaps create or read. Forms, called Interfaces until May 2026, builds forms and simple pages that feed Tables or trigger Zaps.
Why: Together they let you build a small request, approval or logging tool without another app. Both are included in Free, Pro and Team plans as of 2026-09.

Watch out

Making Tables the system of record when the client already runs on a CRM.

Tasks

Also called Zapier pricing, task usage

What: The billing unit on Zapier: one successful action step. Triggers, failed actions and built-in tools such as Filter, Formatter, Paths, Delay and Tables do not count, per the 2026-09 pricing page.
Why: Estimating tasks before quoting avoids surprise upgrades. Free has 100 tasks a month; Professional starts at 750.
Example: A Zap with 3 action steps running 40 times a day uses about 3,600 tasks a month.

Watch out

Looping over line items so one order quietly becomes twenty tasks.

Go deeper