Platform News (Single Page)

Documentation Index

Fetch the complete documentation index at: https://docs.zapier.com/llms.txt

Use this file to discover all available pages before exploring further.

​

New platform guardrails for safer integration versioning

• 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 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 Zaps but are no longer available to new users.

​

What’s changed in v18.6.0

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

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

​

What’s changed in v18.5.1

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

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

​

What’s changed in v18.5.0

**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"}'

• 🎉 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)

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

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

​

What’s changed in v18.4.0

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

{
  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,
      };
    },
  },
}

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

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

• 🎉 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)

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

​

What’s changed in v18.3.0

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

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

​

What’s changed in v18.2.3

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

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

​

What’s changed in v18.2.2

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

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

​

User migrations must stay within the same major version

• 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 Zaps manually or you should use deprecation instead of migration.
• Details and workflow are in Migrate users to a new version.

​

What’s changed in v18.2.1

• 🐛 zapier-platform build no longer raises EEXIST when using a symlink-based package manager (#1244)

​

Pushing unlabelled semantic versions must be sequential

• Patch bump (1.2.3): the exact unlabelled 1.2.2 must already exist.
• Minor bump (1.3.0): at least one unlabelled 1.2.x must exist.
• Major bump (2.0.0 when coming from 1.x): at least one unlabelled 1.x.x must exist.

• 1.2.3: blocked if any unlabelled 1.2.4 or higher on the same 1.2.* line already exists. Pushing 1.3.0 is still allowed when only 1.3.x or 2.x.x exists—those are not on the 1.2.* patch line.
• 1.3.0: blocked if any unlabelled 1.4.x or higher on the same major (1.*) already exists. 2.0.0 is still allowed when only 2.x.x exists.
• 2.0.0: blocked if any unlabelled 3.x.x or higher already exists.

• Plan patch → patch → minor → major (or the minimal chain your history needs) using unlabelled semver when you are ready to record real releases; use labelled snapshots while iterating.
• If you are stuck because old versions were removed, you may still use deprecation and, when appropriate, delete a deprecated version so your remaining unlabelled history matches what you want to push next.

​

What’s changed in v18.2.0

• 🎉 zapier-platform invoke now supports function-based choices (#1237)

• 🐛 If we attempt to stash a large response but it’s bigger than the max limit, throw a descriptive error with the actual size and the limit (#1238)
• 🔨 Add an environment variable to allow suppressing cleaning up env vars (#1242)

• 🔨 CI: Use environment to publish (#1239)
• 🔨 CI: Automate the boilerplate upload (#1240)

​

What’s changed in v18.1.1

• 🐛 Restore missing HTTP error logs (#1227)

• 🔨 Bump lodash from 4.17.21 to 4.17.23 across the board (#1228, #1229, #1230, #1231, #1233, #1234, #1235)

​

What’s changed in v18.1.0

zapier-platform invoke -r

• The integration version you want to test has to be deployed first.
• The invocation results and the bundle payload passed to your integration code will match what you see in live production, which is great for testing.
• Remote mode is slower than local mode (without the -r flag).

• 🎉 Add --remote flag to invoke command (#1220)
• 🐛 Fix package manager detection in build and test commands to include parent directories (#1225)

• 📜 Improve internal development docs (#1221)

​

What’s changed in v18.0.7

• 🔨 Refactor invoke command (#1217)

• 🎉 Allow a sample field to be provided for dynamic outputFields (#1211)

• 🔨 Add publish job in CI (#1212, #1223)

​

What’s changed in v18.0.6

• 💅 CLI build respects the integration’s package manager (#1216)

• 🔨 Bump tmp from 0.2.4 to 0.2.5 (#1207)
• 🔨 Bump form-data from 4.0.4 to 4.0.5 (#1208)

​

What’s changed in v18.0.5

• 🐛 Remove problematic decompress-tar dependency (#1202)

• 🔨 Switch to pnpm as package manager and task runner (#1204)

​

Incident: Unauthorized Access to Zapier NPM Packages

​

What’s changed in v18.0.1

• 🐛 Fix npx resolution issue with dual binary entries (#1191)

• 🐛 Fix children input types when line items are present (#1188)

​

What’s changed in v18.0.0

• 🎉 Add executable name zapier-platform and deprecate zapier (#1181)
• 🔨 Update outdated dependencies with security vulnerabilities (#1111)
• 🔨 Apply prettier formatting to generated auth files since gen.fs.write bypasses transform streams
• 🔨 Add ESM wrapper improvements for better module support

• ❗ Add Node.js 22 support (#1078)
• 🎉 Add throwForThrottling middleware with backward-compatible default behavior (#1151)
• 🐛 Add better error message for 413 responses (#1110)

• ❗ Replace skipCleanArrayInputData with cleanInputData (#1183)
• 🔨 Add global cleanInputData flag for consistent data cleaning behavior

• ❗ Major dependency updates across all packages (#1079)
• 🔨 Update CI configuration for Node.js 22 support
• 🔨 Pin exact xmldom version for security