TopolearnTesting catches mistakes before they touch real customers, and drafts let you change a live Zap without stopping it.
Each step in the editor has a Test button. Testing the trigger fetches sample data. Testing an action really performs it once with that sample: a test email is actually sent, a test row is actually added. So test with harmless data, or point actions at a test spreadsheet or your own inbox first.
Test results show exactly what the app returned. If a step fails here, the error message usually names the problem: a missing required field, a wrong format, or a permission issue.
When everything works, click Publish. The Zap turns on and handles new events from then on.
Changing a live Zap does not interrupt it. Your edits go into a draft, while the published version keeps running. When you publish the draft, it replaces the live Zap. There is only one draft at a time, and deleting a draft leaves the live Zap unchanged.
Every publish creates a numbered version that you can name, such as "v4 - added Slack alert". Run history shows which version handled each run. If a change goes wrong, you can start a new draft from an older version and publish it, which works as a rollback. How long versions are kept depends on your plan.
Good habits:
- Name each Zap after what it does: "New Shopify order -> CRM + Slack".
- Turn the Zap on, then create one real event and check the result yourself.
- Keep related Zaps in folders.
Remember
- Testing an action really performs it, so use safe test data
- Edits to a live Zap go into a draft until you publish
- Each publish creates a version you can roll back to
Watch out for
- Testing a "Send Email" action against a real customer list.