examples: add reviewable private Zapier chat action

[acedatacloud-dev]

Summary

Add one reviewable, source-only AceDataCloud Zapier Create Chat Response action. It validates API tokens with non-billable GET /v1/models, loads the current chat model catalog, sends a single text-only non-streaming completion request, and exposes response and token-usage fields. Credential, access, balance, rate-limit, refusal, and empty-response failures are handled explicitly.

Prepare the private rollout and later App Directory review with an English user guide, API-key screenshots, tagged acquisition links, a marketing homepage, a transparent 512 px / 72 DPI icon, and a publication worksheet. The worksheet records private installation, enabled Zap History, per-call terminal billing, and attribution separately, and includes a current-price two-call budget candidate. Node 22 CI now validates the schema and builds the integration archive.

Validation

Validated on Node 22 on 2026-10-12:

• npm test: 7/7 focused action/auth tests passed.
• npm run validate: no structural errors.
• npm run validate:publish: 26 checks passed, 0 failed, 0 publishing warnings. Two general suggestions remain: D002 for the user-defined connection-name help link and D027 recommending core 19.2.0. The configured package proxy reports latest 19.1.0 and returns 404 for 19.2.0; direct npm registry access failed, so the verified 19.1.0 core/CLI pin is retained.
• npm run build: successful runtime and source archives. Runtime ZIP is 839,035 bytes and omits the CLI dev dependency; source ZIP is 165,557 bytes, includes the guides, and omits node_modules. Neither contains .env or .zapierrc.
• npm audit --omit=dev: 0 vulnerabilities. The full dependency audit still has 36 advisories, including 5 critical in development dependencies; the CLI is excluded from the runtime archive. The form-data override remains at patched 4.0.6.
• Real read-only calls through Zapier core locally: the picker returned 93 chat models and the authentication test rejected an invalid token. No paid completion was executed.
• Marketing, policy, support, tagged navigation, and tutorial-image URLs returned HTTP 200. These HTTP reads do not prove registration or usage attribution.
• git diff --check passed.
• CI run 38204630051 passed all 9 jobs on 90b270f9275e0214b8ccd7b3da8d8d9e8bd0ed27, including the build-enabled Zapier Integration job. The branch has 0 commits behind current main.

Rollout and remaining evidence

0.0.1 remains source-only: no uploaded private version, integration ID, installed Zap, successful enabled Zap History, terminal usage record, or App Directory listing is evidenced. An existing AceDataCloud-owned Developer account/deploy key is required before private push; an authorized owner must handle any Platform Agreement acceptance. The current environment has no available browser or Zapier CLI login file.

The proposed live case is gpt-4o-mini, prompt Reply with exactly: ACE_ZAPIER_OK, at most 32 completion tokens, one editor Test and one enabled Zap run. Current rules estimate about 0.00012110 Credits for two calls assuming 64 input tokens each; the worksheet proposes a 0.01 Credit authorization ceiling. This is not an execution authorization, account-rate verification, or hard spending cap. Confirm the actual package rate and balance precheck first, and disable the test Zap after one event.

A chat POST has no cross-request idempotency key. A 429 asks Zapier to retry, and an uncertain run must be checked against usage before replay. Preserve the production API/auth boundary and do not add an unapproved model fallback.

Before public review, record a matching-domain admin, the secure non-expiring feature-enabled test account, the actual published help URL, and a successful enabled Zap for the action. Prepare a new public version deliberately and read its lifecycle state before any overwrite or promotion. Private upload is D0; only a verified searchable/installable public listing can establish D1. Source/CI success establishes no market availability.

No merge or publication has been performed. Human review remains the next source-release step.

[acedatacloud-dev]

POC validation update: the app definition passes zapier-platform-core@19.1.0's compileApp plus validateApp schema check with zero errors. The token field is now explicitly type: password; 3 focused local tests pass. The standalone CLI package fetch stalled, so this does not claim a Zapier developer-account upload or a live Zap run.