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.
This commit is contained in:
George Lambert 2026-09-09 02:37:36 -04:00
commit b4150c8250
1364 changed files with 6814366 additions and 0 deletions

View file

@ -0,0 +1,6 @@
build
docs
node_modules
*.log
.environment
.env

View file

@ -0,0 +1,7 @@
language: node_js
node_js:
- 8.10.0
before_script: 'npm install -g zapier-platform-cli'
script: 'zapier test'
notifications:
email: false

View file

@ -0,0 +1,7 @@
# HTTP Search Example App For Zapier Platform
[![Build Status](https://travis-ci.org/zapier/zapier-platform-example-app-search.svg?branch=master)](https://travis-ci.org/zapier/zapier-platform-example-app-search)
A simple app that demonstrates how to write a simple search action.
> We recommend using the zapier-platform-cli and `zapier-platform init .`  to create an app - youll be presented with a list of currently available templates to start with.

View file

@ -0,0 +1,35 @@
const search = require('./searches/recipe');
const addAuthHeader = (request, z, bundle) => {
// Hard-coded auth header just for demo
request.headers['X-API-Key'] = 'secret';
return request;
};
// Now we can roll up all our behaviors in an App.
const App = {
// This is just shorthand to reference the installed dependencies you have. Zapier will
// need to know these before we can upload
version: require('./package.json').version,
platformVersion: require('zapier-platform-core').version,
beforeRequest: [addAuthHeader],
afterResponse: [],
resources: {},
// If you want your trigger to show up, you better include it here!
triggers: {},
// If you want your searches to show up, you better include it here!
searches: {
[search.key]: search,
},
// If you want your creates to show up, you better include it here!
creates: {},
};
// Finally, export the app.
module.exports = App;

View file

@ -0,0 +1,25 @@
{
"name": "zapier-platform-example-app-search",
"version": "1.0.0",
"description": "An example app for the Zapier platform.",
"repository": "zapier/zapier-platform-example-app-search",
"homepage": "https://zapier.com/",
"author": "Bryan Helmig <bryan@zapier.com>",
"license": "BSD-3-Clause",
"main": "index.js",
"scripts": {
"test": "mocha --recursive"
},
"engines": {
"node": ">=8.10.0",
"npm": ">=5.6.0"
},
"dependencies": {
"zapier-platform-core": "19.1.0"
},
"devDependencies": {
"mocha": "^5.2.0",
"should": "^13.2.0"
},
"private": true
}

View file

@ -0,0 +1,65 @@
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: 'Find a Recipe',
description: 'Search for recipe by cuisine style.',
},
// `operation` is where we make the call to your API to do the search
operation: {
// This search only has one search field. Your searches might have just one, or many
// search fields.
inputFields: [
{
key: 'style',
type: 'string',
label: 'Style',
helpText:
'Cuisine style to limit to the search to (i.e. mediterranean or italian).',
},
],
perform: (z, bundle) => {
const url = 'https://auth-json-server.zapier-staging.com/recipes';
// Put the search value in a query param. The details of how to build
// a search URL will depend on how your API works.
const options = {
params: {
style: bundle.inputData.style,
},
};
return z.request(url, options).then((response) => response.data);
},
// 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' },
],
},
};

View file

@ -0,0 +1,33 @@
/* globals describe, it */
const should = require('should'); // required to use .exist()
const zapier = require('zapier-platform-core');
const App = require('../index');
const appTester = zapier.createAppTester(App);
describe('searches', () => {
describe('search recipe', () => {
it('should find a recipe', (done) => {
const bundle = {
inputData: {
style: 'style 2',
},
};
appTester(App.searches.recipe.operation.perform, bundle)
.then((results) => {
results.length.should.be.aboveOrEqual(1);
const firstRecipe = results[0];
firstRecipe.style.should.eql('style 2');
should.exist(firstRecipe.name);
should.exist(firstRecipe.directions);
done();
})
.catch(done);
});
});
});