❗ The zapier binary has been removed

The zapier command was deprecated in v18.0.0 in favor of zapier-platform. v19 completes that transition by removing the old binary entirely.

Apart from this major change, here are the detailed release notes for this release (note that ❗ denotes a breaking change):

cli

• ❗ Remove the zapier executable; the CLI now ships only zapier-platform (#1299)

core

None!

schema

None!

The platform now automatically checks for breaking changes when you promote a new integration version. If breaking changes are found and the version doesn't increment the major number, promotion is paused with a clear explanation of what was detected and which version number to use instead.

This helps you catch issues before they reach users — no more accidentally shipping a removal or auth change under a patch bump.

What gets checked

When you promote, the platform compares the new version against the current public version at the schema level — looking at the structure of your triggers, actions, searches, and authentication. The following schema-level breaking changes are detected automatically:

• Removed triggers, actions, or searches — a key present in the current public version is missing in the new version
• Authentication type change — the auth type (e.g., oauth2, apiKey, session) differs between versions
• Trigger type change — a trigger switched between polling and hook type
• Removed searchOrCreate keys — a searchOrCreate present in the current version is missing
• Removed input field keys — an input field key on an existing trigger/action was removed
• Optional input field made required without a default — an existing optional field is now required but has no default value
• Authentication field changes — removing an auth field, adding a new required auth field, or changing an auth field's type
• Input field type changes — changing the type of an input field (e.g., string → list)
• Incompatible JSON field schema changes — backward-incompatible changes to json-type input field schemas

If any of these are detected, you'll see a message explaining the specific changes found and the minimum major version required.

What this means for you

• If you're already following semver, nothing changes. You're good.
• If a promotion is paused, read the message — it tells you exactly which changes triggered the check and what version number to use. Bump the major version and promote again.
• If you need to phase out a trigger, action, or search without a major bump, hide it instead of removing it. Hidden items continue to work for existing Zap workflows but are no longer available to new users.

For the full list of what gets detected and how to choose the right version number, see Version numbering.

zapier-platform invoke auth template returns the static template (with {{placeholders}} for auth fields). zapier-platform invoke auth render substitutes real auth data from .env into that template and returns the final request.

cli

• 🎉 Add invoke auth template and invoke auth render commands (#1282)

core

• 🎉 Add getAuthTemplate and renderAuthTemplate Lambda commands (#1282)

schema

None!

We're renaming zapier to zapier-platform because the zapier binary name will be allocated to the Zapier SDK. The zapier binary still works in v18, but in the next major release (v19), we'll officially remove it — you'll need to use zapier-platform instead. If zapier-platform is too long to type, you can set up a shell alias like alias zp=zapier-platform.

cli

• 📜 Rename binary name from zapier to zapier-platform in docs, source, and help command (#1291, #1292, #1293)

core

• 🐛 Throw actionable error when app definition fails to load (#1288)
• 🐛 Remove platformData from bundle logging (#1289)

schema

None!

Line items are fields with a children property that represent structured, repeating data — like rows in a spreadsheet or items in an order. The invoke command now supports them in both interactive and non-interactive modes:

# Non-interactive: pass line items as JSON
zapier-platform invoke create order --non-interactive \
  -i '{"name": "My Order", "line_items": [{"product_name": "Pens", "quantity": "12", "price": "1.50"}]}'

# Interactive: use the line item editing UI
zapier-platform invoke create order -i '{"name": "My Order"}'

In interactive mode, a sub-menu lets you add, edit, and delete items with per-field editing and required field validation.

cli

• 🎉 Add line item support to invoke command with interactive editing UI (#1272)
• 🎉 Add line-items project template for zapier-platform init (#1272)
• 🐛 Fix invoke bugs: auto-detect auth ID for no-auth apps in remote mode, falsy value handling (0, false) causing infinite dropdown re-prompting, and more (#1272)
• 🔨 Bump lodash from 4.17.23 to 4.18.1 (#1274)

core

• 🔨 Bump lodash from 4.17.23 to 4.18.1 (#1274)

schema

• 🔨 Bump lodash from 4.17.23 to 4.18.1 (#1274)

You can now accept structured JSON input from users with the new json field type. Optionally provide a schema to validate and describe the expected shape:

{
  key: 'product',
  type: 'json',
  label: 'Product',
  helpText: 'Enter a JSON object',
  schema: {
    type: 'object',
    properties: {
      name: { type: 'string' },
      price: { type: 'integer' },
    },
    required: ['name'],
  },
}

We also fixed a bug where pushing code with function-based dynamic dropdowns caused an unexpected validation error on the server. If you want to use function-based dynamic dropdowns, upgrade to 18.4.0 or later:

{
  key: 'project_id',
  label: 'Project',
  type: 'string',
  required: true,
  choices: {
    perform: async (z, bundle) => {
      const response = await z.request('https://api.example.com/projects');
      return {
        results: response.data.map((project) => ({
          id: project.id,
          label: project.name,
        })),
        paging_token: null,
      };
    },
  },
}

cli

• 💅 Clarify zapier-platform versions timestamps with separate "Created at" and "Updated at" columns (#1275)

core

• 🎉 Add JSON field type handling with schema-aware TypeScript inference (#1273)

schema

• 🎉 Add JSON input field type with optional schema property for structured data (#1265)
• 🎉 Validate schema property on JSON fields against JSON Schema meta-schema (#1267)
• 🐛 Fix oneOf ambiguity in FieldChoicesSchema that caused server-side validation errors for function-based dynamic dropdowns (#1268)
• 📜 Update skipThrowForStatus documentation to note 401 errors are not subject to the flag (#1270)

misc

• 🔨 Improve publish workflow with path filters and boilerplate build fixes (#1264, #1266)

cli

• 🎉 Add support for function-based dynamic dropdown to the invoke command (#1206)

core

None!

schema

• 🎉 Add FieldDynamicChoicesSchema for function-based dynamic dropdowns (#1206)

cli

• 🐛 Surface package manager errors in build command (#1254)

core

• 🐛 Declare zapier-platform-legacy-scripting-runner as an optional peer dep to fix pnpm strict module resolution (#1255)

schema

None!

cli

None!

core

• 🐛 Log a warning when zapier-platform-legacy-scripting-runner is installed but fails to load, instead of silently returning null (#1247)

schema

None!

misc

• 🔨 Fix publishing workflow to run on pushes to main (#1243)
• 🔨 Add non-interactive mode to bump script (#1249)

• Migrations are only allowed when the from and to versions share the same major number (e.g. 1.0.0 → 1.0.1, or 2.1.0 → 2.2.0).
• Cross-major moves (e.g. 1.5.0 → 2.0.0) are blocked in both the Platform UI and via zapier-platform migrate. This aligns with long-standing guidance; major releases include breaking changes, so users should update Zap workflows manually or you should use deprecation instead of migration.
• Details and workflow are in Migrate users to a new version.