@elevasis/sdk 0.7.10 → 0.7.12

package/dist/cli.cjs

@@ -43883,7 +43883,7 @@ function wrapAction(commandName, fn) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "0.7.10",
+  version: "0.7.12",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {

package/dist/index.d.ts

@@ -1273,7 +1273,6 @@ type Database = {
                     opening_line: string | null;
                     organization_id: string;
                     pipeline_status: Json;
-                    qualification: string | null;
                     source: string | null;
                     source_id: string | null;
                     status: string;
@@ -1300,7 +1299,6 @@ type Database = {
                     opening_line?: string | null;
                     organization_id: string;
                     pipeline_status?: Json;
-                    qualification?: string | null;
                     source?: string | null;
                     source_id?: string | null;
                     status?: string;
@@ -1327,7 +1325,6 @@ type Database = {
                     opening_line?: string | null;
                     organization_id?: string;
                     pipeline_status?: Json;
-                    qualification?: string | null;
                     source?: string | null;
                     source_id?: string | null;
                     status?: string;
@@ -3464,7 +3461,6 @@ interface AcqContact {
     linkedinUrl: string | null;
     title: string | null;
     headline: string | null;
-    qualification: 'qualified' | 'disqualified' | 'pending' | null;
     filterReason: string | null;
     openingLine: string | null;
     source: string | null;
@@ -3570,7 +3566,6 @@ interface UpdateContactParams {
     linkedinUrl?: string;
     title?: string;
     headline?: string;
-    qualification?: 'qualified' | 'disqualified' | 'pending';
     filterReason?: string;
     openingLine?: string;
     pipelineStatus?: Record<string, unknown>;
@@ -3582,7 +3577,6 @@ interface UpdateContactParams {
 type UpsertContactParams = CreateContactParams;
 interface ContactFilters {
     listId?: string;
-    qualification?: 'qualified' | 'disqualified' | 'pending';
     openingLineIsNull?: boolean;
     pipelineStatus?: Record<string, unknown>;
     batchId?: string;
@@ -4758,21 +4752,36 @@ interface CreateCampaignParams {
     name: string;
     sequences?: Array<{
         steps: Array<{
-            subject: string;
-            body: string;
-            variants?: Array<{
+            type?: string;
+            delay?: number;
+            variants: Array<{
                 subject: string;
                 body: string;
+                v_disabled?: boolean;
             }>;
         }>;
     }>;
     email_list?: string[];
+    campaign_schedule?: {
+        schedules: Array<{
+            name: string;
+            timing: {
+                from: string;
+                to: string;
+            };
+            days: Record<string, boolean>;
+            timezone: string;
+        }>;
+    };
     daily_limit?: number;
+    daily_max_leads?: number;
     stop_on_reply?: boolean;
     stop_on_auto_reply?: boolean;
+    stop_for_company?: boolean;
     track_opens?: boolean;
     track_clicks?: boolean;
     text_only?: boolean;
+    first_email_text_only?: boolean;
 }
 /**
  * Create campaign result

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "0.7.10",
+  "version": "0.7.12",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {

package/reference/_navigation.md

@@ -1,6 +1,6 @@
 # SDK Reference Navigation
 
-Auto-generated from reference file frontmatter. 28 files indexed.
+Auto-generated from reference file frontmatter. 30 files indexed.
 
 All paths are relative to `node_modules/@elevasis/sdk/reference/`.
 
@@ -39,7 +39,8 @@ All paths are relative to `node_modules/@elevasis/sdk/reference/`.
 
 | Resource | Location | Description | When to Load |
 | --- | --- | --- | --- |
-| Typed Adapters | `platform-tools/adapters.mdx` | Type-safe wrappers over platform.call() for all integrations and platform tools -- Attio, Stripe, Notion, Google Sheets, and more -- with full autocomplete, compile-time checking, and zero boilerplate | Using typed adapters instead of raw platform.call(), or needs to know what adapter methods are available |
+| Integration Adapters | `platform-tools/adapters-integration.mdx` | Type-safe wrappers for third-party integrations -- Attio, Stripe, Notion, Google Sheets, Instantly, SignatureAPI, Resend, Dropbox, Apify, Gmail, Mailso, and Tomba -- with full autocomplete and compile-time checking | Using typed adapters for integration tools, or needs to know what integration adapter methods are available |
+| Platform Adapters | `platform-tools/adapters-platform.mdx` | Type-safe singleton adapters for built-in platform services -- scheduler, storage, LLM, PDF, approval, notifications, acqDb, execution, and email -- no credentials required | Using platform service adapters (scheduler, storage, llm, pdf, approval, acqDb, notifications, execution, email) |
 | Platform Tools | `platform-tools/index.mdx` | Access 70+ tools across integration adapters and platform services from your SDK workflows -- typed adapters, credential security model, and working code examples | Connecting to external services |
 
 ## Resources
@@ -56,6 +57,7 @@ All paths are relative to `node_modules/@elevasis/sdk/reference/`.
 | --- | --- | --- | --- |
 | Template: Data Enrichment | `templates/data-enrichment.mdx` | LLM-powered enrichment of existing database records -- read rows, enrich each with an LLM, write results back to Supabase | Applying the data-enrichment workflow template |
 | Template: Email Sender | `templates/email-sender.mdx` | Transactional email via Resend with template support -- send styled emails to one or multiple recipients | Applying the email-sender workflow template |
+| Templates | `templates/index.mdx` | Ready-to-use workflow templates for common automation patterns -- web scraping, data enrichment, email sending, lead scoring, PDF generation, text classification, and recurring jobs | (not specified) |
 | Template: Lead Scorer | `templates/lead-scorer.mdx` | LLM-based lead scoring with Supabase storage -- receive a lead, score it with an LLM, store the result | Applying the lead-scorer workflow template |
 | Template: PDF Generator | `templates/pdf-generator.mdx` | PDF generation from structured data with platform storage upload -- render a PDF from a template and upload to platform storage | Applying the pdf-generator workflow template |
 | Template: Recurring Job | `templates/recurring-job.mdx` | Scheduler-triggered periodic workflow -- run a task on a schedule (daily, weekly, hourly, or custom cron) | Applying the recurring-job workflow template |

package/reference/concepts.mdx

@@ -92,29 +92,11 @@ type MyInput = z.infer<typeof myInput>;
 
 ## The Execution Model
 
-### What Happens When You Run a Workflow
+Each execution creates an ephemeral worker thread from your deployed bundle. The platform validates input against your Zod schema, runs your handler, and returns the result. Workers are terminated immediately after completion -- there is no persistent server.
 
-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
+Key implications: files written to disk disappear after execution, logs appear only after the execution completes (no streaming), and each execution is fully isolated with no shared state between runs. Outbound network access is unrestricted. Memory is capped at 256MB per worker; execution timeout is 300s for workflows and 600s for agents.
 
-### 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
+For the complete execution lifecycle, concurrency model, observability, and resource limits, see [Runtime](runtime.mdx).
 
 ---
 

package/reference/framework/tutorial-system.mdx

@@ -68,11 +68,11 @@ Assessed during `/meta init`. Two independent dimensions.
 
 ### automation dimension
 
-| Level      | Context Loading                                                                                         | Delivery                                                            | Verification                                                      |
-| ---------- | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------- |
-| `none`     | Glossary, Workflow overview, Platform Tools Overview only. Skip Zod, Execution Model, Design Decisions. | Agent writes all code. No code shown to user. Analogies throughout. | CLI primary. Agent runs `elevasis-sdk exec` and narrates results. |
-| `low-code` | All concept sections. Zapier/Make mapping. `adapters.mdx` on-demand.                                    | Map to Zapier/Make equivalents. Show code with explanations.        | CLI primary.                                                      |
-| `custom`   | All docs listed per-lesson and per-module.                                                              | Full technical content, code-first.                                 | CLI primary.                                                      |
+| Level      | Context Loading                                                                                            | Delivery                                                            | Verification                                                      |
+| ---------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------- |
+| `none`     | Glossary, Workflow overview, Platform Tools Overview only. Skip Zod, Execution Model, Design Decisions.    | Agent writes all code. No code shown to user. Analogies throughout. | CLI primary. Agent runs `elevasis-sdk exec` and narrates results. |
+| `low-code` | All concept sections. Zapier/Make mapping. `adapters-integration.mdx` / `adapters-platform.mdx` on-demand. | Map to Zapier/Make equivalents. Show code with explanations.        | CLI primary.                                                      |
+| `custom`   | All docs listed per-lesson and per-module.                                                                 | Full technical content, code-first.                                 | CLI primary.                                                      |
 
 ### platformNavigation dimension
 
@@ -153,17 +153,17 @@ Each lesson: (1) announce title and goal, (2) explain concept per skill level, (
 
 Modules are available any time -- no core path prerequisite. After completing a module the full menu table is shown again.
 
-| #   | Module           | Reference Docs                                                   | Build                                                                                                         | Key Concepts                                                       |
-| --- | ---------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
-| 11  | `hitl`           | `command-center.mdx` (Command Queue)                             | Approval gate with `approval.create()`. Full lifecycle: trigger -> Command Queue -> approve/reject -> resume. | `approval` adapter, pending state, Command Queue UI                |
-| 12  | `schedules`      | `command-center.mdx` (Task Scheduler)                            | All three schedule types: Recurring, Relative, Absolute. `scheduler` adapter for in-workflow.                 | Cron syntax, schedule types, Task Scheduler UI                     |
-| 13  | `notifications`  | `adapters.mdx` (notifications, email)                            | Notification + email steps. Alerts on completion.                                                             | `notifications` singleton, `email` singleton                       |
-| 14  | `integrations`   | `platform-tools/index.mdx` (Credential Security), `adapters.mdx` | Real adapter from `identity.md`. Full end-to-end with OAuth or API key credential.                            | Adapter pattern, credential scoping, external call error handling  |
-| 15  | `error-handling` | `patterns.mdx` (error handling), `troubleshooting.mdx`           | Workflow demonstrating all three error types. `try/catch`, `context.logger`, recovery.                        | `ExecutionError`, `PlatformToolError`, `ToolingError`              |
-| 16  | `workflows`      | `patterns.mdx` (store, logging, organization)                    | Refactor with `context.store`, `context.logger`, domain directories. Advanced schema patterns.                | `context.store`, `context.logger`, schema depth                    |
-| 17  | `composition`    | `command-center.mdx` (Command View), `patterns.mdx`              | Two workflows: first triggers second with `execution.trigger()`. Declare relationship.                        | `execution.trigger`, relationship declarations, Command View edges |
-| 18  | `llm`            | `adapters.mdx` (llm singleton)                                   | `llm.generate()` with structured output. Model selection and temperature.                                     | `llm` singleton, structured output, temperature                    |
-| 19  | `agents`         | `framework/agent.mdx`                                            | Agent definition with tools. LLM tool calling. Agent vs workflow comparison.                                  | Agent definition, tool registration, execution trace               |
+| #   | Module           | Reference Docs                                                               | Build                                                                                                         | Key Concepts                                                       |
+| --- | ---------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
+| 11  | `hitl`           | `command-center.mdx` (Command Queue)                                         | Approval gate with `approval.create()`. Full lifecycle: trigger -> Command Queue -> approve/reject -> resume. | `approval` adapter, pending state, Command Queue UI                |
+| 12  | `schedules`      | `command-center.mdx` (Task Scheduler)                                        | All three schedule types: Recurring, Relative, Absolute. `scheduler` adapter for in-workflow.                 | Cron syntax, schedule types, Task Scheduler UI                     |
+| 13  | `notifications`  | `adapters-platform.mdx` (notifications, email)                               | Notification + email steps. Alerts on completion.                                                             | `notifications` singleton, `email` singleton                       |
+| 14  | `integrations`   | `platform-tools/index.mdx` (Credential Security), `adapters-integration.mdx` | Real adapter from `identity.md`. Full end-to-end with OAuth or API key credential.                            | Adapter pattern, credential scoping, external call error handling  |
+| 15  | `error-handling` | `patterns.mdx` (error handling), `troubleshooting.mdx`                       | Workflow demonstrating all three error types. `try/catch`, `context.logger`, recovery.                        | `ExecutionError`, `PlatformToolError`, `ToolingError`              |
+| 16  | `workflows`      | `patterns.mdx` (store, logging, organization)                                | Refactor with `context.store`, `context.logger`, domain directories. Advanced schema patterns.                | `context.store`, `context.logger`, schema depth                    |
+| 17  | `composition`    | `command-center.mdx` (Command View), `patterns.mdx`                          | Two workflows: first triggers second with `execution.trigger()`. Declare relationship.                        | `execution.trigger`, relationship declarations, Command View edges |
+| 18  | `llm`            | `adapters-platform.mdx` (llm singleton)                                      | `llm.generate()` with structured output. Model selection and temperature.                                     | `llm` singleton, structured output, temperature                    |
+| 19  | `agents`         | `framework/agent.mdx`                                                        | Agent definition with tools. LLM tool calling. Agent vs workflow comparison.                                  | Agent definition, tool registration, execution trace               |
 
 ---
 

package/reference/index.mdx

@@ -6,6 +6,8 @@ loadWhen: "First session or new to the SDK"
 
 `@elevasis/sdk` lets you build workflows, agents, and resources in TypeScript and deploy them to the Elevasis platform with a single command. The developer experience is Vercel-style: write TypeScript, validate locally, deploy -- the platform handles execution, tool access, and observability. You never manage infrastructure. Zod 4.1 is the only peer dependency.
 
+Workflows are step-based automations with typed inputs and outputs. Agents are autonomous AI resources with access to platform tools. Both are defined in TypeScript, exported from a single entry point, and deployed with `elevasis-sdk deploy`. Resources appear in AI Studio immediately after a successful deploy.
+
 ## Quick Start
 
 ```bash
@@ -15,77 +17,28 @@ pnpm install
 elevasis-sdk deploy
 ```
 
-After `pnpm dlx @elevasis/sdk init`, your project is scaffolded with a working echo workflow, config file, TypeScript setup, and a `CLAUDE.md` that gives Claude Code full awareness of the SDK. After `elevasis-sdk deploy`, your resources appear in AI Studio and are available to run immediately.
-
-Here is a minimal workflow definition:
-
-```ts
-import type { WorkflowDefinition, OrganizationResources } from '@elevasis/sdk';
-import { z } from 'zod';
-
-const greetInput = z.object({ name: z.string() });
-const greetOutput = z.object({ message: z.string() });
-
-type GreetInput = z.infer<typeof greetInput>;
-
-const greetWorkflow: WorkflowDefinition = {
-  config: {
-    resourceId: 'greet',
-    name: 'Greet',
-    type: 'workflow',
-    description: 'Returns a greeting for the given name',
-    version: '1.0.0',
-    status: 'dev',
-  },
-  contract: {
-    inputSchema: greetInput,
-    outputSchema: greetOutput,
-  },
-  steps: {
-    greet: {
-      id: 'greet',
-      name: 'Build greeting',
-      description: 'Returns a greeting message',
-      handler: async (input) => {
-        const { name } = input as GreetInput;
-        return { message: `Hello, ${name}!` };
-      },
-      inputSchema: greetInput,
-      outputSchema: greetOutput,
-      next: null,
-    },
-  },
-  entryPoint: 'greet',
-};
-
-const org: OrganizationResources = {
-  workflows: [greetWorkflow],
-};
-
-export default org;
-```
+After `pnpm dlx @elevasis/sdk init`, your project is scaffolded with a working echo workflow, config file, TypeScript setup, and a `CLAUDE.md` that gives Claude Code full awareness of the SDK.
 
 ## What You Can Build
 
-- **Workflows** -- Step-based automation with typed inputs and outputs. Steps can be linear, conditional, or branching. Each step is a plain async function. Workflows are the primary resource type and are fully supported.
+- **Workflows** -- Step-based automation with typed inputs and outputs. Steps can be linear, conditional, or branching. Each step is a plain async function. See [Resources](resources/index.mdx) for the complete definition API.
 - **Agents** -- Autonomous AI resources with access to platform tools. Agents run in the worker runtime with full LLM access and platform tool support. Use `--async` when executing agents to avoid HTTP timeout limits on long-running runs.
 
 ## Platform Tools
 
-Inside any workflow step, import `platform` from `@elevasis/sdk/worker` to call platform tools:
+Inside any workflow step or agent, import from `@elevasis/sdk/worker` to call platform tools via typed adapters:
+
+```typescript
+import { createAttioAdapter, scheduler, llm } from '@elevasis/sdk/worker'
 
-```ts
-import { platform } from '@elevasis/sdk/worker';
+const attio = createAttioAdapter('my-attio')
+const records = await attio.listRecords({ object: 'deals' })
 
-const result = await platform.call({
-  tool: 'gmail',
-  method: 'send',
-  params: { to: 'user@example.com', subject: 'Hello', body: 'World' },
-  credential: 'my-gmail-credential',
-});
+await scheduler.createSchedule({ ... })
+const result = await llm.generate({ messages: [...] })
 ```
 
-The platform exposes 70+ tools across 12 integration adapters -- Gmail, Stripe, Google Sheets, Notion, and more. Credentials are managed server-side; API keys never cross the execution boundary. LLM calls are also available via `platform.call({ tool: 'llm', ... })` with API keys resolved from platform environment variables.
+The platform exposes 70+ tools across 12 integration adapters -- Gmail, Stripe, Google Sheets, Notion, and more. Credentials are managed server-side; API keys never cross the execution boundary.
 
 See [Platform Tools](platform-tools/index.mdx) for the full catalog.
 
@@ -104,7 +57,7 @@ See [Platform Tools](platform-tools/index.mdx) for the full catalog.
 
 - [Resources](resources/index.mdx) - Workflow and agent definition patterns, Zod schemas, step types, and routing
 - [Platform Tools](platform-tools/index.mdx) - Full catalog of 70+ tools, integration adapters, and credential management
-- [Platform Tools](platform-tools/index.mdx#credential-security) - Three-layer credential model, HTTP tool patterns, and credential management
+- [Credential Security](platform-tools/index.mdx#credential-security) - Three-layer credential model, HTTP tool patterns, and credential management
 
 ### Reference
 
@@ -114,6 +67,11 @@ See [Platform Tools](platform-tools/index.mdx) for the full catalog.
 - [Deployment](deployment/index.mdx) - Deploy pipeline, versioning, bundle upload, and registry registration
 - [Runtime](runtime.mdx) - Worker execution model, concurrency, timeouts, cancellation, resource limits, and v1 limitations
 
+### Typed Adapters
+
+- [Integration Adapters](platform-tools/adapters-integration.mdx) - All 12 integration adapters: Attio, Stripe, Notion, Google Sheets, Resend, and more
+- [Platform Adapters](platform-tools/adapters-platform.mdx) - All 9 platform service adapters: scheduler, storage, llm, pdf, approval, and more
+
 ### Framework
 
 - [Development Framework](framework/index.mdx) - How Claude Code helps you build: project structure, agent integration, memory, and documentation
@@ -122,10 +80,9 @@ See [Platform Tools](platform-tools/index.mdx) for the full catalog.
 
 ### More
 
-- [Documentation](framework/index.mdx#resource-documentation) - Writing and deploying MDX documentation alongside your resources
 - [Troubleshooting](troubleshooting.mdx) - Static error catalog for CLI, deployment, schema, and runtime failures
-- [Roadmap](roadmap.mdx) - Planned features including agent execution, streaming logs, and SDK testing utilities
+- [Roadmap](roadmap.mdx) - Planned features including error taxonomy, retry semantics, circuit breaker, and metrics
 
 ---
 
-**Last Updated:** 2026-02-25
+**Last Updated:** 2026-03-19