How would you turn one signup into a Zap?

A Zap starts with a trigger, the event it listens for, and runs the actions you choose. For a waitlist, the trigger can be a new signup and the action can save its ID and interest in a review list.

Sketch the two steps on paper first. For any later test, confirm the selected account and list are disposable before testing the action. A test action can write a row.

Choose the starting event
Use a fake signup with ID demo-103 and the interest “wants a demo.” Write down which fields the starting event needs to supply.
Pick one destination action
Map the ID and interest into a pretend review list. Check whether the real connector action would add a row every time or can save under the same ID.
Check a repeated event
Deliver demo-103 twice on paper and keep one row. If you cannot enforce that outcome in the chosen destination, keep the write manual until you can.

Which parts of a Zap run again after an error?

Use the run details to see what happened. An errored-action replay can retry the failed step while skipping earlier successful steps. Replaying the entire run can repeat actions that already succeeded.

What the run history can tell you
What you see	What to confirm before replay
The destination action shows an error	Find out whether the row exists before sending the same write again. A missing reply and a missing row are different problems.
A full-run replay is available	List the actions that would run again. A second successful action can create another record or use another task.
The trigger filtered a repeated ID	Check the destination anyway. Polling deduplication is scoped to one Zap, and instant triggers have a different boundary.

How can a person approve a Zap action?

Put a Human in the Loop approval before the action. On Professional, you can request approval only from yourself. Team and Enterprise let you select other reviewers. Share the Zap with each reviewer and have them sign in to the Zapier account you selected.

Show the exact proposed action, including the intended recipient and text if it sends a message. Let only an approval reach the action. Set a decline or timeout to end the run or route around sending. Keep sensitive input out of the approval request unless the reviewer needs it.

What counts as a task in Zapier?

A standard successful action generally uses one task. The Free plan listed 100 tasks per month and two-step Zaps in November 2026.

The trigger and some built-in steps have their own rules. Free shares the allowance with applicable MCP tool calls, which have a separate counting rule. A successful action that runs again in a full replay can count again. Check the usage screen and limits before estimating the cost of repeated work.

Can you keep a copy of a Zap?

Zapier documents JSON workflow export and import for Team and Enterprise. Account owners or super admins can export more than their own workflows.

Keep a separate record of the connected accounts and the data in the destination. When you import, check that each action is pointing to the intended account and list before activating the workflow.