@elevasis/sdk 1.28.1 → 1.30.0

package/reference/{platform-tools → sdk/platform-tools}/index.mdx

@@ -1,9 +1,9 @@
 ---
 title: Platform Tools
-description: Access 70+ tools across integration adapters and platform services from your SDK workflows -- typed adapters, credential security model, and working code examples
+description: Access 25 adapters (13 integration + 12 platform) from your SDK workflows -- typed adapters, credential security model, and working code examples
 ---
 
-Your SDK workflows have access to 70+ tools -- Gmail, Stripe, Google Sheets, PDF generation, human-in-the-loop approvals, storage, scheduling, and more. Credentials are managed server-side and never appear in your code.
+Your SDK workflows have access to 25 adapters (13 integration + 12 platform) -- Gmail, Stripe, Google Sheets, PDF generation, human-in-the-loop approvals, storage, scheduling, and more. Credentials are managed server-side and never appear in your code.
 
 **Typed adapters** are the recommended way to call tools. They provide full TypeScript autocomplete, compile-time method checking, and eliminate boilerplate. Use `platform.call()` only for tools that don't have an adapter yet.
 
@@ -39,20 +39,9 @@ Both patterns return a Promise that resolves with the tool result or rejects wit
 
 ## Integration Adapters
 
-Ten integration adapters give you access to 50+ 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         |
-| ------------- | ----------------------------- | ------------------------ |
-| Attio         | 12 (CRUD + schema + notes)    | `{ apiKey }`             |
-| Google Sheets | 13 (read/write/filter/upsert) | OAuth2 / service account |
-| 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 }`             |
-| Dropbox       | 2 (upload/folder)             | `{ accessToken }`        |
-| Apify         | 1 (run actor)                 | `{ token }`              |
+The SDK ships 13 integration adapters (credential-bound factory functions) covering third-party APIs -- Attio, Apify, ClickUp, Dropbox, Gmail, Google Sheets, Instantly, MillionVerifier, Anymailfinder, Tomba, Resend, SignatureAPI, and Stripe. Pass the credential name once at adapter creation. Supabase is covered separately under [Database Access](#database-access) below.
+
+For the full per-adapter method tables, credential shapes, and code examples, see [Integration Adapters](adapters-integration.mdx) -- generated from the adapter source so it never drifts.
 
 ## Credential Security
 
@@ -131,19 +120,9 @@ Credentials are created in the command center UI: navigate to Credentials -> Add
 
 ## Platform Services
 
-Nine built-in platform services are available without a `credential` field. All have typed singleton adapters imported from `@elevasis/sdk/worker`.
+The SDK ships 12 platform service singletons available without a `credential` field -- imported directly from `@elevasis/sdk/worker`: `scheduler`, `llm`, `storage`, `notifications`, `acqDb`, `projects`, `crm`, `list`, `pdf`, `approval`, `execution`, and `email`. The platform injects context server-side, so no credential is passed.
 
-| 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   |
+For the full per-service method tables (including the `acqDb` 41-method surface), see [Platform Adapters](adapters-platform.mdx) -- generated from the adapter source.
 
 ## LLM Tool
 
@@ -207,8 +186,8 @@ const qualified = await platform.call({
 
 ## Documentation
 
-- [Integration Adapters](adapters-integration.mdx) - All 10 integration adapters with method tables and code examples
-- [Platform Adapters](adapters-platform.mdx) - All 9 platform service adapters with method tables and code examples
+- [Integration Adapters](adapters-integration.mdx) - All 13 integration adapters with method tables and code examples
+- [Platform Adapters](adapters-platform.mdx) - All 12 platform service adapters with method tables and code examples
 - [Adapter Type Safety](type-safety.mdx) - Required fields, discriminated unions, and intentionally loose adapter types
 
 ---

package/reference/{resources → sdk/resources}/patterns.mdx

@@ -11,19 +11,23 @@ This page collects the patterns you will reach for most often when writing resou
 
 The simplest pattern: a chain of steps where each step feeds its output into the next.
 
+Each `WorkflowStep` requires `id`, `name`, `description`, `handler`, `inputSchema`, `outputSchema`, and `next`. There is no `type` field on a step -- `StepType` (`LINEAR` / `CONDITIONAL`) is a label for `next.type` only, not a step property.
+
 ```typescript
 import { z } from 'zod';
-import { StepType } from '@elevasis/sdk';
 import type { WorkflowDefinition, WorkflowStep } from '@elevasis/sdk';
 
 const inputSchema = z.object({ orderId: z.string() });
 const outputSchema = z.object({ shipped: z.boolean(), trackingNumber: z.string() });
 
 type Input = z.infer<typeof inputSchema>;
-type Output = z.infer<typeof outputSchema>;
 
 const validateStep: WorkflowStep = {
-  type: StepType.LINEAR,
+  id: 'validate',
+  name: 'Validate Order',
+  description: 'Checks the order exists before shipping',
+  inputSchema: z.object({ orderId: z.string() }),
+  outputSchema: z.object({ order: z.unknown() }),
   handler: async (input: Input) => {
     const order = await getOrder(input.orderId);
     if (!order) throw new Error(`Order ${input.orderId} not found`);
@@ -33,7 +37,11 @@ const validateStep: WorkflowStep = {
 };
 
 const shipStep: WorkflowStep = {
-  type: StepType.LINEAR,
+  id: 'ship',
+  name: 'Ship Order',
+  description: 'Creates a shipment and returns the tracking number',
+  inputSchema: z.object({ order: z.unknown() }),
+  outputSchema: z.object({ shipped: z.boolean(), trackingNumber: z.string() }),
   handler: async (input) => {
     const tracking = await createShipment(input.order);
     return { shipped: true, trackingNumber: tracking.number };
@@ -51,23 +59,29 @@ const fulfillOrder: WorkflowDefinition = {
 
 **Key points:**
 
-- `next: { target: 'stepName' }` routes to the next step
+- Steps require `id`, `name`, `description`, `inputSchema`, `outputSchema`, `handler`, and `next`
+- `next.type` is `'linear'` or `'conditional'` -- this is where `StepType` values apply; the step itself has no `type` field
+- `next: { type: 'linear', target: 'stepName' }` routes to the next step
 - `next: null` marks the terminal step
 - Each step receives the full return value of the previous step as its `input`
-- The terminal step's return value must satisfy `contract.output`
+- The terminal step's return value must satisfy `contract.outputSchema`
 
 ---
 
 ## Conditional Branching
 
-Use `StepType.CONDITIONAL` when the next step depends on the output of the current step.
+Use a `next.type` of `'conditional'` when the next step depends on the output of the current step. The step itself still has no `type` field -- the routing decision lives entirely in `next`.
 
 ```typescript
-import { StepType } from '@elevasis/sdk';
+import { z } from 'zod';
 import type { WorkflowStep } from '@elevasis/sdk';
 
 const scoreStep: WorkflowStep = {
-  type: StepType.CONDITIONAL,
+  id: 'score',
+  name: 'Score Application',
+  description: 'Calculates a risk score and routes on the result',
+  inputSchema: z.object({ applicationId: z.string() }),
+  outputSchema: z.object({ score: z.number(), applicationId: z.string() }),
   handler: async (input) => {
     const score = await calculateRiskScore(input.applicationId);
     return { score, applicationId: input.applicationId };
@@ -103,12 +117,16 @@ const scoreStep: WorkflowStep = {
 Platform tools let your steps call integrations managed by Elevasis (email, CRM, databases, etc.). Import `platform` from `@elevasis/sdk/worker` and call it with the tool name, method, parameters, and an optional credential reference when the tool requires one.
 
 ```typescript
+import { z } from 'zod';
 import { platform, PlatformToolError } from '@elevasis/sdk/worker';
 import type { WorkflowStep } from '@elevasis/sdk';
-import { StepType } from '@elevasis/sdk';
 
 const sendEmailStep: WorkflowStep = {
-  type: StepType.LINEAR,
+  id: 'sendEmail',
+  name: 'Send Email',
+  description: 'Sends a transactional email via the platform email tool',
+  inputSchema: z.object({ recipientEmail: z.string(), subject: z.string(), body: z.string() }),
+  outputSchema: z.object({ sent: z.boolean(), messageId: z.string() }),
   handler: async (input, context) => {
     const result = await platform.call({
       tool: 'email',

package/reference/ui/exports.mdx

@@ -0,0 +1,60 @@
+---
+title: "@elevasis/ui Export Catalog"
+description: "Auto-generated catalog of all published @elevasis/ui subpath exports, derived from packages/ui/reference-manifest.ts."
+---
+
+{/* @generated by .claude/_gen/sync-sdk-catalog.ts — DO NOT EDIT */}
+{/* Regenerate: pnpm gen:sdk-catalog */}
+
+| Import | Title | Group | Description |
+| --- | --- | --- | --- |
+| `@elevasis/ui/provider` | Provider | Provider | Published provider and feature-shell contract for downstream apps. |
+| `@elevasis/ui/provider/ui` | Provider UI | Provider | Published provider UI entry for downstream applications. |
+| `@elevasis/ui/auth` | Auth | Foundation | Published authentication surface for UI integrations. |
+| `@elevasis/ui/auth/context` | Auth Context | Foundation | Published auth context entry for UI integrations. |
+| `@elevasis/ui/hooks` | Hooks | Hooks | Headless hooks surface for executions, sessions, observability, and operations. |
+| `@elevasis/ui/hooks/access` | Hooks Access | Hooks | Published Access Model hook surface for checking route, section, and action access. |
+| `@elevasis/ui/sse` | SSE | Foundation | Published server-sent events helpers and connection utilities. |
+| `@elevasis/ui/initialization` | Initialization | Foundation | Published app initialization provider and bootstrap helpers. |
+| `@elevasis/ui/profile` | Profile | Foundation | Published user profile surface for UI applications. |
+| `@elevasis/ui/organization` | Organization | Foundation | Published organization shell, store, and helper surface. |
+| `@elevasis/ui/features/auth` | Features Auth | Features | Published auth feature surface for downstream shells. |
+| `@elevasis/ui/features/clients` | Features Clients | Features | Published clients feature surface for downstream shells. |
+| `@elevasis/ui/features/crm` | Features CRM | Features | Published CRM feature surface for downstream shells. |
+| `@elevasis/ui/features/dashboard` | Features Dashboard | Features | Published dashboard feature surface for downstream shells. |
+| `@elevasis/ui/features/delivery` | Features Delivery | Features | Published delivery feature surface for downstream shells. |
+| `@elevasis/ui/features/lead-gen` | Features Lead Gen | Features | Published lead generation feature surface for downstream shells. |
+| `@elevasis/ui/features/operations` | Features Operations | Features | Published operations feature surface for downstream shells. |
+| `@elevasis/ui/features/monitoring` | Features Monitoring | Features | Published monitoring feature surface for downstream shells. |
+| `@elevasis/ui/features/monitoring/requests` | Features Monitoring Requests | Features | Published submitted-requests list, detail, and triage surface for downstream shells. |
+| `@elevasis/ui/features/seo` | Features SEO | Features | Published SEO feature surface for downstream shells. |
+| `@elevasis/ui/features/knowledge` | Features Knowledge | Features | Published knowledge feature manifest for downstream shells. |
+| `@elevasis/ui/features/notes` | Features Notes | Features | Published Notes panel view and supporting note components for shared right-panel integrations. |
+| `@elevasis/ui/features/right-panel-host` | Features Right Panel Host | Features | Published right-panel host provider, layer, trigger, keyboard shortcut, store, and view contract. |
+| `@elevasis/ui/knowledge` | Knowledge | Visual | Published knowledge browser primitives: Browser, Tree, NodeList, NodeView, SearchBar, MDX provider, and the generated KNOWLEDGE_BODIES map. |
+| `@elevasis/ui/vite` | Vite | Build | Composite Vite plugin factory (elevasisVite) that bundles all @elevasis/ui Vite plugins into a single array for consumer vite.config.ts files. |
+| `@elevasis/ui/vite-plugin-knowledge` | Vite Plugin Knowledge | Build | Vite plugin that regenerates the build-time knowledge MDX bodies and search index, with HMR support. |
+| `@elevasis/ui/features/settings` | Features Settings | Features | Published settings feature surface for downstream shells. |
+| `@elevasis/ui/types` | Types | Foundation | Published UI types entry for downstream applications. |
+| `@elevasis/ui/components` | Components | Components | Published UI component barrel for downstream applications. |
+| `@elevasis/ui/components/navigation` | Navigation Components | Components | Published navigation component entry for downstream applications. |
+| `@elevasis/ui/components/chat` | Chat Components | Components | Published chat component entry for downstream applications. |
+| `@elevasis/ui/layout` | Layout | Components | Published layout component entry for downstream applications. |
+| `@elevasis/ui/charts` | Charts | Components | Published chart component entry for downstream applications. |
+| `@elevasis/ui/theme` | Theme | Visual | Published theme entry for downstream applications. |
+| `@elevasis/ui/theme/presets` | Theme Presets | Visual | Re-exports the canonical THEME_PRESETS tuple, ThemePresetName union, and ThemePresetEnum Zod enum from @repo/core. Single source of truth for preset names across UI, schemas, and Zustand state. |
+| `@elevasis/ui/api` | API | Foundation | Published API client entry for downstream applications. |
+| `@elevasis/ui/utils` | Utils | Foundation | Published utility entry for downstream applications. |
+| `@elevasis/ui/graph` | Graph | Visual | Published graph helper and visualization entry. |
+| `@elevasis/ui/execution` | Execution | Foundation | Published execution visualization and helper entry. |
+| `@elevasis/ui/router` | Router | Foundation | Published router entry for downstream applications. |
+| `@elevasis/ui/router/context` | Router Context | Foundation | Published router context entry for downstream applications. |
+| `@elevasis/ui/zustand` | Zustand | Foundation | Published Zustand slice entry for downstream applications. |
+| `@elevasis/ui/app` | App | Foundation | Published app factory that composes providers, router, auth, and theme into a mountable React app. |
+| `@elevasis/ui/provider/ElevasisServiceContext` | Elevasis Service Context | Provider | Standalone service context and provider that supplies apiRequest, organizationId, and isReady to child components. |
+| `@elevasis/ui/hooks/delivery` | Hooks Delivery | Hooks | Published delivery hooks for projects, milestones, tasks, and notes. |
+| `@elevasis/ui/hooks/user-notes` | Hooks User Notes | Hooks | Published user-notes query and mutation hooks used by shared Notes surfaces. |
+| `@elevasis/ui/hooks/operations/command-view/utils/transformCommandViewData` | Transform Command View Data | Hooks | Utility that transforms backend CommandViewData arrays into a unified frontend CommandViewGraph with nodes and edges. |
+| `@elevasis/ui/test-utils` | Test Utils | Testing | Published rendering helpers, auth mocks, MSW handlers, and test provider utilities. |
+| `@elevasis/ui/test-utils/setup` | Test Utils Setup | Testing | Vitest setup file for UI consumers using browser mocks and MSW. |
+| `@elevasis/ui/test-utils/setup-integration` | Test Utils Integration Setup | Testing | Vitest setup file for integration tests that avoid MSW and use real network boundaries. |

package/reference/ui/index.mdx

@@ -0,0 +1,75 @@
+---
+title: "@elevasis/ui"
+description: The shared React 19 feature-shell and manifest-backed feature modules for Elevasis — Lead Gen, CRM, Projects, Operations, Monitoring, Settings, SEO, and more. Embeds into any host UI via ElevasisProvider.
+---
+
+`@elevasis/ui` is the shared React feature-shell for the Elevasis platform. It provides an `ElevasisProvider` and a set of manifest-backed feature modules that a host UI embeds and composes. The model is: your shell owns the layout and routing; Elevasis features plug in as self-contained modules.
+
+## Install
+
+```bash
+pnpm add @elevasis/ui
+```
+
+Many peer dependencies are optional. Pull only the peers that the features you use require. If you are not using the graph visualization features, you do not need `cytoscape`. If you are not using TanStack Router, you do not need it either.
+
+## Peer Dependencies
+
+`@elevasis/ui` has a broad peer dependency set. The required peers are React 19 and Mantine 8.2.7. Most others are optional and only needed when specific feature modules are activated.
+
+- **React 19** -- required. The feature modules use React 19 APIs.
+- **Mantine 8.2.7** -- required. The component layer and theming foundation.
+- **TanStack Query** -- required for data-fetching features (most modules).
+- **TanStack Router** -- optional; required if you want the routing-aware feature shells.
+- **Zod 4.1** -- required for schema validation in form-backed features.
+- **Zustand 5** -- required for state management in multi-panel features.
+- **cytoscape** -- optional; required for the graph/knowledge visualization modules only.
+
+## Provider and Feature-Shell Model
+
+The entry point is `ElevasisProvider`, imported from `@elevasis/ui/provider`. Wrap your application root with it to give all child feature modules access to the platform context, auth session, and manifest registry.
+
+```tsx
+import { ElevasisProvider } from "@elevasis/ui/provider";
+
+export function AppRoot() {
+  return (
+    <ElevasisProvider config={elevasisConfig}>
+      {/* your shell and routes */}
+    </ElevasisProvider>
+  );
+}
+```
+
+Feature modules are imported from their own subpaths (e.g. `@elevasis/ui/features/lead-gen`, `@elevasis/ui/features/crm`) and rendered inside the provider tree. Each module is manifest-backed: it reads the platform manifest at runtime to know which resources and workflows are available, so no hard-coded resource IDs are needed in the host UI.
+
+## Available Feature Modules
+
+The published feature surface includes modules for:
+
+- **Lead Gen** -- prospecting pipeline, campaign review, acquisition workflows
+- **CRM** -- client management, deal tracking, contact records
+- **Projects** -- task tracking, project lifecycle, milestones
+- **Operations** -- workflow execution history, operations dashboard
+- **Monitoring** -- execution health, error log, platform diagnostics
+- **Settings** -- organization settings, credential management, member management
+- **SEO** -- content and SEO tooling modules
+- **Notes** -- note capture and structured annotations
+- **Knowledge** -- knowledge base viewer and search UI
+- **Dashboard** -- compatibility components for host-owned dashboard shells
+
+Each module has its own `@elevasis/ui/features/<name>` subpath. See the [Export Catalog](exports.mdx) for the full generated list.
+
+## When To Use @elevasis/ui
+
+Use `@elevasis/ui` when you are building a host application that needs to embed Elevasis features -- lead-gen pipelines, CRM views, operations dashboards -- without re-implementing them. The provider/feature-shell model means you own the shell, navigation, and layout; Elevasis owns the feature logic and UI internals.
+
+You do not need `@elevasis/ui` if you are only writing backend workflows and agents. Tenant automation projects use `@elevasis/sdk` alone.
+
+## Composition With @elevasis/core
+
+`@elevasis/ui` uses `@elevasis/core` internally for entity schemas, org-model types, and auth contracts. Installing `@elevasis/ui` will pull in `@elevasis/core` as a dependency. You do not need to install `@elevasis/core` separately unless you need direct access to its subpaths.
+
+## Export Catalog
+
+See [Export Catalog](exports.mdx) for a generated table of all published subpath exports derived from the reference manifest.

package/reference/platform-tools/adapters-integration.mdx

@@ -1,300 +0,0 @@
----
-title: Integration Adapters
-description: Type-safe wrappers for third-party integrations -- Attio, Stripe, Google Sheets, Instantly, SignatureAPI, Resend, Dropbox, Apify, Gmail, and Tomba -- with full autocomplete and compile-time checking
----
-
-Integration adapters are factory functions that bind a credential once and return a typed object with all methods available for that service. They wrap `platform.call()` with full TypeScript autocomplete and compile-time method checking.
-
-All integration adapters are imported from `@elevasis/sdk/worker`. For platform service adapters (scheduler, storage, llm, etc.), see [Platform Adapters](adapters-platform.mdx).
-
-```typescript
-import {
-  createAttioAdapter, createStripeAdapter,
-  createGoogleSheetsAdapter, createInstantlyAdapter,
-  createSignatureApiAdapter, createResendAdapter, createDropboxAdapter,
-  createApifyAdapter, createGmailAdapter,
-  createTombaAdapter,
-} from '@elevasis/sdk/worker'
-```
-
----
-
-## Quick Reference
-
-| Import                            | Methods | Category            |
-| --------------------------------- | ------- | ------------------- |
-| `createAttioAdapter(cred)`        | 12      | CRM                 |
-| `createGoogleSheetsAdapter(cred)` | 13      | Spreadsheets        |
-| `createStripeAdapter(cred)`       | 6       | Payments            |
-| `createInstantlyAdapter(cred)`    | 5       | Email Campaigns     |
-| `createSignatureApiAdapter(cred)` | 4       | eSignature          |
-| `createTombaAdapter(cred)`        | 3       | Email Discovery     |
-| `createResendAdapter(cred)`       | 2       | Transactional Email |
-| `createDropboxAdapter(cred)`      | 2       | File Storage        |
-| `createApifyAdapter(cred)`        | 1       | Web Scraping        |
-| `createGmailAdapter(cred)`        | 1       | Email (Gmail)       |
-
-Multiple adapters with different credentials work simultaneously:
-
-```typescript
-const prodAttio = createAttioAdapter('prod-attio')
-const testAttio = createAttioAdapter('test-attio')
-```
-
----
-
-## Attio CRM Adapter
-
-Factory pattern -- bind a credential once, use 12 typed methods.
-
-```typescript
-const attio = createAttioAdapter('my-attio-credential')
-```
-
-### Methods
-
-| Method            | Params                  | Returns                 |
-| ----------------- | ----------------------- | ----------------------- |
-| `createRecord`    | `CreateRecordParams`    | `CreateRecordResult`    |
-| `updateRecord`    | `UpdateRecordParams`    | `UpdateRecordResult`    |
-| `listRecords`     | `QueryRecordsParams`    | `QueryRecordsResult`    |
-| `getRecord`       | `GetRecordParams`       | `GetRecordResult`       |
-| `deleteRecord`    | `DeleteRecordParams`    | `DeleteRecordResult`    |
-| `listObjects`     | none                    | `ListObjectsResult`     |
-| `listAttributes`  | `ListAttributesParams`  | `ListAttributesResult`  |
-| `createAttribute` | `CreateAttributeParams` | `CreateAttributeResult` |
-| `updateAttribute` | `UpdateAttributeParams` | `UpdateAttributeResult` |
-| `createNote`      | `CreateNoteParams`      | `CreateNoteResult`      |
-| `listNotes`       | `ListNotesParams`       | `ListNotesResult`       |
-| `deleteNote`      | `DeleteNoteParams`      | `DeleteNoteResult`      |
-
-### Examples
-
-```typescript
-// Create a company record
-const company = await attio.createRecord({
-  object: 'companies',
-  values: {
-    name: [{ value: 'Acme Corp' }],
-    domains: [{ domain: 'acme.com' }],
-  },
-})
-
-// Query deals with filters
-const deals = await attio.listRecords({
-  object: 'deals',
-  filter: {
-    operator: 'and',
-    filters: [
-      { field: 'stage', operator: 'equals', value: 'proposal' },
-    ],
-  },
-  sorts: [{ field: 'created_at', direction: 'desc' }],
-  limit: 20,
-})
-
-// Create a note on a record
-await attio.createNote({
-  parentObject: 'deals',
-  parentRecordId: 'rec_abc123',
-  title: 'Discovery call notes',
-  content: 'Key takeaways from the call...',
-})
-```
-
----
-
-## Google Sheets Adapter
-
-Factory pattern -- 13 methods including workflow-friendly helpers (`getRowByValue`, `upsertRow`, `filterRows`).
-
-```typescript
-const sheets = createGoogleSheetsAdapter('my-google-credential')
-```
-
-### Methods
-
-| Method                   | Params                         | Returns                        |
-| ------------------------ | ------------------------------ | ------------------------------ |
-| `readSheet`              | `ReadSheetParams`              | `ReadSheetResult`              |
-| `writeSheet`             | `WriteSheetParams`             | `WriteSheetResult`             |
-| `appendRows`             | `AppendRowsParams`             | `AppendRowsResult`             |
-| `clearRange`             | `ClearRangeParams`             | `ClearRangeResult`             |
-| `getSpreadsheetMetadata` | `GetSpreadsheetMetadataParams` | `GetSpreadsheetMetadataResult` |
-| `batchUpdate`            | `BatchUpdateParams`            | `BatchUpdateResult`            |
-| `getHeaders`             | `GetHeadersParams`             | `GetHeadersResult`             |
-| `getLastRow`             | `GetLastRowParams`             | `GetLastRowResult`             |
-| `getRowByValue`          | `GetRowByValueParams`          | `GetRowByValueResult`          |
-| `updateRowByValue`       | `UpdateRowByValueParams`       | `UpdateRowByValueResult`       |
-| `upsertRow`              | `UpsertRowParams`              | `UpsertRowResult`              |
-| `filterRows`             | `FilterRowsParams`             | `FilterRowsResult`             |
-| `deleteRowByValue`       | `DeleteRowByValueParams`       | `DeleteRowByValueResult`       |
-
----
-
-## Stripe Adapter
-
-Factory pattern -- 6 methods for payment links and checkout sessions.
-
-```typescript
-const stripe = createStripeAdapter('my-stripe-credential')
-```
-
-### Methods
-
-| Method                  | Params                        | Returns                       |
-| ----------------------- | ----------------------------- | ----------------------------- |
-| `createPaymentLink`     | `CreatePaymentLinkParams`     | `CreatePaymentLinkResult`     |
-| `getPaymentLink`        | `GetPaymentLinkParams`        | `GetPaymentLinkResult`        |
-| `updatePaymentLink`     | `UpdatePaymentLinkParams`     | `UpdatePaymentLinkResult`     |
-| `listPaymentLinks`      | `ListPaymentLinksParams`      | `ListPaymentLinksResult`      |
-| `createAutoPaymentLink` | `CreateAutoPaymentLinkParams` | `CreateAutoPaymentLinkResult` |
-| `createCheckoutSession` | `CreateCheckoutSessionParams` | `CreateCheckoutSessionResult` |
-
----
-
-## Instantly Adapter
-
-Factory pattern -- 5 methods for email campaign management.
-
-```typescript
-const instantly = createInstantlyAdapter('my-instantly-credential')
-```
-
-### Methods
-
-| Method                  | Params                        | Returns                       |
-| ----------------------- | ----------------------------- | ----------------------------- |
-| `sendReply`             | `SendReplyParams`             | `SendReplyResult`             |
-| `removeFromSubsequence` | `RemoveFromSubsequenceParams` | `RemoveFromSubsequenceResult` |
-| `getEmails`             | `GetEmailsParams`             | `GetEmailsResult`             |
-| `updateInterestStatus`  | `UpdateInterestStatusParams`  | `UpdateInterestStatusResult`  |
-| `addToCampaign`         | `AddToCampaignParams`         | `AddToCampaignResult`         |
-
----
-
-## SignatureAPI Adapter
-
-Factory pattern -- 4 methods for eSignature envelope operations.
-
-```typescript
-const signatureApi = createSignatureApiAdapter('my-signatureapi-credential')
-```
-
-### Methods
-
-| Method             | Params                   | Returns                  |
-| ------------------ | ------------------------ | ------------------------ |
-| `createEnvelope`   | `CreateEnvelopeParams`   | `CreateEnvelopeResult`   |
-| `voidEnvelope`     | `VoidEnvelopeParams`     | `VoidEnvelopeResult`     |
-| `downloadDocument` | `DownloadDocumentParams` | `DownloadDocumentResult` |
-| `getEnvelope`      | `GetEnvelopeParams`      | `GetEnvelopeResult`      |
-
----
-
-## Tomba Adapter
-
-Factory pattern -- 3 methods for email discovery and verification.
-
-```typescript
-const tomba = createTombaAdapter('elevasis-tomba')
-```
-
-**Credential type:** `api-key-secret` (requires both API Key and API Secret)
-
-### Methods
-
-| Method          | Params                     | Returns                    |
-| --------------- | -------------------------- | -------------------------- |
-| `emailFinder`   | `TombaEmailFinderParams`   | `TombaEmailFinderResult`   |
-| `domainSearch`  | `TombaDomainSearchParams`  | `TombaDomainSearchResult`  |
-| `emailVerifier` | `TombaEmailVerifierParams` | `TombaEmailVerifierResult` |
-
-### Examples
-
-```typescript
-// Find email by name + domain
-const found = await tomba.emailFinder({
-  domain: 'stripe.com',
-  firstName: 'John',
-  lastName: 'Doe',
-})
-
-// List all emails at a domain (up to 10)
-const results = await tomba.domainSearch({ domain: 'stripe.com' })
-
-// Verify a known email address
-const verified = await tomba.emailVerifier({ email: 'john@stripe.com' })
-```
-
----
-
-## Resend Adapter
-
-Factory pattern -- 2 methods for transactional email.
-
-```typescript
-const resend = createResendAdapter('my-resend-credential')
-```
-
-### Methods
-
-| Method      | Params                  | Returns                 |
-| ----------- | ----------------------- | ----------------------- |
-| `sendEmail` | `ResendSendEmailParams` | `ResendSendEmailResult` |
-| `getEmail`  | `ResendGetEmailParams`  | `ResendGetEmailResult`  |
-
----
-
-## Dropbox Adapter
-
-Factory pattern -- 2 methods for file operations.
-
-```typescript
-const dropbox = createDropboxAdapter('my-dropbox-credential')
-```
-
-### Methods
-
-| Method         | Params               | Returns              |
-| -------------- | -------------------- | -------------------- |
-| `uploadFile`   | `UploadFileParams`   | `UploadFileResult`   |
-| `createFolder` | `CreateFolderParams` | `CreateFolderResult` |
-
----
-
-## Apify Adapter
-
-Factory pattern -- 1 method for running web scraping actors.
-
-```typescript
-const apify = createApifyAdapter('my-apify-credential')
-```
-
-### Methods
-
-| Method     | Params           | Returns          |
-| ---------- | ---------------- | ---------------- |
-| `runActor` | `RunActorParams` | `RunActorResult` |
-
----
-
-## Gmail Adapter
-
-Factory pattern -- 1 method for sending email via Gmail API.
-
-```typescript
-const gmail = createGmailAdapter('my-gmail-credential')
-```
-
-### Methods
-
-| Method      | Params                 | Returns                |
-| ----------- | ---------------------- | ---------------------- |
-| `sendEmail` | `GmailSendEmailParams` | `GmailSendEmailResult` |
-
----
-
-For platform service adapters (scheduler, storage, llm, pdf, approval, acqDb, notifications, execution, email), see [Platform Adapters](adapters-platform.mdx).
-
-**Last Updated:** 2026-03-05