fix(zapier): drop hard-coded field names from static samples (T004)

Field values were spread to the top level and baked into each sample as
`Name`/`Status`. Real runs spread the user's *actual* field names instead,
so those keys never appear live — failing Zapier's T004 check that a static
sample be a subset of the live result's keys. Keep only stable system keys
and an empty `fields` object across all record triggers/creates/searches.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: caoxing9

packages/zapier/src/creates/create_or_update_record.ts

@@ -148,9 +148,9 @@ export default {
     sample: {
       id: 'recXXXXXXXXXXXX',
       createdTime: '2026-01-01T00:00:00.000Z',
-      fields: { Name: 'Acme', Status: 'open' },
-      Name: 'Acme',
-      Status: 'open',
+      // Field names are dynamic per table — don't hard-code them, or the static
+      // sample fails Zapier's T004 subset check against a real run's keys.
+      fields: {},
     },
   },
 };

packages/zapier/src/creates/create_record.ts

@@ -66,9 +66,9 @@ export default {
     sample: {
       id: 'recXXXXXXXXXXXX',
       createdTime: '2026-01-01T00:00:00.000Z',
-      fields: { Name: 'Acme', Status: 'open' },
-      Name: 'Acme',
-      Status: 'open',
+      // Field names are dynamic per table — don't hard-code them, or the static
+      // sample fails Zapier's T004 subset check against a real run's keys.
+      fields: {},
     },
   },
 };

packages/zapier/src/creates/update_record.ts

@@ -71,9 +71,9 @@ export default {
     sample: {
       id: 'recXXXXXXXXXXXX',
       lastModifiedTime: '2026-01-01T00:00:00.000Z',
-      fields: { Name: 'Acme', Status: 'paid' },
-      Name: 'Acme',
-      Status: 'paid',
+      // Field names are dynamic per table — don't hard-code them, or the static
+      // sample fails Zapier's T004 subset check against a real run's keys.
+      fields: {},
     },
   },
 };

packages/zapier/src/searches/find_record.ts

@@ -57,8 +57,9 @@ export default {
     perform,
     sample: {
       id: 'recXXXXXXXXXXXX',
-      fields: { Name: 'Acme' },
-      Name: 'Acme',
+      // Field names are dynamic per table — don't hard-code them, or the static
+      // sample fails Zapier's T004 subset check against a real run's keys.
+      fields: {},
     },
   },
 };

packages/zapier/src/searches/get_record.ts

@@ -61,8 +61,9 @@ export default {
     sample: {
       id: 'recXXXXXXXXXXXX',
       lastModifiedTime: '2026-01-01T00:00:00.000Z',
-      fields: { Name: 'Acme' },
-      Name: 'Acme',
+      // Field names are dynamic per table — don't hard-code them, or the static
+      // sample fails Zapier's T004 subset check against a real run's keys.
+      fields: {},
     },
   },
 };

packages/zapier/src/triggers/new_or_updated_record.ts

@@ -60,14 +60,16 @@ export default {
       },
     ],
     perform,
+    // Only stable system keys here. Field names are dynamic (they differ per
+    // table/user and get spread to the top level by flatten()), so we must NOT
+    // hard-code field names like Name/Status — they won't appear in a live run,
+    // which fails Zapier's T004 "static sample is a subset of live keys" check.
     sample: {
       id: 'recXXXXXXXXXXXX@2026-01-01T00:00:00.000Z',
       recordId: 'recXXXXXXXXXXXX',
       createdTime: '2026-01-01T00:00:00.000Z',
       lastModifiedTime: '2026-01-01T00:00:00.000Z',
-      fields: { Name: 'Acme', Status: 'paid' },
-      Name: 'Acme',
-      Status: 'paid',
+      fields: {},
     },
   },
 };

packages/zapier/src/triggers/new_record.ts

@@ -54,9 +54,9 @@ export default {
       id: 'recXXXXXXXXXXXX',
       createdTime: '2026-01-01T00:00:00.000Z',
       lastModifiedTime: '2026-01-01T00:00:00.000Z',
-      fields: { Name: 'Acme', Status: 'open' },
-      Name: 'Acme',
-      Status: 'open',
+      // Field names are dynamic per table — don't hard-code them, or the static
+      // sample fails Zapier's T004 subset check against a real run's keys.
+      fields: {},
     },
   },
 };