@zapier/zapier-sdk-cli 0.52.10 → 0.53.0

package/CHANGELOG.md

@@ -1,5 +1,61 @@
 # @zapier/zapier-sdk-cli
 
+## 0.53.0
+
+### Minor Changes
+
+- 41a7c26: Add `zapier-sdk signup` for browser-based account setup and local SDK credential provisioning.
+  Add the `signup_success` SDK lifecycle telemetry event type for successful signup OAuth callback acceptance.
+
+### Patch Changes
+
+- Updated dependencies [41a7c26]
+  - @zapier/zapier-sdk@0.68.0
+  - @zapier/zapier-sdk-mcp@0.13.22
+
+## 0.52.12
+
+### Patch Changes
+
+- a950509: Route all debug, diagnostic, and telemetry log output to stderr (`console.error`) instead of stdout (`console.log`) across the SDK and CLI packages. The CLI now reserves stdout exclusively for the program's data payload — command output, JSON envelopes, response bodies — so callers can safely pipe CLI output through `jq`, `> redirect`, or `JSON.parse` even when `--debug` is on or telemetry/logging flags are enabled. Interactive terminal users see no change since both streams interleave in a TTY.
+- 9096184: Extract the plugin framework into a new sibling package `kitcore` that
+  `@zapier/zapier-sdk` consumes as a workspace devDependency (bundled into
+  the published dist, not a runtime dep). Existing SDK code is unaffected:
+  `createZapierSdk`, `createSdk`, the `ZapierSdk` type, every SDK method, and
+  the full `Zapier*` error hierarchy keep their names, codes, and `instanceof`
+  semantics. Internally `createZapierSdk` now builds via the linear
+  `createPluginStack().use(...).toSdk()` path, which substantially speeds up
+  construction. One behavior change to note: `normalizeError` no longer wraps
+  thrown `Error` subclasses, so a handler's `TypeError` or a userland
+  `MyAppError` bubbles through unchanged and `instanceof` works again; only
+  non-`Error` throws get wrapped.
+
+  New stack-based composition surface for building on top of the SDK:
+  `createZapierSdkStack(options)` (from the root and `/experimental`) returns
+  the unsealed `PluginStack` that `createZapierSdk` materializes, and
+  `createPluginStack`, `createCorePlugin`, and `addPlugin` are re-exported from
+  the root. Build by chaining `.use(...)` and sealing with `.toSdk()`, or
+  extend a sealed SDK in place with `addPlugin(sdk, plugin)`. The chain-style
+  `createSdk().addPlugin(...)` pattern is deprecated (now logs a one-time
+  warning) but still works; the CLI and MCP packages moved their internal
+  assembly to stacks with no change to their commands or tools.
+
+- Updated dependencies [a950509]
+- Updated dependencies [9096184]
+  - @zapier/zapier-sdk@0.67.0
+  - @zapier/zapier-sdk-mcp@0.13.21
+
+## 0.52.11
+
+### Patch Changes
+
+- 0eb6a76: Add the `triggerWorkflow` experimental code-substrate plugin. Lives behind `@zapier/zapier-sdk/experimental` only — the stable subpath does not surface it. Looks up the workflow's `trigger_url` via the durableworkflowzaps API, then POSTs the user-supplied JSON payload to that URL. The trigger endpoint is tokenized (the URL embeds a secret) and takes no auth header, so the SDK uses a raw `fetch` rather than the api plugin for the second leg. Custom fetch flows through `sdk.context.options.fetch` for tests. The workflow id is UUID-validated at the input boundary; trigger endpoint failures (non-2xx, or workflow with no published version) surface as descriptive errors. The CLI gets the `workflowIdResolver` picker for the workflow input.
+- Updated dependencies [66db7cb]
+- Updated dependencies [c7c8f64]
+- Updated dependencies [0eb6a76]
+  - @zapier/zapier-sdk@0.66.0
+  - @zapier/zapier-sdk-mcp@0.13.20
+
 ## 0.52.10
 
 ### Patch Changes

package/README.md

@@ -11,6 +11,7 @@
   - [`get-profile`](#get-profile)
   - [`login`](#login)
   - [`logout`](#logout)
+  - [`signup`](#signup)
 - [Actions](#actions)
   - [`get-action`](#get-action)
   - [`get-action-input-fields-schema`](#get-action-input-fields-schema)
@@ -42,6 +43,7 @@
   - [`list-workflows`](#list-workflows--experimental)
   - [`publish-workflow-version`](#publish-workflow-version--experimental)
   - [`run-durable`](#run-durable--experimental)
+  - [`trigger-workflow`](#trigger-workflow--experimental)
   - [`update-workflow`](#update-workflow--experimental)
 - [Connections](#connections)
   - [`find-first-connection`](#find-first-connection)
@@ -218,6 +220,25 @@ Log out of your Zapier account
 npx zapier-sdk logout
 ```
 
+#### `signup`
+
+Set up Zapier account access and SDK credentials
+
+**Options:**
+
+| Option              | Type      | Required | Default | Possible Values | Description                                                                                                                                                                                |
+| ------------------- | --------- | -------- | ------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `--timeout`         | `string`  | ❌       | —       | —               | Signup timeout in seconds (default: 300)                                                                                                                                                   |
+| `--use-approvals`   | `boolean` | ❌       | —       | —               | Require approvals for actions performed with these credentials                                                                                                                             |
+| `--non-interactive` | `boolean` | ❌       | —       | —               | Skip interactive prompts. Uses defaults where possible; errors instead of prompting when input is required. Useful in CI, piped output, or environments where TTY detection is unreliable. |
+| `--headless`        | `boolean` | ❌       | —       | —               | Use when signing up from a machine that has no browser. Prints a signup link to open elsewhere, then accepts the pasted loopback callback URL.                                             |
+
+**Usage:**
+
+```bash
+npx zapier-sdk signup [--timeout] [--use-approvals] [--non-interactive] [--headless]
+```
+
 ### Actions
 
 #### `get-action`
@@ -711,7 +732,7 @@ Run a workflow source file as a run-once durable run on sdkdurableapi (no deploy
 | Option                     | Type      | Required | Default | Possible Values | Description                                                                                                     |
 | -------------------------- | --------- | -------- | ------- | --------------- | --------------------------------------------------------------------------------------------------------------- |
 | `<source_files>`           | `object`  | ✅       | —       | —               | Source files keyed by filename → contents                                                                       |
-| `--input`                  | `string`  | ❌       | —       | —               | Input data passed to the run                                                                                    |
+| `--input`                  | `unknown` | ❌       | —       | —               | Input data passed to the run                                                                                    |
 | `--dependencies`           | `object`  | ❌       | —       | —               | Optional npm package dependencies                                                                               |
 | `--zapier_durable_version` | `string`  | ❌       | —       | —               | Exact semver of @zapier/zapier-durable to use (e.g. "1.2.3"). Defaults to server-configured version if omitted. |
 | `--connections`            | `object`  | ❌       | —       | —               | Named connection aliases. Maps alias names to Zapier connection IDs.                                            |
@@ -724,6 +745,23 @@ Run a workflow source file as a run-once durable run on sdkdurableapi (no deploy
 npx zapier-sdk run-durable <source_files> [--input] [--dependencies] [--zapier_durable_version] [--connections] [--app_versions] [--private]
 ```
 
+#### `trigger-workflow` 🧪 _experimental_
+
+Look up a workflow's trigger URL and fire it manually. The trigger endpoint is tokenized (the URL contains a secret) and takes no auth header, so the SDK uses a raw fetch rather than the api plugin.
+
+**Options:**
+
+| Option       | Type      | Required | Default | Possible Values | Description                                                                                              |
+| ------------ | --------- | -------- | ------- | --------------- | -------------------------------------------------------------------------------------------------------- |
+| `<workflow>` | `string`  | ✅       | —       | —               | Durable workflow ID                                                                                      |
+| `--input`    | `unknown` | ❌       | —       | —               | JSON payload delivered as the trigger body. Sent as `application/json`; omit to fire with an empty body. |
+
+**Usage:**
+
+```bash
+npx zapier-sdk trigger-workflow <workflow> [--input]
+```
+
 #### `update-workflow` 🧪 _experimental_
 
 Update a durable workflow's name and/or description