@elevasis/sdk 0.5.12 → 0.5.14

package/reference/{troubleshooting/common-errors.mdx → troubleshooting.mdx}

@@ -1,210 +1,223 @@
----
-title: "Common Errors"
-description: "Static SDK-level error catalog -- CLI errors, deployment errors, schema validation, platform tool failures, and runtime errors with diagnostic steps"
-loadWhen: "Debugging an unknown error not found in workspace memory"
----
-
-This is the static SDK-level error catalog. Check `.claude/memory/errors/` first for workspace-specific fixes. Use this file when the error is new to the workspace or when the memory has no match.
-
----
-
-## CLI Errors
-
-### ELEVASIS_API_KEY not set
-
-**Cause:** The `.env` file is missing the API key, or the file was not loaded.
-
-**Fix:**
-1. Check that `.env` exists in the workspace root
-2. Confirm it contains `ELEVASIS_API_KEY=sk_...`
-3. Make sure you are running the CLI from the workspace directory (where `.env` is located)
-4. If the file exists with the right content, run `elevasis-sdk check` again
-
-### Cannot connect to API
-
-**Cause:** Network issue or the API URL is incorrect.
-
-**Fix:**
-1. Check your internet connection
-2. If using a custom API URL via `--api-url` or `ELEVASIS_API_URL`, verify it is correct
-3. Remove `NODE_ENV=development` from `.env` if you are not running a local API server
-
-### NODE_ENV=development in .env
-
-**Cause:** The SDK is pointing at a local API server (port 5170 by default) instead of the hosted platform.
-
-**Fix:** Remove `NODE_ENV=development` from `.env`. The CLI connects to the hosted platform by default.
-
----
-
-## Validation Errors (elevasis-sdk check)
-
-### Duplicate resource ID
-
-**Message:** `Duplicate resource ID 'name' in organization 'org'`
-
-**Cause:** Two resources in `src/` share the same `resourceId`.
-
-**Fix:** Each resource must have a unique `resourceId` within your organization. Check all domain directories in `src/` and rename the duplicate.
-
-### Workflow step references non-existent next step
-
-**Message:** `Workflow step 'stepA' references non-existent next step 'stepB'`
-
-**Cause:** A step's `next.target` or `next.routes[*].target` points to a step name that does not exist in the `steps` record.
-
-**Fix:** Check the spelling of the target step name. All target values must exactly match keys in the `steps` object.
-
-### Missing entryPoint
-
-**Cause:** The workflow's `entryPoint` field names a step that does not exist in `steps`.
-
-**Fix:** Confirm `entryPoint` matches an exact key in your `steps` record.
-
----
-
-## Schema Validation Errors
-
-### Schema validation failed (input)
-
-**Message:** `Schema validation failed` with field-level details
-
-**Cause:** The input passed to the workflow does not match the `inputSchema`.
-
-**Fix:**
-1. Read the error's field details -- it names the failing field and expected type
-2. Compare against your `inputSchema` definition
-3. Common causes: wrong type (string vs number), missing required field, extra field not in schema, misspelled field name
-4. Check that `z.infer` types match what your handler actually receives
-
-### outputSchema validation failed
-
-**Cause:** Your handler's return value does not match the workflow's `outputSchema`.
-
-**Fix:**
-1. Compare what your handler returns to what `outputSchema` expects
-2. Check field names for typos (the schema says `companyName`, handler returns `company_name`)
-3. Check types -- the schema says `z.number()` but the handler returns a string
-4. Check required vs optional -- do not return undefined for a required field
-
-### Cannot find name 'z'
-
-**Cause:** Missing Zod import.
-
-**Fix:** Add `import { z } from 'zod'` at the top of the file.
-
----
-
-## TypeScript Errors
-
-### Type 'X' is not assignable to type 'Y'
-
-**Cause:** The data flowing into a step or returned from a handler does not match the declared type.
-
-**Fix:**
-1. Check the input type annotation on the handler: `async (input: MyInput) => ...`
-2. Confirm the `z.infer<typeof mySchema>` type matches what the previous step returns
-3. Check that all optional fields are handled (do not assume they are always present)
-
-### Cannot find module '@elevasis/sdk'
-
-**Cause:** Dependencies are not installed.
-
-**Fix:** Run `pnpm install` in the workspace root.
-
-### Cannot find module '@elevasis/sdk/worker'
-
-**Cause:** Dependencies not installed, or using an old SDK version that does not export the `worker` subpath.
-
-**Fix:**
-1. Run `pnpm install`
-2. Check that `@elevasis/sdk` version is recent enough to include `worker` export
-3. Confirm your `tsconfig.json` has `"moduleResolution": "Bundler"` or `"NodeNext"`
-
----
-
-## Platform Tool Errors
-
-### PlatformToolError: credential not found
-
-**Cause:** The credential name passed to `platform.call()` does not match any credential stored in the platform.
-
-**Fix:**
-1. Check spelling and case -- credential names are case-sensitive
-2. Open the command center and confirm the credential exists and is named exactly as referenced
-3. Check that the credential belongs to the correct organization
-
-### PlatformToolError: credentials_invalid
-
-**Cause:** The credential exists but has the wrong shape for the tool being called.
-
-**Fix:**
-1. For the `http` tool: verify the credential type matches the API's auth method (bearer, api-key-header, basic, etc.)
-2. For the Supabase tool: verify the credential contains `url` and `serviceRoleKey` fields
-3. Re-create the credential in the command center if the format is wrong
-
-### PlatformToolError: timeout_error
-
-**Cause:** The platform tool call took longer than 60 seconds.
-
-**Fix:**
-1. Check if the external API is slow or down
-2. Reduce the amount of data being processed in a single call
-3. For `http` tool: the external endpoint may be unresponsive -- check directly
-
-### PlatformToolError: service_unavailable
-
-**Cause:** The platform service or integration adapter is not available.
-
-**Fix:**
-1. Check the Elevasis status page
-2. Retry -- transient availability issues resolve quickly
-
----
-
-## Runtime Errors
-
-### Execution timeout (300s)
-
-**Cause:** The entire workflow execution exceeded the 300-second limit.
-
-**Fix:**
-1. Identify which step is slow -- check execution logs for step timing
-2. Reduce work per step or parallelize if possible
-3. For long-running operations, consider breaking into multiple workflows with the `execution` platform tool to chain them
-
-### Worker ran out of memory (256MB limit)
-
-**Cause:** The workflow processed too much data in memory at once.
-
-**Fix:**
-1. Reduce the size of data loaded per execution
-2. Use pagination for large data sets (fetch in chunks, process one at a time)
-3. Avoid loading large files or arrays entirely into memory
-
-### Module resolution error at runtime
-
-**Cause:** An import in your workflow bundle cannot be resolved.
-
-**Fix:**
-1. Run `elevasis-sdk check` -- it catches most resolution errors before deploy
-2. If the import is a built-in Node.js module, ensure it is compatible with the worker environment
-3. Avoid imports that require file system access or native modules
-
----
-
-## Memory Error Structure
-
-When recording a new error in `.claude/memory/errors/`, use this table format:
-
-```
-| Error | Context | Fix | Count | Last Seen | Status |
-| --- | --- | --- | --- | --- | --- |
-| `Schema validation failed` on lead-scorer | Added score field | Changed score from z.string() to z.number() | 1 | 2026-02-26 | Resolved |
-```
-
-Status values: `Resolved` (fixed this session), `Recurring` (seen 2+ times), `Promoted` (3+ times, now in Rules).
-
----
-
-**Last Updated:** 2026-02-26
+---
+title: "Common Errors"
+description: "Static SDK-level error catalog -- CLI errors, deployment errors, schema validation, platform tool failures, and runtime errors with diagnostic steps"
+loadWhen: "Debugging an unknown error not found in workspace memory"
+---
+
+This is the static SDK-level error catalog. Check `.claude/memory/errors/` first for workspace-specific fixes. Use this file when the error is new to the workspace or when the memory has no match.
+
+---
+
+## CLI Errors
+
+### ELEVASIS_PLATFORM_KEY not set
+
+**Cause:** The `.env` file is missing the API key, or the file was not loaded.
+
+**Fix:**
+
+1. Check that `.env` exists in the workspace root
+2. Confirm it contains `ELEVASIS_PLATFORM_KEY=sk_...`
+3. Make sure you are running the CLI from the workspace directory (where `.env` is located)
+4. If the file exists with the right content, run `elevasis-sdk check` again
+
+### Cannot connect to API
+
+**Cause:** Network issue or the API URL is incorrect.
+
+**Fix:**
+
+1. Check your internet connection
+2. If using a custom API URL via `--api-url` or `ELEVASIS_API_URL`, verify it is correct
+3. Remove `NODE_ENV=development` from `.env` if you are not running a local API server
+
+### NODE_ENV=development in .env
+
+**Cause:** The SDK is pointing at a local API server (port 5170 by default) instead of the hosted platform.
+
+**Fix:** Remove `NODE_ENV=development` from `.env`. The CLI connects to the hosted platform by default.
+
+---
+
+## Validation Errors (elevasis-sdk check)
+
+### Duplicate resource ID
+
+**Message:** `Duplicate resource ID 'name' in organization 'org'`
+
+**Cause:** Two resources in `src/` share the same `resourceId`.
+
+**Fix:** Each resource must have a unique `resourceId` within your organization. Check all domain directories in `src/` and rename the duplicate.
+
+### Workflow step references non-existent next step
+
+**Message:** `Workflow step 'stepA' references non-existent next step 'stepB'`
+
+**Cause:** A step's `next.target` or `next.routes[*].target` points to a step name that does not exist in the `steps` record.
+
+**Fix:** Check the spelling of the target step name. All target values must exactly match keys in the `steps` object.
+
+### Missing entryPoint
+
+**Cause:** The workflow's `entryPoint` field names a step that does not exist in `steps`.
+
+**Fix:** Confirm `entryPoint` matches an exact key in your `steps` record.
+
+---
+
+## Schema Validation Errors
+
+### Schema validation failed (input)
+
+**Message:** `Schema validation failed` with field-level details
+
+**Cause:** The input passed to the workflow does not match the `inputSchema`.
+
+**Fix:**
+
+1. Read the error's field details -- it names the failing field and expected type
+2. Compare against your `inputSchema` definition
+3. Common causes: wrong type (string vs number), missing required field, extra field not in schema, misspelled field name
+4. Check that `z.infer` types match what your handler actually receives
+
+### outputSchema validation failed
+
+**Cause:** Your handler's return value does not match the workflow's `outputSchema`.
+
+**Fix:**
+
+1. Compare what your handler returns to what `outputSchema` expects
+2. Check field names for typos (the schema says `companyName`, handler returns `company_name`)
+3. Check types -- the schema says `z.number()` but the handler returns a string
+4. Check required vs optional -- do not return undefined for a required field
+
+### Cannot find name 'z'
+
+**Cause:** Missing Zod import.
+
+**Fix:** Add `import { z } from 'zod'` at the top of the file.
+
+---
+
+## TypeScript Errors
+
+### Type 'X' is not assignable to type 'Y'
+
+**Cause:** The data flowing into a step or returned from a handler does not match the declared type.
+
+**Fix:**
+
+1. Check the input type annotation on the handler: `async (input: MyInput) => ...`
+2. Confirm the `z.infer<typeof mySchema>` type matches what the previous step returns
+3. Check that all optional fields are handled (do not assume they are always present)
+
+### Cannot find module '@elevasis/sdk'
+
+**Cause:** Dependencies are not installed.
+
+**Fix:** Run `pnpm install` in the workspace root.
+
+### Cannot find module '@elevasis/sdk/worker'
+
+**Cause:** Dependencies not installed, or using an old SDK version that does not export the `worker` subpath.
+
+**Fix:**
+
+1. Run `pnpm install`
+2. Check that `@elevasis/sdk` version is recent enough to include `worker` export
+3. Confirm your `tsconfig.json` has `"moduleResolution": "Bundler"` or `"NodeNext"`
+
+---
+
+## Platform Tool Errors
+
+### PlatformToolError: credential not found
+
+**Cause:** The credential name passed to `platform.call()` does not match any credential stored in the platform.
+
+**Fix:**
+
+1. Check spelling and case -- credential names are case-sensitive
+2. Open the command center and confirm the credential exists and is named exactly as referenced
+3. Check that the credential belongs to the correct organization
+
+### PlatformToolError: credentials_invalid
+
+**Cause:** The credential exists but has the wrong shape for the tool being called.
+
+**Fix:**
+
+1. For the `http` tool: verify the credential type matches the API's auth method (bearer, api-key-header, basic, etc.)
+2. For the Supabase tool: verify the credential contains `url` and `serviceRoleKey` fields
+3. Re-create the credential in the command center if the format is wrong
+
+### PlatformToolError: timeout_error
+
+**Cause:** The platform tool call took longer than 60 seconds.
+
+**Fix:**
+
+1. Check if the external API is slow or down
+2. Reduce the amount of data being processed in a single call
+3. For `http` tool: the external endpoint may be unresponsive -- check directly
+
+### PlatformToolError: service_unavailable
+
+**Cause:** The platform service or integration adapter is not available.
+
+**Fix:**
+
+1. Check the Elevasis status page
+2. Retry -- transient availability issues resolve quickly
+
+---
+
+## Runtime Errors
+
+### Execution timeout (300s)
+
+**Cause:** The entire workflow execution exceeded the 300-second limit.
+
+**Fix:**
+
+1. Identify which step is slow -- check execution logs for step timing
+2. Reduce work per step or parallelize if possible
+3. For long-running operations, consider breaking into multiple workflows with the `execution` platform tool to chain them
+
+### Worker ran out of memory (256MB limit)
+
+**Cause:** The workflow processed too much data in memory at once.
+
+**Fix:**
+
+1. Reduce the size of data loaded per execution
+2. Use pagination for large data sets (fetch in chunks, process one at a time)
+3. Avoid loading large files or arrays entirely into memory
+
+### Module resolution error at runtime
+
+**Cause:** An import in your workflow bundle cannot be resolved.
+
+**Fix:**
+
+1. Run `elevasis-sdk check` -- it catches most resolution errors before deploy
+2. If the import is a built-in Node.js module, ensure it is compatible with the worker environment
+3. Avoid imports that require file system access or native modules
+
+---
+
+## Memory Error Structure
+
+When recording a new error in `.claude/memory/errors/`, use this table format:
+
+```
+| Error | Context | Fix | Count | Last Seen | Status |
+| --- | --- | --- | --- | --- | --- |
+| `Schema validation failed` on lead-scorer | Added score field | Changed score from z.string() to z.number() | 1 | 2026-02-26 | Resolved |
+```
+
+Status values: `Resolved` (fixed this session), `Recurring` (seen 2+ times), `Promoted` (3+ times, now in Rules).
+
+---
+
+**Last Updated:** 2026-02-26

package/dist/types/worker/adapters/trello.d.ts

@@ -1,14 +0,0 @@
-/**
- * Trello Integration Adapter
- *
- * Typed wrapper over platform.call() for Trello board operations.
- * Uses factory pattern -- credential is bound once at construction time.
- */
-import type { TrelloToolMap } from '../../types/index.js';
-/**
- * Create a typed Trello adapter bound to a specific credential.
- *
- * @param credential - Credential name as configured in the command center
- * @returns Object with 10 typed methods for Trello board operations
- */
-export declare function createTrelloAdapter(credential: string): import("./create-adapter.js").TypedAdapter<TrelloToolMap>;

package/reference/concepts/index.mdx

@@ -1,203 +0,0 @@
----
-title: Concepts Reference
-description: Plain-English explanations of Elevasis SDK concepts -- glossary, workflow analogies, Zod schemas, execution model, platform tools, common errors, and design decisions
-loadWhen: "User asks what is or needs conceptual grounding"
----
-
-This page covers core Elevasis concepts in plain English. It is the teaching vocabulary for the agent when helping you build workflows, and a reference you can return to whenever a term or behavior is unclear.
-
-## Glossary
-
-| Term | Definition |
-| --- | --- |
-| Workflow | A series of named steps that run one after another. Each step does one job. The workflow receives input data and produces output data. |
-| Agent | An autonomous AI resource with access to platform tools. Agents can make decisions and call tools on their own. Run agents with `--async` to avoid HTTP timeout limits on long-running executions. |
-| Resource | Anything you deploy to the platform -- a workflow or an agent. Each resource has a unique ID. |
-| Step | One job inside a workflow. A step receives data, processes it, and passes data to the next step. |
-| Schema | A description of what your data looks like. Schemas validate that input and output data has the right shape -- the right fields with the right types. |
-| Credential | A saved API key or login for an external service (Gmail, Attio, Stripe). Stored securely on the platform, never in your code. |
-| Execution | One run of a resource. Each time someone triggers your workflow, that is one execution. |
-| Deployment | The act of uploading your code to the platform. After deploying, your resources are live and can be executed. |
-| Platform Tool | A pre-built integration the platform provides. You call platform tools from your workflow steps using `platform.call()`. |
-| Organization | Your team or company on the Elevasis platform. Resources, credentials, and executions belong to an organization. |
-| Handler | The function inside a step that does the actual work. It receives input data and returns output data. |
-| Entry Point | The first step that runs when a workflow is executed. Every workflow must have one. |
-| Resource ID | A unique lowercase name for your resource (e.g., `lead-scorer`, `send-welcome-email`). Must be unique within your organization. |
-| Workspace | Your Elevasis project directory. Contains resources (workflows and agents), documentation, and optionally a database connection and custom apps. Created by `elevasis-sdk init`. |
-| Data Table | A table in your database (e.g., Supabase) that stores structured data your workflows can read and write. Defined in `data/schema.ts` as documentation for the agent. |
-
----
-
-## What is a Workflow?
-
-A workflow is a piece of automation that runs on the Elevasis platform. You define the steps in TypeScript; the platform handles running them, logging results, and retrying on failure.
-
-### Two Analogies
-
-**Recipe analogy:** A recipe has ingredients (input), instructions (steps), and a finished dish (output). Each instruction is one step. You follow them in order. If a step fails (you burn the sauce), the recipe stops.
-
-**Assembly line analogy:** Raw material goes in one end (input). Each station does one job (step). The finished product comes out the other end (output).
-
-### When to Use a Workflow
-
-- Automating a repeatable task with defined input and output
-- Chaining multiple actions together (fetch data, process it, send an email)
-- When you need the platform to handle execution, retries, and logging
-
-### When NOT to Use a Workflow
-
-- One-off tasks you will only do once
-- Tasks that need constant human judgment at every step
-
----
-
-## Understanding Schemas (Zod)
-
-### What Schemas Do
-
-Schemas describe and validate the shape of data your workflow expects and produces. If someone sends the wrong data, the platform rejects it before your code runs. This prevents confusing errors deep inside your handler.
-
-The Elevasis SDK uses [Zod](https://zod.dev) for schema definition. Zod is a TypeScript-first validation library. Every workflow has an `inputSchema` and an `outputSchema`.
-
-### Common Zod Types
-
-| Zod Type | What It Means | Example |
-| --- | --- | --- |
-| `z.string()` | Text | `"hello"`, `"user@email.com"` |
-| `z.number()` | A number | `42`, `3.14` |
-| `z.boolean()` | True or false | `true`, `false` |
-| `z.array(z.string())` | A list of text values | `["a", "b", "c"]` |
-| `z.object({ name: z.string() })` | A group of named fields | `{ "name": "Jane" }` |
-| `z.string().optional()` | Text that might be missing | `"hello"` or not provided |
-| `z.enum(['a', 'b', 'c'])` | One of a specific set of values | `"a"` |
-| `z.string().email()` | Text that must be a valid email | `"user@example.com"` |
-
-### Why `z.infer` Exists
-
-`z.infer` creates a TypeScript type from a schema so the type system can check your code. You define the schema once and get both runtime validation and compile-time checking. Without it, you would have to define the same shape twice -- once as a Zod schema and once as a TypeScript type.
-
-```ts
-const myInput = z.object({ name: z.string(), age: z.number() });
-type MyInput = z.infer<typeof myInput>;
-// MyInput is now: { name: string; age: number }
-```
-
-### Common Schema Mistakes
-
-- Forgetting `.optional()` on fields that might be missing -- the platform will reject valid input that omits those fields
-- Returning data from a handler that does not match the output schema -- causes `outputSchema validation failed`
-- Misspelling field names -- the schema says `companyName`, but the handler returns `company_name`
-
----
-
-## The Execution Model
-
-### What Happens When You Run a Workflow
-
-1. A request arrives at the Elevasis platform (someone runs `elevasis-sdk exec` or a schedule triggers)
-2. The platform creates a temporary server just for this execution
-3. Your code runs on that server
-4. The result is sent back
-5. The temporary server is deleted
-
-### Practical Implications
-
-| What You Might Expect | What Actually Happens | Why |
-| --- | --- | --- |
-| Files I create persist | Files disappear after execution | The server is temporary |
-| I can see logs in real-time | Logs appear after execution completes | No streaming from workers |
-| My code runs on my computer | Your code runs on Elevasis servers | That is what "deploy" means |
-| I can use unlimited memory | 256MB memory limit per execution | Prevents runaway processes |
-| Executions share state | Each execution is independent | No shared memory between runs |
-| I can call external APIs | Yes, outbound network is unrestricted | Workers have internet access |
-
-### What "completed" vs "failed" Means
-
-- **completed** -- Your code ran successfully and returned output
-- **failed** -- Something went wrong: your code threw an error, timed out (300s default), or ran out of memory
-
----
-
-## Platform Tools Overview
-
-Platform tools are pre-built integrations the platform provides. You call them from inside workflow steps using `platform.call()` without managing API keys in your code.
-
-### Tool Categories
-
-| Category | Tools | Example Use |
-| --- | --- | --- |
-| Communication | Gmail, Resend, email | Send transactional emails, notifications |
-| CRM | Attio (11 methods) | Create leads, update records, search contacts |
-| Documents | PDF, Google Sheets, Notion | Generate invoices, read spreadsheets, update pages |
-| AI | LLM (GPT, Gemini, Claude) | Classify text, extract data, generate content |
-| Storage | Dropbox, platform storage | Upload files, create signed URLs |
-| Scheduling | Scheduler | Run workflows on a schedule or after a delay |
-| Approvals | Approval gates | Pause workflow until a human approves |
-| Verification | Mailso | Verify email addresses |
-| E-Signatures | SignatureAPI | Create and manage document envelopes |
-| Marketing | Instantly | Send email campaigns |
-| Payments | Stripe | Create payment links, checkout sessions |
-| Automation | Apify | Run web scraping actors |
-
-### How Credentials Work
-
-1. Create a credential in the Elevasis platform (API key, OAuth token, etc.) via the command center UI
-2. Give it a name (e.g., `my-gmail`, `production-attio`)
-3. In your code, pass that name: `platform.call({ credential: 'my-gmail', ... })`
-4. The platform injects the actual API key at runtime -- it never appears in your code
-
-### What Happens When a Credential Name is Wrong
-
-You will see a `PlatformToolError` with the message "credential not found". Check for typos -- credential names are case-sensitive.
-
----
-
-## Common Errors and Fixes
-
-| Error | What It Means | How to Fix |
-| --- | --- | --- |
-| `ELEVASIS_API_KEY not set` | Your `.env` file is missing the API key | Add `ELEVASIS_API_KEY=sk_...` to `.env` |
-| `Schema validation failed` | The input data does not match your Zod schema | Compare the error's field names to your schema definition. Check types (string vs number) and required vs optional fields. |
-| `Cannot find module '@elevasis/sdk'` | Dependencies are not installed | Run `pnpm install` |
-| `PlatformToolError: credential not found` | The credential name in your code does not match any stored credential | Check spelling and case. Verify the credential name in the command center UI. |
-| `Execution timeout (300s)` | Your workflow took too long | Optimize your handler or break it into smaller steps. Check for infinite loops. |
-| `Cannot find name 'z'` | Missing Zod import | Add `import { z } from 'zod'` at the top of your file |
-| `Type 'X' is not assignable to type 'Y'` | Your handler returns data that does not match the output schema | Compare what your handler returns to what `outputSchema` expects. Field names and types must match exactly. |
-| `outputSchema validation failed` | Handler returned data but it does not match the output schema | Check field names, types, and required fields against your output schema. |
-| `Duplicate resource ID` | Two resources have the same `resourceId` | Each resource needs a unique ID within your organization. Rename one. |
-| `NODE_ENV=development` in .env | SDK is trying to connect to a local API server | Remove `NODE_ENV` from your `.env` file. The SDK connects to the hosted platform by default. |
-
----
-
-## Design Decisions Guide
-
-### Single-Step vs Multi-Step
-
-Use a single step when the workflow does one thing -- validate an email, format a message, call one API.
-
-Use multiple steps when you have distinct phases (fetch data, process it, send a notification) or when you want separate error handling per phase. Each step failure is logged independently, making it easier to identify where something went wrong.
-
-### dev vs production Status
-
-- **dev** -- Resource is visible in the dashboard and can be triggered manually, but will not auto-trigger from schedules or webhooks. Use while building and testing.
-- **production** -- Resource is fully live. All trigger sources work. Use when you are confident it works correctly.
-
-You can switch between them by changing `status` in the workflow config and redeploying.
-
-### When to Use Conditional Routing
-
-Use `StepType.CONDITIONAL` when different inputs should follow different processing paths.
-
-Example: score >= 80 goes to the approve path, score >= 50 goes to the review path, everything else goes to the reject path. Each path can have its own steps and logic.
-
-Always include a `defaultTarget` fallback for inputs that do not match any condition. Without a fallback, an unmatched execution will fail.
-
-### When to Use Platform Tools vs Custom Code
-
-Use platform tools when the integration exists in the tool catalog -- they handle auth, retries, and error normalization for you.
-
-Write custom code (e.g., using `fetch` directly) only when you need a service or API method that is not in the catalog, or when you need fine-grained control over the HTTP request.
-
----
-
-**Last Updated:** 2026-02-26