Skip to main content
Released: 2026-04-06 This release introduces the new json input field type, improved zapier versions output, and a schema validation fix. 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)