Rollback‑on‑Demand: 60‑Second Drill Pack (Zapier, Make, n8n)

Use MAJOR.MINOR.PATCH, e.g., v2.3.7.

• Bump MAJOR for breaking changes (data shape/IDs, trigger semantics).
• Bump MINOR for backwards‑compatible feature additions (new step behind a flag, optional field).
• Bump PATCH for fixes/refactors that don’t change contracts. Quick key you can paste into docs: MAJOR=breaks, MINOR=adds, PATCH=fixes.

Tag the exact JSON artifact (Make Blueprint, n8n workflows export, or repo commit) you shipped. Copy‑paste commands (replace placeholders):

# Tag the release
git tag -a v[MAJOR].[MINOR].[PATCH] -m "[CLIENT] [STACK/WORKFLOW]: [CHANGE SUMMARY]"
# Push the tag to origin
git push origin v[MAJOR].[MINOR].[PATCH]

# Use a dedicated deploy branch for prod pulls (recommended)
# Promote main to prod on normal releases
git push origin main:deploy
# Roll back prod instantly to a tagged release
git push origin v[MAJOR].[MINOR].[PATCH]:deploy

Outcome: the deploy branch always points at the live, last known‑good state. Rollbacks are one command.

Properties (Notion database):

• Date (date)
• SemVer (text) → e.g., v1.4.2
• Platform (select) → Zapier | Make | n8n
• Object ID(s) (text) → Zap ID / Make Scenario ID / n8n Workflow ID(s)
• Reason (text) → what changed/why
• Rollback target (text) → tag or version label (e.g., v1.4.1 or Version from 2026‑05‑01 14:12)
• Rollback link (url) → deep link to platform version page or Git tag URL
• Reviewer (people) → who sanity‑checked
• Outcome (select) → Restored | Monitored | Escalated Example row: 2026‑05‑08 | v1.4.2 | Make | Scn_12345 | New mapping for Line Items | v1.4.1 | https://git.example/tags/v1.4.1 | Jordan | Restored.

If the automation is causing harm (duplicate charges, bad emails), PAUSE it first:

• Zapier: toggle the Zap OFF in the editor header (2s) → then run Step 5.
• Make: STOP scheduling or disable the Scenario (2–3s) → then run Step 6.
• n8n: UNPUBLISH the affected workflow(s) (3–5s) → then run Step 7/8. If harm is low (read‑only or idempotent), proceed directly to rollback for the shortest downtime.

Target: restore a prior published Zap version. Path:

1. Open the Zap → Editor → Versions (clock icon in left panel).
2. Select the last known‑good version (check timestamp/notes) → Create draft from version.
3. Run a test on a non‑destructive step (e.g., a Formatter step) to validate mapping still resolves.
4. Publish the draft. Notes:

• Plan gating: Version Rollback has historically been on Professional/Team/Company; confirm in your workspace.
• App major‑version policy (2026): Zapier blocks jumping an app step across semantic MAJORs in Platform tooling. That’s separate from your Zap’s version history. If a step fails due to an app major bump, pin or revert that step’s app version per app docs. Links: Zapier — Restore your Zap to a prior version · App versions in Zapier. Outcome: Zap is live on the previously working configuration.

Target: restore a previously saved scenario version. Path:

1. Scenarios → open the scenario → History → Version History.
2. Choose the last saved good version (within the retention window) → Restore.
3. Save the scenario.
4. Run once manually with a safe test input. Confirm critical mappings resolve. If the needed version isn’t listed or is older than retention: import your Git‑tagged Blueprint. Fallback (Blueprint import):

• Scenarios → + Create a new scenario → Import blueprint (paste JSON from your vX.Y.Z tag; < 2 MB) → Re‑authorize connections if prompted → Save → Run test → Swap schedules to the restored scenario. Links: Make — Restore and recover scenario · Scenario blueprints. Practitioner tip: Use Dynamic Connections to flip between Sandbox/Production credentials without duplicating scenarios when testing fixes. Outcome: Scenario runs on the last known‑good blueprint.

Target: point production to the last known‑good Git tag, then Pull. Recommended pattern: production pulls from a deploy branch.

1. In your Git provider, move deploy to the good tag: git push origin v[MAJOR].[MINOR].[PATCH]:deploy.
2. In n8n: Projects → Source Control → Pull. Expect a brief unpublish/republish of affected workflows (seconds).
3. Smoke test one trigger and one critical action. Links: n8n — Using source control and environments · Push and pull. Outcome: Instance is live on the tagged, audited state.

Target: restore exported workflow JSON(s) from the last known‑good tag. UI path:

1. Workflows → Import from File/URL → select JSON from your vX.Y.Z bundle.
2. Publish the restored workflow(s). CLI path (if you keep scripted backups):

# Import a single workflow by ID
n8n import:workflow --input=/backups/vX.Y.Z/workflows/[WORKFLOW].json
# Import all workflows from a folder
n8n import:workflow --separate --input=/backups/vX.Y.Z/workflows

Links: n8n — Export/import workflows · n8n — CLI commands. Outcome: Broken workflows are replaced with last known‑good JSON and republished.

• Trigger fires on representative input (manual or sample) without error.
• Each critical branch executes (happy path + at least one conditional).
• External writes (CRM, billing, sheets, DB) occur once and with correct fields.
• Logs/alerts are green; no unexpected retries. If any check fails, re‑pause and escalate to a deeper restore (e.g., older tag) or hotfix.

1. Add a Notion change‑log entry with the actual vX.Y.Z and links/screenshots.
2. Create a follow‑up task to root‑cause and fix forward behind a feature flag.
3. If you used a deploy branch: keep deploy pinned to the rollback tag until the fix is tested; promote the new fix by pushing main:deploy when ready.
4. Communicate to the client (one‑liner): what failed, when you rolled back, current status, and next steps.

• Zapier: Add version notes in the Versions panel; avoid publishing structural changes without a saved, labeled prior version.
• Make: Save named versions before risky edits; export a Blueprint to Git on each release.
• n8n: Expect a few seconds of downtime during Pull; schedule outside peak windows. Track CVEs and rehearse upgrades + rollbacks quarterly. References: Zapier Version Rollback · Make Version History · n8n Source Control.