Milestone 0: import zappier billing, Verae middleware, and Zapier research

Compose-ready workspace: packages/zappier (rate card, portal, Stripe),
packages/verae-zapier-middleware (timestamp + NATS), packages/verae-zapier
(CLI app), vendor/zapier-platform, and research/zapier vendor corpus.

Gate 0 structure checks pass. Product code and research are not yet wired.

vendor/zapier-platform/example-apps/middleware/triggers/movie.js

@@ -0,0 +1,41 @@
+module.exports = {
+  key: 'movie',
+
+  noun: 'Movie',
+  display: {
+    label: 'New Movie',
+    description: 'Trigger when a new movie is added.',
+  },
+
+  operation: {
+    perform: {
+      url: 'https://auth-json-server.zapier-staging.com/movies',
+      params: {
+        // Just a demo, this is NOT how you normally do authentication.
+        // Refer to https://docs.zapier.com/platform/reference/cli-docs#authentication
+        api_key: 'secret',
+      },
+    },
+
+    // In cases where Zapier needs to show an example record to the user, but we are unable to get a live example
+    // from the API, Zapier will fallback to this hard-coded sample. It should reflect the data structure of
+    // returned records, and have obviously dummy values that we can show to any user.
+    sample: {
+      id: 1,
+      releaseDate: 1472069465,
+      title: 'Test Title',
+      genre: 'Sci-Fi',
+    },
+
+    // If the resource can have fields that are custom on a per-user basis, define a function to fetch the custom
+    // field definitions. The result will be used to augment the sample.
+    // outputFields: () => { return []; }
+    // Alternatively, a static field definition should be provided, to specify labels for the fields
+    outputFields: [
+      { key: 'id', label: 'ID' },
+      { key: 'releaseDate', label: 'Release Date' },
+      { key: 'title', label: 'Title' },
+      { key: 'genre', label: 'Genre' },
+    ],
+  },
+};

vendor/zapier-platform/example-apps/middleware/triggers/recipe.js

@@ -0,0 +1,48 @@
+module.exports = {
+  key: 'recipe',
+
+  // You'll want to provide some helpful display labels and descriptions
+  // for users. Zapier will put them into the UX.
+  noun: 'Recipe',
+  display: {
+    label: 'New Recipe',
+    description: 'Trigger when a new recipe is added.',
+  },
+
+  // `operation` is where we make the call to your API
+  operation: {
+    perform: {
+      url: 'https://auth-json-server.zapier-staging.com/recipes',
+      params: {
+        // Just a demo, this is NOT how you normally do authentication.
+        // Refer to https://docs.zapier.com/platform/reference/cli-docs#authentication
+        api_key: 'secret',
+      },
+    },
+
+    // In cases where Zapier needs to show an example record to the user, but we are unable to get a live example
+    // from the API, Zapier will fallback to this hard-coded sample. It should reflect the data structure of
+    // returned records, and have obviously dummy values that we can show to any user.
+    sample: {
+      id: 1,
+      createdAt: 1472069465,
+      name: 'Best Spagetti Ever',
+      authorId: 1,
+      directions: '1. Boil Noodles\n2.Serve with sauce',
+      style: 'italian',
+    },
+
+    // If the resource can have fields that are custom on a per-user basis, define a function to fetch the custom
+    // field definitions. The result will be used to augment the sample.
+    // outputFields: () => { return []; }
+    // Alternatively, a static field definition should be provided, to specify labels for the fields
+    outputFields: [
+      { key: 'id', label: 'ID' },
+      { key: 'createdAt', label: 'Created At' },
+      { key: 'name', label: 'Name' },
+      { key: 'directions', label: 'Directions' },
+      { key: 'authorId', label: 'Author ID' },
+      { key: 'style', label: 'Style' },
+    ],
+  },
+};