@elevasis/sdk 0.7.11 → 0.7.13

package/reference/platform-tools/index.mdx

@@ -40,7 +40,7 @@ Both patterns return a Promise that resolves with the tool result or rejects wit
 
 ## Integration Adapters
 
-Eleven integration adapters give you access to 55+ tool methods covering third-party APIs. Pass the `credential` field with the name of the stored credential for that service. Supabase is listed separately under [Database Access](#database-access) below.
+Twelve integration adapters give you access to 58+ tool methods covering third-party APIs. Pass the credential name once at adapter creation. Supabase is listed separately under [Database Access](#database-access) below.
 
 | Adapter       | Tools                         | Credential Shape         |
 | ------------- | ----------------------------- | ------------------------ |
@@ -49,16 +49,17 @@ Eleven integration adapters give you access to 55+ tool methods covering third-p
 | Notion        | 8 (pages + blocks)            | `{ token }`              |
 | Stripe        | 6 (payment links + checkout)  | `{ secretKey }`          |
 | Instantly     | 5 (email campaigns)           | `{ apiKey }`             |
+| SignatureAPI  | 4 (envelopes)                 | `{ apiKey }`             |
+| Tomba         | 3 (email discovery)           | `api-key-secret`         |
 | Gmail         | 2 (send email)                | OAuth2 / service account |
 | Resend        | 2 (send/get email)            | `{ apiKey }`             |
-| SignatureAPI  | 4 (envelopes)                 | `{ apiKey }`             |
 | Dropbox       | 2 (upload/folder)             | `{ accessToken }`        |
 | Apify         | 1 (run actor)                 | `{ token }`              |
 | Mailso        | 1 (verify email)              | `{ apiKey }`             |
 
 ## Credential Security
 
-Integration credentials are never stored in `.env` and never available via `process.env` inside worker threads. Credentials live in the platform credential system (created via the command center UI or CLI) and are accessed through three controlled channels.
+Integration credentials are never stored in `.env` and never available via `process.env` inside worker threads. Credentials live in the platform credential system and are accessed through three controlled channels.
 
 ### Layer 1: Platform Tools (Default)
 
@@ -117,7 +118,7 @@ All `getCredential()` calls are logged. Use `platform.call()` with the `http` to
 
 ### Credential Setup
 
-Credentials are created in the command center UI: navigate to Credentials → Add Credential → select type → enter values → save. The name you give the credential is what you pass as `credential: 'my-cred-name'` in `platform.call()`. Credential names are case-sensitive -- a mismatch causes `PlatformToolError: credential not found`.
+Credentials are created in the command center UI: navigate to Credentials -> Add Credential -> select type -> enter values -> save. The name you give the credential is what you pass as `credential: 'my-cred-name'` in `platform.call()`. Credential names are case-sensitive -- a mismatch causes `PlatformToolError: credential not found`.
 
 ### Choosing a Pattern
 
@@ -135,44 +136,22 @@ Credentials are created in the command center UI: navigate to Credentials → Ad
 
 Nine built-in platform services are available without a `credential` field. All have typed singleton adapters imported from `@elevasis/sdk/worker`.
 
-| Tool Key       | Methods                                                                                                                                                                                     | Purpose                                                         |
-| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
-| `acqDb`        | 35 methods (CRUD + sync)                                                                                                                                                                    | Acquisition database -- `acqDb` singleton adapter               |
-| `email`        | `send`                                                                                                                                                                                      | Send platform email to org members -- `email` singleton adapter |
-| `storage`      | `upload`, `download`, `createSignedUrl`, `delete`, `list`                                                                                                                                   | File storage -- `storage` singleton adapter                     |
-| `pdf`          | `render`, `renderToBuffer`                                                                                                                                                                  | PDF rendering -- `pdf` singleton adapter                        |
-| `notification` | `create`                                                                                                                                                                                    | In-app notifications -- `notifications` singleton adapter       |
-| `approval`     | `create`, `deleteByMetadata`                                                                                                                                                                | HITL approval gates -- `approval` singleton adapter             |
-| `scheduler`    | `createSchedule`, `updateAnchor`, `deleteSchedule`, `findByIdempotencyKey`, `deleteScheduleByIdempotencyKey`, `listSchedules`, `getSchedule`, `cancelSchedule`, `cancelSchedulesByMetadata` | Task scheduling -- `scheduler` singleton adapter                |
-| `llm`          | `generate`                                                                                                                                                                                  | LLM inference -- `llm` singleton adapter                        |
-| `execution`    | `trigger`                                                                                                                                                                                   | Nested child execution -- `execution` singleton adapter         |
+| Tool Key       | Methods                                                                                                                                                                                     | Purpose                                         |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
+| `acqDb`        | 35 methods (CRUD + sync)                                                                                                                                                                    | Acquisition database -- `acqDb` adapter         |
+| `email`        | `send`                                                                                                                                                                                      | Send email to org members -- `email` adapter    |
+| `storage`      | `upload`, `download`, `createSignedUrl`, `delete`, `list`                                                                                                                                   | File storage -- `storage` adapter               |
+| `pdf`          | `render`, `renderToBuffer`                                                                                                                                                                  | PDF rendering -- `pdf` adapter                  |
+| `notification` | `create`                                                                                                                                                                                    | In-app notifications -- `notifications` adapter |
+| `approval`     | `create`, `deleteByMetadata`                                                                                                                                                                | HITL approval gates -- `approval` adapter       |
+| `scheduler`    | `createSchedule`, `updateAnchor`, `deleteSchedule`, `findByIdempotencyKey`, `deleteScheduleByIdempotencyKey`, `listSchedules`, `getSchedule`, `cancelSchedule`, `cancelSchedulesByMetadata` | Task scheduling -- `scheduler` adapter          |
+| `llm`          | `generate`                                                                                                                                                                                  | LLM inference -- `llm` adapter                  |
+| `execution`    | `trigger`                                                                                                                                                                                   | Nested child execution -- `execution` adapter   |
 
 ## LLM Tool
 
 Call any supported LLM from your workflow with no API keys required. Keys are resolved server-side from environment variables.
 
-```typescript
-import { llm } from '@elevasis/sdk/worker'
-
-const result = await llm.generate({
-  provider: 'google',
-  model: 'gemini-3-flash-preview',
-  messages: [
-    { role: 'system', content: 'Classify this email reply.' },
-    { role: 'user', content: emailText }
-  ],
-  responseSchema: {
-    type: 'object',
-    properties: {
-      category: { type: 'string', enum: ['interested', 'not-interested', 'bounced'] },
-      confidence: { type: 'number', minimum: 0, maximum: 1 }
-    },
-    required: ['category', 'confidence']
-  },
-  temperature: 0.2
-})
-```
-
 **Supported models:**
 
 | Provider     | Models                                                                                                         |
@@ -184,21 +163,13 @@ const result = await llm.generate({
 
 **Key params:** `provider`, `model`, `messages` (`{ role, content }[]`), `responseSchema` (optional JSON Schema), `temperature` (optional).
 
+See [Platform Adapters](adapters-platform.mdx#llm-adapter) for full typed usage with structured output.
+
 ## Execution Tool
 
-Trigger another resource as a nested child of the current execution. The child runs synchronously and its result is returned. Maximum depth: 5 levels.
+Trigger another resource as a nested child of the current execution. The child runs synchronously and its result is returned. Maximum depth: 5 levels. The invoked resource must belong to the same organization.
 
-```typescript
-import { execution } from '@elevasis/sdk/worker'
-
-const result = await execution.trigger({
-  resourceId: 'my-other-workflow',
-  input: { key: 'value' },
-})
-// result = { success: true, executionId: '...', output: { ... }, error: undefined }
-```
-
-The invoked resource must belong to the same organization.
+See [Platform Adapters](adapters-platform.mdx#execution-adapter) for usage.
 
 ## Database Access
 
@@ -231,123 +202,16 @@ const qualified = await platform.call({
 | `in`                     | `{ status: 'in.(new,contacted)' }` | In set        |
 | `is`                     | `{ deleted_at: 'is.null' }`        | Null check    |
 
-**Credential setup:** Create a credential with provider `supabase` — config fields are `url` and `serviceRoleKey`. Workflows always use the service role key (server-side, no RLS).
+**Credential setup:** Create a credential with provider `supabase` -- config fields are `url` and `serviceRoleKey`. Workflows always use the service role key (server-side, no RLS).
 
 **`/database init`:** Guided setup that stores your Supabase credential, generates `data/schema.ts`, and creates `docs/database.mdx`.
 
-**`data/schema.ts`:** An agent-readable Zod schema documenting your table structure. Not deployed or executed — the agent reads it to understand your data model.
-
----
-
-## Code Examples
-
-### Email via Resend
-
-```typescript
-import { createResendAdapter } from '@elevasis/sdk/worker'
-
-const resend = createResendAdapter('resend')
-await resend.sendEmail({
-  from: 'hello@yourapp.com',
-  to: 'customer@example.com',
-  subject: 'Your order is confirmed',
-  html: '\<p\>Thank you for your order!\</p\>',
-})
-```
-
-### CRM Record via Attio
-
-```typescript
-import { createAttioAdapter } from '@elevasis/sdk/worker'
-
-const attio = createAttioAdapter('attio')
-const result = await attio.createRecord({
-  object: 'people',
-  values: {
-    name: [{ full_name: 'Jane Smith' }],
-    email_addresses: [{ email_address: 'jane@example.com' }],
-  },
-})
-const recordId = result.data.id
-```
-
-### PDF Generation
-
-```typescript
-import { pdf, storage } from '@elevasis/sdk/worker'
-
-// Render to storage directly
-const result = await pdf.render({
-  document: proposalDocument,
-  storage: { bucket: 'invoices', path: 'invoice-1042.pdf' },
-})
-
-// Or render to buffer for inline processing
-const { buffer } = await pdf.renderToBuffer({ document: proposalDocument })
-await storage.upload({ bucket: 'invoices', path: 'invoice-1042.pdf', content: buffer, contentType: 'application/pdf' })
-```
-
-### LLM with Structured Output
-
-```typescript
-import { llm } from '@elevasis/sdk/worker'
-
-interface TicketClassification {
-  priority: 'low' | 'medium' | 'high' | 'critical'
-  category: 'billing' | 'technical' | 'account' | 'other'
-  summary: string
-}
-
-const response = await llm.generate\<TicketClassification\>({
-  provider: 'anthropic',
-  model: 'claude-sonnet-4-5',
-  messages: [
-    { role: 'system', content: 'Extract structured data from support tickets.' },
-    { role: 'user', content: ticketText },
-  ],
-  responseSchema: {
-    type: 'object',
-    properties: {
-      priority: { type: 'string', enum: ['low', 'medium', 'high', 'critical'] },
-      category: { type: 'string', enum: ['billing', 'technical', 'account', 'other'] },
-      summary: { type: 'string' },
-    },
-    required: ['priority', 'category', 'summary'],
-  },
-  temperature: 0.1,
-})
-const { priority, category, summary } = response.output
-```
-
-### Triggering Another Resource
-
-```typescript
-import { execution } from '@elevasis/sdk/worker'
-
-const outcome = await execution.trigger({
-  resourceId: 'send-welcome-sequence',
-  input: { userId: newUser.id, email: newUser.email, plan: 'pro' },
-})
-if (!outcome.success) throw new Error(`Child workflow failed: ${outcome.error}`)
-```
-
-### File Storage
-
-```typescript
-import { storage } from '@elevasis/sdk/worker'
-
-const reportPath = `exports/report-${Date.now()}.csv`
-await storage.upload({ bucket: 'exports', path: reportPath, content: csvContent, contentType: 'text/csv' })
-
-const { signedUrl } = await storage.createSignedUrl({ bucket: 'exports', path: reportPath })
-// signedUrl is valid for 1 hour (3600 seconds) -- share with user or include in email
-```
-
 ---
 
 ## Documentation
 
-- [Typed Adapters](adapters.mdx) - Type-safe wrappers for all 11 integrations + 9 platform services with full autocomplete (recommended)
+- [Integration Adapters](adapters-integration.mdx) - All 12 integration adapters with method tables and code examples
+- [Platform Adapters](adapters-platform.mdx) - All 9 platform service adapters with method tables and code examples
 
 ---
 

package/reference/templates/index.mdx

@@ -0,0 +1,47 @@
+---
+title: Templates
+description: Ready-to-use workflow templates for common automation patterns -- web scraping, data enrichment, email sending, lead scoring, PDF generation, text classification, and recurring jobs
+---
+
+Templates are pre-built workflow definitions covering the most common SDK automation patterns. Each template includes a complete `WorkflowDefinition` with Zod schemas, step handlers, and real platform tool usage. Scaffold any template through Claude Code (`/work` then describe the template) or adapt the code manually.
+
+Templates follow the same `WorkflowDefinition` structure as any custom resource -- they are reference implementations, not a special feature. The patterns demonstrated (multi-step chains, LLM structured output, Supabase CRUD, scheduler setup) apply directly to custom workflows you build.
+
+All templates are available for any organization. Credentials specific to each template (Supabase, Resend, Apify, etc.) must be created in the command center before running the workflow.
+
+## Documentation
+
+### Data Collection
+
+- [Web Scraper](web-scraper.mdx) - Apify actor runs web scrape, stores structured results in Supabase table
+- [Data Enrichment](data-enrichment.mdx) - Reads Supabase records, enriches each with LLM, writes results back; supports batching
+
+### Communication
+
+- [Email Sender](email-sender.mdx) - Transactional email via Resend with plain text and HTML support, single or multiple recipients
+- [Lead Scorer](lead-scorer.mdx) - Multi-criteria LLM lead scoring with configurable rubric and Supabase result storage
+
+### Documents
+
+- [PDF Generator](pdf-generator.mdx) - Renders structured data to PDF, uploads to platform storage, returns signed download URL
+- [Text Classifier](text-classifier.mdx) - Multi-label text classification via LLM structured output, configurable categories and confidence scoring
+
+### Scheduling
+
+- [Recurring Job](recurring-job.mdx) - Two-workflow setup pattern: a setup workflow creates the schedule, the job workflow runs on each trigger; uses idempotency keys for safe re-registration
+
+## Platform Tools Used
+
+| Template        | Platform Tools      | Credentials Needed              |
+| --------------- | ------------------- | ------------------------------- |
+| Web Scraper     | `apify`, `supabase` | `apify`, `my-database`          |
+| Data Enrichment | `llm`, `supabase`   | `my-database` (LLM server-side) |
+| Email Sender    | `resend`            | `my-resend`                     |
+| Lead Scorer     | `llm`, `supabase`   | `my-database` (LLM server-side) |
+| PDF Generator   | `pdf`, `storage`    | None (platform services)        |
+| Text Classifier | `llm`               | None (LLM server-side)          |
+| Recurring Job   | `scheduler`         | None (platform service)         |
+
+---
+
+**Last Updated:** 2026-03-19