George Lambert
b4150c8250
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.
34 lines
1.5 KiB
JavaScript
34 lines
1.5 KiB
JavaScript
'use strict';
|
|
|
|
// You want to make a request to an endpoint that is either specifically designed
|
|
// to test auth, or one that every user will have access to. eg: `/me`.
|
|
// By returning the entire request object, you have access to the request and
|
|
// response data for testing purposes. Your connection label can access any data
|
|
// from the returned response using the `json.` prefix. eg: `{{json.username}}`.
|
|
const test = (z, bundle) =>
|
|
z.request({
|
|
url: 'https://httpbin.zapier-tooling.com/digest-auth/auth/myuser/mypass',
|
|
});
|
|
|
|
module.exports = {
|
|
// "digest" auth automatically creates "username" and "password" input fields. It
|
|
// also registers default middleware to create the authentication header.
|
|
type: 'digest',
|
|
|
|
// Define any input app's auth requires here. The user will be prompted to enter
|
|
// this info when they connect their account.
|
|
fields: [],
|
|
|
|
// The test method allows Zapier to verify that the credentials a user provides
|
|
// are valid. We'll execute this method whenever a user connects their account for
|
|
// the first time.
|
|
test,
|
|
|
|
// This template string can access all the data returned from the auth test. If
|
|
// you return the test object, you'll access the returned data with a label like
|
|
// `{{json.X}}`. If you return `response.data` from your test, then your label can
|
|
// be `{{X}}`. This can also be a function that returns a label. That function has
|
|
// the standard args `(z, bundle)` and data returned from the test can be accessed
|
|
// in `bundle.inputData.X`.
|
|
connectionLabel: '{{json.username}}',
|
|
};
|