Fix handler

The image/* accept attribute allowed users to select BMP, TIFF, HEIC,
and other image types that are rejected server-side. Replace with the
exact set of supported image MIME types and extensions to match the
copilot upload validation.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.agents/skills/add-block/SKILL.md

@@ -1,825 +0,0 @@
----
-name: add-block
-description: Create or update a Sim integration block with correct subBlocks, conditions, dependsOn, modes, canonicalParamId usage, outputs, and tool wiring. Use when working on `apps/sim/blocks/blocks/{service}.ts` or aligning a block with its tools.
----
-
-# Add Block Skill
-
-You are an expert at creating block configurations for Sim. You understand the serializer, subBlock types, conditions, dependsOn, modes, and all UI patterns.
-
-## Your Task
-
-When the user asks you to create a block:
-1. Create the block file in `apps/sim/blocks/blocks/{service}.ts`
-2. Configure all subBlocks with proper types, conditions, and dependencies
-3. Wire up tools correctly
-
-## Block Configuration Structure
-
-```typescript
-import { {ServiceName}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {ServiceName}Block: BlockConfig = {
-  type: '{service}',                    // snake_case identifier
-  name: '{Service Name}',               // Human readable
-  description: 'Brief description',     // One sentence
-  longDescription: 'Detailed description for docs',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',                    // 'tools' | 'blocks' | 'triggers'
-  bgColor: '#HEXCOLOR',                 // Brand color
-  icon: {ServiceName}Icon,
-
-  // Auth mode
-  authMode: AuthMode.OAuth,             // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Define all UI fields here
-  ],
-
-  tools: {
-    access: ['tool_id_1', 'tool_id_2'], // Array of tool IDs this block can use
-    config: {
-      tool: (params) => `{service}_${params.operation}`,  // Tool selector function
-      params: (params) => ({
-        // Transform subBlock values to tool params
-      }),
-    },
-  },
-
-  inputs: {
-    // Optional: define expected inputs from other blocks
-  },
-
-  outputs: {
-    // Define outputs available to downstream blocks
-  },
-}
-```
-
-## SubBlock Types Reference
-
-**Critical:** Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions.
-
-### Text Inputs
-```typescript
-// Single-line input
-{ id: 'field', title: 'Label', type: 'short-input', placeholder: '...' }
-
-// Multi-line input
-{ id: 'field', title: 'Label', type: 'long-input', placeholder: '...', rows: 6 }
-
-// Password input
-{ id: 'apiKey', title: 'API Key', type: 'short-input', password: true }
-```
-
-### Selection Inputs
-```typescript
-// Dropdown (static options)
-{
-  id: 'operation',
-  title: 'Operation',
-  type: 'dropdown',
-  options: [
-    { label: 'Create', id: 'create' },
-    { label: 'Update', id: 'update' },
-  ],
-  value: () => 'create',  // Default value function
-}
-
-// Combobox (searchable dropdown)
-{
-  id: 'field',
-  title: 'Label',
-  type: 'combobox',
-  options: [...],
-  searchable: true,
-}
-```
-
-### Code/JSON Inputs
-```typescript
-{
-  id: 'code',
-  title: 'Code',
-  type: 'code',
-  language: 'javascript',  // 'javascript' | 'json' | 'python'
-  placeholder: '// Enter code...',
-}
-```
-
-### OAuth/Credentials
-```typescript
-{
-  id: 'credential',
-  title: 'Account',
-  type: 'oauth-input',
-  serviceId: '{service}',  // Must match OAuth provider service key
-  requiredScopes: getScopesForService('{service}'),  // Import from @/lib/oauth/utils
-  placeholder: 'Select account',
-  required: true,
-}
-```
-
-**Scopes:** Always use `getScopesForService(serviceId)` from `@/lib/oauth/utils` for `requiredScopes`. Never hardcode scope arrays — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-**Scope descriptions:** When adding a new OAuth provider, also add human-readable descriptions for all scopes in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`.
-
-### Selectors (with dynamic options)
-```typescript
-// Channel selector (Slack, Discord, etc.)
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  serviceId: '{service}',
-  placeholder: 'Select channel',
-  dependsOn: ['credential'],
-}
-
-// Project selector (Jira, etc.)
-{
-  id: 'project',
-  title: 'Project',
-  type: 'project-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-
-// File selector (Google Drive, etc.)
-{
-  id: 'file',
-  title: 'File',
-  type: 'file-selector',
-  serviceId: '{service}',
-  mimeType: 'application/pdf',
-  dependsOn: ['credential'],
-}
-
-// User selector
-{
-  id: 'user',
-  title: 'User',
-  type: 'user-selector',
-  serviceId: '{service}',
-  dependsOn: ['credential'],
-}
-```
-
-### Other Types
-```typescript
-// Switch/toggle
-{ id: 'enabled', type: 'switch' }
-
-// Slider
-{ id: 'temperature', title: 'Temperature', type: 'slider', min: 0, max: 2, step: 0.1 }
-
-// Table (key-value pairs)
-{ id: 'headers', title: 'Headers', type: 'table', columns: ['Key', 'Value'] }
-
-// File upload
-{
-  id: 'files',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,
-  acceptedTypes: 'image/*,application/pdf',
-}
-```
-
-## File Input Handling
-
-When your block accepts file uploads, use the basic/advanced mode pattern with `normalizeFileInput`.
-
-### Basic/Advanced File Pattern
-
-```typescript
-// Basic mode: Visual file upload
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from other blocks
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Both map to 'file' param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any subblock's `id` in the same block
-- Values are stored under subblock `id`, not `canonicalParamId`
-
-### Normalizing File Input in tools.config
-
-Use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  access: ['service_upload'],
-  config: {
-    tool: (params) => {
-      // Check all field IDs: uploadFile (basic), fileRef (advanced), fileContent (legacy)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `service_${params.operation}`
-    },
-  },
-}
-```
-
-**Why this pattern?**
-- Values come through as `params.uploadFile` or `params.fileRef` (the subblock IDs)
-- `canonicalParamId` only controls UI/schema mapping, not runtime values
-- `normalizeFileInput` handles JSON strings from advanced mode template resolution
-
-### File Input Types in `inputs`
-
-Use `type: 'json'` for file inputs:
-
-```typescript
-inputs: {
-  uploadFile: { type: 'json', description: 'Uploaded file (UserFile)' },
-  fileRef: { type: 'json', description: 'File reference from previous block' },
-  // Legacy field for backwards compatibility
-  fileContent: { type: 'string', description: 'Legacy: base64 encoded content' },
-}
-```
-
-### Multiple Files
-
-For multiple file uploads:
-
-```typescript
-{
-  id: 'attachments',
-  title: 'Attachments',
-  type: 'file-upload',
-  multiple: true,  // Allow multiple files
-  maxSize: 25,     // Max size in MB per file
-  acceptedTypes: 'image/*,application/pdf,.doc,.docx',
-}
-
-// In tools.config:
-const normalizedFiles = normalizeFileInput(
-  params.attachments || params.attachmentRefs,
-  // No { single: true } - returns array
-)
-if (normalizedFiles) {
-  params.files = normalizedFiles
-}
-```
-
-## Condition Syntax
-
-Controls when a field is shown based on other field values.
-
-### Simple Condition
-```typescript
-condition: { field: 'operation', value: 'create' }
-// Shows when operation === 'create'
-```
-
-### Multiple Values (OR)
-```typescript
-condition: { field: 'operation', value: ['create', 'update'] }
-// Shows when operation is 'create' OR 'update'
-```
-
-### Negation
-```typescript
-condition: { field: 'operation', value: 'delete', not: true }
-// Shows when operation !== 'delete'
-```
-
-### Compound (AND)
-```typescript
-condition: {
-  field: 'operation',
-  value: 'send',
-  and: {
-    field: 'type',
-    value: 'dm',
-    not: true,
-  }
-}
-// Shows when operation === 'send' AND type !== 'dm'
-```
-
-### Complex Example
-```typescript
-condition: {
-  field: 'operation',
-  value: ['list', 'search'],
-  not: true,
-  and: {
-    field: 'authMethod',
-    value: 'oauth',
-  }
-}
-// Shows when operation NOT in ['list', 'search'] AND authMethod === 'oauth'
-```
-
-## DependsOn Pattern
-
-Controls when a field is enabled and when its options are refetched.
-
-### Simple Array (all must be set)
-```typescript
-dependsOn: ['credential']
-// Enabled only when credential has a value
-// Options refetch when credential changes
-
-dependsOn: ['credential', 'projectId']
-// Enabled only when BOTH have values
-```
-
-### Complex (all + any)
-```typescript
-dependsOn: {
-  all: ['authMethod'],           // All must be set
-  any: ['credential', 'apiKey']  // At least one must be set
-}
-// Enabled when authMethod is set AND (credential OR apiKey is set)
-```
-
-## Required Pattern
-
-Can be boolean or condition-based.
-
-### Simple Boolean
-```typescript
-required: true
-required: false
-```
-
-### Conditional Required
-```typescript
-required: { field: 'operation', value: 'create' }
-// Required only when operation === 'create'
-
-required: { field: 'operation', value: ['create', 'update'] }
-// Required when operation is 'create' OR 'update'
-```
-
-## Mode Pattern (Basic vs Advanced)
-
-Controls which UI view shows the field.
-
-### Mode Options
-- `'basic'` - Only in basic view (default UI)
-- `'advanced'` - Only in advanced view
-- `'both'` - Both views (default if not specified)
-- `'trigger'` - Only in trigger configuration
-
-### canonicalParamId Pattern
-
-Maps multiple UI fields to a single serialized parameter:
-
-```typescript
-// Basic mode: Visual selector
-{
-  id: 'channel',
-  title: 'Channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  dependsOn: ['credential'],
-}
-
-// Advanced mode: Manual input
-{
-  id: 'channelId',
-  title: 'Channel ID',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',  // Both map to 'channel' param
-  placeholder: 'Enter channel ID manually',
-}
-```
-
-**How it works:**
-- In basic mode: `channel` selector value → `params.channel`
-- In advanced mode: `channelId` input value → `params.channel`
-- The serializer consolidates based on current mode
-
-**Critical constraints:**
-- `canonicalParamId` must NOT match any other subblock's `id` in the same block (causes conflicts)
-- `canonicalParamId` must be unique per block (only one basic/advanced pair per canonicalParamId)
-- ONLY use `canonicalParamId` to link basic/advanced mode alternatives for the same logical parameter
-- Do NOT use it for any other purpose
-
-## WandConfig Pattern
-
-Enables AI-assisted field generation.
-
-```typescript
-{
-  id: 'query',
-  title: 'Query',
-  type: 'code',
-  language: 'json',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a query based on the user request. Return ONLY the JSON.',
-    placeholder: 'Describe what you want to query...',
-    generationType: 'json-object',  // Optional: affects AI behavior
-    maintainHistory: true,          // Optional: keeps conversation context
-  },
-}
-```
-
-### Generation Types
-- `'javascript-function-body'` - JS code generation
-- `'json-object'` - Raw JSON (adds "no markdown" instruction)
-- `'json-schema'` - JSON Schema definitions
-- `'sql-query'` - SQL statements
-- `'timestamp'` - Adds current date/time context
-
-## Tools Configuration
-
-**Important:** `tools.config.tool` runs during serialization before variable resolution. Put `Number()` and other type coercions in `tools.config.params` instead, which runs at execution time after variables are resolved.
-
-**Preferred:** Use tool names directly as dropdown option IDs to avoid switch cases:
-```typescript
-// Dropdown options use tool IDs directly
-options: [
-  { label: 'Create', id: 'service_create' },
-  { label: 'Read', id: 'service_read' },
-]
-
-// Tool selector just returns the operation value
-tool: (params) => params.operation,
-```
-
-### With Parameter Transformation
-```typescript
-tools: {
-  access: ['service_action'],
-  config: {
-    tool: (params) => 'service_action',
-    params: (params) => ({
-      id: params.resourceId,
-      data: typeof params.data === 'string' ? JSON.parse(params.data) : params.data,
-    }),
-  },
-}
-```
-
-### V2 Versioned Tool Selector
-```typescript
-import { createVersionedToolSelector } from '@/blocks/utils'
-
-tools: {
-  access: [
-    'service_create_v2',
-    'service_read_v2',
-    'service_update_v2',
-  ],
-  config: {
-    tool: createVersionedToolSelector({
-      baseToolSelector: (params) => `service_${params.operation}`,
-      suffix: '_v2',
-      fallbackToolId: 'service_create_v2',
-    }),
-  },
-}
-```
-
-## Outputs Definition
-
-**IMPORTANT:** Block outputs have a simpler schema than tool outputs. Block outputs do NOT support:
-- `optional: true` - This is only for tool outputs
-- `items` property - This is only for tool outputs with array types
-
-Block outputs only support:
-- `type` - The data type ('string', 'number', 'boolean', 'json', 'array')
-- `description` - Human readable description
-- Nested object structure (for complex types)
-
-```typescript
-outputs: {
-  // Simple outputs
-  id: { type: 'string', description: 'Resource ID' },
-  success: { type: 'boolean', description: 'Whether operation succeeded' },
-
-  // Use type: 'json' for complex objects or arrays (NOT type: 'array' with items)
-  items: { type: 'json', description: 'List of items' },
-  metadata: { type: 'json', description: 'Response metadata' },
-
-  // Nested outputs (for structured data)
-  user: {
-    id: { type: 'string', description: 'User ID' },
-    name: { type: 'string', description: 'User name' },
-    email: { type: 'string', description: 'User email' },
-  },
-}
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **describe the inner fields in the description** so downstream blocks know what properties are available. For well-known, stable objects, use nested output definitions instead:
-
-```typescript
-outputs: {
-  // BAD: Opaque json with no info about what's inside
-  plan: { type: 'json', description: 'Zone plan information' },
-
-  // GOOD: Describe the known fields in the description
-  plan: {
-    type: 'json',
-    description: 'Zone plan information (id, name, price, currency, frequency, is_subscribed)',
-  },
-
-  // BEST: Use nested output definition when the shape is stable and well-known
-  plan: {
-    id: { type: 'string', description: 'Plan identifier' },
-    name: { type: 'string', description: 'Plan name' },
-    price: { type: 'number', description: 'Plan price' },
-    currency: { type: 'string', description: 'Price currency' },
-  },
-}
-```
-
-Use the nested pattern when:
-- The object has a small, stable set of fields (< 10)
-- Downstream blocks will commonly access specific properties
-- The API response shape is well-documented and unlikely to change
-
-Use `type: 'json'` with a descriptive string when:
-- The object has many fields or a dynamic shape
-- It represents a list/array of items
-- The shape varies by operation
-
-## V2 Block Pattern
-
-When creating V2 blocks (alongside legacy V1):
-
-```typescript
-// V1 Block - mark as legacy
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service (Legacy)',
-  hideFromToolbar: true,  // Hide from toolbar
-  // ... rest of config
-}
-
-// V2 Block - visible, uses V2 tools
-export const ServiceV2Block: BlockConfig = {
-  type: 'service_v2',
-  name: 'Service',              // Clean name
-  hideFromToolbar: false,       // Visible
-  subBlocks: ServiceBlock.subBlocks,  // Reuse UI
-  tools: {
-    access: ServiceBlock.tools?.access?.map(id => `${id}_v2`) || [],
-    config: {
-      tool: createVersionedToolSelector({
-        baseToolSelector: (params) => (ServiceBlock.tools?.config as any)?.tool(params),
-        suffix: '_v2',
-        fallbackToolId: 'service_default_v2',
-      }),
-      params: ServiceBlock.tools?.config?.params,
-    },
-  },
-  outputs: {
-    // Flat, API-aligned outputs (not wrapped in content/metadata)
-  },
-}
-```
-
-## Registering Blocks
-
-After creating the block, remind the user to:
-1. Import in `apps/sim/blocks/registry.ts`
-2. Add to the `registry` object (alphabetically):
-
-```typescript
-import { ServiceBlock } from '@/blocks/blocks/service'
-
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  service: ServiceBlock,
-}
-```
-
-## Complete Example
-
-```typescript
-import { ServiceIcon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service',
-  description: 'Integrate with Service API',
-  longDescription: 'Full description for documentation...',
-  docsLink: 'https://docs.sim.ai/tools/service',
-  category: 'tools',
-  bgColor: '#FF6B6B',
-  icon: ServiceIcon,
-  authMode: AuthMode.OAuth,
-
-  subBlocks: [
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Create', id: 'create' },
-        { label: 'Read', id: 'read' },
-        { label: 'Update', id: 'update' },
-        { label: 'Delete', id: 'delete' },
-      ],
-      value: () => 'create',
-    },
-    {
-      id: 'credential',
-      title: 'Service Account',
-      type: 'oauth-input',
-      serviceId: 'service',
-      requiredScopes: getScopesForService('service'),
-      placeholder: 'Select account',
-      required: true,
-    },
-    {
-      id: 'resourceId',
-      title: 'Resource ID',
-      type: 'short-input',
-      placeholder: 'Enter resource ID',
-      condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-      required: { field: 'operation', value: ['read', 'update', 'delete'] },
-    },
-    {
-      id: 'name',
-      title: 'Name',
-      type: 'short-input',
-      placeholder: 'Resource name',
-      condition: { field: 'operation', value: ['create', 'update'] },
-      required: { field: 'operation', value: 'create' },
-    },
-  ],
-
-  tools: {
-    access: ['service_create', 'service_read', 'service_update', 'service_delete'],
-    config: {
-      tool: (params) => `service_${params.operation}`,
-    },
-  },
-
-  outputs: {
-    id: { type: 'string', description: 'Resource ID' },
-    name: { type: 'string', description: 'Resource name' },
-    createdAt: { type: 'string', description: 'Creation timestamp' },
-  },
-}
-```
-
-## Connecting Blocks with Triggers
-
-If the service supports webhooks, connect the block to its triggers.
-
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const ServiceBlock: BlockConfig = {
-  // ... basic config ...
-
-  triggers: {
-    enabled: true,
-    available: ['service_event_a', 'service_event_b', 'service_webhook'],
-  },
-
-  subBlocks: [
-    // Tool subBlocks first...
-    { id: 'operation', /* ... */ },
-
-    // Then spread trigger subBlocks
-    ...getTrigger('service_event_a').subBlocks,
-    ...getTrigger('service_event_b').subBlocks,
-    ...getTrigger('service_webhook').subBlocks,
-  ],
-}
-```
-
-See the `/add-trigger` skill for creating triggers.
-
-## Icon Requirement
-
-If the icon doesn't already exist in `@/components/icons.tsx`, **do NOT search for it yourself**. After completing the block, ask the user to provide the SVG:
-
-```
-The block is complete, but I need an icon for {Service}.
-Please provide the SVG and I'll convert it to a React component.
-
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-```
-
-## Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. This includes:
-- Pagination tokens
-- Time range filters (start/end time)
-- Sort order options
-- Reply settings
-- Rarely used IDs (e.g., reply-to tweet ID, quote tweet ID)
-- Max results / limits
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  placeholder: 'ISO 8601 timestamp',
-  condition: { field: 'operation', value: ['search', 'list'] },
-  mode: 'advanced',  // Rarely used, hide from basic view
-}
-```
-
-## WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually, such as timestamps, comma-separated lists, and complex query strings. This gives users an AI-assisted input experience.
-
-```typescript
-// Timestamps - use generationType: 'timestamp' to inject current date context
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp based on the user description. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-
-// Comma-separated lists - simple prompt without generationType
-{
-  id: 'mediaIds',
-  title: 'Media IDs',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate a comma-separated list of media IDs. Return ONLY the comma-separated values.',
-  },
-}
-```
-
-## Naming Convention
-
-All tool IDs referenced in `tools.access` and returned by `tools.config.tool` MUST use `snake_case` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase.
-
-## Checklist Before Finishing
-
-- [ ] All subBlocks have `id`, `title` (except switch), and `type`
-- [ ] Conditions use correct syntax (field, value, not, and)
-- [ ] DependsOn set for fields that need other values
-- [ ] Required fields marked correctly (boolean or condition)
-- [ ] OAuth inputs have correct `serviceId` and `requiredScopes: getScopesForService(serviceId)`
-- [ ] Scope descriptions added to `SCOPE_DESCRIPTIONS` in `lib/oauth/utils.ts` for any new scopes
-- [ ] Tools.access lists all tool IDs (snake_case)
-- [ ] Tools.config.tool returns correct tool ID (snake_case)
-- [ ] Outputs match tool outputs
-- [ ] Block registered in registry.ts
-- [ ] If icon missing: asked user to provide SVG
-- [ ] If triggers exist: `triggers` config set, trigger subBlocks spread
-- [ ] Optional/rarely-used fields set to `mode: 'advanced'`
-- [ ] Timestamps and complex inputs have `wandConfig` enabled
-
-## Final Validation (Required)
-
-After creating the block, you MUST validate it against every tool it references:
-
-1. **Read every tool definition** that appears in `tools.access` — do not skip any
-2. **For each tool, verify the block has correct:**
-   - SubBlock inputs that cover all required tool params (with correct `condition` to show for that operation)
-   - SubBlock input types that match the tool param types (e.g., dropdown for enums, short-input for strings)
-   - `tools.config.params` correctly maps subBlock IDs to tool param names (if they differ)
-   - Type coercions in `tools.config.params` for any params that need conversion (Number(), Boolean(), JSON.parse())
-3. **Verify block outputs** cover the key fields returned by all tools
-4. **Verify conditions** — each subBlock should only show for the operations that actually use it

.agents/skills/add-block/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Block"
-  short_description: "Build a Sim block definition"
-  brand_color: "#2563EB"
-  default_prompt: "Use $add-block to create or update the block for a Sim integration."

.agents/skills/add-connector/SKILL.md

@@ -1,528 +0,0 @@
----
-name: add-connector
-description: Add or update a Sim knowledge base connector for syncing documents from an external source, including auth mode, config fields, pagination, document mapping, tags, and registry wiring. Use when working in `apps/sim/connectors/{service}/` or adding a new external document source.
----
-
-# Add Connector Skill
-
-You are an expert at adding knowledge base connectors to Sim. A connector syncs documents from an external source (Confluence, Google Drive, Notion, etc.) into a knowledge base.
-
-## Your Task
-
-When the user asks you to create a connector:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Determine the auth mode: **OAuth** (if Sim already has an OAuth provider for the service) or **API key** (if the service uses API key / Bearer token auth)
-3. Create the connector directory and config
-4. Register it in the connector registry
-
-## Directory Structure
-
-Create files in `apps/sim/connectors/{service}/`:
-```
-connectors/{service}/
-├── index.ts          # Barrel export
-└── {service}.ts      # ConnectorConfig definition
-```
-
-## Authentication
-
-Connectors use a discriminated union for auth config (`ConnectorAuthConfig` in `connectors/types.ts`):
-
-```typescript
-type ConnectorAuthConfig =
-  | { mode: 'oauth'; provider: OAuthService; requiredScopes?: string[] }
-  | { mode: 'apiKey'; label?: string; placeholder?: string }
-```
-
-### OAuth mode
-For services with existing OAuth providers in `apps/sim/lib/oauth/types.ts`. The `provider` must match an `OAuthService`. The modal shows a credential picker and handles token refresh automatically.
-
-### API key mode
-For services that use API key / Bearer token auth. The modal shows a password input with the configured `label` and `placeholder`. The API key is encrypted at rest using AES-256-GCM and stored in a dedicated `encryptedApiKey` column on the connector record. The sync engine decrypts it automatically — connectors receive the raw access token in `listDocuments`, `getDocument`, and `validateConfig`.
-
-## ConnectorConfig Structure
-
-### OAuth connector example
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { {Service}Icon } from '@/components/icons'
-import { fetchWithRetry } from '@/lib/knowledge/documents/utils'
-import type { ConnectorConfig, ExternalDocument, ExternalDocumentList } from '@/connectors/types'
-
-const logger = createLogger('{Service}Connector')
-
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'oauth',
-    provider: '{service}',          // Must match OAuthService in lib/oauth/types.ts
-    requiredScopes: ['read:...'],
-  },
-
-  configFields: [
-    // Rendered dynamically by the add-connector modal UI
-    // Supports 'short-input' and 'dropdown' types
-  ],
-
-  listDocuments: async (accessToken, sourceConfig, cursor) => {
-    // Return metadata stubs with contentDeferred: true (if per-doc content fetch needed)
-    // Or full documents with content (if list API returns content inline)
-    // Return { documents: ExternalDocument[], nextCursor?, hasMore }
-  },
-
-  getDocument: async (accessToken, sourceConfig, externalId) => {
-    // Fetch full content for a single document
-    // Return ExternalDocument with contentDeferred: false, or null
-  },
-
-  validateConfig: async (accessToken, sourceConfig) => {
-    // Return { valid: true } or { valid: false, error: 'message' }
-  },
-
-  // Optional: map source metadata to semantic tag keys (translated to slots by sync engine)
-  mapTags: (metadata) => {
-    // Return Record<string, unknown> with keys matching tagDefinitions[].id
-  },
-}
-```
-
-### API key connector example
-
-```typescript
-export const {service}Connector: ConnectorConfig = {
-  id: '{service}',
-  name: '{Service}',
-  description: 'Sync documents from {Service} into your knowledge base',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  auth: {
-    mode: 'apiKey',
-    label: 'API Key',                       // Shown above the input field
-    placeholder: 'Enter your {Service} API key',  // Input placeholder
-  },
-
-  configFields: [ /* ... */ ],
-  listDocuments: async (accessToken, sourceConfig, cursor) => { /* ... */ },
-  getDocument: async (accessToken, sourceConfig, externalId) => { /* ... */ },
-  validateConfig: async (accessToken, sourceConfig) => { /* ... */ },
-}
-```
-
-## ConfigField Types
-
-The add-connector modal renders these automatically — no custom UI needed.
-
-Three field types are supported: `short-input`, `dropdown`, and `selector`.
-
-```typescript
-// Text input
-{
-  id: 'domain',
-  title: 'Domain',
-  type: 'short-input',
-  placeholder: 'yoursite.example.com',
-  required: true,
-}
-
-// Dropdown (static options)
-{
-  id: 'contentType',
-  title: 'Content Type',
-  type: 'dropdown',
-  required: false,
-  options: [
-    { label: 'Pages only', id: 'page' },
-    { label: 'Blog posts only', id: 'blogpost' },
-    { label: 'All content', id: 'all' },
-  ],
-}
-```
-
-## Dynamic Selectors (Canonical Pairs)
-
-Use `type: 'selector'` to fetch options dynamically from the existing selector registry (`hooks/selectors/registry.ts`). Selectors are always paired with a manual fallback input using the **canonical pair** pattern — a `selector` field (basic mode) and a `short-input` field (advanced mode) linked by `canonicalParamId`.
-
-The user sees a toggle button (ArrowLeftRight) to switch between the selector dropdown and manual text input. On submit, the modal resolves each canonical pair to the active mode's value, keyed by `canonicalParamId`.
-
-### Rules
-
-1. **Every selector field MUST have a canonical pair** — a corresponding `short-input` (or `dropdown`) field with the same `canonicalParamId` and `mode: 'advanced'`.
-2. **`required` must be set identically on both fields** in a pair. If the selector is required, the manual input must also be required.
-3. **`canonicalParamId` must match the key the connector expects in `sourceConfig`** (e.g. `baseId`, `channel`, `teamId`). The advanced field's `id` should typically match `canonicalParamId`.
-4. **`dependsOn` references the selector field's `id`**, not the `canonicalParamId`. The modal propagates dependency clearing across canonical siblings automatically — changing either field in a parent pair clears dependent children.
-
-### Selector canonical pair example (Airtable base → table cascade)
-
-```typescript
-configFields: [
-  // Base: selector (basic) + manual (advanced)
-  {
-    id: 'baseSelector',
-    title: 'Base',
-    type: 'selector',
-    selectorKey: 'airtable.bases',     // Must exist in hooks/selectors/registry.ts
-    canonicalParamId: 'baseId',
-    mode: 'basic',
-    placeholder: 'Select a base',
-    required: true,
-  },
-  {
-    id: 'baseId',
-    title: 'Base ID',
-    type: 'short-input',
-    canonicalParamId: 'baseId',
-    mode: 'advanced',
-    placeholder: 'e.g. appXXXXXXXXXXXXXX',
-    required: true,
-  },
-  // Table: selector depends on base (basic) + manual (advanced)
-  {
-    id: 'tableSelector',
-    title: 'Table',
-    type: 'selector',
-    selectorKey: 'airtable.tables',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'basic',
-    dependsOn: ['baseSelector'],       // References the selector field ID
-    placeholder: 'Select a table',
-    required: true,
-  },
-  {
-    id: 'tableIdOrName',
-    title: 'Table Name or ID',
-    type: 'short-input',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'advanced',
-    placeholder: 'e.g. Tasks',
-    required: true,
-  },
-  // Non-selector fields stay as-is
-  { id: 'maxRecords', title: 'Max Records', type: 'short-input', ... },
-]
-```
-
-### Selector with domain dependency (Jira/Confluence pattern)
-
-When a selector depends on a plain `short-input` field (no canonical pair), `dependsOn` references that field's `id` directly. The `domain` field's value maps to `SelectorContext.domain` automatically via `SELECTOR_CONTEXT_FIELDS`.
-
-```typescript
-configFields: [
-  {
-    id: 'domain',
-    title: 'Jira Domain',
-    type: 'short-input',
-    placeholder: 'yoursite.atlassian.net',
-    required: true,
-  },
-  {
-    id: 'projectSelector',
-    title: 'Project',
-    type: 'selector',
-    selectorKey: 'jira.projects',
-    canonicalParamId: 'projectKey',
-    mode: 'basic',
-    dependsOn: ['domain'],
-    placeholder: 'Select a project',
-    required: true,
-  },
-  {
-    id: 'projectKey',
-    title: 'Project Key',
-    type: 'short-input',
-    canonicalParamId: 'projectKey',
-    mode: 'advanced',
-    placeholder: 'e.g. ENG, PROJ',
-    required: true,
-  },
-]
-```
-
-### How `dependsOn` maps to `SelectorContext`
-
-The connector selector field builds a `SelectorContext` from dependency values. For the mapping to work, each dependency's `canonicalParamId` (or field `id` for non-canonical fields) must exist in `SELECTOR_CONTEXT_FIELDS` (`lib/workflows/subblocks/context.ts`):
-
-```
-oauthCredential, domain, teamId, projectId, knowledgeBaseId, planId,
-siteId, collectionId, spreadsheetId, fileId, baseId, datasetId, serviceDeskId
-```
-
-### Available selector keys
-
-Check `hooks/selectors/types.ts` for the full `SelectorKey` union. Common ones for connectors:
-
-| SelectorKey | Context Deps | Returns |
-|-------------|-------------|---------|
-| `airtable.bases` | credential | Base ID + name |
-| `airtable.tables` | credential, `baseId` | Table ID + name |
-| `slack.channels` | credential | Channel ID + name |
-| `gmail.labels` | credential | Label ID + name |
-| `google.calendar` | credential | Calendar ID + name |
-| `linear.teams` | credential | Team ID + name |
-| `linear.projects` | credential, `teamId` | Project ID + name |
-| `jira.projects` | credential, `domain` | Project key + name |
-| `confluence.spaces` | credential, `domain` | Space key + name |
-| `notion.databases` | credential | Database ID + name |
-| `asana.workspaces` | credential | Workspace GID + name |
-| `microsoft.teams` | credential | Team ID + name |
-| `microsoft.channels` | credential, `teamId` | Channel ID + name |
-| `webflow.sites` | credential | Site ID + name |
-| `outlook.folders` | credential | Folder ID + name |
-
-## ExternalDocument Shape
-
-Every document returned from `listDocuments`/`getDocument` must include:
-
-```typescript
-{
-  externalId: string          // Source-specific unique ID
-  title: string               // Document title
-  content: string             // Extracted plain text (or '' if contentDeferred)
-  contentDeferred?: boolean   // true = content will be fetched via getDocument
-  mimeType: 'text/plain'     // Always text/plain (content is extracted)
-  contentHash: string         // Metadata-based hash for change detection
-  sourceUrl?: string          // Link back to original (stored on document record)
-  metadata?: Record<string, unknown>  // Source-specific data (fed to mapTags)
-}
-```
-
-## Content Deferral (Required for file/content-download connectors)
-
-**All connectors that require per-document API calls to fetch content MUST use `contentDeferred: true`.** This is the standard pattern — `listDocuments` returns lightweight metadata stubs, and content is fetched lazily by the sync engine via `getDocument` only for new/changed documents.
-
-This pattern is critical for reliability: the sync engine processes documents in batches and enqueues each batch for processing immediately. If a sync times out, all previously-batched documents are already queued. Without deferral, content downloads during listing can exhaust the sync task's time budget before any documents are saved.
-
-### When to use `contentDeferred: true`
-
-- The service's list API does NOT return document content (only metadata)
-- Content requires a separate download/export API call per document
-- Examples: Google Drive, OneDrive, SharePoint, Dropbox, Notion, Confluence, Gmail, Obsidian, Evernote, GitHub
-
-### When NOT to use `contentDeferred`
-
-- The list API already returns the full content inline (e.g., Slack messages, Reddit posts, HubSpot notes)
-- No per-document API call is needed to get content
-
-### Content Hash Strategy
-
-Use a **metadata-based** `contentHash` — never a content-based hash. The hash must be derivable from the list response metadata alone, so the sync engine can detect changes without downloading content.
-
-Good metadata hash sources:
-- `modifiedTime` / `lastModifiedDateTime` — changes when file is edited
-- Git blob SHA — unique per content version
-- API-provided content hash (e.g., Dropbox `content_hash`)
-- Version number (e.g., Confluence page version)
-
-Format: `{service}:{id}:{changeIndicator}`
-
-```typescript
-// Google Drive: modifiedTime changes on edit
-contentHash: `gdrive:${file.id}:${file.modifiedTime ?? ''}`
-
-// GitHub: blob SHA is a content-addressable hash
-contentHash: `gitsha:${item.sha}`
-
-// Dropbox: API provides content_hash
-contentHash: `dropbox:${entry.id}:${entry.content_hash ?? entry.server_modified}`
-
-// Confluence: version number increments on edit
-contentHash: `confluence:${page.id}:${page.version.number}`
-```
-
-**Critical invariant:** The `contentHash` MUST be identical whether produced by `listDocuments` (stub) or `getDocument` (full doc). Both should use the same stub function to guarantee this.
-
-### Implementation Pattern
-
-```typescript
-// 1. Create a stub function (sync, no API calls)
-function fileToStub(file: ServiceFile): ExternalDocument {
-  return {
-    externalId: file.id,
-    title: file.name || 'Untitled',
-    content: '',
-    contentDeferred: true,
-    mimeType: 'text/plain',
-    sourceUrl: `https://service.com/file/${file.id}`,
-    contentHash: `service:${file.id}:${file.modifiedTime ?? ''}`,
-    metadata: { /* fields needed by mapTags */ },
-  }
-}
-
-// 2. listDocuments returns stubs (fast, metadata only)
-listDocuments: async (accessToken, sourceConfig, cursor) => {
-  const response = await fetchWithRetry(listUrl, { ... })
-  const files = (await response.json()).files
-  const documents = files.map(fileToStub)
-  return { documents, nextCursor, hasMore }
-}
-
-// 3. getDocument fetches content and returns full doc with SAME contentHash
-getDocument: async (accessToken, sourceConfig, externalId) => {
-  const metadata = await fetchWithRetry(metadataUrl, { ... })
-  const file = await metadata.json()
-  if (file.trashed) return null
-
-  try {
-    const content = await fetchContent(accessToken, file)
-    if (!content.trim()) return null
-    const stub = fileToStub(file)
-    return { ...stub, content, contentDeferred: false }
-  } catch (error) {
-    logger.warn(`Failed to fetch content for: ${file.name}`, { error })
-    return null
-  }
-}
-```
-
-### Reference Implementations
-
-- **Google Drive**: `connectors/google-drive/google-drive.ts` — file download/export with `modifiedTime` hash
-- **GitHub**: `connectors/github/github.ts` — git blob SHA hash
-- **Notion**: `connectors/notion/notion.ts` — blocks API with `last_edited_time` hash
-- **Confluence**: `connectors/confluence/confluence.ts` — version number hash
-
-## tagDefinitions — Declared Tag Definitions
-
-Declare which tags the connector populates using semantic IDs. Shown in the add-connector modal as opt-out checkboxes.
-On connector creation, slots are **dynamically assigned** via `getNextAvailableSlot` — connectors never hardcode slot names.
-
-```typescript
-tagDefinitions: [
-  { id: 'labels', displayName: 'Labels', fieldType: 'text' },
-  { id: 'version', displayName: 'Version', fieldType: 'number' },
-  { id: 'lastModified', displayName: 'Last Modified', fieldType: 'date' },
-],
-```
-
-Each entry has:
-- `id`: Semantic key matching a key returned by `mapTags` (e.g. `'labels'`, `'version'`)
-- `displayName`: Human-readable name shown in the UI (e.g. "Labels", "Last Modified")
-- `fieldType`: `'text'` | `'number'` | `'date'` | `'boolean'` — determines which slot pool to draw from
-
-Users can opt out of specific tags in the modal. Disabled IDs are stored in `sourceConfig.disabledTagIds`.
-The assigned mapping (`semantic id → slot`) is stored in `sourceConfig.tagSlotMapping`.
-
-## mapTags — Metadata to Semantic Keys
-
-Maps source metadata to semantic tag keys. Required if `tagDefinitions` is set.
-The sync engine calls this automatically and translates semantic keys to actual DB slots
-using the `tagSlotMapping` stored on the connector.
-
-Return keys must match the `id` values declared in `tagDefinitions`.
-
-```typescript
-mapTags: (metadata: Record<string, unknown>): Record<string, unknown> => {
-  const result: Record<string, unknown> = {}
-
-  // Validate arrays before casting — metadata may be malformed
-  const labels = Array.isArray(metadata.labels) ? (metadata.labels as string[]) : []
-  if (labels.length > 0) result.labels = labels.join(', ')
-
-  // Validate numbers — guard against NaN
-  if (metadata.version != null) {
-    const num = Number(metadata.version)
-    if (!Number.isNaN(num)) result.version = num
-  }
-
-  // Validate dates — guard against Invalid Date
-  if (typeof metadata.lastModified === 'string') {
-    const date = new Date(metadata.lastModified)
-    if (!Number.isNaN(date.getTime())) result.lastModified = date
-  }
-
-  return result
-}
-```
-
-## External API Calls — Use `fetchWithRetry`
-
-All external API calls must use `fetchWithRetry` from `@/lib/knowledge/documents/utils` instead of raw `fetch()`. This provides exponential backoff with retries on 429/502/503/504 errors. It returns a standard `Response` — all `.ok`, `.json()`, `.text()` checks work unchanged.
-
-For `validateConfig` (user-facing, called on save), pass `VALIDATE_RETRY_OPTIONS` to cap wait time at ~7s. Background operations (`listDocuments`, `getDocument`) use the built-in defaults (5 retries, ~31s max).
-
-```typescript
-import { VALIDATE_RETRY_OPTIONS, fetchWithRetry } from '@/lib/knowledge/documents/utils'
-
-// Background sync — use defaults
-const response = await fetchWithRetry(url, {
-  method: 'GET',
-  headers: { Authorization: `Bearer ${accessToken}` },
-})
-
-// validateConfig — tighter retry budget
-const response = await fetchWithRetry(url, { ... }, VALIDATE_RETRY_OPTIONS)
-```
-
-## sourceUrl
-
-If `ExternalDocument.sourceUrl` is set, the sync engine stores it on the document record. Always construct the full URL (not a relative path).
-
-## Sync Engine Behavior (Do Not Modify)
-
-The sync engine (`lib/knowledge/connectors/sync-engine.ts`) is connector-agnostic. It:
-1. Calls `listDocuments` with pagination until `hasMore` is false
-2. Compares `contentHash` to detect new/changed/unchanged documents
-3. Stores `sourceUrl` and calls `mapTags` on insert/update automatically
-4. Handles soft-delete of removed documents
-5. Resolves access tokens automatically — OAuth tokens are refreshed, API keys are decrypted from the `encryptedApiKey` column
-
-You never need to modify the sync engine when adding a connector.
-
-## Icon
-
-The `icon` field on `ConnectorConfig` is used throughout the UI — in the connector list, the add-connector modal, and as the document icon in the knowledge base table (replacing the generic file type icon for connector-sourced documents). The icon is read from `CONNECTOR_REGISTRY[connectorType].icon` at runtime — no separate icon map to maintain.
-
-If the service already has an icon in `apps/sim/components/icons.tsx` (from a tool integration), reuse it. Otherwise, ask the user to provide the SVG.
-
-## Registering
-
-Add one line to `apps/sim/connectors/registry.ts`:
-
-```typescript
-import { {service}Connector } from '@/connectors/{service}'
-
-export const CONNECTOR_REGISTRY: ConnectorRegistry = {
-  // ... existing connectors ...
-  {service}: {service}Connector,
-}
-```
-
-## Reference Implementations
-
-- **OAuth + contentDeferred**: `apps/sim/connectors/google-drive/google-drive.ts` — file download with metadata-based hash, `orderBy` for deterministic pagination
-- **OAuth + contentDeferred (blocks API)**: `apps/sim/connectors/notion/notion.ts` — complex block content extraction deferred to `getDocument`
-- **OAuth + contentDeferred (git)**: `apps/sim/connectors/github/github.ts` — blob SHA hash, tree listing
-- **OAuth + inline content**: `apps/sim/connectors/confluence/confluence.ts` — multiple config field types, `mapTags`, label fetching
-- **API key**: `apps/sim/connectors/fireflies/fireflies.ts` — GraphQL API with Bearer token auth
-
-## Checklist
-
-- [ ] Created `connectors/{service}/{service}.ts` with full ConnectorConfig
-- [ ] Created `connectors/{service}/index.ts` barrel export
-- [ ] **Auth configured correctly:**
-  - OAuth: `auth.provider` matches an existing `OAuthService` in `lib/oauth/types.ts`
-  - API key: `auth.label` and `auth.placeholder` set appropriately
-- [ ] **Selector fields configured correctly (if applicable):**
-  - Every `type: 'selector'` field has a canonical pair (`short-input` or `dropdown` with same `canonicalParamId` and `mode: 'advanced'`)
-  - `required` is identical on both fields in each canonical pair
-  - `selectorKey` exists in `hooks/selectors/registry.ts`
-  - `dependsOn` references selector field IDs (not `canonicalParamId`)
-  - Dependency `canonicalParamId` values exist in `SELECTOR_CONTEXT_FIELDS`
-- [ ] `listDocuments` handles pagination with metadata-based content hashes
-- [ ] `contentDeferred: true` used if content requires per-doc API calls (file download, export, blocks fetch)
-- [ ] `contentHash` is metadata-based (not content-based) and identical between stub and `getDocument`
-- [ ] `sourceUrl` set on each ExternalDocument (full URL, not relative)
-- [ ] `metadata` includes source-specific data for tag mapping
-- [ ] `tagDefinitions` declared for each semantic key returned by `mapTags`
-- [ ] `mapTags` implemented if source has useful metadata (labels, dates, versions)
-- [ ] `validateConfig` verifies the source is accessible
-- [ ] All external API calls use `fetchWithRetry` (not raw `fetch`)
-- [ ] All optional config fields validated in `validateConfig`
-- [ ] Icon exists in `components/icons.tsx` (or asked user to provide SVG)
-- [ ] Registered in `connectors/registry.ts`

.agents/skills/add-connector/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Connector"
-  short_description: "Build a Sim knowledge connector"
-  brand_color: "#0F766E"
-  default_prompt: "Use $add-connector to add or update a Sim knowledge connector for a service."

.agents/skills/add-integration/SKILL.md

@@ -1,760 +0,0 @@
----
-name: add-integration
-description: Add a complete Sim integration from API docs, covering tools, block, icon, optional triggers, registrations, and integration conventions. Use when introducing a new service under `apps/sim/tools`, `apps/sim/blocks`, and `apps/sim/triggers`.
----
-
-# Add Integration Skill
-
-You are an expert at adding complete integrations to Sim. This skill orchestrates the full process of adding a new service integration.
-
-## Overview
-
-Adding an integration involves these steps in order:
-1. **Research** - Read the service's API documentation
-2. **Create Tools** - Build tool configurations for each API operation
-3. **Create Block** - Build the block UI configuration
-4. **Add Icon** - Add the service's brand icon
-5. **Create Triggers** (optional) - If the service supports webhooks
-6. **Register** - Register tools, block, and triggers in their registries
-7. **Generate Docs** - Run the docs generation script
-
-## Step 1: Research the API
-
-Before writing any code:
-1. Use Context7 to find official documentation: `mcp__plugin_context7_context7__resolve-library-id`
-2. Or use WebFetch to read API docs directly
-3. Identify:
-   - Authentication method (OAuth, API Key, both)
-   - Available operations (CRUD, search, etc.)
-   - Required vs optional parameters
-   - Response structures
-
-## Step 2: Create Tools
-
-### Directory Structure
-```
-apps/sim/tools/{service}/
-├── index.ts          # Barrel exports
-├── types.ts          # TypeScript interfaces
-├── {action1}.ts      # Tool for action 1
-├── {action2}.ts      # Tool for action 2
-└── ...
-```
-
-### Key Patterns
-
-**types.ts:**
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-export interface {Service}{Action}Params {
-  accessToken: string      // For OAuth services
-  // OR
-  apiKey: string          // For API key services
-
-  requiredParam: string
-  optionalParam?: string
-}
-
-export interface {Service}Response extends ToolResponse {
-  output: {
-    // Define output structure
-  }
-}
-```
-
-**Tool file pattern:**
-```typescript
-export const {service}{Action}Tool: ToolConfig<Params, Response> = {
-  id: '{service}_{action}',
-  name: '{Service} {Action}',
-  description: '...',
-  version: '1.0.0',
-
-  oauth: { required: true, provider: '{service}' },  // If OAuth
-
-  params: {
-    accessToken: { type: 'string', required: true, visibility: 'hidden', description: '...' },
-    // ... other params
-  },
-
-  request: { url, method, headers, body },
-
-  transformResponse: async (response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        field: data.field ?? null,  // Always handle nullables
-      },
-    }
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Critical Rules
-- `visibility: 'hidden'` for OAuth tokens
-- `visibility: 'user-only'` for API keys and user credentials
-- `visibility: 'user-or-llm'` for operation parameters
-- Always use `?? null` for nullable API response fields
-- Always use `?? []` for optional array fields
-- Set `optional: true` for outputs that may not exist
-- Never output raw JSON dumps - extract meaningful fields
-- When using `type: 'json'` and you know the object shape, define `properties` with the inner fields so downstream consumers know the structure. Only use bare `type: 'json'` when the shape is truly dynamic
-
-## Step 3: Create Block
-
-### File Location
-`apps/sim/blocks/blocks/{service}.ts`
-
-### Block Structure
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import type { BlockConfig } from '@/blocks/types'
-import { AuthMode } from '@/blocks/types'
-import { getScopesForService } from '@/lib/oauth/utils'
-
-export const {Service}Block: BlockConfig = {
-  type: '{service}',
-  name: '{Service}',
-  description: '...',
-  longDescription: '...',
-  docsLink: 'https://docs.sim.ai/tools/{service}',
-  category: 'tools',
-  bgColor: '#HEXCOLOR',
-  icon: {Service}Icon,
-  authMode: AuthMode.OAuth,  // or AuthMode.ApiKey
-
-  subBlocks: [
-    // Operation dropdown
-    {
-      id: 'operation',
-      title: 'Operation',
-      type: 'dropdown',
-      options: [
-        { label: 'Operation 1', id: 'action1' },
-        { label: 'Operation 2', id: 'action2' },
-      ],
-      value: () => 'action1',
-    },
-    // Credential field
-    {
-      id: 'credential',
-      title: '{Service} Account',
-      type: 'oauth-input',
-      serviceId: '{service}',
-      requiredScopes: getScopesForService('{service}'),
-      required: true,
-    },
-    // Conditional fields per operation
-    // ...
-  ],
-
-  tools: {
-    access: ['{service}_action1', '{service}_action2'],
-    config: {
-      tool: (params) => `{service}_${params.operation}`,
-    },
-  },
-
-  outputs: { /* ... */ },
-}
-```
-
-### Key SubBlock Patterns
-
-**Condition-based visibility:**
-```typescript
-{
-  id: 'resourceId',
-  title: 'Resource ID',
-  type: 'short-input',
-  condition: { field: 'operation', value: ['read', 'update', 'delete'] },
-  required: { field: 'operation', value: ['read', 'update', 'delete'] },
-}
-```
-
-**DependsOn for cascading selectors:**
-```typescript
-{
-  id: 'project',
-  type: 'project-selector',
-  dependsOn: ['credential'],
-},
-{
-  id: 'issue',
-  type: 'file-selector',
-  dependsOn: ['credential', 'project'],
-}
-```
-
-**Basic/Advanced mode for dual UX:**
-```typescript
-// Basic: Visual selector
-{
-  id: 'channel',
-  type: 'channel-selector',
-  mode: 'basic',
-  canonicalParamId: 'channel',
-  dependsOn: ['credential'],
-},
-// Advanced: Manual input
-{
-  id: 'channelId',
-  type: 'short-input',
-  mode: 'advanced',
-  canonicalParamId: 'channel',
-}
-```
-
-**Critical Canonical Param Rules:**
-- `canonicalParamId` must NOT match any subblock's `id` in the block
-- `canonicalParamId` must be unique per operation/condition context
-- Only use `canonicalParamId` to link basic/advanced alternatives for the same logical parameter
-- `mode` only controls UI visibility, NOT serialization. Without `canonicalParamId`, both basic and advanced field values would be sent
-- Every subblock `id` must be unique within the block. Duplicate IDs cause conflicts even with different conditions
-- **Required consistency:** If one subblock in a canonical group has `required: true`, ALL subblocks in that group must have `required: true` (prevents bypassing validation by switching modes)
-- **Inputs section:** Must list canonical param IDs (e.g., `fileId`), NOT raw subblock IDs (e.g., `fileSelector`, `manualFileId`)
-- **Params function:** Must use canonical param IDs, NOT raw subblock IDs (raw IDs are deleted after canonical transformation)
-
-## Step 4: Add Icon
-
-### File Location
-`apps/sim/components/icons.tsx`
-
-### Pattern
-```typescript
-export function {Service}Icon(props: SVGProps<SVGSVGElement>) {
-  return (
-    <svg
-      {...props}
-      viewBox="0 0 24 24"
-      fill="none"
-      xmlns="http://www.w3.org/2000/svg"
-    >
-      {/* SVG paths from user-provided SVG */}
-    </svg>
-  )
-}
-```
-
-### Getting Icons
-**Do NOT search for icons yourself.** At the end of implementation, ask the user to provide the SVG:
-
-```
-I've completed the integration. Before I can add the icon, please provide the SVG for {Service}.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-Once the user provides the SVG:
-1. Extract the SVG paths/content
-2. Create a React component that spreads props
-3. Ensure viewBox is preserved from the original SVG
-
-## Step 5: Create Triggers (Optional)
-
-If the service supports webhooks, create triggers using the generic `buildTriggerSubBlocks` helper.
-
-### Directory Structure
-```
-apps/sim/triggers/{service}/
-├── index.ts      # Barrel exports
-├── utils.ts      # Trigger options, setup instructions, extra fields
-├── {event_a}.ts  # Primary trigger (includes dropdown)
-├── {event_b}.ts  # Secondary triggers (no dropdown)
-└── webhook.ts    # Generic webhook (optional)
-```
-
-### Key Pattern
-
-```typescript
-import { buildTriggerSubBlocks } from '@/triggers'
-import { {service}TriggerOptions, {service}SetupInstructions, build{Service}ExtraFields } from './utils'
-
-// Primary trigger - includeDropdown: true
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,  // Only for primary trigger!
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-  // ...
-}
-
-// Secondary triggers - no dropdown
-export const {service}EventBTrigger: TriggerConfig = {
-  id: '{service}_event_b',
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_b',
-    triggerOptions: {service}TriggerOptions,
-    // No includeDropdown!
-    setupInstructions: {service}SetupInstructions('Event B'),
-    extraFields: build{Service}ExtraFields('{service}_event_b'),
-  }),
-  // ...
-}
-```
-
-### Connect to Block
-```typescript
-import { getTrigger } from '@/triggers'
-
-export const {Service}Block: BlockConfig = {
-  triggers: {
-    enabled: true,
-    available: ['{service}_event_a', '{service}_event_b'],
-  },
-  subBlocks: [
-    // Tool fields...
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-  ],
-}
-```
-
-See `/add-trigger` skill for complete documentation.
-
-## Step 6: Register Everything
-
-### Tools Registry (`apps/sim/tools/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}Action1Tool,
-  {service}Action2Tool,
-} from '@/tools/{service}'
-
-// Add to tools object (alphabetically)
-export const tools: Record<string, ToolConfig> = {
-  // ... existing tools ...
-  {service}_action1: {service}Action1Tool,
-  {service}_action2: {service}Action2Tool,
-}
-```
-
-### Block Registry (`apps/sim/blocks/registry.ts`)
-
-```typescript
-// Add import (alphabetically)
-import { {Service}Block } from '@/blocks/blocks/{service}'
-
-// Add to registry (alphabetically)
-export const registry: Record<string, BlockConfig> = {
-  // ... existing blocks ...
-  {service}: {Service}Block,
-}
-```
-
-### Trigger Registry (`apps/sim/triggers/registry.ts`) - If triggers exist
-
-```typescript
-// Add import (alphabetically)
-import {
-  {service}EventATrigger,
-  {service}EventBTrigger,
-  {service}WebhookTrigger,
-} from '@/triggers/{service}'
-
-// Add to TRIGGER_REGISTRY (alphabetically)
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing triggers ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-  {service}_webhook: {service}WebhookTrigger,
-}
-```
-
-## Step 7: Generate Docs
-
-Run the documentation generator:
-```bash
-bun run scripts/generate-docs.ts
-```
-
-This creates `apps/docs/content/docs/en/tools/{service}.mdx`
-
-## V2 Integration Pattern
-
-If creating V2 versions (API-aligned outputs):
-
-1. **V2 Tools** - Add `_v2` suffix, version `2.0.0`, flat outputs
-2. **V2 Block** - Add `_v2` type, use `createVersionedToolSelector`
-3. **V1 Block** - Add `(Legacy)` to name, set `hideFromToolbar: true`
-4. **Registry** - Register both versions
-
-```typescript
-// In registry
-{service}: {Service}Block,        // V1 (legacy, hidden)
-{service}_v2: {Service}V2Block,   // V2 (visible)
-```
-
-## Complete Checklist
-
-### Tools
-- [ ] Created `tools/{service}/` directory
-- [ ] Created `types.ts` with all interfaces
-- [ ] Created tool file for each operation
-- [ ] All params have correct visibility
-- [ ] All nullable fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all tools in `tools/registry.ts`
-
-### Block
-- [ ] Created `blocks/blocks/{service}.ts`
-- [ ] Defined operation dropdown with all operations
-- [ ] Added credential field with `requiredScopes: getScopesForService('{service}')`
-- [ ] Added conditional fields per operation
-- [ ] Set up dependsOn for cascading selectors
-- [ ] Configured tools.access with all tool IDs
-- [ ] Configured tools.config.tool selector
-- [ ] Defined outputs matching tool outputs
-- [ ] Registered block in `blocks/registry.ts`
-- [ ] If triggers: set `triggers.enabled` and `triggers.available`
-- [ ] If triggers: spread trigger subBlocks with `getTrigger()`
-
-### OAuth Scopes (if OAuth service)
-- [ ] Defined scopes in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS`
-- [ ] Added scope descriptions in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] Used `getCanonicalScopesForProvider()` in `auth.ts` (never hardcode)
-- [ ] Used `getScopesForService()` in block `requiredScopes` (never hardcode)
-
-### Icon
-- [ ] Asked user to provide SVG
-- [ ] Added icon to `components/icons.tsx`
-- [ ] Icon spreads props correctly
-
-### Triggers (if service supports webhooks)
-- [ ] Created `triggers/{service}/` directory
-- [ ] Created `utils.ts` with options, instructions, and extra fields helpers
-- [ ] Primary trigger uses `includeDropdown: true`
-- [ ] Secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] Created `index.ts` barrel export
-- [ ] Registered all triggers in `triggers/registry.ts`
-
-### Docs
-- [ ] Ran `bun run scripts/generate-docs.ts`
-- [ ] Verified docs file created
-
-### Final Validation (Required)
-- [ ] Read every tool file and cross-referenced inputs/outputs against the API docs
-- [ ] Verified block subBlocks cover all required tool params with correct conditions
-- [ ] Verified block outputs match what the tools actually return
-- [ ] Verified `tools.config.params` correctly maps and coerces all param types
-
-## Example Command
-
-When the user asks to add an integration:
-
-```
-User: Add a Stripe integration
-
-You: I'll add the Stripe integration. Let me:
-
-1. First, research the Stripe API using Context7
-2. Create the tools for key operations (payments, subscriptions, etc.)
-3. Create the block with operation dropdown
-4. Register everything
-5. Generate docs
-6. Ask you for the Stripe icon SVG
-
-[Proceed with implementation...]
-
-[After completing steps 1-5...]
-
-I've completed the Stripe integration. Before I can add the icon, please provide the SVG for Stripe.
-You can usually find this in the service's brand/press kit page, or copy it from their website.
-
-Paste the SVG code here and I'll convert it to a React component.
-```
-
-## File Handling
-
-When your integration handles file uploads or downloads, follow these patterns to work with `UserFile` objects consistently.
-
-### What is a UserFile?
-
-A `UserFile` is the standard file representation in Sim:
-
-```typescript
-interface UserFile {
-  id: string       // Unique identifier
-  name: string     // Original filename
-  url: string      // Presigned URL for download
-  size: number     // File size in bytes
-  type: string     // MIME type (e.g., 'application/pdf')
-  base64?: string  // Optional base64 content (if small file)
-  key?: string     // Internal storage key
-  context?: object // Storage context metadata
-}
-```
-
-### File Input Pattern (Uploads)
-
-For tools that accept file uploads, **always route through an internal API endpoint** rather than calling external APIs directly. This ensures proper file content retrieval.
-
-#### 1. Block SubBlocks for File Input
-
-Use the basic/advanced mode pattern:
-
-```typescript
-// Basic mode: File upload UI
-{
-  id: 'uploadFile',
-  title: 'File',
-  type: 'file-upload',
-  canonicalParamId: 'file',  // Maps to 'file' param
-  placeholder: 'Upload file',
-  mode: 'basic',
-  multiple: false,
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-// Advanced mode: Reference from previous block
-{
-  id: 'fileRef',
-  title: 'File',
-  type: 'short-input',
-  canonicalParamId: 'file',  // Same canonical param
-  placeholder: 'Reference file (e.g., {{file_block.output}})',
-  mode: 'advanced',
-  required: true,
-  condition: { field: 'operation', value: 'upload' },
-},
-```
-
-**Critical:** `canonicalParamId` must NOT match any subblock `id`.
-
-#### 2. Normalize File Input in Block Config
-
-In `tools.config.tool`, use `normalizeFileInput` to handle all input variants:
-
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-
-tools: {
-  config: {
-    tool: (params) => {
-      // Normalize file from basic (uploadFile), advanced (fileRef), or legacy (fileContent)
-      const normalizedFile = normalizeFileInput(
-        params.uploadFile || params.fileRef || params.fileContent,
-        { single: true }
-      )
-      if (normalizedFile) {
-        params.file = normalizedFile
-      }
-      return `{service}_${params.operation}`
-    },
-  },
-}
-```
-
-#### 3. Create Internal API Route
-
-Create `apps/sim/app/api/tools/{service}/{action}/route.ts`:
-
-```typescript
-import { createLogger } from '@sim/logger'
-import { NextResponse, type NextRequest } from 'next/server'
-import { z } from 'zod'
-import { checkInternalAuth } from '@/lib/auth/hybrid'
-import { generateRequestId } from '@/lib/core/utils/request'
-import { FileInputSchema, type RawFileInput } from '@/lib/uploads/utils/file-schemas'
-import { processFilesToUserFiles } from '@/lib/uploads/utils/file-utils'
-import { downloadFileFromStorage } from '@/lib/uploads/utils/file-utils.server'
-
-const logger = createLogger('{Service}UploadAPI')
-
-const RequestSchema = z.object({
-  accessToken: z.string(),
-  file: FileInputSchema.optional().nullable(),
-  // Legacy field for backwards compatibility
-  fileContent: z.string().optional().nullable(),
-  // ... other params
-})
-
-export async function POST(request: NextRequest) {
-  const requestId = generateRequestId()
-
-  const authResult = await checkInternalAuth(request, { requireWorkflowId: false })
-  if (!authResult.success) {
-    return NextResponse.json({ success: false, error: 'Unauthorized' }, { status: 401 })
-  }
-
-  const body = await request.json()
-  const data = RequestSchema.parse(body)
-
-  let fileBuffer: Buffer
-  let fileName: string
-
-  // Prefer UserFile input, fall back to legacy base64
-  if (data.file) {
-    const userFiles = processFilesToUserFiles([data.file as RawFileInput], requestId, logger)
-    if (userFiles.length === 0) {
-      return NextResponse.json({ success: false, error: 'Invalid file' }, { status: 400 })
-    }
-    const userFile = userFiles[0]
-    fileBuffer = await downloadFileFromStorage(userFile, requestId, logger)
-    fileName = userFile.name
-  } else if (data.fileContent) {
-    // Legacy: base64 string (backwards compatibility)
-    fileBuffer = Buffer.from(data.fileContent, 'base64')
-    fileName = 'file'
-  } else {
-    return NextResponse.json({ success: false, error: 'File required' }, { status: 400 })
-  }
-
-  // Now call external API with fileBuffer
-  const response = await fetch('https://api.{service}.com/upload', {
-    method: 'POST',
-    headers: { Authorization: `Bearer ${data.accessToken}` },
-    body: new Uint8Array(fileBuffer),  // Convert Buffer for fetch
-  })
-
-  // ... handle response
-}
-```
-
-#### 4. Update Tool to Use Internal Route
-
-```typescript
-export const {service}UploadTool: ToolConfig<Params, Response> = {
-  id: '{service}_upload',
-  // ...
-  params: {
-    file: { type: 'file', required: false, visibility: 'user-or-llm' },
-    fileContent: { type: 'string', required: false, visibility: 'hidden' }, // Legacy
-  },
-  request: {
-    url: '/api/tools/{service}/upload',  // Internal route
-    method: 'POST',
-    body: (params) => ({
-      accessToken: params.accessToken,
-      file: params.file,
-      fileContent: params.fileContent,
-    }),
-  },
-}
-```
-
-### File Output Pattern (Downloads)
-
-For tools that return files, use `FileToolProcessor` to store files and return `UserFile` objects.
-
-#### In Tool transformResponse
-
-```typescript
-import { FileToolProcessor } from '@/executor/utils/file-tool-processor'
-
-transformResponse: async (response, context) => {
-  const data = await response.json()
-
-  // Process file outputs to UserFile objects
-  const fileProcessor = new FileToolProcessor(context)
-  const file = await fileProcessor.processFileData({
-    data: data.content,      // base64 or buffer
-    mimeType: data.mimeType,
-    filename: data.filename,
-  })
-
-  return {
-    success: true,
-    output: { file },
-  }
-}
-```
-
-#### In API Route (for complex file handling)
-
-```typescript
-// Return file data that FileToolProcessor can handle
-return NextResponse.json({
-  success: true,
-  output: {
-    file: {
-      data: base64Content,
-      mimeType: 'application/pdf',
-      filename: 'document.pdf',
-    },
-  },
-})
-```
-
-### Key Helpers Reference
-
-| Helper | Location | Purpose |
-|--------|----------|---------|
-| `normalizeFileInput` | `@/blocks/utils` | Normalize file params in block config |
-| `processFilesToUserFiles` | `@/lib/uploads/utils/file-utils` | Convert raw inputs to UserFile[] |
-| `downloadFileFromStorage` | `@/lib/uploads/utils/file-utils.server` | Get file Buffer from UserFile |
-| `FileToolProcessor` | `@/executor/utils/file-tool-processor` | Process tool output files |
-| `isUserFile` | `@/lib/core/utils/user-file` | Type guard for UserFile objects |
-| `FileInputSchema` | `@/lib/uploads/utils/file-schemas` | Zod schema for file validation |
-
-### Advanced Mode for Optional Fields
-
-Optional fields that are rarely used should be set to `mode: 'advanced'` so they don't clutter the basic UI. Examples: pagination tokens, time range filters, sort order, max results, reply settings.
-
-### WandConfig for Complex Inputs
-
-Use `wandConfig` for fields that are hard to fill out manually:
-- **Timestamps**: Use `generationType: 'timestamp'` to inject current date context into the AI prompt
-- **JSON arrays**: Use `generationType: 'json-object'` for structured data
-- **Complex queries**: Use a descriptive prompt explaining the expected format
-
-```typescript
-{
-  id: 'startTime',
-  title: 'Start Time',
-  type: 'short-input',
-  mode: 'advanced',
-  wandConfig: {
-    enabled: true,
-    prompt: 'Generate an ISO 8601 timestamp. Return ONLY the timestamp string.',
-    generationType: 'timestamp',
-  },
-}
-```
-
-### OAuth Scopes (Centralized System)
-
-Scopes are maintained in a single source of truth and reused everywhere:
-
-1. **Define scopes** in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-2. **Add descriptions** in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for the OAuth modal UI
-3. **Reference in auth.ts** using `getCanonicalScopesForProvider(providerId)` from `@/lib/oauth/utils`
-4. **Reference in blocks** using `getScopesForService(serviceId)` from `@/lib/oauth/utils`
-
-**Never hardcode scope arrays** in `auth.ts` or block `requiredScopes`. Always import from the centralized source.
-
-```typescript
-// In auth.ts (Better Auth config)
-scopes: getCanonicalScopesForProvider('{service}'),
-
-// In block credential sub-block
-requiredScopes: getScopesForService('{service}'),
-```
-
-### Common Gotchas
-
-1. **OAuth serviceId must match** - The `serviceId` in oauth-input must match the OAuth provider configuration
-2. **All tool IDs MUST be snake_case** - `stripe_create_payment`, not `stripeCreatePayment`. This applies to tool `id` fields, registry keys, `tools.access` arrays, and `tools.config.tool` return values
-3. **Block type is snake_case** - `type: 'stripe'`, not `type: 'Stripe'`
-4. **Alphabetical ordering** - Keep imports and registry entries alphabetically sorted
-5. **Required can be conditional** - Use `required: { field: 'op', value: 'create' }` instead of always true
-6. **DependsOn clears options** - When a dependency changes, selector options are refetched
-7. **Never pass Buffer directly to fetch** - Convert to `new Uint8Array(buffer)` for TypeScript compatibility
-8. **Always handle legacy file params** - Keep hidden `fileContent` params for backwards compatibility
-9. **Optional fields use advanced mode** - Set `mode: 'advanced'` on rarely-used optional fields
-10. **Complex inputs need wandConfig** - Timestamps, JSON arrays, and other hard-to-type values should have `wandConfig` enabled
-11. **Never hardcode scopes** - Use `getScopesForService()` in blocks and `getCanonicalScopesForProvider()` in auth.ts
-12. **Always add scope descriptions** - New scopes must have entries in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`

.agents/skills/add-integration/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Integration"
-  short_description: "Build a full Sim integration"
-  brand_color: "#7C3AED"
-  default_prompt: "Use $add-integration to add a complete Sim integration for a service."

.agents/skills/add-tools/SKILL.md

@@ -1,321 +0,0 @@
----
-name: add-tools
-description: Create or update Sim tool configurations from service API docs, including typed params, request mapping, response transforms, outputs, and registry entries. Use when working in `apps/sim/tools/{service}/` or fixing tool definitions for an integration.
----
-
-# Add Tools Skill
-
-You are an expert at creating tool configurations for Sim integrations. Your job is to read API documentation and create properly structured tool files.
-
-## Your Task
-
-When the user asks you to create tools for a service:
-1. Use Context7 or WebFetch to read the service's API documentation
-2. Create the tools directory structure
-3. Generate properly typed tool configurations
-
-## Directory Structure
-
-Create files in `apps/sim/tools/{service}/`:
-```
-tools/{service}/
-├── index.ts      # Barrel export
-├── types.ts      # Parameter & response types
-└── {action}.ts   # Individual tool files (one per operation)
-```
-
-## Tool Configuration Structure
-
-Every tool MUST follow this exact structure:
-
-```typescript
-import type { {ServiceName}{Action}Params } from '@/tools/{service}/types'
-import type { ToolConfig } from '@/tools/types'
-
-interface {ServiceName}{Action}Response {
-  success: boolean
-  output: {
-    // Define output structure here
-  }
-}
-
-export const {serviceName}{Action}Tool: ToolConfig<
-  {ServiceName}{Action}Params,
-  {ServiceName}{Action}Response
-> = {
-  id: '{service}_{action}',           // snake_case, matches tool name
-  name: '{Service} {Action}',         // Human readable
-  description: 'Brief description',   // One sentence
-  version: '1.0.0',
-
-  // OAuth config (if service uses OAuth)
-  oauth: {
-    required: true,
-    provider: '{service}',            // Must match OAuth provider ID
-  },
-
-  params: {
-    // Hidden params (system-injected, only use hidden for oauth accessToken)
-    accessToken: {
-      type: 'string',
-      required: true,
-      visibility: 'hidden',
-      description: 'OAuth access token',
-    },
-    // User-only params (credentials, api key, IDs user must provide)
-    someId: {
-      type: 'string',
-      required: true,
-      visibility: 'user-only',
-      description: 'The ID of the resource',
-    },
-    // User-or-LLM params (everything else, can be provided by user OR computed by LLM)
-    query: {
-      type: 'string',
-      required: false,                // Use false for optional
-      visibility: 'user-or-llm',
-      description: 'Search query',
-    },
-  },
-
-  request: {
-    url: (params) => `https://api.service.com/v1/resource/${params.id}`,
-    method: 'POST',
-    headers: (params) => ({
-      Authorization: `Bearer ${params.accessToken}`,
-      'Content-Type': 'application/json',
-    }),
-    body: (params) => ({
-      // Request body - only for POST/PUT/PATCH
-      // Trim ID fields to prevent copy-paste whitespace errors:
-      // userId: params.userId?.trim(),
-    }),
-  },
-
-  transformResponse: async (response: Response) => {
-    const data = await response.json()
-    return {
-      success: true,
-      output: {
-        // Map API response to output
-        // Use ?? null for nullable fields
-        // Use ?? [] for optional arrays
-      },
-    }
-  },
-
-  outputs: {
-    // Define each output field
-  },
-}
-```
-
-## Critical Rules for Parameters
-
-### Visibility Options
-- `'hidden'` - System-injected (OAuth tokens, internal params). User never sees.
-- `'user-only'` - User must provide (credentials, api keys, account-specific IDs)
-- `'user-or-llm'` - User provides OR LLM can compute (search queries, content, filters, most fall into this category)
-
-### Parameter Types
-- `'string'` - Text values
-- `'number'` - Numeric values
-- `'boolean'` - True/false
-- `'json'` - Complex objects (NOT 'object', use 'json')
-- `'file'` - Single file
-- `'file[]'` - Multiple files
-
-### Required vs Optional
-- Always explicitly set `required: true` or `required: false`
-- Optional params should have `required: false`
-
-## Critical Rules for Outputs
-
-### Output Types
-- `'string'`, `'number'`, `'boolean'` - Primitives
-- `'json'` - Complex objects (use this, NOT 'object')
-- `'array'` - Arrays with `items` property
-- `'object'` - Objects with `properties` property
-
-### Optional Outputs
-Add `optional: true` for fields that may not exist in the response:
-```typescript
-closedAt: {
-  type: 'string',
-  description: 'When the issue was closed',
-  optional: true,
-},
-```
-
-### Typed JSON Outputs
-
-When using `type: 'json'` and you know the object shape in advance, **always define the inner structure** using `properties` so downstream consumers know what fields are available:
-
-```typescript
-// BAD: Opaque json with no info about what's inside
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-},
-
-// GOOD: Define the known properties
-metadata: {
-  type: 'json',
-  description: 'Response metadata',
-  properties: {
-    id: { type: 'string', description: 'Unique ID' },
-    status: { type: 'string', description: 'Current status' },
-    count: { type: 'number', description: 'Total count' },
-  },
-},
-```
-
-For arrays of objects, define the item structure:
-```typescript
-items: {
-  type: 'array',
-  description: 'List of items',
-  items: {
-    type: 'object',
-    properties: {
-      id: { type: 'string', description: 'Item ID' },
-      name: { type: 'string', description: 'Item name' },
-    },
-  },
-},
-```
-
-Only use bare `type: 'json'` without `properties` when the shape is truly dynamic or unknown.
-
-## Critical Rules for transformResponse
-
-### Handle Nullable Fields
-ALWAYS use `?? null` for fields that may be undefined:
-```typescript
-transformResponse: async (response: Response) => {
-  const data = await response.json()
-  return {
-    success: true,
-    output: {
-      id: data.id,
-      title: data.title,
-      body: data.body ?? null,           // May be undefined
-      assignee: data.assignee ?? null,   // May be undefined
-      labels: data.labels ?? [],         // Default to empty array
-      closedAt: data.closed_at ?? null,  // May be undefined
-    },
-  }
-}
-```
-
-### Never Output Raw JSON Dumps
-DON'T do this:
-```typescript
-output: {
-  data: data,  // BAD - raw JSON dump
-}
-```
-
-DO this instead - extract meaningful fields:
-```typescript
-output: {
-  id: data.id,
-  name: data.name,
-  status: data.status,
-  metadata: {
-    createdAt: data.created_at,
-    updatedAt: data.updated_at,
-  },
-}
-```
-
-## Types File Pattern
-
-Create `types.ts` with interfaces for all params and responses:
-
-```typescript
-import type { ToolResponse } from '@/tools/types'
-
-// Parameter interfaces
-export interface {Service}{Action}Params {
-  accessToken: string
-  requiredField: string
-  optionalField?: string
-}
-
-// Response interfaces (extend ToolResponse)
-export interface {Service}{Action}Response extends ToolResponse {
-  output: {
-    field1: string
-    field2: number
-    optionalField?: string | null
-  }
-}
-```
-
-## Index.ts Barrel Export Pattern
-
-```typescript
-// Export all tools
-export { serviceTool1 } from './{action1}'
-export { serviceTool2 } from './{action2}'
-
-// Export types
-export * from './types'
-```
-
-## Registering Tools
-
-After creating tools, remind the user to:
-1. Import tools in `apps/sim/tools/registry.ts`
-2. Add to the `tools` object with snake_case keys:
-```typescript
-import { serviceActionTool } from '@/tools/{service}'
-
-export const tools = {
-  // ... existing tools ...
-  {service}_{action}: serviceActionTool,
-}
-```
-
-## V2 Tool Pattern
-
-If creating V2 tools (API-aligned outputs), use `_v2` suffix:
-- Tool ID: `{service}_{action}_v2`
-- Variable name: `{action}V2Tool`
-- Version: `'2.0.0'`
-- Outputs: Flat, API-aligned (no content/metadata wrapper)
-
-## Naming Convention
-
-All tool IDs MUST use `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`). Never use camelCase or PascalCase for tool IDs.
-
-## Checklist Before Finishing
-
-- [ ] All tool IDs use snake_case
-- [ ] All params have explicit `required: true` or `required: false`
-- [ ] All params have appropriate `visibility`
-- [ ] All nullable response fields use `?? null`
-- [ ] All optional outputs have `optional: true`
-- [ ] No raw JSON dumps in outputs
-- [ ] Types file has all interfaces
-- [ ] Index.ts exports all tools
-
-## Final Validation (Required)
-
-After creating all tools, you MUST validate every tool before finishing:
-
-1. **Read every tool file** you created — do not skip any
-2. **Cross-reference with the API docs** to verify:
-   - All required params are marked `required: true`
-   - All optional params are marked `required: false`
-   - Param types match the API (string, number, boolean, json)
-   - Request URL, method, headers, and body match the API spec
-   - `transformResponse` extracts the correct fields from the API response
-   - All output fields match what the API actually returns
-   - No fields are missing from outputs that the API provides
-   - No extra fields are defined in outputs that the API doesn't return
-3. **Verify consistency** across tools:
-   - Shared types in `types.ts` match all tools that use them
-   - Tool IDs in the barrel export match the tool file definitions
-   - Error handling is consistent (error checks, meaningful messages)

.agents/skills/add-tools/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Tools"
-  short_description: "Build Sim tools from API docs"
-  brand_color: "#EA580C"
-  default_prompt: "Use $add-tools to create or update Sim tool definitions from service API docs."

.agents/skills/add-trigger/SKILL.md

@@ -1,708 +0,0 @@
----
-name: add-trigger
-description: Create or update Sim webhook triggers using the generic trigger builder, service-specific setup instructions, outputs, and registry wiring. Use when working in `apps/sim/triggers/{service}/` or adding webhook support to an integration.
----
-
-# Add Trigger Skill
-
-You are an expert at creating webhook triggers for Sim. You understand the trigger system, the generic `buildTriggerSubBlocks` helper, and how triggers connect to blocks.
-
-## Your Task
-
-When the user asks you to create triggers for a service:
-1. Research what webhook events the service supports
-2. Create the trigger files using the generic builder
-3. Register triggers and connect them to the block
-
-## Directory Structure
-
-```
-apps/sim/triggers/{service}/
-├── index.ts              # Barrel exports
-├── utils.ts              # Service-specific helpers (trigger options, setup instructions, extra fields)
-├── {event_a}.ts          # Primary trigger (includes dropdown)
-├── {event_b}.ts          # Secondary trigger (no dropdown)
-├── {event_c}.ts          # Secondary trigger (no dropdown)
-└── webhook.ts            # Generic webhook trigger (optional, for "all events")
-```
-
-## Step 1: Create utils.ts
-
-This file contains service-specific helpers used by all triggers.
-
-```typescript
-import type { SubBlockConfig } from '@/blocks/types'
-import type { TriggerOutput } from '@/triggers/types'
-
-/**
- * Dropdown options for the trigger type selector.
- * These appear in the primary trigger's dropdown.
- */
-export const {service}TriggerOptions = [
-  { label: 'Event A', id: '{service}_event_a' },
-  { label: 'Event B', id: '{service}_event_b' },
-  { label: 'Event C', id: '{service}_event_c' },
-  { label: 'Generic Webhook (All Events)', id: '{service}_webhook' },
-]
-
-/**
- * Generates HTML setup instructions for the trigger.
- * Displayed to users to help them configure webhooks in the external service.
- */
-export function {service}SetupInstructions(eventType: string): string {
-  const instructions = [
-    'Copy the <strong>Webhook URL</strong> above',
-    'Go to <strong>{Service} Settings > Webhooks</strong>',
-    'Click <strong>Add Webhook</strong>',
-    'Paste the webhook URL',
-    `Select the <strong>${eventType}</strong> event type`,
-    'Save the webhook configuration',
-    'Click "Save" above to activate your trigger',
-  ]
-
-  return instructions
-    .map((instruction, index) =>
-      `<div class="mb-3"><strong>${index + 1}.</strong> ${instruction}</div>`
-    )
-    .join('')
-}
-
-/**
- * Service-specific extra fields to add to triggers.
- * These are inserted between webhookUrl and triggerSave.
- */
-export function build{Service}ExtraFields(triggerId: string): SubBlockConfig[] {
-  return [
-    {
-      id: 'projectId',
-      title: 'Project ID (Optional)',
-      type: 'short-input',
-      placeholder: 'Leave empty for all projects',
-      description: 'Optionally filter to a specific project',
-      mode: 'trigger',
-      condition: { field: 'selectedTriggerId', value: triggerId },
-    },
-  ]
-}
-
-/**
- * Build outputs for this trigger type.
- * Outputs define what data is available to downstream blocks.
- */
-export function build{Service}Outputs(): Record<string, TriggerOutput> {
-  return {
-    eventType: { type: 'string', description: 'The type of event that triggered this workflow' },
-    resourceId: { type: 'string', description: 'ID of the affected resource' },
-    timestamp: { type: 'string', description: 'When the event occurred (ISO 8601)' },
-    // Nested outputs for complex data
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-      status: { type: 'string', description: 'Current status' },
-    },
-    webhook: { type: 'json', description: 'Full webhook payload' },
-  }
-}
-```
-
-## Step 2: Create the Primary Trigger
-
-The **primary trigger** is the first one listed. It MUST include `includeDropdown: true` so users can switch between trigger types.
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import { buildTriggerSubBlocks } from '@/triggers'
-import {
-  build{Service}ExtraFields,
-  build{Service}Outputs,
-  {service}SetupInstructions,
-  {service}TriggerOptions,
-} from '@/triggers/{service}/utils'
-import type { TriggerConfig } from '@/triggers/types'
-
-/**
- * {Service} Event A Trigger
- *
- * This is the PRIMARY trigger - it includes the dropdown for selecting trigger type.
- */
-export const {service}EventATrigger: TriggerConfig = {
-  id: '{service}_event_a',
-  name: '{Service} Event A',
-  provider: '{service}',
-  description: 'Trigger workflow when Event A occurs',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_a',
-    triggerOptions: {service}TriggerOptions,
-    includeDropdown: true,  // PRIMARY TRIGGER - includes dropdown
-    setupInstructions: {service}SetupInstructions('Event A'),
-    extraFields: build{Service}ExtraFields('{service}_event_a'),
-  }),
-
-  outputs: build{Service}Outputs(),
-
-  webhook: {
-    method: 'POST',
-    headers: {
-      'Content-Type': 'application/json',
-    },
-  },
-}
-```
-
-## Step 3: Create Secondary Triggers
-
-Secondary triggers do NOT include the dropdown (it's already in the primary trigger).
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import { buildTriggerSubBlocks } from '@/triggers'
-import {
-  build{Service}ExtraFields,
-  build{Service}Outputs,
-  {service}SetupInstructions,
-  {service}TriggerOptions,
-} from '@/triggers/{service}/utils'
-import type { TriggerConfig } from '@/triggers/types'
-
-/**
- * {Service} Event B Trigger
- */
-export const {service}EventBTrigger: TriggerConfig = {
-  id: '{service}_event_b',
-  name: '{Service} Event B',
-  provider: '{service}',
-  description: 'Trigger workflow when Event B occurs',
-  version: '1.0.0',
-  icon: {Service}Icon,
-
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_event_b',
-    triggerOptions: {service}TriggerOptions,
-    // NO includeDropdown - secondary trigger
-    setupInstructions: {service}SetupInstructions('Event B'),
-    extraFields: build{Service}ExtraFields('{service}_event_b'),
-  }),
-
-  outputs: build{Service}Outputs(),
-
-  webhook: {
-    method: 'POST',
-    headers: {
-      'Content-Type': 'application/json',
-    },
-  },
-}
-```
-
-## Step 4: Create index.ts Barrel Export
-
-```typescript
-export { {service}EventATrigger } from './event_a'
-export { {service}EventBTrigger } from './event_b'
-export { {service}EventCTrigger } from './event_c'
-export { {service}WebhookTrigger } from './webhook'
-```
-
-## Step 5: Register Triggers
-
-### Trigger Registry (`apps/sim/triggers/registry.ts`)
-
-```typescript
-// Add import
-import {
-  {service}EventATrigger,
-  {service}EventBTrigger,
-  {service}EventCTrigger,
-  {service}WebhookTrigger,
-} from '@/triggers/{service}'
-
-// Add to TRIGGER_REGISTRY
-export const TRIGGER_REGISTRY: TriggerRegistry = {
-  // ... existing triggers ...
-  {service}_event_a: {service}EventATrigger,
-  {service}_event_b: {service}EventBTrigger,
-  {service}_event_c: {service}EventCTrigger,
-  {service}_webhook: {service}WebhookTrigger,
-}
-```
-
-## Step 6: Connect Triggers to Block
-
-In the block file (`apps/sim/blocks/blocks/{service}.ts`):
-
-```typescript
-import { {Service}Icon } from '@/components/icons'
-import { getTrigger } from '@/triggers'
-import type { BlockConfig } from '@/blocks/types'
-
-export const {Service}Block: BlockConfig = {
-  type: '{service}',
-  name: '{Service}',
-  // ... other config ...
-
-  // Enable triggers and list available trigger IDs
-  triggers: {
-    enabled: true,
-    available: [
-      '{service}_event_a',
-      '{service}_event_b',
-      '{service}_event_c',
-      '{service}_webhook',
-    ],
-  },
-
-  subBlocks: [
-    // Regular tool subBlocks first
-    { id: 'operation', /* ... */ },
-    { id: 'credential', /* ... */ },
-    // ... other tool fields ...
-
-    // Then spread ALL trigger subBlocks
-    ...getTrigger('{service}_event_a').subBlocks,
-    ...getTrigger('{service}_event_b').subBlocks,
-    ...getTrigger('{service}_event_c').subBlocks,
-    ...getTrigger('{service}_webhook').subBlocks,
-  ],
-
-  // ... tools config ...
-}
-```
-
-## Automatic Webhook Registration (Preferred)
-
-If the service's API supports programmatic webhook creation, implement automatic webhook registration instead of requiring users to manually configure webhooks. This provides a much better user experience.
-
-### When to Use Automatic Registration
-
-Check the service's API documentation for endpoints like:
-- `POST /webhooks` or `POST /hooks` - Create webhook
-- `DELETE /webhooks/{id}` - Delete webhook
-
-Services that support this pattern include: Grain, Lemlist, Calendly, Airtable, Webflow, Typeform, etc.
-
-### Implementation Steps
-
-#### 1. Add API Key to Extra Fields
-
-Update your `build{Service}ExtraFields` function to include an API key field:
-
-```typescript
-export function build{Service}ExtraFields(triggerId: string): SubBlockConfig[] {
-  return [
-    {
-      id: 'apiKey',
-      title: 'API Key',
-      type: 'short-input',
-      placeholder: 'Enter your {Service} API key',
-      description: 'Required to create the webhook in {Service}.',
-      password: true,
-      required: true,
-      mode: 'trigger',
-      condition: { field: 'selectedTriggerId', value: triggerId },
-    },
-    // Other optional fields (e.g., campaign filter, project filter)
-    {
-      id: 'projectId',
-      title: 'Project ID (Optional)',
-      type: 'short-input',
-      placeholder: 'Leave empty for all projects',
-      mode: 'trigger',
-      condition: { field: 'selectedTriggerId', value: triggerId },
-    },
-  ]
-}
-```
-
-#### 2. Update Setup Instructions for Automatic Creation
-
-Change instructions to indicate automatic webhook creation:
-
-```typescript
-export function {service}SetupInstructions(eventType: string): string {
-  const instructions = [
-    'Enter your {Service} API Key above.',
-    'You can find your API key in {Service} at <strong>Settings > API</strong>.',
-    `Click <strong>"Save Configuration"</strong> to automatically create the webhook in {Service} for <strong>${eventType}</strong> events.`,
-    'The webhook will be automatically deleted when you remove this trigger.',
-  ]
-
-  return instructions
-    .map((instruction, index) =>
-      `<div class="mb-3"><strong>${index + 1}.</strong> ${instruction}</div>`
-    )
-    .join('')
-}
-```
-
-#### 3. Add Webhook Creation to API Route
-
-In `apps/sim/app/api/webhooks/route.ts`, add provider-specific logic after the database save:
-
-```typescript
-// --- {Service} specific logic ---
-if (savedWebhook && provider === '{service}') {
-  logger.info(`[${requestId}] {Service} provider detected. Creating webhook subscription.`)
-  try {
-    const result = await create{Service}WebhookSubscription(
-      {
-        id: savedWebhook.id,
-        path: savedWebhook.path,
-        providerConfig: savedWebhook.providerConfig,
-      },
-      requestId
-    )
-
-    if (result) {
-      // Update the webhook record with the external webhook ID
-      const updatedConfig = {
-        ...(savedWebhook.providerConfig as Record<string, any>),
-        externalId: result.id,
-      }
-      await db
-        .update(webhook)
-        .set({
-          providerConfig: updatedConfig,
-          updatedAt: new Date(),
-        })
-        .where(eq(webhook.id, savedWebhook.id))
-
-      savedWebhook.providerConfig = updatedConfig
-      logger.info(`[${requestId}] Successfully created {Service} webhook`, {
-        externalHookId: result.id,
-        webhookId: savedWebhook.id,
-      })
-    }
-  } catch (err) {
-    logger.error(
-      `[${requestId}] Error creating {Service} webhook subscription, rolling back webhook`,
-      err
-    )
-    await db.delete(webhook).where(eq(webhook.id, savedWebhook.id))
-    return NextResponse.json(
-      {
-        error: 'Failed to create webhook in {Service}',
-        details: err instanceof Error ? err.message : 'Unknown error',
-      },
-      { status: 500 }
-    )
-  }
-}
-// --- End {Service} specific logic ---
-```
-
-Then add the helper function at the end of the file:
-
-```typescript
-async function create{Service}WebhookSubscription(
-  webhookData: any,
-  requestId: string
-): Promise<{ id: string } | undefined> {
-  try {
-    const { path, providerConfig } = webhookData
-    const { apiKey, triggerId, projectId } = providerConfig || {}
-
-    if (!apiKey) {
-      throw new Error('{Service} API Key is required.')
-    }
-
-    // Map trigger IDs to service event types
-    const eventTypeMap: Record<string, string | undefined> = {
-      {service}_event_a: 'eventA',
-      {service}_event_b: 'eventB',
-      {service}_webhook: undefined, // Generic - no filter
-    }
-
-    const eventType = eventTypeMap[triggerId]
-    const notificationUrl = `${getBaseUrl()}/api/webhooks/trigger/${path}`
-
-    const requestBody: Record<string, any> = {
-      url: notificationUrl,
-    }
-
-    if (eventType) {
-      requestBody.eventType = eventType
-    }
-
-    if (projectId) {
-      requestBody.projectId = projectId
-    }
-
-    const response = await fetch('https://api.{service}.com/webhooks', {
-      method: 'POST',
-      headers: {
-        Authorization: `Bearer ${apiKey}`,
-        'Content-Type': 'application/json',
-      },
-      body: JSON.stringify(requestBody),
-    })
-
-    const responseBody = await response.json()
-
-    if (!response.ok) {
-      const errorMessage = responseBody.message || 'Unknown API error'
-      let userFriendlyMessage = 'Failed to create webhook in {Service}'
-
-      if (response.status === 401) {
-        userFriendlyMessage = 'Invalid API Key. Please verify and try again.'
-      } else if (errorMessage) {
-        userFriendlyMessage = `{Service} error: ${errorMessage}`
-      }
-
-      throw new Error(userFriendlyMessage)
-    }
-
-    return { id: responseBody.id }
-  } catch (error: any) {
-    logger.error(`Exception during {Service} webhook creation`, { error: error.message })
-    throw error
-  }
-}
-```
-
-#### 4. Add Webhook Deletion to Provider Subscriptions
-
-In `apps/sim/lib/webhooks/provider-subscriptions.ts`:
-
-1. Add a logger:
-```typescript
-const {service}Logger = createLogger('{Service}Webhook')
-```
-
-2. Add the delete function:
-```typescript
-export async function delete{Service}Webhook(webhook: any, requestId: string): Promise<void> {
-  try {
-    const config = getProviderConfig(webhook)
-    const apiKey = config.apiKey as string | undefined
-    const externalId = config.externalId as string | undefined
-
-    if (!apiKey || !externalId) {
-      {service}Logger.warn(`[${requestId}] Missing apiKey or externalId, skipping cleanup`)
-      return
-    }
-
-    const response = await fetch(`https://api.{service}.com/webhooks/${externalId}`, {
-      method: 'DELETE',
-      headers: {
-        Authorization: `Bearer ${apiKey}`,
-      },
-    })
-
-    if (!response.ok && response.status !== 404) {
-      {service}Logger.warn(`[${requestId}] Failed to delete webhook (non-fatal): ${response.status}`)
-    } else {
-      {service}Logger.info(`[${requestId}] Successfully deleted webhook ${externalId}`)
-    }
-  } catch (error) {
-    {service}Logger.warn(`[${requestId}] Error deleting webhook (non-fatal)`, error)
-  }
-}
-```
-
-3. Add to `cleanupExternalWebhook`:
-```typescript
-export async function cleanupExternalWebhook(...): Promise<void> {
-  // ... existing providers ...
-  } else if (webhook.provider === '{service}') {
-    await delete{Service}Webhook(webhook, requestId)
-  }
-}
-```
-
-### Key Points for Automatic Registration
-
-- **API Key visibility**: Always use `password: true` for API key fields
-- **Error handling**: Roll back the database webhook if external creation fails
-- **External ID storage**: Save the external webhook ID in `providerConfig.externalId`
-- **Graceful cleanup**: Don't fail webhook deletion if cleanup fails (use non-fatal logging)
-- **User-friendly errors**: Map HTTP status codes to helpful error messages
-
-## The buildTriggerSubBlocks Helper
-
-This is the generic helper from `@/triggers` that creates consistent trigger subBlocks.
-
-### Function Signature
-
-```typescript
-interface BuildTriggerSubBlocksOptions {
-  triggerId: string                              // e.g., 'service_event_a'
-  triggerOptions: Array<{ label: string; id: string }>  // Dropdown options
-  includeDropdown?: boolean                      // true only for primary trigger
-  setupInstructions: string                      // HTML instructions
-  extraFields?: SubBlockConfig[]                 // Service-specific fields
-  webhookPlaceholder?: string                    // Custom placeholder text
-}
-
-function buildTriggerSubBlocks(options: BuildTriggerSubBlocksOptions): SubBlockConfig[]
-```
-
-### What It Creates
-
-The helper creates this structure:
-1. **Dropdown** (only if `includeDropdown: true`) - Trigger type selector
-2. **Webhook URL** - Read-only field with copy button
-3. **Extra Fields** - Your service-specific fields (filters, options, etc.)
-4. **Save Button** - Activates the trigger
-5. **Instructions** - Setup guide for users
-
-All fields automatically have:
-- `mode: 'trigger'` - Only shown in trigger mode
-- `condition: { field: 'selectedTriggerId', value: triggerId }` - Only shown when this trigger is selected
-
-## Trigger Outputs & Webhook Input Formatting
-
-### Important: Two Sources of Truth
-
-There are two related but separate concerns:
-
-1. **Trigger `outputs`** - Schema/contract defining what fields SHOULD be available. Used by UI for tag dropdown.
-2. **`formatWebhookInput`** - Implementation that transforms raw webhook payload into actual data. Located in `apps/sim/lib/webhooks/utils.server.ts`.
-
-**These MUST be aligned.** The fields returned by `formatWebhookInput` should match what's defined in trigger `outputs`. If they differ:
-- Tag dropdown shows fields that don't exist (broken variable resolution)
-- Or actual data has fields not shown in dropdown (users can't discover them)
-
-### When to Add a formatWebhookInput Handler
-
-- **Simple providers**: If the raw webhook payload structure already matches your outputs, you don't need a handler. The generic fallback returns `body` directly.
-- **Complex providers**: If you need to transform, flatten, extract nested data, compute fields, or handle conditional logic, add a handler.
-
-### Adding a Handler
-
-In `apps/sim/lib/webhooks/utils.server.ts`, add a handler block:
-
-```typescript
-if (foundWebhook.provider === '{service}') {
-  // Transform raw webhook body to match trigger outputs
-  return {
-    eventType: body.type,
-    resourceId: body.data?.id || '',
-    timestamp: body.created_at,
-    resource: body.data,
-  }
-}
-```
-
-**Key rules:**
-- Return fields that match your trigger `outputs` definition exactly
-- No wrapper objects like `webhook: { data: ... }` or `{service}: { ... }`
-- No duplication (don't spread body AND add individual fields)
-- Use `null` for missing optional data, not empty objects with empty strings
-
-### Verify Alignment
-
-Run the alignment checker:
-```bash
-bunx scripts/check-trigger-alignment.ts {service}
-```
-
-## Trigger Outputs
-
-Trigger outputs use the same schema as block outputs (NOT tool outputs).
-
-**Supported:**
-- `type` and `description` for simple fields
-- Nested object structure for complex data
-
-**NOT Supported:**
-- `optional: true` (tool outputs only)
-- `items` property (tool outputs only)
-
-```typescript
-export function buildOutputs(): Record<string, TriggerOutput> {
-  return {
-    // Simple fields
-    eventType: { type: 'string', description: 'Event type' },
-    timestamp: { type: 'string', description: 'When it occurred' },
-
-    // Complex data - use type: 'json'
-    payload: { type: 'json', description: 'Full event payload' },
-
-    // Nested structure
-    resource: {
-      id: { type: 'string', description: 'Resource ID' },
-      name: { type: 'string', description: 'Resource name' },
-    },
-  }
-}
-```
-
-## Generic Webhook Trigger Pattern
-
-For services with many event types, create a generic webhook that accepts all events:
-
-```typescript
-export const {service}WebhookTrigger: TriggerConfig = {
-  id: '{service}_webhook',
-  name: '{Service} Webhook (All Events)',
-  // ...
-
-  subBlocks: buildTriggerSubBlocks({
-    triggerId: '{service}_webhook',
-    triggerOptions: {service}TriggerOptions,
-    setupInstructions: {service}SetupInstructions('All Events'),
-    extraFields: [
-      // Event type filter (optional)
-      {
-        id: 'eventTypes',
-        title: 'Event Types',
-        type: 'dropdown',
-        multiSelect: true,
-        options: [
-          { label: 'Event A', id: 'event_a' },
-          { label: 'Event B', id: 'event_b' },
-        ],
-        placeholder: 'Leave empty for all events',
-        mode: 'trigger',
-        condition: { field: 'selectedTriggerId', value: '{service}_webhook' },
-      },
-      // Plus any other service-specific fields
-      ...build{Service}ExtraFields('{service}_webhook'),
-    ],
-  }),
-}
-```
-
-## Checklist Before Finishing
-
-### Utils
-- [ ] Created `{service}TriggerOptions` array with all trigger IDs
-- [ ] Created `{service}SetupInstructions` function with clear steps
-- [ ] Created `build{Service}ExtraFields` for service-specific fields
-- [ ] Created output builders for each trigger type
-
-### Triggers
-- [ ] Primary trigger has `includeDropdown: true`
-- [ ] Secondary triggers do NOT have `includeDropdown`
-- [ ] All triggers use `buildTriggerSubBlocks` helper
-- [ ] All triggers have proper outputs defined
-- [ ] Created `index.ts` barrel export
-
-### Registration
-- [ ] All triggers imported in `triggers/registry.ts`
-- [ ] All triggers added to `TRIGGER_REGISTRY`
-- [ ] Block has `triggers.enabled: true`
-- [ ] Block has all trigger IDs in `triggers.available`
-- [ ] Block spreads all trigger subBlocks: `...getTrigger('id').subBlocks`
-
-### Automatic Webhook Registration (if supported)
-- [ ] Added API key field to `build{Service}ExtraFields` with `password: true`
-- [ ] Updated setup instructions for automatic webhook creation
-- [ ] Added provider-specific logic to `apps/sim/app/api/webhooks/route.ts`
-- [ ] Added `create{Service}WebhookSubscription` helper function
-- [ ] Added `delete{Service}Webhook` function to `provider-subscriptions.ts`
-- [ ] Added provider to `cleanupExternalWebhook` function
-
-### Webhook Input Formatting
-- [ ] Added handler in `apps/sim/lib/webhooks/utils.server.ts` (if custom formatting needed)
-- [ ] Handler returns fields matching trigger `outputs` exactly
-- [ ] Run `bunx scripts/check-trigger-alignment.ts {service}` to verify alignment
-
-### Testing
-- [ ] Run `bun run type-check` to verify no TypeScript errors
-- [ ] Restart dev server to pick up new triggers
-- [ ] Test trigger UI shows correctly in the block
-- [ ] Test automatic webhook creation works (if applicable)

.agents/skills/add-trigger/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Add Trigger"
-  short_description: "Build Sim webhook triggers"
-  brand_color: "#DC2626"
-  default_prompt: "Use $add-trigger to create or update webhook triggers for a Sim integration."

.agents/skills/validate-connector/SKILL.md

@@ -1,333 +0,0 @@
----
-name: validate-connector
-description: Audit an existing Sim knowledge base connector against the service API docs and repository conventions, then report and fix issues in auth, config fields, pagination, document mapping, tags, and registry entries. Use when validating or repairing code in `apps/sim/connectors/{service}/`.
----
-
-# Validate Connector Skill
-
-You are an expert auditor for Sim knowledge base connectors. Your job is to thoroughly validate that an existing connector is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate a connector:
-1. Read the service's API documentation (via Context7 or WebFetch)
-2. Read the connector implementation, OAuth config, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the connector — do not skip any:
-
-```
-apps/sim/connectors/{service}/{service}.ts   # Connector implementation
-apps/sim/connectors/{service}/index.ts       # Barrel export
-apps/sim/connectors/registry.ts              # Connector registry entry
-apps/sim/connectors/types.ts                 # ConnectorConfig interface, ExternalDocument, etc.
-apps/sim/connectors/utils.ts                 # Shared utilities (computeContentHash, htmlToPlainText, etc.)
-apps/sim/lib/oauth/oauth.ts                  # OAUTH_PROVIDERS — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts                  # getCanonicalScopesForProvider, getScopesForService, SCOPE_DESCRIPTIONS
-apps/sim/lib/oauth/types.ts                  # OAuthService union type
-apps/sim/components/icons.tsx                 # Icon definition for the service
-```
-
-If the connector uses selectors, also read:
-```
-apps/sim/hooks/selectors/registry.ts         # Selector key definitions
-apps/sim/hooks/selectors/types.ts            # SelectorKey union type
-apps/sim/lib/workflows/subblocks/context.ts  # SELECTOR_CONTEXT_FIELDS
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (cursor, offset, next token)
-- Rate limits and error formats
-- OAuth scopes and their meanings
-
-Use Context7 (resolve-library-id → query-docs) or WebFetch to retrieve documentation. If both fail, note which claims are based on training knowledge vs verified docs.
-
-## Step 3: Validate API Endpoints
-
-For **every** API call in the connector (`listDocuments`, `getDocument`, `validateConfig`, and any helper functions), verify against the API docs:
-
-### URLs and Methods
-- [ ] Base URL is correct for the service's API version
-- [ ] Endpoint paths match the API docs exactly
-- [ ] HTTP method is correct (GET, POST, PUT, PATCH, DELETE)
-- [ ] Path parameters are correctly interpolated and URI-encoded where needed
-- [ ] Query parameters use correct names and formats per the API docs
-
-### Headers
-- [ ] Authorization header uses the correct format:
-  - OAuth: `Authorization: Bearer ${accessToken}`
-  - API Key: correct header name per the service's docs
-- [ ] `Content-Type` is set for POST/PUT/PATCH requests
-- [ ] Any service-specific headers are present (e.g., `Notion-Version`, `Dropbox-API-Arg`)
-- [ ] No headers are sent that the API doesn't support or silently ignores
-
-### Request Bodies
-- [ ] POST/PUT body fields match API parameter names exactly
-- [ ] Required fields are always sent
-- [ ] Optional fields are conditionally included (not sent as `null` or empty unless the API expects that)
-- [ ] Field value types match API expectations (string vs number vs boolean)
-
-### Input Sanitization
-- [ ] User-controlled values interpolated into query strings are properly escaped:
-  - OData `$filter`: single quotes escaped with `''` (e.g., `externalId.replace(/'/g, "''")`)
-  - SOQL: single quotes escaped with `\'`
-  - GraphQL variables: passed as variables, not interpolated into query strings
-  - URL path segments: `encodeURIComponent()` applied
-- [ ] URL-type config fields (e.g., `siteUrl`, `instanceUrl`) are normalized:
-  - Strip `https://` / `http://` prefix if the API expects bare domains
-  - Strip trailing `/`
-  - Apply `.trim()` before validation
-
-### Response Parsing
-- [ ] Response structure is correctly traversed (e.g., `data.results` vs `data.items` vs `data`)
-- [ ] Field names extracted match what the API actually returns
-- [ ] Nullable fields are handled with `?? null` or `|| undefined`
-- [ ] Error responses are checked before accessing data fields
-
-## Step 4: Validate OAuth Scopes (if OAuth connector)
-
-Scopes must be correctly declared and sufficient for all API calls the connector makes.
-
-### Connector requiredScopes
-- [ ] `requiredScopes` in the connector's `auth` config lists all scopes needed by the connector
-- [ ] Each scope in `requiredScopes` is a real, valid scope recognized by the service's API
-- [ ] No invalid, deprecated, or made-up scopes are listed
-- [ ] No unnecessary excess scopes beyond what the connector actually needs
-
-### Scope Subset Validation (CRITICAL)
-- [ ] Every scope in `requiredScopes` exists in the OAuth provider's `scopes` array in `lib/oauth/oauth.ts`
-- [ ] Find the provider in `OAUTH_PROVIDERS[providerGroup].services[serviceId].scopes`
-- [ ] Verify: `requiredScopes` ⊆ `OAUTH_PROVIDERS scopes` (every required scope is present in the provider config)
-- [ ] If a required scope is NOT in the provider config, flag as **critical** — the connector will fail at runtime
-
-### Scope Sufficiency
-For each API endpoint the connector calls:
-- [ ] Identify which scopes are required per the API docs
-- [ ] Verify those scopes are included in the connector's `requiredScopes`
-- [ ] If the connector calls endpoints requiring scopes not in `requiredScopes`, flag as **warning**
-
-### Token Refresh Config
-- [ ] Check the `getOAuthTokenRefreshConfig` function in `lib/oauth/oauth.ts` for this provider
-- [ ] `useBasicAuth` matches the service's token exchange requirements
-- [ ] `supportsRefreshTokenRotation` matches whether the service issues rotating refresh tokens
-- [ ] Token endpoint URL is correct
-
-## Step 5: Validate Pagination
-
-### listDocuments Pagination
-- [ ] Cursor/pagination parameter name matches the API docs
-- [ ] Response pagination field is correctly extracted (e.g., `next_cursor`, `nextPageToken`, `@odata.nextLink`, `offset`)
-- [ ] `hasMore` is correctly determined from the response
-- [ ] `nextCursor` is correctly passed back for the next page
-- [ ] `maxItems` / `maxRecords` cap is correctly applied across pages using `syncContext.totalDocsFetched`
-- [ ] Page size is within the API's allowed range (not exceeding max page size)
-- [ ] Last page precision: when a `maxItems` cap exists, the final page request uses `Math.min(PAGE_SIZE, remaining)` to avoid fetching more records than needed
-- [ ] No off-by-one errors in pagination tracking
-- [ ] The connector does NOT hit known API pagination limits silently (e.g., HubSpot search 10k cap)
-
-### Pagination State Across Pages
-- [ ] `syncContext` is used to cache state across pages (user names, field maps, instance URLs, portal IDs, etc.)
-- [ ] Cached state in `syncContext` is correctly initialized on first page and reused on subsequent pages
-
-## Step 6: Validate Data Transformation
-
-### Content Deferral (CRITICAL)
-Connectors that require per-document API calls to fetch content (file download, export, blocks fetch) MUST use `contentDeferred: true`. This is the standard pattern for reliability — without it, content downloads during listing can exhaust the sync task's time budget before any documents are saved.
-
-- [ ] If the connector downloads content per-doc during `listDocuments`, it MUST use `contentDeferred: true` instead
-- [ ] `listDocuments` returns lightweight stubs with `content: ''` and `contentDeferred: true`
-- [ ] `getDocument` fetches actual content and returns the full document with `contentDeferred: false`
-- [ ] A shared stub function (e.g., `fileToStub`) is used by both `listDocuments` and `getDocument` to guarantee `contentHash` consistency
-- [ ] `contentHash` is metadata-based (e.g., `service:{id}:{modifiedTime}`), NOT content-based — it must be derivable from list metadata alone
-- [ ] The `contentHash` is identical whether produced by `listDocuments` or `getDocument`
-
-Connectors where the list API already returns content inline (e.g., Slack messages, Reddit posts) do NOT need `contentDeferred`.
-
-### ExternalDocument Construction
-- [ ] `externalId` is a stable, unique identifier from the source API
-- [ ] `title` is extracted from the correct field and has a sensible fallback (e.g., `'Untitled'`)
-- [ ] `content` is plain text — HTML content is stripped using `htmlToPlainText` from `@/connectors/utils`
-- [ ] `mimeType` is `'text/plain'`
-- [ ] `contentHash` uses a metadata-based format (e.g., `service:{id}:{modifiedTime}`) for connectors with `contentDeferred: true`, or `computeContentHash` from `@/connectors/utils` for inline-content connectors
-- [ ] `sourceUrl` is a valid, complete URL back to the original resource (not relative)
-- [ ] `metadata` contains all fields referenced by `mapTags` and `tagDefinitions`
-
-### Content Extraction
-- [ ] Rich text / HTML fields are converted to plain text before indexing
-- [ ] Important content is not silently dropped (e.g., nested blocks, table cells, code blocks)
-- [ ] Content is not silently truncated without logging a warning
-- [ ] Empty/blank documents are properly filtered out
-- [ ] Size checks use `Buffer.byteLength(text, 'utf8')` not `text.length` when comparing against byte-based limits (e.g., `MAX_FILE_SIZE` in bytes)
-
-## Step 7: Validate Tag Definitions and mapTags
-
-### tagDefinitions
-- [ ] Each `tagDefinition` has an `id`, `displayName`, and `fieldType`
-- [ ] `fieldType` matches the actual data type: `'text'` for strings, `'number'` for numbers, `'date'` for dates, `'boolean'` for booleans
-- [ ] Every `id` in `tagDefinitions` is returned by `mapTags`
-- [ ] No `tagDefinition` references a field that `mapTags` never produces
-
-### mapTags
-- [ ] Return keys match `tagDefinition` `id` values exactly
-- [ ] Date values are properly parsed using `parseTagDate` from `@/connectors/utils`
-- [ ] Array values are properly joined using `joinTagArray` from `@/connectors/utils`
-- [ ] Number values are validated (not `NaN`)
-- [ ] Metadata field names accessed in `mapTags` match what `listDocuments`/`getDocument` store in `metadata`
-
-## Step 8: Validate Config Fields and Validation
-
-### configFields
-- [ ] Every field has `id`, `title`, `type`
-- [ ] `required` is set explicitly (not omitted)
-- [ ] Dropdown fields have `options` with `label` and `id` for each option
-- [ ] Selector fields follow the canonical pair pattern:
-  - A `type: 'selector'` field with `selectorKey`, `canonicalParamId`, `mode: 'basic'`
-  - A `type: 'short-input'` field with the same `canonicalParamId`, `mode: 'advanced'`
-  - `required` is identical on both fields in the pair
-- [ ] `selectorKey` values exist in the selector registry
-- [ ] `dependsOn` references selector field `id` values, not `canonicalParamId`
-
-### validateConfig
-- [ ] Validates all required fields are present before making API calls
-- [ ] Validates optional numeric fields (checks `Number.isNaN`, positive values)
-- [ ] Makes a lightweight API call to verify access (e.g., fetch 1 record, get profile)
-- [ ] Uses `VALIDATE_RETRY_OPTIONS` for retry budget
-- [ ] Returns `{ valid: true }` on success
-- [ ] Returns `{ valid: false, error: 'descriptive message' }` on failure
-- [ ] Catches exceptions and returns user-friendly error messages
-- [ ] Does NOT make expensive calls (full data listing, large queries)
-
-## Step 9: Validate getDocument
-
-- [ ] Fetches a single document by `externalId`
-- [ ] Returns `null` for 404 / not found (does not throw)
-- [ ] Returns the same `ExternalDocument` shape as `listDocuments`
-- [ ] If `listDocuments` uses `contentDeferred: true`, `getDocument` MUST fetch actual content and return `contentDeferred: false`
-- [ ] If `listDocuments` uses `contentDeferred: true`, `getDocument` MUST use the same stub function to ensure `contentHash` is identical
-- [ ] Handles all content types that `listDocuments` can produce (e.g., if `listDocuments` returns both pages and blogposts, `getDocument` must handle both — not hardcode one endpoint)
-- [ ] Forwards `syncContext` if it needs cached state (user names, field maps, etc.)
-- [ ] Error handling is graceful (catches, logs, returns null or throws with context)
-- [ ] Does not redundantly re-fetch data already included in the initial API response (e.g., if comments come back with the post, don't fetch them again separately)
-
-## Step 10: Validate General Quality
-
-### fetchWithRetry Usage
-- [ ] All external API calls use `fetchWithRetry` from `@/lib/knowledge/documents/utils`
-- [ ] No raw `fetch()` calls to external APIs
-- [ ] `VALIDATE_RETRY_OPTIONS` used in `validateConfig`
-- [ ] If `validateConfig` calls a shared helper (e.g., `linearGraphQL`, `resolveId`), that helper must accept and forward `retryOptions` to `fetchWithRetry`
-- [ ] Default retry options used in `listDocuments`/`getDocument`
-
-### API Efficiency
-- [ ] APIs that support field selection (e.g., `$select`, `sysparm_fields`, `fields`) should request only the fields the connector needs — in both `listDocuments` AND `getDocument`
-- [ ] No redundant API calls: if a helper already fetches data (e.g., site metadata), callers should reuse the result instead of making a second call for the same information
-- [ ] Sequential per-item API calls (fetching details for each document in a loop) should be batched with `Promise.all` and a concurrency limit of 3-5
-
-### Error Handling
-- [ ] Individual document failures are caught and logged without aborting the sync
-- [ ] API error responses include status codes in error messages
-- [ ] No unhandled promise rejections in concurrent operations
-
-### Concurrency
-- [ ] Concurrent API calls use reasonable batch sizes (3-5 is typical)
-- [ ] No unbounded `Promise.all` over large arrays
-
-### Logging
-- [ ] Uses `createLogger` from `@sim/logger` (not `console.log`)
-- [ ] Logs sync progress at `info` level
-- [ ] Logs errors at `warn` or `error` level with context
-
-### Registry
-- [ ] Connector is exported from `connectors/{service}/index.ts`
-- [ ] Connector is registered in `connectors/registry.ts`
-- [ ] Registry key matches the connector's `id` field
-
-## Step 11: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors, data loss, or auth failures):
-- Wrong API endpoint URL or HTTP method
-- Invalid or missing OAuth scopes (not in provider config)
-- Incorrect response field mapping (accessing wrong path)
-- SOQL/query fields that don't exist on the target object
-- Pagination that silently hits undocumented API limits
-- Missing error handling that would crash the sync
-- `requiredScopes` not a subset of OAuth provider scopes
-- Query/filter injection: user-controlled values interpolated into OData `$filter`, SOQL, or query strings without escaping
-- Per-document content download in `listDocuments` without `contentDeferred: true` — causes sync timeouts for large document sets
-- `contentHash` mismatch between `listDocuments` stub and `getDocument` return — causes unnecessary re-processing every sync
-
-**Warning** (incorrect behavior, data quality issues, or convention violations):
-- HTML content not stripped via `htmlToPlainText`
-- `getDocument` not forwarding `syncContext`
-- `getDocument` hardcoded to one content type when `listDocuments` returns multiple (e.g., only pages but not blogposts)
-- Missing `tagDefinition` for metadata fields returned by `mapTags`
-- Incorrect `useBasicAuth` or `supportsRefreshTokenRotation` in token refresh config
-- Invalid scope names that the API doesn't recognize (even if silently ignored)
-- Private resources excluded from name-based lookup despite scopes being available
-- Silent data truncation without logging
-- Size checks using `text.length` (character count) instead of `Buffer.byteLength` (byte count) for byte-based limits
-- URL-type config fields not normalized (protocol prefix, trailing slashes cause API failures)
-- `VALIDATE_RETRY_OPTIONS` not threaded through helper functions called by `validateConfig`
-
-**Suggestion** (minor improvements):
-- Missing incremental sync support despite API supporting it
-- Overly broad scopes that could be narrowed (not wrong, but could be tighter)
-- Source URL format could be more specific
-- Missing `orderBy` for deterministic pagination
-- Redundant API calls that could be cached in `syncContext`
-- Sequential per-item API calls that could be batched with `Promise.all` (concurrency 3-5)
-- API supports field selection but connector fetches all fields (e.g., missing `$select`, `sysparm_fields`, `fields`)
-- `getDocument` re-fetches data already included in the initial API response (e.g., comments returned with post)
-- Last page of pagination requests full `PAGE_SIZE` when fewer records remain (`Math.min(PAGE_SIZE, remaining)`)
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes
-2. TypeScript compiles clean
-3. Re-read all modified files to verify fixes are correct
-
-## Checklist Summary
-
-- [ ] Read connector implementation, types, utils, registry, and OAuth config
-- [ ] Pulled and read official API documentation for the service
-- [ ] Validated every API endpoint URL, method, headers, and body against API docs
-- [ ] Validated input sanitization: no query/filter injection, URL fields normalized
-- [ ] Validated OAuth scopes: `requiredScopes` ⊆ OAuth provider `scopes` in `oauth.ts`
-- [ ] Validated each scope is real and recognized by the service's API
-- [ ] Validated scopes are sufficient for all API endpoints the connector calls
-- [ ] Validated token refresh config (`useBasicAuth`, `supportsRefreshTokenRotation`)
-- [ ] Validated pagination: cursor names, page sizes, hasMore logic, no silent caps
-- [ ] Validated content deferral: `contentDeferred: true` used when per-doc content fetch required, metadata-based `contentHash` consistent between stub and `getDocument`
-- [ ] Validated data transformation: plain text extraction, HTML stripping, content hashing
-- [ ] Validated tag definitions match mapTags output, correct fieldTypes
-- [ ] Validated config fields: canonical pairs, selector keys, required flags
-- [ ] Validated validateConfig: lightweight check, error messages, retry options
-- [ ] Validated getDocument: null on 404, all content types handled, no redundant re-fetches, syncContext forwarding
-- [ ] Validated fetchWithRetry used for all external calls (no raw fetch), VALIDATE_RETRY_OPTIONS threaded through helpers
-- [ ] Validated API efficiency: field selection used, no redundant calls, sequential fetches batched
-- [ ] Validated error handling: graceful failures, no unhandled rejections
-- [ ] Validated logging: createLogger, no console.log
-- [ ] Validated registry: correct export, correct key
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.agents/skills/validate-connector/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Validate Connector"
-  short_description: "Audit a Sim knowledge connector"
-  brand_color: "#059669"
-  default_prompt: "Use $validate-connector to audit and fix a Sim knowledge connector against its API docs."

.agents/skills/validate-integration/SKILL.md

@@ -1,289 +0,0 @@
----
-name: validate-integration
-description: Audit an existing Sim integration against the service API docs and repository conventions, then report and fix issues across tools, blocks, outputs, OAuth scopes, triggers, and registry entries. Use when validating or repairing a service integration under `apps/sim/tools`, `apps/sim/blocks`, or `apps/sim/triggers`.
----
-
-# Validate Integration Skill
-
-You are an expert auditor for Sim integrations. Your job is to thoroughly validate that an existing integration is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate an integration:
-1. Read the service's API documentation (via WebFetch or Context7)
-2. Read every tool, the block, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the integration — do not skip any:
-
-```
-apps/sim/tools/{service}/          # All tool files, types.ts, index.ts
-apps/sim/blocks/blocks/{service}.ts # Block definition
-apps/sim/tools/registry.ts          # Tool registry entries for this service
-apps/sim/blocks/registry.ts         # Block registry entry for this service
-apps/sim/components/icons.tsx        # Icon definition
-apps/sim/lib/auth/auth.ts           # OAuth config — should use getCanonicalScopesForProvider()
-apps/sim/lib/oauth/oauth.ts         # OAuth provider config — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts               # Scope utilities, SCOPE_DESCRIPTIONS for modal UI
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (which param name, which response field)
-- Rate limits and error formats
-
-## Step 3: Validate Tools
-
-For **every** tool file, check:
-
-### Tool ID and Naming
-- [ ] Tool ID uses `snake_case`: `{service}_{action}` (e.g., `x_create_tweet`, `slack_send_message`)
-- [ ] Tool `name` is human-readable (e.g., `'X Create Tweet'`)
-- [ ] Tool `description` is a concise one-liner describing what it does
-- [ ] Tool `version` is set (`'1.0.0'` or `'2.0.0'` for V2)
-
-### Params
-- [ ] All required API params are marked `required: true`
-- [ ] All optional API params are marked `required: false`
-- [ ] Every param has explicit `required: true` or `required: false` — never omitted
-- [ ] Param types match the API (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] Visibility is correct:
-  - `'hidden'` — ONLY for OAuth access tokens and system-injected params
-  - `'user-only'` — for API keys, credentials, and account-specific IDs the user must provide
-  - `'user-or-llm'` — for everything else (search queries, content, filters, IDs that could come from other blocks)
-- [ ] Every param has a `description` that explains what it does
-
-### Request
-- [ ] URL matches the API endpoint exactly (correct base URL, path segments, path params)
-- [ ] HTTP method matches the API spec (GET, POST, PUT, PATCH, DELETE)
-- [ ] Headers include correct auth pattern:
-  - OAuth: `Authorization: Bearer ${params.accessToken}`
-  - API Key: correct header name and format per the service's docs
-- [ ] `Content-Type` header is set for POST/PUT/PATCH requests
-- [ ] Body sends all required fields and only includes optional fields when provided
-- [ ] For GET requests with query params: URL is constructed correctly with query string
-- [ ] ID fields in URL paths are `.trim()`-ed to prevent copy-paste whitespace errors
-- [ ] Path params use template literals correctly: `` `https://api.service.com/v1/${params.id.trim()}` ``
-
-### Response / transformResponse
-- [ ] Correctly parses the API response (`await response.json()`)
-- [ ] Extracts the right fields from the response structure (e.g., `data.data` vs `data` vs `data.results`)
-- [ ] All nullable fields use `?? null`
-- [ ] All optional arrays use `?? []`
-- [ ] Error cases are handled: checks for missing/empty data and returns meaningful error
-- [ ] Does NOT do raw JSON dumps — extracts meaningful, individual fields
-
-### Outputs
-- [ ] All output fields match what the API actually returns
-- [ ] No fields are missing that the API provides and users would commonly need
-- [ ] No phantom fields defined that the API doesn't return
-- [ ] `optional: true` is set on fields that may not exist in all responses
-- [ ] When using `type: 'json'` and the shape is known, `properties` defines the inner fields
-- [ ] When using `type: 'array'`, `items` defines the item structure with `properties`
-- [ ] Field descriptions are accurate and helpful
-
-### Types (types.ts)
-- [ ] Has param interfaces for every tool (e.g., `XCreateTweetParams`)
-- [ ] Has response interfaces for every tool (extending `ToolResponse`)
-- [ ] Optional params use `?` in the interface (e.g., `replyTo?: string`)
-- [ ] Field names in types match actual API field names
-- [ ] Shared response types are properly reused (e.g., `XTweetResponse` shared across tweet tools)
-
-### Barrel Export (index.ts)
-- [ ] Every tool is exported
-- [ ] All types are re-exported (`export * from './types'`)
-- [ ] No orphaned exports (tools that don't exist)
-
-### Tool Registry (tools/registry.ts)
-- [ ] Every tool is imported and registered
-- [ ] Registry keys use snake_case and match tool IDs exactly
-- [ ] Entries are in alphabetical order within the file
-
-## Step 4: Validate Block
-
-### Block ↔ Tool Alignment (CRITICAL)
-
-This is the most important validation — the block must be perfectly aligned with every tool it references.
-
-For **each tool** in `tools.access`:
-- [ ] The operation dropdown has an option whose ID matches the tool ID (or the `tools.config.tool` function correctly maps to it)
-- [ ] Every **required** tool param (except `accessToken`) has a corresponding subBlock input that is:
-  - Shown when that operation is selected (correct `condition`)
-  - Marked as `required: true` (or conditionally required)
-- [ ] Every **optional** tool param has a corresponding subBlock input (or is intentionally omitted if truly never needed)
-- [ ] SubBlock `id` values are unique across the entire block — no duplicates even across different conditions
-- [ ] The `tools.config.tool` function returns the correct tool ID for every possible operation value
-- [ ] The `tools.config.params` function correctly maps subBlock IDs to tool param names when they differ
-
-### SubBlocks
-- [ ] Operation dropdown lists ALL tool operations available in `tools.access`
-- [ ] Dropdown option labels are human-readable and descriptive
-- [ ] Conditions use correct syntax:
-  - Single value: `{ field: 'operation', value: 'x_create_tweet' }`
-  - Multiple values (OR): `{ field: 'operation', value: ['x_create_tweet', 'x_delete_tweet'] }`
-  - Negation: `{ field: 'operation', value: 'delete', not: true }`
-  - Compound: `{ field: 'op', value: 'send', and: { field: 'type', value: 'dm' } }`
-- [ ] Condition arrays include ALL operations that use that field — none missing
-- [ ] `dependsOn` is set for fields that need other values (selectors depending on credential, cascading dropdowns)
-- [ ] SubBlock types match tool param types:
-  - Enum/fixed options → `dropdown`
-  - Free text → `short-input`
-  - Long text/content → `long-input`
-  - True/false → `dropdown` with Yes/No options (not `switch` unless purely UI toggle)
-  - Credentials → `oauth-input` with correct `serviceId`
-- [ ] Dropdown `value: () => 'default'` is set for dropdowns with a sensible default
-
-### Advanced Mode
-- [ ] Optional, rarely-used fields are set to `mode: 'advanced'`:
-  - Pagination tokens / next tokens
-  - Time range filters (start/end time)
-  - Sort order / direction options
-  - Max results / per page limits
-  - Reply settings / threading options
-  - Rarely used IDs (reply-to, quote-tweet, etc.)
-  - Exclude filters
-- [ ] **Required** fields are NEVER set to `mode: 'advanced'`
-- [ ] Fields that users fill in most of the time are NOT set to `mode: 'advanced'`
-
-### WandConfig
-- [ ] Timestamp fields have `wandConfig` with `generationType: 'timestamp'`
-- [ ] Comma-separated list fields have `wandConfig` with a descriptive prompt
-- [ ] Complex filter/query fields have `wandConfig` with format examples in the prompt
-- [ ] All `wandConfig` prompts end with "Return ONLY the [format] - no explanations, no extra text."
-- [ ] `wandConfig.placeholder` describes what to type in natural language
-
-### Tools Config
-- [ ] `tools.access` lists **every** tool ID the block can use — none missing
-- [ ] `tools.config.tool` returns the correct tool ID for each operation
-- [ ] Type coercions are in `tools.config.params` (runs at execution time), NOT in `tools.config.tool` (runs at serialization time before variable resolution)
-- [ ] `tools.config.params` handles:
-  - `Number()` conversion for numeric params that come as strings from inputs
-  - `Boolean` / string-to-boolean conversion for toggle params
-  - Empty string → `undefined` conversion for optional dropdown values
-  - Any subBlock ID → tool param name remapping
-- [ ] No `Number()`, `JSON.parse()`, or other coercions in `tools.config.tool` — these would destroy dynamic references like `<Block.output>`
-
-### Block Outputs
-- [ ] Outputs cover the key fields returned by ALL tools (not just one operation)
-- [ ] Output types are correct (`'string'`, `'number'`, `'boolean'`, `'json'`)
-- [ ] `type: 'json'` outputs either:
-  - Describe inner fields in the description string (GOOD): `'User profile (id, name, username, bio)'`
-  - Use nested output definitions (BEST): `{ id: { type: 'string' }, name: { type: 'string' } }`
-- [ ] No opaque `type: 'json'` with vague descriptions like `'Response data'`
-- [ ] Outputs that only appear for certain operations use `condition` if supported, or document which operations return them
-
-### Block Metadata
-- [ ] `type` is snake_case (e.g., `'x'`, `'cloudflare'`)
-- [ ] `name` is human-readable (e.g., `'X'`, `'Cloudflare'`)
-- [ ] `description` is a concise one-liner
-- [ ] `longDescription` provides detail for docs
-- [ ] `docsLink` points to `'https://docs.sim.ai/tools/{service}'`
-- [ ] `category` is `'tools'`
-- [ ] `bgColor` uses the service's brand color hex
-- [ ] `icon` references the correct icon component from `@/components/icons`
-- [ ] `authMode` is set correctly (`AuthMode.OAuth` or `AuthMode.ApiKey`)
-- [ ] Block is registered in `blocks/registry.ts` alphabetically
-
-### Block Inputs
-- [ ] `inputs` section lists all subBlock params that the block accepts
-- [ ] Input types match the subBlock types
-- [ ] When using `canonicalParamId`, inputs list the canonical ID (not the raw subBlock IDs)
-
-## Step 5: Validate OAuth Scopes (if OAuth service)
-
-Scopes are centralized — the single source of truth is `OAUTH_PROVIDERS` in `lib/oauth/oauth.ts`.
-
-- [ ] Scopes defined in `lib/oauth/oauth.ts` under `OAUTH_PROVIDERS[provider].services[service].scopes`
-- [ ] `auth.ts` uses `getCanonicalScopesForProvider(providerId)` — NOT a hardcoded array
-- [ ] Block `requiredScopes` uses `getScopesForService(serviceId)` — NOT a hardcoded array
-- [ ] No hardcoded scope arrays in `auth.ts` or block files (should all use utility functions)
-- [ ] Each scope has a human-readable description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-- [ ] No excess scopes that aren't needed by any tool
-
-## Step 6: Validate Pagination Consistency
-
-If any tools support pagination:
-- [ ] Pagination param names match the API docs (e.g., `pagination_token` vs `next_token` vs `cursor`)
-- [ ] Different API endpoints that use different pagination param names have separate subBlocks in the block
-- [ ] Pagination response fields (`nextToken`, `cursor`, etc.) are included in tool outputs
-- [ ] Pagination subBlocks are set to `mode: 'advanced'`
-
-## Step 7: Validate Error Handling
-
-- [ ] `transformResponse` checks for error conditions before accessing data
-- [ ] Error responses include meaningful messages (not just generic "failed")
-- [ ] HTTP error status codes are handled (check `response.ok` or status codes)
-
-## Step 8: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors or incorrect behavior):
-- Wrong endpoint URL or HTTP method
-- Missing required params or wrong `required` flag
-- Incorrect response field mapping (accessing wrong path in response)
-- Missing error handling that would cause crashes
-- Tool ID mismatch between tool file, registry, and block `tools.access`
-- OAuth scopes missing in `auth.ts` that tools need
-- `tools.config.tool` returning wrong tool ID for an operation
-- Type coercions in `tools.config.tool` instead of `tools.config.params`
-
-**Warning** (follows conventions incorrectly or has usability issues):
-- Optional field not set to `mode: 'advanced'`
-- Missing `wandConfig` on timestamp/complex fields
-- Wrong `visibility` on params (e.g., `'hidden'` instead of `'user-or-llm'`)
-- Missing `optional: true` on nullable outputs
-- Opaque `type: 'json'` without property descriptions
-- Missing `.trim()` on ID fields in request URLs
-- Missing `?? null` on nullable response fields
-- Block condition array missing an operation that uses that field
-- Hardcoded scope arrays instead of using `getScopesForService()` / `getCanonicalScopesForProvider()`
-- Missing scope description in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts`
-
-**Suggestion** (minor improvements):
-- Better description text
-- Inconsistent naming across tools
-- Missing `longDescription` or `docsLink`
-- Pagination fields that could benefit from `wandConfig`
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes with no fixes needed
-2. TypeScript compiles clean (no type errors)
-3. Re-read all modified files to verify fixes are correct
-
-## Checklist Summary
-
-- [ ] Read ALL tool files, block, types, index, and registries
-- [ ] Pulled and read official API documentation
-- [ ] Validated every tool's ID, params, request, response, outputs, and types against API docs
-- [ ] Validated block ↔ tool alignment (every tool param has a subBlock, every condition is correct)
-- [ ] Validated advanced mode on optional/rarely-used fields
-- [ ] Validated wandConfig on timestamps and complex inputs
-- [ ] Validated tools.config mapping, tool selector, and type coercions
-- [ ] Validated block outputs match what tools return, with typed JSON where possible
-- [ ] Validated OAuth scopes use centralized utilities (getScopesForService, getCanonicalScopesForProvider) — no hardcoded arrays
-- [ ] Validated scope descriptions exist in `SCOPE_DESCRIPTIONS` within `lib/oauth/utils.ts` for all scopes
-- [ ] Validated pagination consistency across tools and block
-- [ ] Validated error handling (error checks, meaningful messages)
-- [ ] Validated registry entries (tools and block, alphabetical, correct imports)
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.agents/skills/validate-integration/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Validate Integration"
-  short_description: "Audit a Sim service integration"
-  brand_color: "#B45309"
-  default_prompt: "Use $validate-integration to audit and fix a Sim integration against its API docs."

.claude/commands/add-block.md

@@ -19,7 +19,7 @@ When the user asks you to create a block:
 ```typescript
 import { {ServiceName}Icon } from '@/components/icons'
 import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
+import { AuthMode } from '@/blocks/types'
 import { getScopesForService } from '@/lib/oauth/utils'
 
 export const {ServiceName}Block: BlockConfig = {
@@ -29,8 +29,6 @@ export const {ServiceName}Block: BlockConfig = {
   longDescription: 'Detailed description for docs',
   docsLink: 'https://docs.sim.ai/tools/{service}',
   category: 'tools',                    // 'tools' | 'blocks' | 'triggers'
-  integrationType: IntegrationType.X,   // Primary category (see IntegrationType enum)
-  tags: ['oauth', 'api'],              // Cross-cutting tags (see IntegrationTag type)
   bgColor: '#HEXCOLOR',                 // Brand color
   icon: {ServiceName}Icon,
 
@@ -631,7 +629,7 @@ export const registry: Record<string, BlockConfig> = {
 ```typescript
 import { ServiceIcon } from '@/components/icons'
 import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
+import { AuthMode } from '@/blocks/types'
 import { getScopesForService } from '@/lib/oauth/utils'
 
 export const ServiceBlock: BlockConfig = {
@@ -641,8 +639,6 @@ export const ServiceBlock: BlockConfig = {
   longDescription: 'Full description for documentation...',
   docsLink: 'https://docs.sim.ai/tools/service',
   category: 'tools',
-  integrationType: IntegrationType.DeveloperTools,
-  tags: ['oauth', 'api'],
   bgColor: '#FF6B6B',
   icon: ServiceIcon,
   authMode: AuthMode.OAuth,
@@ -800,8 +796,6 @@ All tool IDs referenced in `tools.access` and returned by `tools.config.tool` MU
 
 ## Checklist Before Finishing
 
-- [ ] `integrationType` is set to the correct `IntegrationType` enum value
-- [ ] `tags` array includes all applicable `IntegrationTag` values
 - [ ] All subBlocks have `id`, `title` (except switch), and `type`
 - [ ] Conditions use correct syntax (field, value, not, and)
 - [ ] DependsOn set for fields that need other values

.claude/commands/add-connector.md

@@ -117,8 +117,6 @@ export const {service}Connector: ConnectorConfig = {
 
 The add-connector modal renders these automatically — no custom UI needed.
 
-Three field types are supported: `short-input`, `dropdown`, and `selector`.
-
 ```typescript
 // Text input
 {
@@ -143,136 +141,6 @@ Three field types are supported: `short-input`, `dropdown`, and `selector`.
 }
 ```
 
-## Dynamic Selectors (Canonical Pairs)
-
-Use `type: 'selector'` to fetch options dynamically from the existing selector registry (`hooks/selectors/registry.ts`). Selectors are always paired with a manual fallback input using the **canonical pair** pattern — a `selector` field (basic mode) and a `short-input` field (advanced mode) linked by `canonicalParamId`.
-
-The user sees a toggle button (ArrowLeftRight) to switch between the selector dropdown and manual text input. On submit, the modal resolves each canonical pair to the active mode's value, keyed by `canonicalParamId`.
-
-### Rules
-
-1. **Every selector field MUST have a canonical pair** — a corresponding `short-input` (or `dropdown`) field with the same `canonicalParamId` and `mode: 'advanced'`.
-2. **`required` must be set identically on both fields** in a pair. If the selector is required, the manual input must also be required.
-3. **`canonicalParamId` must match the key the connector expects in `sourceConfig`** (e.g. `baseId`, `channel`, `teamId`). The advanced field's `id` should typically match `canonicalParamId`.
-4. **`dependsOn` references the selector field's `id`**, not the `canonicalParamId`. The modal propagates dependency clearing across canonical siblings automatically — changing either field in a parent pair clears dependent children.
-
-### Selector canonical pair example (Airtable base → table cascade)
-
-```typescript
-configFields: [
-  // Base: selector (basic) + manual (advanced)
-  {
-    id: 'baseSelector',
-    title: 'Base',
-    type: 'selector',
-    selectorKey: 'airtable.bases',     // Must exist in hooks/selectors/registry.ts
-    canonicalParamId: 'baseId',
-    mode: 'basic',
-    placeholder: 'Select a base',
-    required: true,
-  },
-  {
-    id: 'baseId',
-    title: 'Base ID',
-    type: 'short-input',
-    canonicalParamId: 'baseId',
-    mode: 'advanced',
-    placeholder: 'e.g. appXXXXXXXXXXXXXX',
-    required: true,
-  },
-  // Table: selector depends on base (basic) + manual (advanced)
-  {
-    id: 'tableSelector',
-    title: 'Table',
-    type: 'selector',
-    selectorKey: 'airtable.tables',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'basic',
-    dependsOn: ['baseSelector'],       // References the selector field ID
-    placeholder: 'Select a table',
-    required: true,
-  },
-  {
-    id: 'tableIdOrName',
-    title: 'Table Name or ID',
-    type: 'short-input',
-    canonicalParamId: 'tableIdOrName',
-    mode: 'advanced',
-    placeholder: 'e.g. Tasks',
-    required: true,
-  },
-  // Non-selector fields stay as-is
-  { id: 'maxRecords', title: 'Max Records', type: 'short-input', ... },
-]
-```
-
-### Selector with domain dependency (Jira/Confluence pattern)
-
-When a selector depends on a plain `short-input` field (no canonical pair), `dependsOn` references that field's `id` directly. The `domain` field's value maps to `SelectorContext.domain` automatically via `SELECTOR_CONTEXT_FIELDS`.
-
-```typescript
-configFields: [
-  {
-    id: 'domain',
-    title: 'Jira Domain',
-    type: 'short-input',
-    placeholder: 'yoursite.atlassian.net',
-    required: true,
-  },
-  {
-    id: 'projectSelector',
-    title: 'Project',
-    type: 'selector',
-    selectorKey: 'jira.projects',
-    canonicalParamId: 'projectKey',
-    mode: 'basic',
-    dependsOn: ['domain'],
-    placeholder: 'Select a project',
-    required: true,
-  },
-  {
-    id: 'projectKey',
-    title: 'Project Key',
-    type: 'short-input',
-    canonicalParamId: 'projectKey',
-    mode: 'advanced',
-    placeholder: 'e.g. ENG, PROJ',
-    required: true,
-  },
-]
-```
-
-### How `dependsOn` maps to `SelectorContext`
-
-The connector selector field builds a `SelectorContext` from dependency values. For the mapping to work, each dependency's `canonicalParamId` (or field `id` for non-canonical fields) must exist in `SELECTOR_CONTEXT_FIELDS` (`lib/workflows/subblocks/context.ts`):
-
-```
-oauthCredential, domain, teamId, projectId, knowledgeBaseId, planId,
-siteId, collectionId, spreadsheetId, fileId, baseId, datasetId, serviceDeskId
-```
-
-### Available selector keys
-
-Check `hooks/selectors/types.ts` for the full `SelectorKey` union. Common ones for connectors:
-
-| SelectorKey | Context Deps | Returns |
-|-------------|-------------|---------|
-| `airtable.bases` | credential | Base ID + name |
-| `airtable.tables` | credential, `baseId` | Table ID + name |
-| `slack.channels` | credential | Channel ID + name |
-| `gmail.labels` | credential | Label ID + name |
-| `google.calendar` | credential | Calendar ID + name |
-| `linear.teams` | credential | Team ID + name |
-| `linear.projects` | credential, `teamId` | Project ID + name |
-| `jira.projects` | credential, `domain` | Project key + name |
-| `confluence.spaces` | credential, `domain` | Space key + name |
-| `notion.databases` | credential | Database ID + name |
-| `asana.workspaces` | credential | Workspace GID + name |
-| `microsoft.teams` | credential | Team ID + name |
-| `microsoft.channels` | credential, `teamId` | Channel ID + name |
-| `webflow.sites` | credential | Site ID + name |
-| `outlook.folders` | credential | Folder ID + name |
-
 ## ExternalDocument Shape
 
 Every document returned from `listDocuments`/`getDocument` must include:
@@ -419,12 +287,6 @@ export const CONNECTOR_REGISTRY: ConnectorRegistry = {
 - [ ] **Auth configured correctly:**
   - OAuth: `auth.provider` matches an existing `OAuthService` in `lib/oauth/types.ts`
   - API key: `auth.label` and `auth.placeholder` set appropriately
-- [ ] **Selector fields configured correctly (if applicable):**
-  - Every `type: 'selector'` field has a canonical pair (`short-input` or `dropdown` with same `canonicalParamId` and `mode: 'advanced'`)
-  - `required` is identical on both fields in each canonical pair
-  - `selectorKey` exists in `hooks/selectors/registry.ts`
-  - `dependsOn` references selector field IDs (not `canonicalParamId`)
-  - Dependency `canonicalParamId` values exist in `SELECTOR_CONTEXT_FIELDS`
 - [ ] `listDocuments` handles pagination and computes content hashes
 - [ ] `sourceUrl` set on each ExternalDocument (full URL, not relative)
 - [ ] `metadata` includes source-specific data for tag mapping

.claude/commands/add-integration.md

@@ -113,7 +113,7 @@ export const {service}{Action}Tool: ToolConfig<Params, Response> = {
 ```typescript
 import { {Service}Icon } from '@/components/icons'
 import type { BlockConfig } from '@/blocks/types'
-import { AuthMode, IntegrationType } from '@/blocks/types'
+import { AuthMode } from '@/blocks/types'
 import { getScopesForService } from '@/lib/oauth/utils'
 
 export const {Service}Block: BlockConfig = {
@@ -123,8 +123,6 @@ export const {Service}Block: BlockConfig = {
   longDescription: '...',
   docsLink: 'https://docs.sim.ai/tools/{service}',
   category: 'tools',
-  integrationType: IntegrationType.X,   // Primary category (see IntegrationType enum)
-  tags: ['oauth', 'api'],              // Cross-cutting tags (see IntegrationTag type)
   bgColor: '#HEXCOLOR',
   icon: {Service}Icon,
   authMode: AuthMode.OAuth,  // or AuthMode.ApiKey
@@ -412,8 +410,6 @@ If creating V2 versions (API-aligned outputs):
 
 ### Block
 - [ ] Created `blocks/blocks/{service}.ts`
-- [ ] Set `integrationType` to the correct `IntegrationType` enum value
-- [ ] Set `tags` array with all applicable `IntegrationTag` values
 - [ ] Defined operation dropdown with all operations
 - [ ] Added credential field with `requiredScopes: getScopesForService('{service}')`
 - [ ] Added conditional fields per operation

.claude/commands/validate-connector.md

@@ -1,316 +0,0 @@
----
-description: Validate an existing knowledge base connector against its service's API docs
-argument-hint: <service-name> [api-docs-url]
----
-
-# Validate Connector Skill
-
-You are an expert auditor for Sim knowledge base connectors. Your job is to thoroughly validate that an existing connector is correct, complete, and follows all conventions.
-
-## Your Task
-
-When the user asks you to validate a connector:
-1. Read the service's API documentation (via Context7 or WebFetch)
-2. Read the connector implementation, OAuth config, and registry entries
-3. Cross-reference everything against the API docs and Sim conventions
-4. Report all issues found, grouped by severity (critical, warning, suggestion)
-5. Fix all issues after reporting them
-
-## Step 1: Gather All Files
-
-Read **every** file for the connector — do not skip any:
-
-```
-apps/sim/connectors/{service}/{service}.ts   # Connector implementation
-apps/sim/connectors/{service}/index.ts       # Barrel export
-apps/sim/connectors/registry.ts              # Connector registry entry
-apps/sim/connectors/types.ts                 # ConnectorConfig interface, ExternalDocument, etc.
-apps/sim/connectors/utils.ts                 # Shared utilities (computeContentHash, htmlToPlainText, etc.)
-apps/sim/lib/oauth/oauth.ts                  # OAUTH_PROVIDERS — single source of truth for scopes
-apps/sim/lib/oauth/utils.ts                  # getCanonicalScopesForProvider, getScopesForService, SCOPE_DESCRIPTIONS
-apps/sim/lib/oauth/types.ts                  # OAuthService union type
-apps/sim/components/icons.tsx                 # Icon definition for the service
-```
-
-If the connector uses selectors, also read:
-```
-apps/sim/hooks/selectors/registry.ts         # Selector key definitions
-apps/sim/hooks/selectors/types.ts            # SelectorKey union type
-apps/sim/lib/workflows/subblocks/context.ts  # SELECTOR_CONTEXT_FIELDS
-```
-
-## Step 2: Pull API Documentation
-
-Fetch the official API docs for the service. This is the **source of truth** for:
-- Endpoint URLs, HTTP methods, and auth headers
-- Required vs optional parameters
-- Parameter types and allowed values
-- Response shapes and field names
-- Pagination patterns (cursor, offset, next token)
-- Rate limits and error formats
-- OAuth scopes and their meanings
-
-Use Context7 (resolve-library-id → query-docs) or WebFetch to retrieve documentation. If both fail, note which claims are based on training knowledge vs verified docs.
-
-## Step 3: Validate API Endpoints
-
-For **every** API call in the connector (`listDocuments`, `getDocument`, `validateConfig`, and any helper functions), verify against the API docs:
-
-### URLs and Methods
-- [ ] Base URL is correct for the service's API version
-- [ ] Endpoint paths match the API docs exactly
-- [ ] HTTP method is correct (GET, POST, PUT, PATCH, DELETE)
-- [ ] Path parameters are correctly interpolated and URI-encoded where needed
-- [ ] Query parameters use correct names and formats per the API docs
-
-### Headers
-- [ ] Authorization header uses the correct format:
-  - OAuth: `Authorization: Bearer ${accessToken}`
-  - API Key: correct header name per the service's docs
-- [ ] `Content-Type` is set for POST/PUT/PATCH requests
-- [ ] Any service-specific headers are present (e.g., `Notion-Version`, `Dropbox-API-Arg`)
-- [ ] No headers are sent that the API doesn't support or silently ignores
-
-### Request Bodies
-- [ ] POST/PUT body fields match API parameter names exactly
-- [ ] Required fields are always sent
-- [ ] Optional fields are conditionally included (not sent as `null` or empty unless the API expects that)
-- [ ] Field value types match API expectations (string vs number vs boolean)
-
-### Input Sanitization
-- [ ] User-controlled values interpolated into query strings are properly escaped:
-  - OData `$filter`: single quotes escaped with `''` (e.g., `externalId.replace(/'/g, "''")`)
-  - SOQL: single quotes escaped with `\'`
-  - GraphQL variables: passed as variables, not interpolated into query strings
-  - URL path segments: `encodeURIComponent()` applied
-- [ ] URL-type config fields (e.g., `siteUrl`, `instanceUrl`) are normalized:
-  - Strip `https://` / `http://` prefix if the API expects bare domains
-  - Strip trailing `/`
-  - Apply `.trim()` before validation
-
-### Response Parsing
-- [ ] Response structure is correctly traversed (e.g., `data.results` vs `data.items` vs `data`)
-- [ ] Field names extracted match what the API actually returns
-- [ ] Nullable fields are handled with `?? null` or `|| undefined`
-- [ ] Error responses are checked before accessing data fields
-
-## Step 4: Validate OAuth Scopes (if OAuth connector)
-
-Scopes must be correctly declared and sufficient for all API calls the connector makes.
-
-### Connector requiredScopes
-- [ ] `requiredScopes` in the connector's `auth` config lists all scopes needed by the connector
-- [ ] Each scope in `requiredScopes` is a real, valid scope recognized by the service's API
-- [ ] No invalid, deprecated, or made-up scopes are listed
-- [ ] No unnecessary excess scopes beyond what the connector actually needs
-
-### Scope Subset Validation (CRITICAL)
-- [ ] Every scope in `requiredScopes` exists in the OAuth provider's `scopes` array in `lib/oauth/oauth.ts`
-- [ ] Find the provider in `OAUTH_PROVIDERS[providerGroup].services[serviceId].scopes`
-- [ ] Verify: `requiredScopes` ⊆ `OAUTH_PROVIDERS scopes` (every required scope is present in the provider config)
-- [ ] If a required scope is NOT in the provider config, flag as **critical** — the connector will fail at runtime
-
-### Scope Sufficiency
-For each API endpoint the connector calls:
-- [ ] Identify which scopes are required per the API docs
-- [ ] Verify those scopes are included in the connector's `requiredScopes`
-- [ ] If the connector calls endpoints requiring scopes not in `requiredScopes`, flag as **warning**
-
-### Token Refresh Config
-- [ ] Check the `getOAuthTokenRefreshConfig` function in `lib/oauth/oauth.ts` for this provider
-- [ ] `useBasicAuth` matches the service's token exchange requirements
-- [ ] `supportsRefreshTokenRotation` matches whether the service issues rotating refresh tokens
-- [ ] Token endpoint URL is correct
-
-## Step 5: Validate Pagination
-
-### listDocuments Pagination
-- [ ] Cursor/pagination parameter name matches the API docs
-- [ ] Response pagination field is correctly extracted (e.g., `next_cursor`, `nextPageToken`, `@odata.nextLink`, `offset`)
-- [ ] `hasMore` is correctly determined from the response
-- [ ] `nextCursor` is correctly passed back for the next page
-- [ ] `maxItems` / `maxRecords` cap is correctly applied across pages using `syncContext.totalDocsFetched`
-- [ ] Page size is within the API's allowed range (not exceeding max page size)
-- [ ] Last page precision: when a `maxItems` cap exists, the final page request uses `Math.min(PAGE_SIZE, remaining)` to avoid fetching more records than needed
-- [ ] No off-by-one errors in pagination tracking
-- [ ] The connector does NOT hit known API pagination limits silently (e.g., HubSpot search 10k cap)
-
-### Pagination State Across Pages
-- [ ] `syncContext` is used to cache state across pages (user names, field maps, instance URLs, portal IDs, etc.)
-- [ ] Cached state in `syncContext` is correctly initialized on first page and reused on subsequent pages
-
-## Step 6: Validate Data Transformation
-
-### ExternalDocument Construction
-- [ ] `externalId` is a stable, unique identifier from the source API
-- [ ] `title` is extracted from the correct field and has a sensible fallback (e.g., `'Untitled'`)
-- [ ] `content` is plain text — HTML content is stripped using `htmlToPlainText` from `@/connectors/utils`
-- [ ] `mimeType` is `'text/plain'`
-- [ ] `contentHash` is computed using `computeContentHash` from `@/connectors/utils`
-- [ ] `sourceUrl` is a valid, complete URL back to the original resource (not relative)
-- [ ] `metadata` contains all fields referenced by `mapTags` and `tagDefinitions`
-
-### Content Extraction
-- [ ] Rich text / HTML fields are converted to plain text before indexing
-- [ ] Important content is not silently dropped (e.g., nested blocks, table cells, code blocks)
-- [ ] Content is not silently truncated without logging a warning
-- [ ] Empty/blank documents are properly filtered out
-- [ ] Size checks use `Buffer.byteLength(text, 'utf8')` not `text.length` when comparing against byte-based limits (e.g., `MAX_FILE_SIZE` in bytes)
-
-## Step 7: Validate Tag Definitions and mapTags
-
-### tagDefinitions
-- [ ] Each `tagDefinition` has an `id`, `displayName`, and `fieldType`
-- [ ] `fieldType` matches the actual data type: `'text'` for strings, `'number'` for numbers, `'date'` for dates, `'boolean'` for booleans
-- [ ] Every `id` in `tagDefinitions` is returned by `mapTags`
-- [ ] No `tagDefinition` references a field that `mapTags` never produces
-
-### mapTags
-- [ ] Return keys match `tagDefinition` `id` values exactly
-- [ ] Date values are properly parsed using `parseTagDate` from `@/connectors/utils`
-- [ ] Array values are properly joined using `joinTagArray` from `@/connectors/utils`
-- [ ] Number values are validated (not `NaN`)
-- [ ] Metadata field names accessed in `mapTags` match what `listDocuments`/`getDocument` store in `metadata`
-
-## Step 8: Validate Config Fields and Validation
-
-### configFields
-- [ ] Every field has `id`, `title`, `type`
-- [ ] `required` is set explicitly (not omitted)
-- [ ] Dropdown fields have `options` with `label` and `id` for each option
-- [ ] Selector fields follow the canonical pair pattern:
-  - A `type: 'selector'` field with `selectorKey`, `canonicalParamId`, `mode: 'basic'`
-  - A `type: 'short-input'` field with the same `canonicalParamId`, `mode: 'advanced'`
-  - `required` is identical on both fields in the pair
-- [ ] `selectorKey` values exist in the selector registry
-- [ ] `dependsOn` references selector field `id` values, not `canonicalParamId`
-
-### validateConfig
-- [ ] Validates all required fields are present before making API calls
-- [ ] Validates optional numeric fields (checks `Number.isNaN`, positive values)
-- [ ] Makes a lightweight API call to verify access (e.g., fetch 1 record, get profile)
-- [ ] Uses `VALIDATE_RETRY_OPTIONS` for retry budget
-- [ ] Returns `{ valid: true }` on success
-- [ ] Returns `{ valid: false, error: 'descriptive message' }` on failure
-- [ ] Catches exceptions and returns user-friendly error messages
-- [ ] Does NOT make expensive calls (full data listing, large queries)
-
-## Step 9: Validate getDocument
-
-- [ ] Fetches a single document by `externalId`
-- [ ] Returns `null` for 404 / not found (does not throw)
-- [ ] Returns the same `ExternalDocument` shape as `listDocuments`
-- [ ] Handles all content types that `listDocuments` can produce (e.g., if `listDocuments` returns both pages and blogposts, `getDocument` must handle both — not hardcode one endpoint)
-- [ ] Forwards `syncContext` if it needs cached state (user names, field maps, etc.)
-- [ ] Error handling is graceful (catches, logs, returns null or throws with context)
-- [ ] Does not redundantly re-fetch data already included in the initial API response (e.g., if comments come back with the post, don't fetch them again separately)
-
-## Step 10: Validate General Quality
-
-### fetchWithRetry Usage
-- [ ] All external API calls use `fetchWithRetry` from `@/lib/knowledge/documents/utils`
-- [ ] No raw `fetch()` calls to external APIs
-- [ ] `VALIDATE_RETRY_OPTIONS` used in `validateConfig`
-- [ ] If `validateConfig` calls a shared helper (e.g., `linearGraphQL`, `resolveId`), that helper must accept and forward `retryOptions` to `fetchWithRetry`
-- [ ] Default retry options used in `listDocuments`/`getDocument`
-
-### API Efficiency
-- [ ] APIs that support field selection (e.g., `$select`, `sysparm_fields`, `fields`) should request only the fields the connector needs — in both `listDocuments` AND `getDocument`
-- [ ] No redundant API calls: if a helper already fetches data (e.g., site metadata), callers should reuse the result instead of making a second call for the same information
-- [ ] Sequential per-item API calls (fetching details for each document in a loop) should be batched with `Promise.all` and a concurrency limit of 3-5
-
-### Error Handling
-- [ ] Individual document failures are caught and logged without aborting the sync
-- [ ] API error responses include status codes in error messages
-- [ ] No unhandled promise rejections in concurrent operations
-
-### Concurrency
-- [ ] Concurrent API calls use reasonable batch sizes (3-5 is typical)
-- [ ] No unbounded `Promise.all` over large arrays
-
-### Logging
-- [ ] Uses `createLogger` from `@sim/logger` (not `console.log`)
-- [ ] Logs sync progress at `info` level
-- [ ] Logs errors at `warn` or `error` level with context
-
-### Registry
-- [ ] Connector is exported from `connectors/{service}/index.ts`
-- [ ] Connector is registered in `connectors/registry.ts`
-- [ ] Registry key matches the connector's `id` field
-
-## Step 11: Report and Fix
-
-### Report Format
-
-Group findings by severity:
-
-**Critical** (will cause runtime errors, data loss, or auth failures):
-- Wrong API endpoint URL or HTTP method
-- Invalid or missing OAuth scopes (not in provider config)
-- Incorrect response field mapping (accessing wrong path)
-- SOQL/query fields that don't exist on the target object
-- Pagination that silently hits undocumented API limits
-- Missing error handling that would crash the sync
-- `requiredScopes` not a subset of OAuth provider scopes
-- Query/filter injection: user-controlled values interpolated into OData `$filter`, SOQL, or query strings without escaping
-
-**Warning** (incorrect behavior, data quality issues, or convention violations):
-- HTML content not stripped via `htmlToPlainText`
-- `getDocument` not forwarding `syncContext`
-- `getDocument` hardcoded to one content type when `listDocuments` returns multiple (e.g., only pages but not blogposts)
-- Missing `tagDefinition` for metadata fields returned by `mapTags`
-- Incorrect `useBasicAuth` or `supportsRefreshTokenRotation` in token refresh config
-- Invalid scope names that the API doesn't recognize (even if silently ignored)
-- Private resources excluded from name-based lookup despite scopes being available
-- Silent data truncation without logging
-- Size checks using `text.length` (character count) instead of `Buffer.byteLength` (byte count) for byte-based limits
-- URL-type config fields not normalized (protocol prefix, trailing slashes cause API failures)
-- `VALIDATE_RETRY_OPTIONS` not threaded through helper functions called by `validateConfig`
-
-**Suggestion** (minor improvements):
-- Missing incremental sync support despite API supporting it
-- Overly broad scopes that could be narrowed (not wrong, but could be tighter)
-- Source URL format could be more specific
-- Missing `orderBy` for deterministic pagination
-- Redundant API calls that could be cached in `syncContext`
-- Sequential per-item API calls that could be batched with `Promise.all` (concurrency 3-5)
-- API supports field selection but connector fetches all fields (e.g., missing `$select`, `sysparm_fields`, `fields`)
-- `getDocument` re-fetches data already included in the initial API response (e.g., comments returned with post)
-- Last page of pagination requests full `PAGE_SIZE` when fewer records remain (`Math.min(PAGE_SIZE, remaining)`)
-
-### Fix All Issues
-
-After reporting, fix every **critical** and **warning** issue. Apply **suggestions** where they don't add unnecessary complexity.
-
-### Validation Output
-
-After fixing, confirm:
-1. `bun run lint` passes
-2. TypeScript compiles clean
-3. Re-read all modified files to verify fixes are correct
-
-## Checklist Summary
-
-- [ ] Read connector implementation, types, utils, registry, and OAuth config
-- [ ] Pulled and read official API documentation for the service
-- [ ] Validated every API endpoint URL, method, headers, and body against API docs
-- [ ] Validated input sanitization: no query/filter injection, URL fields normalized
-- [ ] Validated OAuth scopes: `requiredScopes` ⊆ OAuth provider `scopes` in `oauth.ts`
-- [ ] Validated each scope is real and recognized by the service's API
-- [ ] Validated scopes are sufficient for all API endpoints the connector calls
-- [ ] Validated token refresh config (`useBasicAuth`, `supportsRefreshTokenRotation`)
-- [ ] Validated pagination: cursor names, page sizes, hasMore logic, no silent caps
-- [ ] Validated data transformation: plain text extraction, HTML stripping, content hashing
-- [ ] Validated tag definitions match mapTags output, correct fieldTypes
-- [ ] Validated config fields: canonical pairs, selector keys, required flags
-- [ ] Validated validateConfig: lightweight check, error messages, retry options
-- [ ] Validated getDocument: null on 404, all content types handled, no redundant re-fetches, syncContext forwarding
-- [ ] Validated fetchWithRetry used for all external calls (no raw fetch), VALIDATE_RETRY_OPTIONS threaded through helpers
-- [ ] Validated API efficiency: field selection used, no redundant calls, sequential fetches batched
-- [ ] Validated error handling: graceful failures, no unhandled rejections
-- [ ] Validated logging: createLogger, no console.log
-- [ ] Validated registry: correct export, correct key
-- [ ] Reported all issues grouped by severity
-- [ ] Fixed all critical and warning issues
-- [ ] Ran `bun run lint` after fixes
-- [ ] Verified TypeScript compiles clean

.cursor/skills/add-hosted-key/SKILL.md

@@ -192,7 +192,7 @@ In the block config (`blocks/blocks/{service}.ts`), add `hideWhenHosted: true` t
 },
 ```
 
-The visibility is controlled by `isSubBlockHidden()` in `lib/workflows/subblocks/visibility.ts`, which checks both the `isHosted` feature flag (`hideWhenHosted`) and optional env var conditions (`hideWhenEnvSet`).
+The visibility is controlled by `isSubBlockHiddenByHostedKey()` in `lib/workflows/subblocks/visibility.ts`, which checks the `isHosted` feature flag.
 
 ### Excluding Specific Operations from Hosted Key Support
 

.devcontainer/Dockerfile

@@ -1,4 +1,4 @@
-FROM oven/bun:1.3.11-alpine
+FROM oven/bun:1.3.10-alpine
 
 # Install necessary packages for development
 RUN apk add --no-cache \

.github/workflows/ci.yml

@@ -2,9 +2,9 @@ name: CI
 
 on:
   push:
-    branches: [main, staging, dev]
+    branches: [main, staging]
   pull_request:
-    branches: [main, staging, dev]
+    branches: [main, staging]
 
 concurrency:
   group: ci-${{ github.ref }}
@@ -23,7 +23,7 @@ jobs:
   detect-version:
     name: Detect Version
     runs-on: blacksmith-4vcpu-ubuntu-2404
-    if: github.event_name == 'push' && (github.ref == 'refs/heads/main' || github.ref == 'refs/heads/staging' || github.ref == 'refs/heads/dev')
+    if: github.event_name == 'push' && (github.ref == 'refs/heads/main' || github.ref == 'refs/heads/staging')
     outputs:
       version: ${{ steps.extract.outputs.version }}
       is_release: ${{ steps.extract.outputs.is_release }}
@@ -49,7 +49,7 @@ jobs:
   build-amd64:
     name: Build AMD64
     needs: [test-build, detect-version]
-    if: github.event_name == 'push' && (github.ref == 'refs/heads/main' || github.ref == 'refs/heads/staging' || github.ref == 'refs/heads/dev')
+    if: github.event_name == 'push' && (github.ref == 'refs/heads/main' || github.ref == 'refs/heads/staging')
     runs-on: blacksmith-8vcpu-ubuntu-2404
     permissions:
       contents: read
@@ -75,8 +75,8 @@ jobs:
       - name: Configure AWS credentials
         uses: aws-actions/configure-aws-credentials@v4
         with:
-          role-to-assume: ${{ github.ref == 'refs/heads/main' && secrets.AWS_ROLE_TO_ASSUME || github.ref == 'refs/heads/dev' && secrets.DEV_AWS_ROLE_TO_ASSUME || secrets.STAGING_AWS_ROLE_TO_ASSUME }}
-          aws-region: ${{ github.ref == 'refs/heads/main' && secrets.AWS_REGION || github.ref == 'refs/heads/dev' && secrets.DEV_AWS_REGION || secrets.STAGING_AWS_REGION }}
+          role-to-assume: ${{ github.ref == 'refs/heads/main' && secrets.AWS_ROLE_TO_ASSUME || secrets.STAGING_AWS_ROLE_TO_ASSUME }}
+          aws-region: ${{ github.ref == 'refs/heads/main' && secrets.AWS_REGION || secrets.STAGING_AWS_REGION }}
 
       - name: Login to Amazon ECR
         id: login-ecr
@@ -109,8 +109,6 @@ jobs:
           # ECR tags (always build for ECR)
           if [ "${{ github.ref }}" = "refs/heads/main" ]; then
             ECR_TAG="latest"
-          elif [ "${{ github.ref }}" = "refs/heads/dev" ]; then
-            ECR_TAG="dev"
           else
             ECR_TAG="staging"
           fi

.github/workflows/docs-embeddings.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: 1.3.11
+          bun-version: 1.3.10
 
       - name: Setup Node
         uses: actions/setup-node@v4

.github/workflows/i18n.yml

@@ -23,7 +23,7 @@ jobs:
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: 1.3.11
+          bun-version: 1.3.10
 
       - name: Cache Bun dependencies
         uses: actions/cache@v4
@@ -122,7 +122,7 @@ jobs:
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: 1.3.11
+          bun-version: 1.3.10
 
       - name: Cache Bun dependencies
         uses: actions/cache@v4

.github/workflows/images.yml

@@ -36,8 +36,8 @@ jobs:
       - name: Configure AWS credentials
         uses: aws-actions/configure-aws-credentials@v4
         with:
-          role-to-assume: ${{ github.ref == 'refs/heads/main' && secrets.AWS_ROLE_TO_ASSUME || github.ref == 'refs/heads/dev' && secrets.DEV_AWS_ROLE_TO_ASSUME || secrets.STAGING_AWS_ROLE_TO_ASSUME }}
-          aws-region: ${{ github.ref == 'refs/heads/main' && secrets.AWS_REGION || github.ref == 'refs/heads/dev' && secrets.DEV_AWS_REGION || secrets.STAGING_AWS_REGION }}
+          role-to-assume: ${{ github.ref == 'refs/heads/main' && secrets.AWS_ROLE_TO_ASSUME || secrets.STAGING_AWS_ROLE_TO_ASSUME }}
+          aws-region: ${{ github.ref == 'refs/heads/main' && secrets.AWS_REGION || secrets.STAGING_AWS_REGION }}
 
       - name: Login to Amazon ECR
         id: login-ecr
@@ -70,8 +70,6 @@ jobs:
           # ECR tags (always build for ECR)
           if [ "${{ github.ref }}" = "refs/heads/main" ]; then
             ECR_TAG="latest"
-          elif [ "${{ github.ref }}" = "refs/heads/dev" ]; then
-            ECR_TAG="dev"
           else
             ECR_TAG="staging"
           fi

.github/workflows/migrations.yml

@@ -19,7 +19,7 @@ jobs:
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: 1.3.11
+          bun-version: 1.3.10
 
       - name: Cache Bun dependencies
         uses: actions/cache@v4

.github/workflows/publish-cli.yml

@@ -19,7 +19,7 @@ jobs:
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: 1.3.11
+          bun-version: 1.3.10
 
       - name: Setup Node.js for npm publishing
         uses: actions/setup-node@v4

.github/workflows/publish-ts-sdk.yml

@@ -19,7 +19,7 @@ jobs:
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: 1.3.11
+          bun-version: 1.3.10
 
       - name: Setup Node.js for npm publishing
         uses: actions/setup-node@v4

.github/workflows/test-build.yml

@@ -19,7 +19,7 @@ jobs:
       - name: Setup Bun
         uses: oven-sh/setup-bun@v2
         with:
-          bun-version: 1.3.11
+          bun-version: 1.3.10
 
       - name: Setup Node
         uses: actions/setup-node@v4

AGENTS.md

@@ -1,383 +0,0 @@
-# Sim Development Guidelines
-
-You are a professional software engineer. All code must follow best practices: accurate, readable, clean, and efficient.
-
-## Global Standards
-
-- **Logging**: Import `createLogger` from `@sim/logger`. Use `logger.info`, `logger.warn`, `logger.error` instead of `console.log`
-- **Comments**: Use TSDoc for documentation. No `====` separators. No non-TSDoc comments
-- **Styling**: Never update global styles. Keep all styling local to components
-- **Package Manager**: Use `bun` and `bunx`, not `npm` and `npx`
-
-## Architecture
-
-### Core Principles
-1. Single Responsibility: Each component, hook, store has one clear purpose
-2. Composition Over Complexity: Break down complex logic into smaller pieces
-3. Type Safety First: TypeScript interfaces for all props, state, return types
-4. Predictable State: Zustand for global state, useState for UI-only concerns
-
-### Root Structure
-```
-apps/sim/
-├── app/           # Next.js app router (pages, API routes)
-├── blocks/        # Block definitions and registry
-├── components/    # Shared UI (emcn/, ui/)
-├── executor/      # Workflow execution engine
-├── hooks/         # Shared hooks (queries/, selectors/)
-├── lib/           # App-wide utilities
-├── providers/     # LLM provider integrations
-├── stores/        # Zustand stores
-├── tools/         # Tool definitions
-└── triggers/      # Trigger definitions
-```
-
-### Naming Conventions
-- Components: PascalCase (`WorkflowList`)
-- Hooks: `use` prefix (`useWorkflowOperations`)
-- Files: kebab-case (`workflow-list.tsx`)
-- Stores: `stores/feature/store.ts`
-- Constants: SCREAMING_SNAKE_CASE
-- Interfaces: PascalCase with suffix (`WorkflowListProps`)
-
-## Imports
-
-**Always use absolute imports.** Never use relative imports.
-
-```typescript
-// ✓ Good
-import { useWorkflowStore } from '@/stores/workflows/store'
-
-// ✗ Bad
-import { useWorkflowStore } from '../../../stores/workflows/store'
-```
-
-Use barrel exports (`index.ts`) when a folder has 3+ exports. Do not re-export from non-barrel files; import directly from the source.
-
-### Import Order
-1. React/core libraries
-2. External libraries
-3. UI components (`@/components/emcn`, `@/components/ui`)
-4. Utilities (`@/lib/...`)
-5. Stores (`@/stores/...`)
-6. Feature imports
-7. CSS imports
-
-Use `import type { X }` for type-only imports.
-
-## TypeScript
-
-1. No `any` - Use proper types or `unknown` with type guards
-2. Always define props interface for components
-3. `as const` for constant objects/arrays
-4. Explicit ref types: `useRef<HTMLDivElement>(null)`
-
-## Components
-
-```typescript
-'use client' // Only if using hooks
-
-const CONFIG = { SPACING: 8 } as const
-
-interface ComponentProps {
-  requiredProp: string
-  optionalProp?: boolean
-}
-
-export function Component({ requiredProp, optionalProp = false }: ComponentProps) {
-  // Order: refs → external hooks → store hooks → custom hooks → state → useMemo → useCallback → useEffect → return
-}
-```
-
-Extract when: 50+ lines, used in 2+ files, or has own state/logic. Keep inline when: < 10 lines, single use, purely presentational.
-
-## Hooks
-
-```typescript
-interface UseFeatureProps { id: string }
-
-export function useFeature({ id }: UseFeatureProps) {
-  const idRef = useRef(id)
-  const [data, setData] = useState<Data | null>(null)
-  
-  useEffect(() => { idRef.current = id }, [id])
-  
-  const fetchData = useCallback(async () => { ... }, []) // Empty deps when using refs
-  
-  return { data, fetchData }
-}
-```
-
-## Zustand Stores
-
-Stores live in `stores/`. Complex stores split into `store.ts` + `types.ts`.
-
-```typescript
-import { create } from 'zustand'
-import { devtools } from 'zustand/middleware'
-
-const initialState = { items: [] as Item[] }
-
-export const useFeatureStore = create<FeatureState>()(
-  devtools(
-    (set, get) => ({
-      ...initialState,
-      setItems: (items) => set({ items }),
-      reset: () => set(initialState),
-    }),
-    { name: 'feature-store' }
-  )
-)
-```
-
-Use `devtools` middleware. Use `persist` only when data should survive reload with `partialize` to persist only necessary state.
-
-## React Query
-
-All React Query hooks live in `hooks/queries/`. All server state must go through React Query — never use `useState` + `fetch` in components for data fetching or mutations.
-
-### Query Key Factory
-
-Every file must have a hierarchical key factory with an `all` root key and intermediate plural keys for prefix invalidation:
-
-```typescript
-export const entityKeys = {
-  all: ['entity'] as const,
-  lists: () => [...entityKeys.all, 'list'] as const,
-  list: (workspaceId?: string) => [...entityKeys.lists(), workspaceId ?? ''] as const,
-  details: () => [...entityKeys.all, 'detail'] as const,
-  detail: (id?: string) => [...entityKeys.details(), id ?? ''] as const,
-}
-```
-
-### Query Hooks
-
-- Every `queryFn` must forward `signal` for request cancellation
-- Every query must have an explicit `staleTime`
-- Use `keepPreviousData` only on variable-key queries (where params change), never on static keys
-
-```typescript
-export function useEntityList(workspaceId?: string) {
-  return useQuery({
-    queryKey: entityKeys.list(workspaceId),
-    queryFn: ({ signal }) => fetchEntities(workspaceId as string, signal),
-    enabled: Boolean(workspaceId),
-    staleTime: 60 * 1000,
-    placeholderData: keepPreviousData, // OK: workspaceId varies
-  })
-}
-```
-
-### Mutation Hooks
-
-- Use targeted invalidation (`entityKeys.lists()`) not broad (`entityKeys.all`) when possible
-- For optimistic updates: use `onSettled` (not `onSuccess`) for cache reconciliation — `onSettled` fires on both success and error
-- Don't include mutation objects in `useCallback` deps — `.mutate()` is stable in TanStack Query v5
-
-```typescript
-export function useUpdateEntity() {
-  const queryClient = useQueryClient()
-  return useMutation({
-    mutationFn: async (variables) => { /* ... */ },
-    onMutate: async (variables) => {
-      await queryClient.cancelQueries({ queryKey: entityKeys.detail(variables.id) })
-      const previous = queryClient.getQueryData(entityKeys.detail(variables.id))
-      queryClient.setQueryData(entityKeys.detail(variables.id), /* optimistic */)
-      return { previous }
-    },
-    onError: (_err, variables, context) => {
-      queryClient.setQueryData(entityKeys.detail(variables.id), context?.previous)
-    },
-    onSettled: (_data, _error, variables) => {
-      queryClient.invalidateQueries({ queryKey: entityKeys.lists() })
-      queryClient.invalidateQueries({ queryKey: entityKeys.detail(variables.id) })
-    },
-  })
-}
-```
-
-## Styling
-
-Use Tailwind only, no inline styles. Use `cn()` from `@/lib/utils` for conditional classes.
-
-```typescript
-<div className={cn('base-classes', isActive && 'active-classes')} />
-```
-
-## EMCN Components
-
-Import from `@/components/emcn`, never from subpaths (except CSS files). Use CVA when 2+ variants exist.
-
-## Testing
-
-Use Vitest. Test files: `feature.ts` → `feature.test.ts`. See `.cursor/rules/sim-testing.mdc` for full details.
-
-### Global Mocks (vitest.setup.ts)
-
-`@sim/db`, `drizzle-orm`, `@sim/logger`, `@/blocks/registry`, `@trigger.dev/sdk`, and store mocks are provided globally. Do NOT re-mock them unless overriding behavior.
-
-### Standard Test Pattern
-
-```typescript
-/**
- * @vitest-environment node
- */
-import { createMockRequest } from '@sim/testing'
-import { beforeEach, describe, expect, it, vi } from 'vitest'
-
-const { mockGetSession } = vi.hoisted(() => ({
-  mockGetSession: vi.fn(),
-}))
-
-vi.mock('@/lib/auth', () => ({
-  auth: { api: { getSession: vi.fn() } },
-  getSession: mockGetSession,
-}))
-
-import { GET } from '@/app/api/my-route/route'
-
-describe('my route', () => {
-  beforeEach(() => {
-    vi.clearAllMocks()
-    mockGetSession.mockResolvedValue({ user: { id: 'user-1' } })
-  })
-  it('returns data', async () => { ... })
-})
-```
-
-### Performance Rules
-
-- **NEVER** use `vi.resetModules()` + `vi.doMock()` + `await import()` — use `vi.hoisted()` + `vi.mock()` + static imports
-- **NEVER** use `vi.importActual()` — mock everything explicitly
-- **NEVER** use `mockAuth()`, `mockConsoleLogger()`, `setupCommonApiMocks()` from `@sim/testing` — they use `vi.doMock()` internally
-- **Mock heavy deps** (`@/blocks`, `@/tools/registry`, `@/triggers`) in tests that don't need them
-- **Use `@vitest-environment node`** unless DOM APIs are needed (`window`, `document`, `FormData`)
-- **Avoid real timers** — use 1ms delays or `vi.useFakeTimers()`
-
-Use `@sim/testing` mocks/factories over local test data.
-
-## Utils Rules
-
-- Never create `utils.ts` for single consumer - inline it
-- Create `utils.ts` when 2+ files need the same helper
-- Check existing sources in `lib/` before duplicating
-
-## Adding Integrations
-
-New integrations require: **Tools** → **Block** → **Icon** → (optional) **Trigger**
-
-Always look up the service's API docs first.
-
-### 1. Tools (`tools/{service}/`)
-
-```
-tools/{service}/
-├── index.ts      # Barrel export
-├── types.ts      # Params/response types
-└── {action}.ts   # Tool implementation
-```
-
-**Tool structure:**
-```typescript
-export const serviceTool: ToolConfig<Params, Response> = {
-  id: 'service_action',
-  name: 'Service Action',
-  description: '...',
-  version: '1.0.0',
-  oauth: { required: true, provider: 'service' },
-  params: { /* ... */ },
-  request: { url: '/api/tools/service/action', method: 'POST', ... },
-  transformResponse: async (response) => { /* ... */ },
-  outputs: { /* ... */ },
-}
-```
-
-Register in `tools/registry.ts`.
-
-### 2. Block (`blocks/blocks/{service}.ts`)
-
-```typescript
-export const ServiceBlock: BlockConfig = {
-  type: 'service',
-  name: 'Service',
-  description: '...',
-  category: 'tools',
-  bgColor: '#hexcolor',
-  icon: ServiceIcon,
-  subBlocks: [ /* see SubBlock Properties */ ],
-  tools: { access: ['service_action'], config: { tool: (p) => `service_${p.operation}`, params: (p) => ({ /* type coercions here */ }) } },
-  inputs: { /* ... */ },
-  outputs: { /* ... */ },
-}
-```
-
-Register in `blocks/registry.ts` (alphabetically).
-
-**Important:** `tools.config.tool` runs during serialization (before variable resolution). Never do `Number()` or other type coercions there — dynamic references like `<Block.output>` will be destroyed. Use `tools.config.params` for type coercions (it runs during execution, after variables are resolved).
-
-**SubBlock Properties:**
-```typescript
-{
-  id: 'field', title: 'Label', type: 'short-input', placeholder: '...',
-  required: true,                    // or condition object
-  condition: { field: 'op', value: 'send' },  // show/hide
-  dependsOn: ['credential'],         // clear when dep changes
-  mode: 'basic',                     // 'basic' | 'advanced' | 'both' | 'trigger'
-}
-```
-
-**condition examples:**
-- `{ field: 'op', value: 'send' }` - show when op === 'send'
-- `{ field: 'op', value: ['a','b'] }` - show when op is 'a' OR 'b'
-- `{ field: 'op', value: 'x', not: true }` - show when op !== 'x'
-- `{ field: 'op', value: 'x', not: true, and: { field: 'type', value: 'dm', not: true } }` - complex
-
-**dependsOn:** `['field']` or `{ all: ['a'], any: ['b', 'c'] }`
-
-**File Input Pattern (basic/advanced mode):**
-```typescript
-// Basic: file-upload UI
-{ id: 'uploadFile', type: 'file-upload', canonicalParamId: 'file', mode: 'basic' },
-// Advanced: reference from other blocks
-{ id: 'fileRef', type: 'short-input', canonicalParamId: 'file', mode: 'advanced' },
-```
-
-In `tools.config.tool`, normalize with:
-```typescript
-import { normalizeFileInput } from '@/blocks/utils'
-const file = normalizeFileInput(params.uploadFile || params.fileRef, { single: true })
-if (file) params.file = file
-```
-
-For file uploads, create an internal API route (`/api/tools/{service}/upload`) that uses `downloadFileFromStorage` to get file content from `UserFile` objects.
-
-### 3. Icon (`components/icons.tsx`)
-
-```typescript
-export function ServiceIcon(props: SVGProps<SVGSVGElement>) {
-  return <svg {...props}>/* SVG from brand assets */</svg>
-}
-```
-
-### 4. Trigger (`triggers/{service}/`) - Optional
-
-```
-triggers/{service}/
-├── index.ts      # Barrel export
-├── webhook.ts    # Webhook handler
-└── {event}.ts    # Event-specific handlers
-```
-
-Register in `triggers/registry.ts`.
-
-### Integration Checklist
-
-- [ ] Look up API docs
-- [ ] Create `tools/{service}/` with types and tools
-- [ ] Register tools in `tools/registry.ts`
-- [ ] Add icon to `components/icons.tsx`
-- [ ] Create block in `blocks/blocks/{service}.ts`
-- [ ] Register block in `blocks/registry.ts`
-- [ ] (Optional) Create and register triggers
-- [ ] (If file uploads) Create internal API route with `downloadFileFromStorage`
-- [ ] (If file uploads) Use `normalizeFileInput` in block config

README.md

@@ -1,20 +1,16 @@
 <p align="center">
   <a href="https://sim.ai" target="_blank" rel="noopener noreferrer">
-    <picture>
-      <source media="(prefers-color-scheme: dark)" srcset="apps/sim/public/logo/wordmark.svg">
-      <source media="(prefers-color-scheme: light)" srcset="apps/sim/public/logo/wordmark-dark.svg">
-      <img src="apps/sim/public/logo/wordmark-dark.svg" alt="Sim Logo" width="380"/>
-    </picture>
+    <img src="apps/sim/public/logo/reverse/text/large.png" alt="Sim Logo" width="500"/>
   </a>
 </p>
 
 <p align="center">The open-source platform to build AI agents and run your agentic workforce. Connect 1,000+ integrations and LLMs to orchestrate agentic workflows.</p>
 
 <p align="center">
-  <a href="https://sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/sim.ai-33c482" alt="Sim.ai"></a>
+  <a href="https://sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/sim.ai-6F3DFA" alt="Sim.ai"></a>
   <a href="https://discord.gg/Hr4UWYEcTT" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Discord-Join%20Server-5865F2?logo=discord&logoColor=white" alt="Discord"></a>
   <a href="https://x.com/simdotai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/twitter/follow/simdotai?style=social" alt="Twitter"></a>
-  <a href="https://docs.sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Docs-33c482.svg" alt="Documentation"></a>
+  <a href="https://docs.sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Docs-6F3DFA.svg" alt="Documentation"></a>
 </p>
 
 <p align="center">
@@ -46,7 +42,7 @@ Upload documents to a vector store and let agents answer questions grounded in y
 
 ### Cloud-hosted: [sim.ai](https://sim.ai)
 
-<a href="https://sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/sim.ai-33c482?logo=data:image/svg%2bxml;base64,PHN2ZyB3aWR0aD0iNjE2IiBoZWlnaHQ9IjYxNiIgdmlld0JveD0iMCAwIDYxNiA2MTYiIGZpbGw9Im5vbmUiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+CjxnIGNsaXAtcGF0aD0idXJsKCNjbGlwMF8xMTU5XzMxMykiPgo8cGF0aCBkPSJNNjE2IDBIMFY2MTZINjE2VjBaIiBmaWxsPSIjMzNjNDgyIi8+CjxwYXRoIGQ9Ik04MyAzNjUuNTY3SDExM0MxMTMgMzczLjgwNSAxMTYgMzgwLjM3MyAxMjIgMzg1LjI3MkMxMjggMzg5Ljk0OCAxMzYuMTExIDM5Mi4yODUgMTQ2LjMzMyAzOTIuMjg1QzE1Ny40NDQgMzkyLjI4NSAxNjYgMzkwLjE3MSAxNzIgMzg1LjkzOUMxNzcuOTk5IDM4MS40ODcgMTgxIDM3NS41ODYgMTgxIDM2OC4yMzlDMTgxIDM2Mi44OTUgMTc5LjMzMyAzNTguNDQyIDE3NiAzNTQuODhDMTcyLjg4OSAzNTEuMzE4IDE2Ny4xMTEgMzQ4LjQyMiAxNTguNjY3IDM0Ni4xOTZMMTMwIDMzOS41MTdDMTE1LjU1NSAzMzUuOTU1IDEwNC43NzggMzMwLjQ5OSA5Ny42NjY1IDMyMy4xNTFDOTAuNzc3NSAzMTUuODA0IDg3LjMzMzQgMzA2LjExOSA4Ny4zMzM0IDI5NC4wOTZDODcuMzMzNCAyODQuMDc2IDg5Ljg4OSAyNzUuMzkyIDk0Ljk5OTYgMjY4LjA0NUMxMDAuMzMzIDI2MC42OTcgMTA3LjU1NSAyNTUuMDIgMTE2LjY2NiAyNTEuMDEyQzEyNiAyNDcuMDA0IDEzNi42NjcgMjQ1IDE0OC42NjYgMjQ1QzE2MC42NjcgMjQ1IDE3MSAyNDcuMTE2IDE3OS42NjcgMjUxLjM0NkMxODguNTU1IDI1NS41NzYgMTk1LjQ0NCAyNjEuNDc3IDIwMC4zMzMgMjY5LjA0N0MyMDUuNDQ0IDI3Ni42MTcgMjA4LjExMSAyODUuNjM0IDIwOC4zMzMgMjk2LjA5OUgxNzguMzMzQzE3OC4xMTEgMjg3LjYzOCAxNzUuMzMzIDI4MS4wNyAxNjkuOTk5IDI3Ni4zOTRDMTY0LjY2NiAyNzEuNzE5IDE1Ny4yMjIgMjY5LjM4MSAxNDcuNjY3IDI2OS4zODFDMTM3Ljg4OSAyNjkuMzgxIDEzMC4zMzMgMjcxLjQ5NiAxMjUgMjc1LjcyNkMxMTkuNjY2IDI3OS45NTcgMTE3IDI4NS43NDYgMTE3IDI5My4wOTNDMTE3IDMwNC4wMDMgMTI1IDMxMS40NjIgMTQxIDMxNS40N0wxNjkuNjY3IDMyMi40ODNDMTgzLjQ0NSAzMjUuNiAxOTMuNzc4IDMzMC43MjIgMjAwLjY2NyAzMzcuODQ3QzIwNy41NTUgMzQ0Ljc0OSAyMTEgMzU0LjIxMiAyMTEgMzY2LjIzNUMyMTEgMzc2LjQ3NyAyMDguMjIyIDM4NS40OTQgMjAyLjY2NiAzOTMuMjg3QzE5Ny4xMTEgNDAwLjg1NyAxODkuNDQ0IDQwNi43NTggMTc5LjY2NyA0MTAuOTg5QzE3MC4xMTEgNDE0Ljk5NiAxNTguNzc4IDQxNyAxNDUuNjY3IDQxN0MxMjYuNTU1IDQxNyAxMTEuMzMzIDQxMi4zMjUgOTkuOTk5NyA0MDIuOTczQzg4LjY2NjggMzkzLjYyMSA4MyAzODEuMTUzIDgzIDM2NS41NjdaIiBmaWxsPSJ3aGl0ZSIvPgo8cGF0aCBkPSJNMjMyLjI5MSA0MTNWMjUwLjA4MkMyNDQuNjg0IDI1NC42MTQgMjUwLjE0OCAyNTQuNjE0IDI2My4zNzEgMjUwLjA4MlY0MTNIMjMyLjI5MVpNMjQ3LjUgMjM5LjMxM0MyNDEuOTkgMjM5LjMxMyAyMzcuMTQgMjM3LjMxMyAyMzIuOTUyIDIzMy4zMTZDMjI4Ljk4NCAyMjkuMDk1IDIyNyAyMjQuMjA5IDIyNyAyMTguNjU2QzIyNyAyMTIuODgyIDIyOC45ODQgMjA3Ljk5NSAyMzIuOTUyIDIwMy45OTdDMjM3LjE0IDE5OS45OTkgMjQxLjk5IDE5OCAyNDcuNSAxOThDMjUzLjIzMSAxOTggMjU4LjA4IDE5OS45OTkgMjYyLjA0OSAyMDMuOTk3QzI2Ni4wMTYgMjA3Ljk5NSAyNjggMjEyLjg4MiAyNjggMjE4LjY1NkMyNjggMjI0LjIwOSAyNjYuMDE2IDIyOS4wOTUgMjYyLjA0OSAyMzMuMzE2QzI1OC4wOCAyMzcuMzEzIDI1My4yMzEgMjM5LjMxMyAyNDcuNSAyMzkuMzEzWiIgZmlsbD0id2hpdGUiLz4KPHBhdGggZD0iTTMxOS4zMzMgNDEzSDI4OFYyNDkuNjc2SDMxNlYyNzcuMjMzQzMxOS4zMzMgMjY4LjEwNCAzMjUuNzc4IDI2MC4zNjQgMzM0LjY2NyAyNTQuMzUyQzM0My43NzggMjQ4LjExNyAzNTQuNzc4IDI0NSAzNjcuNjY3IDI0NUMzODIuMTExIDI0NSAzOTQuMTEyIDI0OC44OTcgNDAzLjY2NyAyNTYuNjlDNDEzLjIyMiAyNjQuNDg0IDQxOS40NDQgMjc0LjgzNyA0MjIuMzM0IDI4Ny43NTJINDE2LjY2N0M0MTguODg5IDI3NC44MzcgNDI1IDI2NC40ODQgNDM1IDI1Ni42OUM0NDUgMjQ4Ljg5NyA0NTcuMzM0IDI0NSA0NzIgMjQ1QzQ5MC42NjYgMjQ1IDUwNS4zMzQgMjUwLjQ1NSA1MTYgMjYxLjM2NkM1MjYuNjY3IDI3Mi4yNzYgNTMyIDI4Ny4xOTUgNTMyIDMwNi4xMjFWNDEzSDUwMS4zMzNWMzEzLjgwNEM1MDEuMzMzIDMwMC44ODkgNDk4IDI5MC45ODEgNDkxLjMzMyAyODQuMDc4QzQ4NC44ODkgMjc2Ljk1MiA0NzYuMTExIDI3My4zOSA0NjUgMjczLjM5QzQ1Ny4yMjIgMjczLjM5IDQ1MC4zMzMgMjc1LjE3MSA0NDQuMzM0IDI3OC43MzRDNDM4LjU1NiAyODIuMDc0IDQzNCAyODYuOTcyIDQzMC42NjcgMjkzLjQzQzQyNy4zMzMgMjk5Ljg4NyA0MjUuNjY3IDMwNy40NTcgNDI1LjY2NyAzMTYuMTQxVjQxM0gzOTQuNjY3VjMxMy40NjlDMzk0LjY2NyAzMDAuNTU1IDM5MS40NDUgMjkwLjc1OCAzODUgMjg0LjA3OEMzNzguNTU2IDI3Ny4xNzUgMzY5Ljc3OCAyNzMuNzI0IDM1OC42NjcgMjczLjcyNEMzNTAuODg5IDI3My43MjQgMzQ0IDI3NS41MDUgMzM4IDI3OS4wNjhDMzMyLjIyMiAyODIuNDA4IDMyNy42NjcgMjg3LjMwNyAzMjQuMzMzIDI5My43NjNDMzIxIDI5OS45OTggMzE5LjMzMyAzMDcuNDU3IDMxOS4zMzMgMzE2LjE0MVY0MTNaIiBmaWxsPSJ3aGl0ZSIvPgo8L2c+CjxkZWZzPgo8Y2xpcFBhdGggaWQ9ImNsaXAwXzExNTlfMzEzIj4KPHJlY3Qgd2lkdGg9IjYxNiIgaGVpZ2h0PSI2MTYiIGZpbGw9IndoaXRlIi8+CjwvY2xpcFBhdGg+CjwvZGVmcz4KPC9zdmc+&logoColor=white" alt="Sim.ai"></a>
+<a href="https://sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/sim.ai-6F3DFA?logo=data:image/svg%2bxml;base64,PHN2ZyB3aWR0aD0iNjE2IiBoZWlnaHQ9IjYxNiIgdmlld0JveD0iMCAwIDYxNiA2MTYiIGZpbGw9Im5vbmUiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+CjxnIGNsaXAtcGF0aD0idXJsKCNjbGlwMF8xMTU5XzMxMykiPgo8cGF0aCBkPSJNNjE2IDBIMFY2MTZINjE2VjBaIiBmaWxsPSIjNkYzREZBIi8+CjxwYXRoIGQ9Ik04MyAzNjUuNTY3SDExM0MxMTMgMzczLjgwNSAxMTYgMzgwLjM3MyAxMjIgMzg1LjI3MkMxMjggMzg5Ljk0OCAxMzYuMTExIDM5Mi4yODUgMTQ2LjMzMyAzOTIuMjg1QzE1Ny40NDQgMzkyLjI4NSAxNjYgMzkwLjE3MSAxNzIgMzg1LjkzOUMxNzcuOTk5IDM4MS40ODcgMTgxIDM3NS41ODYgMTgxIDM2OC4yMzlDMTgxIDM2Mi44OTUgMTc5LjMzMyAzNTguNDQyIDE3NiAzNTQuODhDMTcyLjg4OSAzNTEuMzE4IDE2Ny4xMTEgMzQ4LjQyMiAxNTguNjY3IDM0Ni4xOTZMMTMwIDMzOS41MTdDMTE1LjU1NSAzMzUuOTU1IDEwNC43NzggMzMwLjQ5OSA5Ny42NjY1IDMyMy4xNTFDOTAuNzc3NSAzMTUuODA0IDg3LjMzMzQgMzA2LjExOSA4Ny4zMzM0IDI5NC4wOTZDODcuMzMzNCAyODQuMDc2IDg5Ljg4OSAyNzUuMzkyIDk0Ljk5OTYgMjY4LjA0NUMxMDAuMzMzIDI2MC42OTcgMTA3LjU1NSAyNTUuMDIgMTE2LjY2NiAyNTEuMDEyQzEyNiAyNDcuMDA0IDEzNi42NjcgMjQ1IDE0OC42NjYgMjQ1QzE2MC42NjcgMjQ1IDE3MSAyNDcuMTE2IDE3OS42NjcgMjUxLjM0NkMxODguNTU1IDI1NS41NzYgMTk1LjQ0NCAyNjEuNDc3IDIwMC4zMzMgMjY5LjA0N0MyMDUuNDQ0IDI3Ni42MTcgMjA4LjExMSAyODUuNjM0IDIwOC4zMzMgMjk2LjA5OUgxNzguMzMzQzE3OC4xMTEgMjg3LjYzOCAxNzUuMzMzIDI4MS4wNyAxNjkuOTk5IDI3Ni4zOTRDMTY0LjY2NiAyNzEuNzE5IDE1Ny4yMjIgMjY5LjM4MSAxNDcuNjY3IDI2OS4zODFDMTM3Ljg4OSAyNjkuMzgxIDEzMC4zMzMgMjcxLjQ5NiAxMjUgMjc1LjcyNkMxMTkuNjY2IDI3OS45NTcgMTE3IDI4NS43NDYgMTE3IDI5My4wOTNDMTE3IDMwNC4wMDMgMTI1IDMxMS40NjIgMTQxIDMxNS40N0wxNjkuNjY3IDMyMi40ODNDMTgzLjQ0NSAzMjUuNiAxOTMuNzc4IDMzMC43MjIgMjAwLjY2NyAzMzcuODQ3QzIwNy41NTUgMzQ0Ljc0OSAyMTEgMzU0LjIxMiAyMTEgMzY2LjIzNUMyMTEgMzc2LjQ3NyAyMDguMjIyIDM4NS40OTQgMjAyLjY2NiAzOTMuMjg3QzE5Ny4xMTEgNDAwLjg1NyAxODkuNDQ0IDQwNi43NTggMTc5LjY2NyA0MTAuOTg5QzE3MC4xMTEgNDE0Ljk5NiAxNTguNzc4IDQxNyAxNDUuNjY3IDQxN0MxMjYuNTU1IDQxNyAxMTEuMzMzIDQxMi4zMjUgOTkuOTk5NyA0MDIuOTczQzg4LjY2NjggMzkzLjYyMSA4MyAzODEuMTUzIDgzIDM2NS41NjdaIiBmaWxsPSJ3aGl0ZSIvPgo8cGF0aCBkPSJNMjMyLjI5MSA0MTNWMjUwLjA4MkMyNDQuNjg0IDI1NC42MTQgMjUwLjE0OCAyNTQuNjE0IDI2My4zNzEgMjUwLjA4MlY0MTNIMjMyLjI5MVpNMjQ3LjUgMjM5LjMxM0MyNDEuOTkgMjM5LjMxMyAyMzcuMTQgMjM3LjMxMyAyMzIuOTUyIDIzMy4zMTZDMjI4Ljk4NCAyMjkuMDk1IDIyNyAyMjQuMjA5IDIyNyAyMTguNjU2QzIyNyAyMTIuODgyIDIyOC45ODQgMjA3Ljk5NSAyMzIuOTUyIDIwMy45OTdDMjM3LjE0IDE5OS45OTkgMjQxLjk5IDE5OCAyNDcuNSAxOThDMjUzLjIzMSAxOTggMjU4LjA4IDE5OS45OTkgMjYyLjA0OSAyMDMuOTk3QzI2Ni4wMTYgMjA3Ljk5NSAyNjggMjEyLjg4MiAyNjggMjE4LjY1NkMyNjggMjI0LjIwOSAyNjYuMDE2IDIyOS4wOTUgMjYyLjA0OSAyMzMuMzE2QzI1OC4wOCAyMzcuMzEzIDI1My4yMzEgMjM5LjMxMyAyNDcuNSAyMzkuMzEzWiIgZmlsbD0id2hpdGUiLz4KPHBhdGggZD0iTTMxOS4zMzMgNDEzSDI4OFYyNDkuNjc2SDMxNlYyNzcuMjMzQzMxOS4zMzMgMjY4LjEwNCAzMjUuNzc4IDI2MC4zNjQgMzM0LjY2NyAyNTQuMzUyQzM0My43NzggMjQ4LjExNyAzNTQuNzc4IDI0NSAzNjcuNjY3IDI0NUMzODIuMTExIDI0NSAzOTQuMTEyIDI0OC44OTcgNDAzLjY2NyAyNTYuNjlDNDEzLjIyMiAyNjQuNDg0IDQxOS40NDQgMjc0LjgzNyA0MjIuMzM0IDI4Ny43NTJINDE2LjY2N0M0MTguODg5IDI3NC44MzcgNDI1IDI2NC40ODQgNDM1IDI1Ni42OUM0NDUgMjQ4Ljg5NyA0NTcuMzM0IDI0NSA0NzIgMjQ1QzQ5MC42NjYgMjQ1IDUwNS4zMzQgMjUwLjQ1NSA1MTYgMjYxLjM2NkM1MjYuNjY3IDI3Mi4yNzYgNTMyIDI4Ny4xOTUgNTMyIDMwNi4xMjFWNDEzSDUwMS4zMzNWMzEzLjgwNEM1MDEuMzMzIDMwMC44ODkgNDk4IDI5MC45ODEgNDkxLjMzMyAyODQuMDc4QzQ4NC44ODkgMjc2Ljk1MiA0NzYuMTExIDI3My4zOSA0NjUgMjczLjM5QzQ1Ny4yMjIgMjczLjM5IDQ1MC4zMzMgMjc1LjE3MSA0NDQuMzM0IDI3OC43MzRDNDM4LjU1NiAyODIuMDc0IDQzNCAyODYuOTcyIDQzMC42NjcgMjkzLjQzQzQyNy4zMzMgMjk5Ljg4NyA0MjUuNjY3IDMwNy40NTcgNDI1LjY2NyAzMTYuMTQxVjQxM0gzOTQuNjY3VjMxMy40NjlDMzk0LjY2NyAzMDAuNTU1IDM5MS40NDUgMjkwLjc1OCAzODUgMjg0LjA3OEMzNzguNTU2IDI3Ny4xNzUgMzY5Ljc3OCAyNzMuNzI0IDM1OC42NjcgMjczLjcyNEMzNTAuODg5IDI3My43MjQgMzQ0IDI3NS41MDUgMzM4IDI3OS4wNjhDMzMyLjIyMiAyODIuNDA4IDMyNy42NjcgMjg3LjMwNyAzMjQuMzMzIDI5My43NjNDMzIxIDI5OS45OTggMzE5LjMzMyAzMDcuNDU3IDMxOS4zMzMgMzE2LjE0MVY0MTNaIiBmaWxsPSJ3aGl0ZSIvPgo8L2c+CjxkZWZzPgo8Y2xpcFBhdGggaWQ9ImNsaXAwXzExNTlfMzEzIj4KPHJlY3Qgd2lkdGg9IjYxNiIgaGVpZ2h0PSI2MTYiIGZpbGw9IndoaXRlIi8+CjwvY2xpcFBhdGg+CjwvZGVmcz4KPC9zdmc+Cg==&logoColor=white" alt="Sim.ai"></a>
 
 ### Self-hosted: NPM Package
 
@@ -74,11 +70,43 @@ docker compose -f docker-compose.prod.yml up -d
 
 Open [http://localhost:3000](http://localhost:3000)
 
-#### Background worker note
+#### Using Local Models with Ollama
 
-The Docker Compose stack starts a dedicated worker container by default. If `REDIS_URL` is not configured, the worker will start, log that it is idle, and do no queue processing. This is expected. Queue-backed API, webhook, and schedule execution requires Redis; installs without Redis continue to use the inline execution path.
+Run Sim with local AI models using [Ollama](https://ollama.ai) - no external APIs required:
 
-Sim also supports local models via [Ollama](https://ollama.ai) and [vLLM](https://docs.vllm.ai/) — see the [Docker self-hosting docs](https://docs.sim.ai/self-hosting/docker) for setup details.
+```bash
+# Start with GPU support (automatically downloads gemma3:4b model)
+docker compose -f docker-compose.ollama.yml --profile setup up -d
+
+# For CPU-only systems:
+docker compose -f docker-compose.ollama.yml --profile cpu --profile setup up -d
+```
+
+Wait for the model to download, then visit [http://localhost:3000](http://localhost:3000). Add more models with:
+```bash
+docker compose -f docker-compose.ollama.yml exec ollama ollama pull llama3.1:8b
+```
+
+#### Using an External Ollama Instance
+
+If Ollama is running on your host machine, use `host.docker.internal` instead of `localhost`:
+
+```bash
+OLLAMA_URL=http://host.docker.internal:11434 docker compose -f docker-compose.prod.yml up -d
+```
+
+On Linux, use your host's IP address or add `extra_hosts: ["host.docker.internal:host-gateway"]` to the compose file.
+
+#### Using vLLM
+
+Sim supports [vLLM](https://docs.vllm.ai/) for self-hosted models. Set `VLLM_BASE_URL` and optionally `VLLM_API_KEY` in your environment.
+
+### Self-hosted: Dev Containers
+
+1. Open VS Code with the [Remote - Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
+2. Open the project and click "Reopen in Container" when prompted
+3. Run `bun run dev:full` in the terminal or use the `sim-start` alias
+   - This starts both the main application and the realtime socket server
 
 ### Self-hosted: Manual Setup
 
@@ -90,7 +118,6 @@ Sim also supports local models via [Ollama](https://ollama.ai) and [vLLM](https:
 git clone https://github.com/simstudioai/sim.git
 cd sim
 bun install
-bun run prepare  # Set up pre-commit hooks
 ```
 
 2. Set up PostgreSQL with pgvector:
@@ -105,11 +132,6 @@ Or install manually via the [pgvector guide](https://github.com/pgvector/pgvecto
 
 ```bash
 cp apps/sim/.env.example apps/sim/.env
-# Create your secrets
-perl -i -pe "s/your_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env
-perl -i -pe "s/your_internal_api_secret/$(openssl rand -hex 32)/" apps/sim/.env
-perl -i -pe "s/your_api_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env
-# DB configs for migration
 cp packages/db/.env.example packages/db/.env
 # Edit both .env files to set DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio"
 ```
@@ -117,18 +139,16 @@ cp packages/db/.env.example packages/db/.env
 4. Run migrations:
 
 ```bash
-cd packages/db && bun run db:migrate
+cd packages/db && bunx drizzle-kit migrate --config=./drizzle.config.ts
 ```
 
 5. Start development servers:
 
 ```bash
-bun run dev:full  # Starts Next.js app, realtime socket server, and the BullMQ worker
+bun run dev:full  # Starts both Next.js app and realtime socket server
 ```
 
-If `REDIS_URL` is not configured, the worker will remain idle and execution continues inline.
-
-Or run separately: `bun run dev` (Next.js), `cd apps/sim && bun run dev:sockets` (realtime), and `cd apps/sim && bun run worker` (BullMQ worker).
+Or run separately: `bun run dev` (Next.js) and `cd apps/sim && bun run dev:sockets` (realtime).
 
 ## Copilot API Keys
 
@@ -139,7 +159,18 @@ Copilot is a Sim-managed service. To use Copilot on a self-hosted instance:
 
 ## Environment Variables
 
-See the [environment variables reference](https://docs.sim.ai/self-hosting/environment-variables) for the full list, or [`apps/sim/.env.example`](apps/sim/.env.example) for defaults.
+Key environment variables for self-hosted deployments. See [`.env.example`](apps/sim/.env.example) for defaults or [`env.ts`](apps/sim/lib/core/config/env.ts) for the full list.
+
+| Variable | Required | Description |
+|----------|----------|-------------|
+| `DATABASE_URL` | Yes | PostgreSQL connection string with pgvector |
+| `BETTER_AUTH_SECRET` | Yes | Auth secret (`openssl rand -hex 32`) |
+| `BETTER_AUTH_URL` | Yes | Your app URL (e.g., `http://localhost:3000`) |
+| `NEXT_PUBLIC_APP_URL` | Yes | Public app URL (same as above) |
+| `ENCRYPTION_KEY` | Yes | Encrypts environment variables (`openssl rand -hex 32`) |
+| `INTERNAL_API_SECRET` | Yes | Encrypts internal API routes (`openssl rand -hex 32`) |
+| `API_ENCRYPTION_KEY` | Yes | Encrypts API keys (`openssl rand -hex 32`) |
+| `COPILOT_API_KEY` | No | API key from sim.ai for Copilot features |
 
 ## Tech Stack
 

apps/docs/app/layout.tsx

@@ -1,30 +1,17 @@
 import type { ReactNode } from 'react'
-import type { Viewport } from 'next'
 
 export default function RootLayout({ children }: { children: ReactNode }) {
   return children
 }
 
-export const viewport: Viewport = {
-  width: 'device-width',
-  initialScale: 1,
-  themeColor: [
-    { media: '(prefers-color-scheme: light)', color: '#ffffff' },
-    { media: '(prefers-color-scheme: dark)', color: '#0c0c0c' },
-  ],
-}
-
 export const metadata = {
   metadataBase: new URL('https://docs.sim.ai'),
   title: {
     default: 'Sim Documentation — Build AI Agents & Run Your Agentic Workforce',
-    template: '%s | Sim Docs',
+    template: '%s',
   },
   description:
     'Documentation for Sim — the open-source platform to build AI agents and run your agentic workforce. Connect 1,000+ integrations and LLMs to deploy and orchestrate agentic workflows.',
-  applicationName: 'Sim Docs',
-  generator: 'Next.js',
-  referrer: 'origin-when-cross-origin' as const,
   keywords: [
     'AI agents',
     'agentic workforce',
@@ -50,28 +37,17 @@ export const metadata = {
   manifest: '/favicon/site.webmanifest',
   icons: {
     icon: [
-      { url: '/icon.svg', type: 'image/svg+xml', sizes: 'any' },
       { url: '/favicon/favicon-16x16.png', sizes: '16x16', type: 'image/png' },
       { url: '/favicon/favicon-32x32.png', sizes: '32x32', type: 'image/png' },
-      { url: '/favicon/android-chrome-192x192.png', sizes: '192x192', type: 'image/png' },
-      { url: '/favicon/android-chrome-512x512.png', sizes: '512x512', type: 'image/png' },
     ],
     apple: '/favicon/apple-touch-icon.png',
-    shortcut: '/icon.svg',
+    shortcut: '/favicon/favicon.ico',
   },
   appleWebApp: {
     capable: true,
     statusBarStyle: 'default',
     title: 'Sim Docs',
   },
-  formatDetection: {
-    telephone: false,
-  },
-  other: {
-    'apple-mobile-web-app-capable': 'yes',
-    'mobile-web-app-capable': 'yes',
-    'msapplication-TileColor': '#33C482',
-  },
   openGraph: {
     type: 'website',
     locale: 'en_US',

apps/docs/components/ui/animated-blocks.tsx

@@ -1,7 +1,18 @@
-import { memo } from 'react'
+'use client'
 
+import { memo, useEffect, useState } from 'react'
+
+/** Shared corner radius from Figma export for all decorative rects. */
 const RX = '2.59574'
 
+const ENTER_STAGGER = 0.06
+const ENTER_DURATION = 0.3
+const EXIT_STAGGER = 0.12
+const EXIT_DURATION = 0.5
+const INITIAL_HOLD = 3000
+const HOLD_BETWEEN = 3000
+const TRANSITION_PAUSE = 400
+
 interface BlockRect {
   opacity: number
   width: string
@@ -12,6 +23,8 @@ interface BlockRect {
   transform?: string
 }
 
+type AnimState = 'visible' | 'exiting' | 'hidden'
+
 const RECTS = {
   topRight: [
     { opacity: 1, x: '0', y: '0', width: '16.8626', height: '33.7252', fill: '#2ABBF8' },
@@ -54,33 +67,76 @@ const RECTS = {
       fill: '#FA4EDF',
     },
   ],
-  bottomLeft: [
-    { opacity: 1, x: '0', y: '0', width: '16.8626', height: '33.7252', fill: '#2ABBF8' },
-    { opacity: 0.6, x: '0', y: '0', width: '85.3433', height: '16.8626', fill: '#2ABBF8' },
-    { opacity: 1, x: '0', y: '0', width: '16.8626', height: '16.8626', fill: '#2ABBF8' },
-    { opacity: 0.6, x: '34.2403', y: '0', width: '34.2403', height: '33.7252', fill: '#2ABBF8' },
-    { opacity: 1, x: '34.2403', y: '0', width: '16.8626', height: '16.8626', fill: '#2ABBF8' },
+  left: [
+    {
+      opacity: 0.6,
+      width: '34.240',
+      height: '33.725',
+      fill: '#FA4EDF',
+      transform: 'matrix(0 1 1 0 0 0)',
+    },
+    {
+      opacity: 0.6,
+      width: '16.8626',
+      height: '68.480',
+      fill: '#FA4EDF',
+      transform: 'matrix(-1 0 0 1 33.727 0)',
+    },
     {
       opacity: 1,
-      x: '51.6188',
-      y: '16.8626',
       width: '16.8626',
       height: '16.8626',
-      fill: '#2ABBF8',
+      fill: '#FA4EDF',
+      transform: 'matrix(-1 0 0 1 33.727 17.378)',
+    },
+    {
+      opacity: 0.6,
+      width: '16.8626',
+      height: '33.986',
+      fill: '#FA4EDF',
+      transform: 'matrix(0 1 1 0 0 51.616)',
+    },
+    {
+      opacity: 0.6,
+      width: '16.8626',
+      height: '140.507',
+      fill: '#00F701',
+      transform: 'matrix(-1 0 0 1 33.986 85.335)',
+    },
+    {
+      opacity: 0.4,
+      x: '17.119',
+      y: '136.962',
+      width: '34.240',
+      height: '16.8626',
+      fill: '#FFCC02',
+      transform: 'rotate(-90 17.119 136.962)',
+    },
+    {
+      opacity: 1,
+      x: '17.119',
+      y: '136.962',
+      width: '16.8626',
+      height: '16.8626',
+      fill: '#FFCC02',
+      transform: 'rotate(-90 17.119 136.962)',
+    },
+    {
+      opacity: 0.5,
+      width: '34.240',
+      height: '33.725',
+      fill: '#00F701',
+      transform: 'matrix(0 1 1 0 0.257 153.825)',
     },
-    { opacity: 1, x: '68.4812', y: '0', width: '54.6502', height: '16.8626', fill: '#00F701' },
-    { opacity: 0.6, x: '106.268', y: '0', width: '34.2403', height: '33.7252', fill: '#00F701' },
-    { opacity: 0.6, x: '106.268', y: '0', width: '51.103', height: '16.8626', fill: '#00F701' },
     {
       opacity: 1,
-      x: '123.6484',
-      y: '16.8626',
       width: '16.8626',
       height: '16.8626',
       fill: '#00F701',
+      transform: 'matrix(0 1 1 0 0.257 153.825)',
     },
   ],
-  bottomRight: [
+  right: [
     {
       opacity: 0.6,
       width: '16.8626',
@@ -119,33 +175,68 @@ const RECTS = {
     {
       opacity: 0.6,
       width: '16.8626',
-      height: '34.24',
+      height: '33.726',
+      fill: '#FA4EDF',
+      transform: 'matrix(0 1 1 0 0.012 68.510)',
+    },
+    {
+      opacity: 0.6,
+      width: '16.8626',
+      height: '102.384',
       fill: '#2ABBF8',
-      transform: 'matrix(-1 0 0 1 33.787 68)',
+      transform: 'matrix(-1 0 0 1 33.787 102.384)',
     },
     {
       opacity: 0.4,
+      x: '17.131',
+      y: '153.859',
+      width: '34.241',
+      height: '16.8626',
+      fill: '#00F701',
+      transform: 'rotate(-90 17.131 153.859)',
+    },
+    {
+      opacity: 1,
+      x: '17.131',
+      y: '153.859',
       width: '16.8626',
       height: '16.8626',
-      fill: '#1A8FCC',
-      transform: 'matrix(-1 0 0 1 33.787 85)',
+      fill: '#00F701',
+      transform: 'rotate(-90 17.131 153.859)',
     },
   ],
 } as const satisfies Record<string, readonly BlockRect[]>
 
-const GLOBAL_OPACITY = 0.55
+type Position = keyof typeof RECTS
+
+function enterTime(pos: Position): number {
+  return (RECTS[pos].length - 1) * ENTER_STAGGER + ENTER_DURATION
+}
+
+function exitTime(pos: Position): number {
+  return (RECTS[pos].length - 1) * EXIT_STAGGER + EXIT_DURATION
+}
+
+interface BlockGroupProps {
+  width: number
+  height: number
+  viewBox: string
+  rects: readonly BlockRect[]
+  animState: AnimState
+  globalOpacity: number
+}
 
 const BlockGroup = memo(function BlockGroup({
   width,
   height,
   viewBox,
   rects,
-}: {
-  width: number
-  height: number
-  viewBox: string
-  rects: readonly BlockRect[]
-}) {
+  animState,
+  globalOpacity,
+}: BlockGroupProps) {
+  const isVisible = animState === 'visible'
+  const isExiting = animState === 'exiting'
+
   return (
     <svg
       width={width}
@@ -154,7 +245,7 @@ const BlockGroup = memo(function BlockGroup({
       fill='none'
       xmlns='http://www.w3.org/2000/svg'
       className='h-auto w-full'
-      style={{ opacity: GLOBAL_OPACITY }}
+      style={{ opacity: globalOpacity }}
     >
       {rects.map((r, i) => (
         <rect
@@ -166,29 +257,114 @@ const BlockGroup = memo(function BlockGroup({
           rx={RX}
           fill={r.fill}
           transform={r.transform}
-          opacity={r.opacity}
+          style={{
+            opacity: isVisible ? r.opacity : 0,
+            transition: `opacity ${isExiting ? EXIT_DURATION : ENTER_DURATION}s ease ${
+              isVisible ? i * ENTER_STAGGER : isExiting ? i * EXIT_STAGGER : 0
+            }s`,
+          }}
         />
       ))}
     </svg>
   )
 })
 
+function useGroupState(): [AnimState, (s: AnimState) => void] {
+  return useState<AnimState>('visible')
+}
+
+function useBlockCycle() {
+  const [topRight, setTopRight] = useGroupState()
+  const [left, setLeft] = useGroupState()
+  const [right, setRight] = useGroupState()
+
+  useEffect(() => {
+    if (typeof window !== 'undefined' && !window.matchMedia('(min-width: 1024px)').matches) return
+
+    const cancelled = { current: false }
+    const wait = (ms: number) => new Promise<void>((r) => setTimeout(r, ms))
+
+    async function exit(setter: (s: AnimState) => void, pos: Position, pauseAfter: number) {
+      if (cancelled.current) return
+      setter('exiting')
+      await wait(exitTime(pos) * 1000)
+      if (cancelled.current) return
+      setter('hidden')
+      await wait(pauseAfter)
+    }
+
+    async function enter(setter: (s: AnimState) => void, pos: Position, pauseAfter: number) {
+      if (cancelled.current) return
+      setter('visible')
+      await wait(enterTime(pos) * 1000 + pauseAfter)
+    }
+
+    const run = async () => {
+      await wait(INITIAL_HOLD)
+
+      while (!cancelled.current) {
+        await exit(setTopRight, 'topRight', TRANSITION_PAUSE)
+        await exit(setLeft, 'left', HOLD_BETWEEN)
+        await enter(setLeft, 'left', TRANSITION_PAUSE)
+        await enter(setTopRight, 'topRight', TRANSITION_PAUSE)
+        await exit(setRight, 'right', HOLD_BETWEEN)
+        await enter(setRight, 'right', HOLD_BETWEEN)
+      }
+    }
+
+    run()
+    return () => {
+      cancelled.current = true
+    }
+  }, [])
+
+  return { topRight, left, right } as const
+}
+
+/**
+ * Ambient animated block decorations for the docs layout.
+ * Adapts the landing page's colorful block patterns with slightly reduced
+ * opacity and the same staggered enter/exit animation cycle.
+ */
 export function AnimatedBlocks() {
+  const states = useBlockCycle()
+
   return (
     <div
       className='pointer-events-none fixed inset-0 z-0 hidden overflow-hidden lg:block'
       aria-hidden='true'
     >
       <div className='absolute top-[93px] right-0 w-[calc(140px+10.76vw)] max-w-[295px]'>
-        <BlockGroup width={295} height={34} viewBox='0 0 295 34' rects={RECTS.topRight} />
+        <BlockGroup
+          width={295}
+          height={34}
+          viewBox='0 0 295 34'
+          rects={RECTS.topRight}
+          animState={states.topRight}
+          globalOpacity={0.75}
+        />
       </div>
 
-      <div className='-left-24 absolute bottom-0 w-[calc(140px+10.76vw)] max-w-[295px] rotate-180'>
-        <BlockGroup width={295} height={34} viewBox='0 0 295 34' rects={RECTS.bottomLeft} />
+      <div className='-translate-y-1/2 absolute top-[50%] left-0 w-[calc(16px+1.25vw)] max-w-[34px] scale-x-[-1]'>
+        <BlockGroup
+          width={34}
+          height={226}
+          viewBox='0 0 34 226.021'
+          rects={RECTS.left}
+          animState={states.left}
+          globalOpacity={0.75}
+        />
       </div>
 
-      <div className='-bottom-2 absolute right-0 w-[calc(16px+1.25vw)] max-w-[34px]'>
-        <BlockGroup width={34} height={102} viewBox='0 0 34 102' rects={RECTS.bottomRight} />
+      <div className='-translate-y-1/2 absolute top-[50%] right-0 w-[calc(16px+1.25vw)] max-w-[34px]'>
+        <BlockGroup
+          width={34}
+          height={205}
+          viewBox='0 0 34 204.769'
+          rects={RECTS.right}
+          animState={states.right}
+          globalOpacity={0.75}
+        />
       </div>
     </div>
   )

apps/docs/components/ui/icon-mapping.ts

@@ -5,7 +5,6 @@
 import type { ComponentType, SVGProps } from 'react'
 import {
   A2AIcon,
-  AgentMailIcon,
   AhrefsIcon,
   AirtableIcon,
   AirweaveIcon,
@@ -17,8 +16,6 @@ import {
   AsanaIcon,
   AshbyIcon,
   AttioIcon,
-  AzureIcon,
-  BoxCompanyIcon,
   BrainIcon,
   BrandfetchIcon,
   BrowserUseIcon,
@@ -27,9 +24,7 @@ import {
   CirclebackIcon,
   ClayIcon,
   ClerkIcon,
-  CloudFormationIcon,
   CloudflareIcon,
-  CloudWatchIcon,
   ConfluenceIcon,
   CursorIcon,
   DatabricksIcon,
@@ -37,7 +32,6 @@ import {
   DevinIcon,
   DiscordIcon,
   DocumentIcon,
-  DocuSignIcon,
   DropboxIcon,
   DsPyIcon,
   DubIcon,
@@ -48,7 +42,6 @@ import {
   EnrichSoIcon,
   EvernoteIcon,
   ExaAIIcon,
-  ExtendIcon,
   EyeIcon,
   FathomIcon,
   FirecrawlIcon,
@@ -78,7 +71,6 @@ import {
   GoogleVaultIcon,
   GrafanaIcon,
   GrainIcon,
-  GranolaIcon,
   GreenhouseIcon,
   GreptileIcon,
   HexIcon,
@@ -87,15 +79,12 @@ import {
   HunterIOIcon,
   ImageIcon,
   IncidentioIcon,
-  InfisicalIcon,
   IntercomIcon,
   JinaAIIcon,
   JiraIcon,
   JiraServiceManagementIcon,
   KalshiIcon,
-  KetchIcon,
   LangsmithIcon,
-  LaunchDarklyIcon,
   LemlistIcon,
   LinearIcon,
   LinkedInIcon,
@@ -118,7 +107,6 @@ import {
   Neo4jIcon,
   NotionIcon,
   ObsidianIcon,
-  OktaIcon,
   OnePasswordIcon,
   OpenAIIcon,
   OutlookIcon,
@@ -131,22 +119,17 @@ import {
   PolymarketIcon,
   PostgresIcon,
   PosthogIcon,
-  ProfoundIcon,
   PulseIcon,
   QdrantIcon,
-  QuiverIcon,
   RDSIcon,
   RedditIcon,
   RedisIcon,
   ReductoIcon,
   ResendIcon,
   RevenueCatIcon,
-  RipplingIcon,
-  RootlyIcon,
   S3Icon,
   SalesforceIcon,
   SearchIcon,
-  SecretsManagerIcon,
   SendgridIcon,
   SentryIcon,
   SerperIcon,
@@ -162,7 +145,6 @@ import {
   StagehandIcon,
   StripeIcon,
   SupabaseIcon,
-  TailscaleIcon,
   TavilyIcon,
   TelegramIcon,
   TextractIcon,
@@ -180,7 +162,6 @@ import {
   WhatsAppIcon,
   WikipediaIcon,
   WordpressIcon,
-  WorkdayIcon,
   xIcon,
   YouTubeIcon,
   ZendeskIcon,
@@ -192,7 +173,6 @@ type IconComponent = ComponentType<SVGProps<SVGSVGElement>>
 
 export const blockTypeToIconMap: Record<string, IconComponent> = {
   a2a: A2AIcon,
-  agentmail: AgentMailIcon,
   ahrefs: AhrefsIcon,
   airtable: AirtableIcon,
   airweave: AirweaveIcon,
@@ -204,7 +184,6 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   asana: AsanaIcon,
   ashby: AshbyIcon,
   attio: AttioIcon,
-  box: BoxCompanyIcon,
   brandfetch: BrandfetchIcon,
   browser_use: BrowserUseIcon,
   calcom: CalComIcon,
@@ -213,15 +192,12 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   clay: ClayIcon,
   clerk: ClerkIcon,
   cloudflare: CloudflareIcon,
-  cloudformation: CloudFormationIcon,
-  cloudwatch: CloudWatchIcon,
   confluence_v2: ConfluenceIcon,
   cursor_v2: CursorIcon,
   databricks: DatabricksIcon,
   datadog: DatadogIcon,
   devin: DevinIcon,
   discord: DiscordIcon,
-  docusign: DocuSignIcon,
   dropbox: DropboxIcon,
   dspy: DsPyIcon,
   dub: DubIcon,
@@ -232,7 +208,6 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   enrich: EnrichSoIcon,
   evernote: EvernoteIcon,
   exa: ExaAIIcon,
-  extend_v2: ExtendIcon,
   fathom: FathomIcon,
   file_v3: DocumentIcon,
   firecrawl: FirecrawlIcon,
@@ -262,7 +237,6 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   google_vault: GoogleVaultIcon,
   grafana: GrafanaIcon,
   grain: GrainIcon,
-  granola: GranolaIcon,
   greenhouse: GreenhouseIcon,
   greptile: GreptileIcon,
   hex: HexIcon,
@@ -272,16 +246,13 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   image_generator: ImageIcon,
   imap: MailServerIcon,
   incidentio: IncidentioIcon,
-  infisical: InfisicalIcon,
   intercom_v2: IntercomIcon,
   jina: JinaAIIcon,
   jira: JiraIcon,
   jira_service_management: JiraServiceManagementIcon,
   kalshi_v2: KalshiIcon,
-  ketch: KetchIcon,
   knowledge: PackageSearchIcon,
   langsmith: LangsmithIcon,
-  launchdarkly: LaunchDarklyIcon,
   lemlist: LemlistIcon,
   linear: LinearIcon,
   linkedin: LinkedInIcon,
@@ -292,7 +263,6 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   mailgun: MailgunIcon,
   mem0: Mem0Icon,
   memory: BrainIcon,
-  microsoft_ad: AzureIcon,
   microsoft_dataverse: MicrosoftDataverseIcon,
   microsoft_excel_v2: MicrosoftExcelIcon,
   microsoft_planner: MicrosoftPlannerIcon,
@@ -303,7 +273,6 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   neo4j: Neo4jIcon,
   notion_v2: NotionIcon,
   obsidian: ObsidianIcon,
-  okta: OktaIcon,
   onedrive: MicrosoftOneDriveIcon,
   onepassword: OnePasswordIcon,
   openai: OpenAIIcon,
@@ -316,22 +285,17 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   polymarket: PolymarketIcon,
   postgresql: PostgresIcon,
   posthog: PosthogIcon,
-  profound: ProfoundIcon,
   pulse_v2: PulseIcon,
   qdrant: QdrantIcon,
-  quiver: QuiverIcon,
   rds: RDSIcon,
   reddit: RedditIcon,
   redis: RedisIcon,
   reducto_v2: ReductoIcon,
   resend: ResendIcon,
   revenuecat: RevenueCatIcon,
-  rippling: RipplingIcon,
-  rootly: RootlyIcon,
   s3: S3Icon,
   salesforce: SalesforceIcon,
   search: SearchIcon,
-  secrets_manager: SecretsManagerIcon,
   sendgrid: SendgridIcon,
   sentry: SentryIcon,
   serper: SerperIcon,
@@ -348,7 +312,6 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   stripe: StripeIcon,
   stt_v2: STTIcon,
   supabase: SupabaseIcon,
-  tailscale: TailscaleIcon,
   tavily: TavilyIcon,
   telegram: TelegramIcon,
   textract_v2: TextractIcon,
@@ -368,7 +331,6 @@ export const blockTypeToIconMap: Record<string, IconComponent> = {
   whatsapp: WhatsAppIcon,
   wikipedia: WikipediaIcon,
   wordpress: WordpressIcon,
-  workday: WorkdayIcon,
   x: xIcon,
   youtube: YouTubeIcon,
   zendesk: ZendeskIcon,

apps/docs/content/docs/de/blocks/guardrails.mdx

@@ -131,7 +131,7 @@ Erkennt personenbezogene Daten mithilfe von Microsoft Presidio. Unterstützt üb
 **Anwendungsfälle:**
 - Blockieren von Inhalten mit sensiblen persönlichen Informationen
 - Maskieren von personenbezogenen Daten vor der Protokollierung oder Speicherung
-- Einhaltung der DSGVO und anderer Datenschutzbestimmungen
+- Einhaltung der DSGVO, HIPAA und anderer Datenschutzbestimmungen
 - Bereinigung von Benutzereingaben vor der Verarbeitung
 
 ## Konfiguration

apps/docs/content/docs/en/blocks/credential.mdx

@@ -1,150 +0,0 @@
----
-title: Credential
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { Image } from '@/components/ui/image'
-import { FAQ } from '@/components/ui/faq'
-
-The Credential block has two operations: **Select Credential** picks a single OAuth credential and outputs its ID reference for downstream blocks; **List Credentials** returns all OAuth credentials in the workspace (optionally filtered by provider) as an array for iteration.
-
-<div className="flex justify-center">
-  <Image
-    src="/static/blocks/credential.png"
-    alt="Credential Block"
-    width={400}
-    height={300}
-    className="my-6"
-  />
-</div>
-
-<Callout>
-  The Credential block outputs credential **ID references**, not secrets. Downstream blocks receive the ID and resolve the actual OAuth token securely during their own execution.
-</Callout>
-
-## Configuration Options
-
-### Operation
-
-| Value | Description |
-|---|---|
-| **Select Credential** | Pick one OAuth credential and output its reference — use this to wire a single credential into downstream blocks |
-| **List Credentials** | Return all OAuth credentials in the workspace as an array — use this with a ForEach loop |
-
-### Credential (Select operation)
-
-Select an OAuth credential from your workspace. The dropdown shows all connected OAuth accounts (Google, GitHub, Slack, etc.).
-
-In advanced mode, paste a credential ID directly. You can copy a credential ID from your workspace's Credentials settings page.
-
-### Provider (List operation)
-
-Filter the returned OAuth credentials by provider. Select one or more providers from the dropdown — only providers you have credentials for will appear. Leave empty to return all OAuth credentials.
-
-| Example | Returns |
-|---|---|
-| Gmail | Gmail credentials only |
-| Slack | Slack credentials only |
-| Gmail + Slack | Gmail and Slack credentials |
-
-## Outputs
-
-<Tabs items={['Select Credential', 'List Credentials']}>
-  <Tab>
-    | Output | Type | Description |
-    |---|---|---|
-    | `credentialId` | `string` | The credential ID — pipe this into other blocks' credential fields |
-    | `displayName` | `string` | Human-readable name (e.g. "waleed@company.com") |
-    | `providerId` | `string` | OAuth provider ID (e.g. `google-email`, `slack`) |
-  </Tab>
-  <Tab>
-    | Output | Type | Description |
-    |---|---|---|
-    | `credentials` | `json` | Array of OAuth credential objects (see shape below) |
-    | `count` | `number` | Number of credentials returned |
-
-    Each object in the `credentials` array:
-
-    | Field | Type | Description |
-    |---|---|---|
-    | `credentialId` | `string` | The credential ID |
-    | `displayName` | `string` | Human-readable name |
-    | `providerId` | `string` | OAuth provider ID |
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-**Shared credential across multiple blocks** — Define once, use everywhere
-```
-Credential (Select, Google) → Gmail (Send) & Google Drive (Upload) & Google Calendar (Create)
-```
-
-**Multi-account workflows** — Route to different credentials based on logic
-```
-Agent (Determine account) → Condition → Credential A or Credential B → Slack (Post)
-```
-
-**Iterate over all Gmail accounts**
-```
-Credential (List, Provider: Gmail) → ForEach Loop → Gmail (Send) using <loop.currentItem.credentialId>
-```
-
-<div className="flex justify-center">
-  <Image
-    src="/static/blocks/credential-loop.png"
-    alt="Credential List wired into a ForEach Loop"
-    width={900}
-    height={400}
-    className="my-6"
-  />
-</div>
-
-## How to wire a Credential block
-
-### Select Credential
-
-1. Drop a **Credential** block and select your OAuth credential from the picker
-2. In the downstream block, switch to **advanced mode** on its credential field
-3. Enter `<credentialBlockName.credentialId>` as the value
-
-<Tabs items={['Gmail', 'Slack']}>
-  <Tab>
-    In the Gmail block's credential field (advanced mode):
-    ```
-    <myCredential.credentialId>
-    ```
-  </Tab>
-  <Tab>
-    In the Slack block's credential field (advanced mode):
-    ```
-    <myCredential.credentialId>
-    ```
-  </Tab>
-</Tabs>
-
-### List Credentials
-
-1. Drop a **Credential** block, set Operation to **List Credentials**
-2. Optionally select one or more **Providers** to narrow results (only your connected providers appear)
-3. Wire `<credentialBlockName.credentials>` into a **ForEach Loop** as the items source
-4. Inside the loop, reference `<loop.currentItem.credentialId>` in downstream blocks' credential fields
-
-## Best Practices
-
-- **Define once, reference many times**: When five blocks use the same Google account, use one Credential block and wire all five to `<credential.credentialId>` instead of selecting the account five times
-- **Outputs are safe to log**: The `credentialId` output is a UUID reference, not a secret. It is safe to inspect in execution logs
-- **Use for environment switching**: Pair with a Condition block to route to a production or staging OAuth credential based on a workflow variable
-- **Advanced mode is required**: Downstream blocks must be in advanced mode on their credential field to accept a dynamic reference
-- **Use List + ForEach for fan-out**: When you need to run the same action across all accounts of a provider, List Credentials feeds naturally into a ForEach loop
-- **Narrow by provider**: Use the Provider multiselect to filter to specific services — only providers you have credentials for are shown
-
-<FAQ items={[
-  { question: "Does the Credential block expose my secret or token?", answer: "No. The block outputs a credential ID (a UUID), not the actual OAuth token. Downstream blocks receive the ID and resolve the token securely in their own execution context. Secrets never appear in workflow state, logs, or the canvas." },
-  { question: "What credential types does it support?", answer: "OAuth connected accounts only (Google, GitHub, Slack, etc.). Environment variables and service accounts cannot be resolved by ID in downstream blocks, so they are not supported." },
-  { question: "How is Select different from just copying a credential ID into advanced mode?", answer: "Functionally identical — both pass the same credential ID to the downstream block. The Credential block adds value when you need to use one credential in many blocks (change it once), or when you want to select between credentials dynamically using a Condition block." },
-  { question: "Can I list all OAuth credentials in my workspace?", answer: "Yes. Set the Operation to 'List Credentials'. Optionally filter by provider using the Provider multiselect. Wire the credentials output into a ForEach loop to process each credential individually." },
-  { question: "Can I use a Credential block output in a Function block?", answer: "Yes. Reference <credential.credentialId> in your Function block's code. Note that the function will receive the raw UUID string — if you need the resolved token, the downstream block must handle the resolution (as integration blocks do). The Function block does not automatically resolve credential IDs." },
-  { question: "What happens if the credential is deleted?", answer: "The Select operation will throw an error at execution time: 'Credential not found'. The List operation will simply omit the deleted credential from the results. Update the Credential block to select a valid credential before re-running." },
-]} />

apps/docs/content/docs/en/blocks/guardrails.mdx

@@ -132,7 +132,7 @@ Detects personally identifiable information using Microsoft Presidio. Supports o
 **Use Cases:**
 - Block content containing sensitive personal information
 - Mask PII before logging or storing data
-- Compliance with GDPR and other privacy regulations
+- Compliance with GDPR, HIPAA, and other privacy regulations
 - Sanitize user inputs before processing
 
 ## Configuration

apps/docs/content/docs/en/blocks/meta.json

@@ -4,7 +4,6 @@
     "agent",
     "api",
     "condition",
-    "credential",
     "evaluator",
     "function",
     "guardrails",

apps/docs/content/docs/en/blocks/response.mdx

@@ -20,7 +20,7 @@ The Response block formats and sends structured HTTP responses back to API calle
 </div>
 
 <Callout type="info">
-  Response blocks are exit points — when a Response block executes, it ends the workflow and sends the HTTP response immediately. Multiple Response blocks can be placed on different branches (e.g. after a Router or Condition), but only the first one to execute determines the API response.
+  Response blocks are terminal blocks - they end workflow execution and cannot connect to other blocks.
 </Callout>
 
 ## Configuration Options
@@ -77,11 +77,7 @@ Condition (Error Detected) → Router → Response (400/500, Error Details)
 
 ## Outputs
 
-Response blocks are exit points — when one executes, no further blocks run. The block defines outputs (`data`, `status`, `headers`) which are used to construct the HTTP response sent back to the API caller.
-
-<Callout type="warning">
-  If a Response block is placed on a parallel branch, there are no guarantees about whether other parallel blocks will run or not. Execution order across parallel branches is non-deterministic, so a parallel block may execute before or after the Response block on any given run. Avoid placing Response blocks in parallel with blocks that have important side effects.
-</Callout>
+Response blocks are terminal — no downstream blocks execute after them. However, the block does define outputs (`data`, `status`, `headers`) which are used to construct the HTTP response sent back to the API caller.
 
 ## Variable References
 
@@ -114,10 +110,10 @@ Use the `<variable.name>` syntax to dynamically insert workflow variables into y
 - **Validate variable references**: Ensure all referenced variables exist and contain the expected data types before the Response block executes
 
 <FAQ items={[
-  { question: "Can I have multiple Response blocks in a workflow?", answer: "Yes. You can place multiple Response blocks on different branches (e.g. after a Router or Condition block). The first Response block to execute determines the API response and ends the workflow. This is useful for returning different responses based on conditions — for example, a 200 on the success branch and a 500 on the error branch." },
+  { question: "Can I have multiple Response blocks in a workflow?", answer: "No. The Response block is a single-instance block — only one is allowed per workflow. If you need different responses for different conditions, use a Condition or Router block upstream to determine what data reaches the single Response block." },
   { question: "What triggers require a Response block?", answer: "The Response block is designed for use with the API Trigger. When your workflow is invoked via the API, the Response block sends the structured HTTP response back to the caller. Other trigger types (like webhooks or schedules) do not require a Response block." },
   { question: "What is the difference between Builder and Editor mode?", answer: "Builder mode provides a visual interface for constructing your response structure with fields and types. Editor mode gives you a raw JSON code editor where you can write the response body directly. Builder mode is recommended for most use cases." },
   { question: "What is the default status code?", answer: "If you do not specify a status code, the Response block defaults to 200 (OK). You can set any valid HTTP status code including error codes like 400, 404, or 500." },
-  { question: "Can the Response block connect to downstream blocks?", answer: "No. Response blocks are exit points — they end workflow execution and send the HTTP response. No further blocks can execute after a Response block." },
+  { question: "Can the Response block connect to downstream blocks?", answer: "No. Response blocks are terminal — they end workflow execution and send the HTTP response. No further blocks can be connected after a Response block." },
 ]} />
 

apps/docs/content/docs/en/credentials/google-service-account.mdx

@@ -1,206 +0,0 @@
----
-title: Google Service Accounts
-description: Set up Google service accounts with domain-wide delegation for Gmail, Sheets, Drive, Calendar, and other Google services
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Image } from '@/components/ui/image'
-import { FAQ } from '@/components/ui/faq'
-
-Google service accounts with domain-wide delegation let your workflows access Google APIs on behalf of users in your Google Workspace domain — without requiring each user to complete an OAuth consent flow. This is ideal for automated workflows that need to send emails, read spreadsheets, or manage files across your organization.
-
-For example, you could build a workflow that iterates through a list of employees, impersonates each one to read their Google Docs, and uploads the contents to a shared knowledge base — all without requiring any of those users to sign in.
-
-## Prerequisites
-
-Before adding a service account to Sim, you need to configure it in the Google Cloud Console and Google Workspace Admin Console.
-
-### 1. Create a Service Account in Google Cloud
-
-<Steps>
-  <Step>
-    Go to the [Google Cloud Console](https://console.cloud.google.com/) and select your project (or create one)
-  </Step>
-  <Step>
-    Navigate to **IAM & Admin** → **Service Accounts**
-  </Step>
-  <Step>
-    Click **Create Service Account**, give it a name and description, then click **Create and Continue**
-
-    <div className="flex justify-center">
-      <Image
-        src="/static/credentials/gcp-create-service-account.png"
-        alt="Google Cloud Console — Create service account form"
-        width={700}
-        height={500}
-        className="my-4"
-      />
-    </div>
-  </Step>
-  <Step>
-    Skip the optional role and user access steps and click **Done**
-  </Step>
-  <Step>
-    Click on the newly created service account, go to the **Keys** tab, and click **Add Key** → **Create new key**
-  </Step>
-  <Step>
-    Select **JSON** as the key type and click **Create**. A JSON key file will download — keep this safe
-
-    <div className="flex justify-center">
-      <Image
-        src="/static/credentials/gcp-create-private-key.png"
-        alt="Google Cloud Console — Create private key dialog with JSON selected"
-        width={700}
-        height={400}
-        className="my-4"
-      />
-    </div>
-  </Step>
-</Steps>
-
-<Callout type="warn">
-The JSON key file contains your service account's private key. Treat it like a password — do not commit it to source control or share it publicly.
-</Callout>
-
-### 2. Enable the Required APIs
-
-In the Google Cloud Console, go to **APIs & Services** → **Library** and enable the APIs for the services your workflows will use. See the [scopes reference](#scopes-reference) below for the full list of APIs by service.
-
-### 3. Set Up Domain-Wide Delegation
-
-<Steps>
-  <Step>
-    In the Google Cloud Console, go to **IAM & Admin** → **Service Accounts**, click on your service account, and copy the **Client ID** (the numeric ID, not the email)
-  </Step>
-  <Step>
-    Open the [Google Workspace Admin Console](https://admin.google.com/) and navigate to **Security** → **Access and data control** → **API controls**
-  </Step>
-  <Step>
-    Click **Manage Domain Wide Delegation**, then click **Add new**
-  </Step>
-  <Step>
-    Paste the **Client ID** from your service account, then add the OAuth scopes for the services your workflows need. Copy the full scope URLs from the [scopes reference](#scopes-reference) below — only authorize scopes for services you plan to use.
-
-    <div className="flex justify-center">
-      <Image
-        src="/static/credentials/gcp-add-client-id.png"
-        alt="Google Workspace Admin Console — Add a new client ID with OAuth scopes"
-        width={350}
-        height={300}
-        className="my-4"
-      />
-    </div>
-  </Step>
-  <Step>
-    Click **Authorize**
-  </Step>
-</Steps>
-
-<Callout type="info">
-Domain-wide delegation must be configured by a Google Workspace admin. If you are not an admin, send the Client ID and required scopes to your admin.
-</Callout>
-
-### Scopes Reference
-
-The table below lists every Google service that supports service account authentication in Sim, the API to enable in Google Cloud Console, and the delegation scopes to authorize. Copy the scope string for each service you need and paste it into the Google Workspace Admin Console.
-
-<table>
-  <thead>
-    <tr>
-      <th className="whitespace-nowrap">Service</th>
-      <th className="whitespace-nowrap">API to Enable</th>
-      <th>Delegation Scopes</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr><td>Gmail</td><td>Gmail API</td><td><code>{'https://www.googleapis.com/auth/gmail.send'}</code><br/><code>{'https://www.googleapis.com/auth/gmail.modify'}</code><br/><code>{'https://www.googleapis.com/auth/gmail.labels'}</code></td></tr>
-    <tr><td>Google Sheets</td><td>Google Sheets API, Google Drive API</td><td><code>{'https://www.googleapis.com/auth/drive'}</code><br/><code>{'https://www.googleapis.com/auth/drive.file'}</code></td></tr>
-    <tr><td>Google Drive</td><td>Google Drive API</td><td><code>{'https://www.googleapis.com/auth/drive'}</code><br/><code>{'https://www.googleapis.com/auth/drive.file'}</code></td></tr>
-    <tr><td>Google Docs</td><td>Google Docs API, Google Drive API</td><td><code>{'https://www.googleapis.com/auth/drive'}</code><br/><code>{'https://www.googleapis.com/auth/drive.file'}</code></td></tr>
-    <tr><td>Google Slides</td><td>Google Slides API, Google Drive API</td><td><code>{'https://www.googleapis.com/auth/drive'}</code><br/><code>{'https://www.googleapis.com/auth/drive.file'}</code></td></tr>
-    <tr><td>Google Forms</td><td>Google Forms API, Google Drive API</td><td><code>{'https://www.googleapis.com/auth/drive'}</code><br/><code>{'https://www.googleapis.com/auth/forms.body'}</code><br/><code>{'https://www.googleapis.com/auth/forms.responses.readonly'}</code></td></tr>
-    <tr><td>Google Calendar</td><td>Google Calendar API</td><td><code>{'https://www.googleapis.com/auth/calendar'}</code></td></tr>
-    <tr><td>Google Contacts</td><td>People API</td><td><code>{'https://www.googleapis.com/auth/contacts'}</code></td></tr>
-    <tr><td>BigQuery</td><td>BigQuery API</td><td><code>{'https://www.googleapis.com/auth/bigquery'}</code></td></tr>
-    <tr><td>Google Tasks</td><td>Tasks API</td><td><code>{'https://www.googleapis.com/auth/tasks'}</code></td></tr>
-    <tr><td>Google Vault</td><td>Vault API, Cloud Storage API</td><td><code>{'https://www.googleapis.com/auth/ediscovery'}</code><br/><code>{'https://www.googleapis.com/auth/devstorage.read_only'}</code></td></tr>
-    <tr><td>Google Groups</td><td>Admin SDK API</td><td><code>{'https://www.googleapis.com/auth/admin.directory.group'}</code><br/><code>{'https://www.googleapis.com/auth/admin.directory.group.member'}</code></td></tr>
-    <tr><td>Google Meet</td><td>Google Meet API</td><td><code>{'https://www.googleapis.com/auth/meetings.space.created'}</code><br/><code>{'https://www.googleapis.com/auth/meetings.space.readonly'}</code></td></tr>
-  </tbody>
-</table>
-
-<Callout type="info">
-You only need to enable APIs and authorize scopes for the services you plan to use. When authorizing multiple services, combine their scope strings with commas into a single entry in the Admin Console.
-</Callout>
-
-## Adding the Service Account to Sim
-
-Once Google Cloud and Workspace are configured, add the service account as a credential in Sim.
-
-<Steps>
-  <Step>
-    Open your workspace **Settings** and go to the **Integrations** tab
-  </Step>
-  <Step>
-    Search for "Google Service Account" and click **Connect**
-
-    <div className="flex justify-center">
-      <Image
-        src="/static/credentials/integrations-service-account.png"
-        alt="Integrations page showing Google Service Account"
-        width={800}
-        height={150}
-        className="my-4"
-      />
-    </div>
-  </Step>
-  <Step>
-    Paste the full contents of your JSON key file into the text area
-    <div className="flex justify-center">
-      <Image
-        src="/static/credentials/add-service-account.png"
-        alt="Add Google Service Account dialog"
-        width={350}
-        height={420}
-        className="my-6"
-      />
-    </div>
-  </Step>
-  <Step>
-    Give the credential a display name (the service account email is used by default)
-  </Step>
-  <Step>
-    Click **Save**
-  </Step>
-</Steps>
-
-The JSON key file is validated for the required fields (`type`, `client_email`, `private_key`, `project_id`) and encrypted before being stored.
-
-## Using Delegated Access in Workflows
-
-When you use a Google block (Gmail, Sheets, Drive, etc.) in a workflow and select a service account credential, an **Impersonate User Email** field appears below the credential selector.
-
-Enter the email address of the Google Workspace user you want the service account to act as. For example, if you enter `alice@yourcompany.com`, the workflow will send emails from Alice's account, read her spreadsheets, or access her calendar — depending on the scopes you authorized.
-
-<div className="flex justify-center">
-  <Image
-    src="/static/credentials/workflow-impersonated-account.png"
-    alt="Gmail block in a workflow showing the Impersonated Account field with a service account credential"
-    width={800}
-    height={350}
-    className="my-4"
-  />
-</div>
-
-<Callout type="warn">
-The impersonated email must belong to a user in the Google Workspace domain where you configured domain-wide delegation. Impersonating external email addresses will fail.
-</Callout>
-
-<FAQ items={[
-  { question: "Can I use a service account without domain-wide delegation?", answer: "Yes, but it will only be able to access resources owned by the service account itself (e.g., spreadsheets shared directly with the service account email). Without delegation, you cannot impersonate users or access their personal data like Gmail." },
-  { question: "What happens if the impersonation email field is left blank?", answer: "The service account will authenticate as itself. This works for accessing shared resources (like a Google Sheet shared with the service account email) but will fail for user-specific APIs like Gmail." },
-  { question: "Can I use the same service account for multiple Google services?", answer: "Yes. A single service account can be used across Gmail, Sheets, Drive, Calendar, and other Google services — as long as the required API is enabled in Google Cloud and the corresponding scopes are authorized in the Workspace admin console." },
-  { question: "How do I rotate the service account key?", answer: "Create a new JSON key in the Google Cloud Console under your service account's Keys tab, then update the credential in Sim with the new key. Delete the old key from Google Cloud once the new one is working." },
-  { question: "Does the impersonated user need a Google Workspace license?", answer: "Yes. Domain-wide delegation only works with users who have a Google Workspace account in the domain. Consumer Gmail accounts (e.g., @gmail.com) cannot be impersonated." },
-]} />

apps/docs/content/docs/en/credentials/meta.json

@@ -1,5 +0,0 @@
-{
-  "title": "Credentials",
-  "pages": ["index", "google-service-account"],
-  "defaultOpen": false
-}

apps/docs/content/docs/en/execution/basics.mdx

@@ -96,9 +96,8 @@ Understanding these core principles will help you build better workflows:
 2. **Automatic Parallelization**: Independent blocks run concurrently without configuration
 3. **Smart Data Flow**: Outputs flow automatically to connected blocks
 4. **Error Handling**: Failed blocks stop their execution path but don't affect independent paths
-5. **Response Blocks as Exit Points**: When a Response block executes, the entire workflow stops and the API response is sent immediately. Multiple Response blocks can exist on different branches — the first one to execute wins
-6. **State Persistence**: All block outputs and execution details are preserved for debugging
-7. **Cycle Protection**: Workflows that call other workflows (via Workflow blocks, MCP tools, or API blocks) are tracked with a call chain. If the chain exceeds 25 hops, execution is stopped to prevent infinite loops
+5. **State Persistence**: All block outputs and execution details are preserved for debugging
+6. **Cycle Protection**: Workflows that call other workflows (via Workflow blocks, MCP tools, or API blocks) are tracked with a call chain. If the chain exceeds 25 hops, execution is stopped to prevent infinite loops
 
 ## Next Steps
 

apps/docs/content/docs/en/execution/costs.mdx

@@ -195,17 +195,6 @@ By default, your usage is capped at the credits included in your plan. To allow
 
 Max (individual) shares the same rate limits as team plans. Team plans (Pro or Max for Teams) use the Max-tier rate limits.
 
-### Concurrent Execution Limits
-
-| Plan | Concurrent Executions |
-|------|----------------------|
-| **Free** | 5 |
-| **Pro** | 50 |
-| **Max / Team** | 200 |
-| **Enterprise** | 200 (customizable) |
-
-Concurrent execution limits control how many workflow executions can run simultaneously within a workspace. When the limit is reached, new executions are queued and admitted as running executions complete. Manual runs from the editor are not subject to these limits.
-
 ### File Storage
 
 | Plan | Storage |

apps/docs/content/docs/en/meta.json

@@ -13,7 +13,6 @@
     "mailer",
     "skills",
     "knowledgebase",
-    "tables",
     "variables",
     "credentials",
     "execution",

apps/docs/content/docs/en/tables/index.mdx

@@ -1,158 +0,0 @@
----
-title: Tables
-description: Store, query, and manage structured data directly within your workspace
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Image } from '@/components/ui/image'
-import { FAQ } from '@/components/ui/faq'
-
-Tables let you store and manage structured data directly in your workspace. Use them to maintain reference data, collect workflow outputs, or build lightweight databases — all without leaving Sim.
-
-<Image src="/static/tables/tables-overview.png" alt="Tables view showing structured data with typed columns for name, title, company, role, and more" width={800} height={500} />
-
-Each table has a schema of typed columns, supports filtering and sorting, and is fully accessible through the [Tables API](/docs/en/api-reference/(generated)/tables).
-
-## Creating a Table
-
-1. Open the **Tables** section from your workspace sidebar
-2. Click **New table**
-3. Name your table and start adding columns
-
-Tables start with a single text column. Add more columns by clicking **New column** in the column header area.
-
-## Column Types
-
-Each column has a type that determines how values are stored and validated.
-
-| Type | Description | Example Values |
-|------|-------------|----------------|
-| **Text** | Free-form string | `"Acme Corp"`, `"hello@example.com"` |
-| **Number** | Numeric value | `42`, `3.14`, `-100` |
-| **Boolean** | True or false | `true`, `false` |
-| **Date** | Date value | `2026-03-16` |
-| **JSON** | Structured object or array | `{"key": "value"}`, `[1, 2, 3]` |
-
-<Callout type="info">
-Column types are enforced on input. For example, typing into a Number column is restricted to digits, dots, and minus signs. Non-numeric values entered via paste are coerced to `0`.
-</Callout>
-
-## Working with Rows
-
-### Adding Rows
-
-- Click **New row** below the last row to append a new row
-- Press **Shift + Enter** while a cell is selected to insert a row below
-- Paste tabular data (from a spreadsheet or TSV) to bulk-create rows
-
-### Editing Cells
-
-Click a cell to select it, then press **Enter**, **F2**, or start typing to edit. Press **Escape** to cancel, or **Tab** to save and move to the next cell.
-
-### Selecting Rows
-
-Click a row's checkbox to select it. Selecting additional checkboxes adds to the selection without clearing previous selections.
-
-| Action | Behavior |
-|--------|----------|
-| Click checkbox | Toggle that row's selection |
-| Shift + click checkbox | Select range from last clicked to current |
-| Click header checkbox | Select all / deselect all |
-| Shift + Space | Toggle row selection from keyboard |
-
-### Deleting Rows
-
-Right-click a selected row (or group of selected rows) and choose **Delete row** from the context menu.
-
-## Filtering and Sorting
-
-Use the toolbar above the table to filter and sort your data.
-
-- **Filter**: Set conditions on any column (e.g., "Name contains Acme"). Multiple filters are combined with AND logic.
-- **Sort**: Order rows by any column, ascending or descending.
-
-Filters and sorts are applied in real time and do not modify the underlying data.
-
-## Keyboard Shortcuts
-
-All shortcuts work when the table is focused and no cell is being edited.
-
-<Callout type="info">
-**Mod** refers to `Cmd` on macOS and `Ctrl` on Windows/Linux.
-</Callout>
-
-### Navigation
-
-| Shortcut | Action |
-|----------|--------|
-| Arrow keys | Move one cell |
-| `Mod` + Arrow keys | Jump to edge of table |
-| `Tab` / `Shift` + `Tab` | Move to next / previous cell |
-| `Escape` | Clear selection |
-
-### Selection
-
-| Shortcut | Action |
-|----------|--------|
-| `Shift` + Arrow keys | Extend selection by one cell |
-| `Mod` + `Shift` + Arrow keys | Extend selection to edge |
-| `Mod` + `A` | Select all rows |
-| `Shift` + `Space` | Toggle current row selection |
-
-### Editing
-
-| Shortcut | Action |
-|----------|--------|
-| `Enter` or `F2` | Start editing selected cell |
-| `Escape` | Cancel editing |
-| Type any character | Start editing with that character |
-| `Shift` + `Enter` | Insert new row below |
-| `Space` | Expand row details |
-
-### Clipboard
-
-| Shortcut | Action |
-|----------|--------|
-| `Mod` + `C` | Copy selected cells |
-| `Mod` + `X` | Cut selected cells |
-| `Mod` + `V` | Paste |
-| `Delete` / `Backspace` | Clear selected cells (all columns when using checkbox selection) |
-
-### History
-
-| Shortcut | Action |
-|----------|--------|
-| `Mod` + `Z` | Undo |
-| `Mod` + `Shift` + `Z` | Redo |
-| `Mod` + `Y` | Redo (alternative) |
-
-## Using Tables in Workflows
-
-Tables can be read from and written to within your workflows using the **Table** block. Common patterns include:
-
-- **Lookup**: Query a table for reference data (e.g., pricing rules, customer metadata)
-- **Write-back**: Store workflow outputs in a table for later review or reporting
-- **Iteration**: Process each row in a table as part of a batch workflow
-
-## API Access
-
-Tables are fully accessible through the REST API. You can create, read, update, and delete both tables and rows programmatically.
-
-See the [Tables API Reference](/docs/en/api-reference/(generated)/tables) for endpoints, parameters, and examples.
-
-## Best Practices
-
-- **Use typed columns** to enforce data integrity — prefer Number and Boolean over storing everything as Text
-- **Name columns descriptively** so they are self-documenting when referenced in workflows
-- **Use JSON columns sparingly** — they are flexible but harder to filter and sort against
-- **Leverage the API** for bulk imports rather than manually entering large datasets
-
-<FAQ items={[
-  { question: "Is there a row limit per table?", answer: "Tables are designed for working datasets. For very large datasets (100k+ rows), consider paginating API reads or splitting data across multiple tables." },
-  { question: "Can I import data from a spreadsheet?", answer: "Yes. Copy rows from any spreadsheet application and paste them directly into the table. Column values will be validated against the column types." },
-  { question: "Do tables support formulas?", answer: "Tables store raw data and do not support computed formulas. Use workflow logic (Function block or Agent block) to derive computed values and write them back to the table." },
-  { question: "Can multiple workflows write to the same table?", answer: "Yes. Table writes are atomic at the row level, so multiple workflows can safely write to the same table concurrently." },
-  { question: "How do I reference a table from a workflow?", answer: "Use the Table block in your workflow. Select the target table from the dropdown, choose an operation (read, write, update), and configure the parameters." },
-  { question: "Are tables shared across workspace members?", answer: "Yes. Tables are workspace-scoped and accessible to all members with appropriate permissions." },
-  { question: "Can I undo changes?", answer: "In the table editor, Cmd/Ctrl+Z undoes recent cell edits, row insertions, and row deletions. API-driven changes are not covered by the editor's undo history." },
-]} />

apps/docs/content/docs/en/tools/agentmail.mdx

@@ -1,592 +0,0 @@
----
-title: AgentMail
-description: Manage email inboxes, threads, and messages with AgentMail
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="agentmail"
-  color="#000000"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[AgentMail](https://agentmail.to/) is an API-first email platform built for agents and automation. AgentMail lets you create email inboxes on the fly, send and receive messages, reply to threads, manage drafts, and organize conversations with labels — all through a simple REST API designed for programmatic access.
-
-**Why AgentMail?**
-- **Agent-Native Email:** Purpose-built for AI agents and automation — create inboxes, send messages, and manage threads without human-facing UI overhead.
-- **Full Email Lifecycle:** Send new messages, reply to threads, forward emails, manage drafts, and schedule sends — all from a single API.
-- **Thread & Conversation Management:** Organize emails into threads with full read, reply, forward, and label support for structured conversation tracking.
-- **Draft Workflow:** Compose drafts, update them, schedule sends, and dispatch when ready — perfect for review-before-send workflows.
-- **Label Organization:** Tag threads and messages with custom labels for filtering, routing, and downstream automation.
-
-**Using AgentMail in Sim**
-
-Sim's AgentMail integration connects your agentic workflows directly to AgentMail using an API key. With 20 operations spanning inboxes, threads, messages, and drafts, you can build powerful email automations without writing backend code.
-
-**Key benefits of using AgentMail in Sim:**
-- **Dynamic inbox creation:** Spin up new inboxes on the fly for each agent, workflow, or customer — perfect for multi-tenant email handling.
-- **Automated email processing:** List and read incoming messages, then trigger downstream actions based on content, sender, or labels.
-- **Conversational email:** Reply to threads and forward messages to keep conversations flowing naturally within your automated workflows.
-- **Draft and review workflows:** Create drafts, update them with AI-generated content, and send when approved — ideal for human-in-the-loop patterns.
-- **Email organization:** Apply labels to threads and messages to categorize, filter, and route emails through your automation pipeline.
-
-Whether you're building an AI email assistant, automating customer support replies, processing incoming leads, or managing multi-agent email workflows, AgentMail in Sim gives you direct, secure access to the full AgentMail API — no middleware required. Simply configure your API key, select the operation you need, and let Sim handle the rest.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate AgentMail into your workflow. Create and manage email inboxes, send and receive messages, reply to threads, manage drafts, and organize threads with labels. Requires API Key.
-
-
-
-## Tools
-
-### `agentmail_create_draft`
-
-Create a new email draft in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to create the draft in |
-| `to` | string | No | Recipient email addresses \(comma-separated\) |
-| `subject` | string | No | Draft subject line |
-| `text` | string | No | Plain text draft body |
-| `html` | string | No | HTML draft body |
-| `cc` | string | No | CC recipient email addresses \(comma-separated\) |
-| `bcc` | string | No | BCC recipient email addresses \(comma-separated\) |
-| `inReplyTo` | string | No | ID of message being replied to |
-| `sendAt` | string | No | ISO 8601 timestamp to schedule sending |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `draftId` | string | Unique identifier for the draft |
-| `inboxId` | string | Inbox the draft belongs to |
-| `subject` | string | Draft subject |
-| `to` | array | Recipient email addresses |
-| `cc` | array | CC email addresses |
-| `bcc` | array | BCC email addresses |
-| `text` | string | Plain text content |
-| `html` | string | HTML content |
-| `preview` | string | Draft preview text |
-| `labels` | array | Labels assigned to the draft |
-| `inReplyTo` | string | Message ID this draft replies to |
-| `sendStatus` | string | Send status \(scheduled, sending, failed\) |
-| `sendAt` | string | Scheduled send time |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last updated timestamp |
-
-### `agentmail_create_inbox`
-
-Create a new email inbox with AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `username` | string | No | Username for the inbox email address |
-| `domain` | string | No | Domain for the inbox email address |
-| `displayName` | string | No | Display name for the inbox |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `inboxId` | string | Unique identifier for the inbox |
-| `email` | string | Email address of the inbox |
-| `displayName` | string | Display name of the inbox |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last updated timestamp |
-
-### `agentmail_delete_draft`
-
-Delete an email draft in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the draft |
-| `draftId` | string | Yes | ID of the draft to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the draft was successfully deleted |
-
-### `agentmail_delete_inbox`
-
-Delete an email inbox in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the inbox was successfully deleted |
-
-### `agentmail_delete_thread`
-
-Delete an email thread in AgentMail (moves to trash, or permanently deletes if already in trash)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the thread |
-| `threadId` | string | Yes | ID of the thread to delete |
-| `permanent` | boolean | No | Force permanent deletion instead of moving to trash |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the thread was successfully deleted |
-
-### `agentmail_forward_message`
-
-Forward an email message to new recipients in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the message |
-| `messageId` | string | Yes | ID of the message to forward |
-| `to` | string | Yes | Recipient email addresses \(comma-separated\) |
-| `subject` | string | No | Override subject line |
-| `text` | string | No | Additional plain text to prepend |
-| `html` | string | No | Additional HTML to prepend |
-| `cc` | string | No | CC recipient email addresses \(comma-separated\) |
-| `bcc` | string | No | BCC recipient email addresses \(comma-separated\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `messageId` | string | ID of the forwarded message |
-| `threadId` | string | ID of the thread |
-
-### `agentmail_get_draft`
-
-Get details of a specific email draft in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox the draft belongs to |
-| `draftId` | string | Yes | ID of the draft to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `draftId` | string | Unique identifier for the draft |
-| `inboxId` | string | Inbox the draft belongs to |
-| `subject` | string | Draft subject |
-| `to` | array | Recipient email addresses |
-| `cc` | array | CC email addresses |
-| `bcc` | array | BCC email addresses |
-| `text` | string | Plain text content |
-| `html` | string | HTML content |
-| `preview` | string | Draft preview text |
-| `labels` | array | Labels assigned to the draft |
-| `inReplyTo` | string | Message ID this draft replies to |
-| `sendStatus` | string | Send status \(scheduled, sending, failed\) |
-| `sendAt` | string | Scheduled send time |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last updated timestamp |
-
-### `agentmail_get_inbox`
-
-Get details of a specific email inbox in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `inboxId` | string | Unique identifier for the inbox |
-| `email` | string | Email address of the inbox |
-| `displayName` | string | Display name of the inbox |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last updated timestamp |
-
-### `agentmail_get_message`
-
-Get details of a specific email message in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the message |
-| `messageId` | string | Yes | ID of the message to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `messageId` | string | Unique identifier for the message |
-| `threadId` | string | ID of the thread this message belongs to |
-| `from` | string | Sender email address |
-| `to` | array | Recipient email addresses |
-| `cc` | array | CC email addresses |
-| `bcc` | array | BCC email addresses |
-| `subject` | string | Message subject |
-| `text` | string | Plain text content |
-| `html` | string | HTML content |
-| `createdAt` | string | Creation timestamp |
-
-### `agentmail_get_thread`
-
-Get details of a specific email thread including messages in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the thread |
-| `threadId` | string | Yes | ID of the thread to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `threadId` | string | Unique identifier for the thread |
-| `subject` | string | Thread subject |
-| `senders` | array | List of sender email addresses |
-| `recipients` | array | List of recipient email addresses |
-| `messageCount` | number | Number of messages in the thread |
-| `labels` | array | Labels assigned to the thread |
-| `lastMessageAt` | string | Timestamp of last message |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last updated timestamp |
-| `messages` | array | Messages in the thread |
-|   ↳ `messageId` | string | Unique identifier for the message |
-|   ↳ `from` | string | Sender email address |
-|   ↳ `to` | array | Recipient email addresses |
-|   ↳ `cc` | array | CC email addresses |
-|   ↳ `bcc` | array | BCC email addresses |
-|   ↳ `subject` | string | Message subject |
-|   ↳ `text` | string | Plain text content |
-|   ↳ `html` | string | HTML content |
-|   ↳ `createdAt` | string | Creation timestamp |
-
-### `agentmail_list_drafts`
-
-List email drafts in an inbox in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to list drafts from |
-| `limit` | number | No | Maximum number of drafts to return |
-| `pageToken` | string | No | Pagination token for next page of results |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `drafts` | array | List of drafts |
-|   ↳ `draftId` | string | Unique identifier for the draft |
-|   ↳ `inboxId` | string | Inbox the draft belongs to |
-|   ↳ `subject` | string | Draft subject |
-|   ↳ `to` | array | Recipient email addresses |
-|   ↳ `cc` | array | CC email addresses |
-|   ↳ `bcc` | array | BCC email addresses |
-|   ↳ `preview` | string | Draft preview text |
-|   ↳ `sendStatus` | string | Send status \(scheduled, sending, failed\) |
-|   ↳ `sendAt` | string | Scheduled send time |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last updated timestamp |
-| `count` | number | Total number of drafts |
-| `nextPageToken` | string | Token for retrieving the next page |
-
-### `agentmail_list_inboxes`
-
-List all email inboxes in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `limit` | number | No | Maximum number of inboxes to return |
-| `pageToken` | string | No | Pagination token for next page of results |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `inboxes` | array | List of inboxes |
-|   ↳ `inboxId` | string | Unique identifier for the inbox |
-|   ↳ `email` | string | Email address of the inbox |
-|   ↳ `displayName` | string | Display name of the inbox |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last updated timestamp |
-| `count` | number | Total number of inboxes |
-| `nextPageToken` | string | Token for retrieving the next page |
-
-### `agentmail_list_messages`
-
-List messages in an inbox in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to list messages from |
-| `limit` | number | No | Maximum number of messages to return |
-| `pageToken` | string | No | Pagination token for next page of results |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `messages` | array | List of messages in the inbox |
-|   ↳ `messageId` | string | Unique identifier for the message |
-|   ↳ `from` | string | Sender email address |
-|   ↳ `to` | array | Recipient email addresses |
-|   ↳ `subject` | string | Message subject |
-|   ↳ `preview` | string | Message preview text |
-|   ↳ `createdAt` | string | Creation timestamp |
-| `count` | number | Total number of messages |
-| `nextPageToken` | string | Token for retrieving the next page |
-
-### `agentmail_list_threads`
-
-List email threads in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to list threads from |
-| `limit` | number | No | Maximum number of threads to return |
-| `pageToken` | string | No | Pagination token for next page of results |
-| `labels` | string | No | Comma-separated labels to filter threads by |
-| `before` | string | No | Filter threads before this ISO 8601 timestamp |
-| `after` | string | No | Filter threads after this ISO 8601 timestamp |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `threads` | array | List of email threads |
-|   ↳ `threadId` | string | Unique identifier for the thread |
-|   ↳ `subject` | string | Thread subject |
-|   ↳ `senders` | array | List of sender email addresses |
-|   ↳ `recipients` | array | List of recipient email addresses |
-|   ↳ `messageCount` | number | Number of messages in the thread |
-|   ↳ `lastMessageAt` | string | Timestamp of last message |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last updated timestamp |
-| `count` | number | Total number of threads |
-| `nextPageToken` | string | Token for retrieving the next page |
-
-### `agentmail_reply_message`
-
-Reply to an existing email message in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to reply from |
-| `messageId` | string | Yes | ID of the message to reply to |
-| `text` | string | No | Plain text reply body |
-| `html` | string | No | HTML reply body |
-| `to` | string | No | Override recipient email addresses \(comma-separated\) |
-| `cc` | string | No | CC email addresses \(comma-separated\) |
-| `bcc` | string | No | BCC email addresses \(comma-separated\) |
-| `replyAll` | boolean | No | Reply to all recipients of the original message |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `messageId` | string | ID of the sent reply message |
-| `threadId` | string | ID of the thread |
-
-### `agentmail_send_draft`
-
-Send an existing email draft in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the draft |
-| `draftId` | string | Yes | ID of the draft to send |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `messageId` | string | ID of the sent message |
-| `threadId` | string | ID of the thread |
-
-### `agentmail_send_message`
-
-Send an email message from an AgentMail inbox
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to send from |
-| `to` | string | Yes | Recipient email address \(comma-separated for multiple\) |
-| `subject` | string | Yes | Email subject line |
-| `text` | string | No | Plain text email body |
-| `html` | string | No | HTML email body |
-| `cc` | string | No | CC recipient email addresses \(comma-separated\) |
-| `bcc` | string | No | BCC recipient email addresses \(comma-separated\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `threadId` | string | ID of the created thread |
-| `messageId` | string | ID of the sent message |
-| `subject` | string | Email subject line |
-| `to` | string | Recipient email address |
-
-### `agentmail_update_draft`
-
-Update an existing email draft in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the draft |
-| `draftId` | string | Yes | ID of the draft to update |
-| `to` | string | No | Recipient email addresses \(comma-separated\) |
-| `subject` | string | No | Draft subject line |
-| `text` | string | No | Plain text draft body |
-| `html` | string | No | HTML draft body |
-| `cc` | string | No | CC recipient email addresses \(comma-separated\) |
-| `bcc` | string | No | BCC recipient email addresses \(comma-separated\) |
-| `sendAt` | string | No | ISO 8601 timestamp to schedule sending |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `draftId` | string | Unique identifier for the draft |
-| `inboxId` | string | Inbox the draft belongs to |
-| `subject` | string | Draft subject |
-| `to` | array | Recipient email addresses |
-| `cc` | array | CC email addresses |
-| `bcc` | array | BCC email addresses |
-| `text` | string | Plain text content |
-| `html` | string | HTML content |
-| `preview` | string | Draft preview text |
-| `labels` | array | Labels assigned to the draft |
-| `inReplyTo` | string | Message ID this draft replies to |
-| `sendStatus` | string | Send status \(scheduled, sending, failed\) |
-| `sendAt` | string | Scheduled send time |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last updated timestamp |
-
-### `agentmail_update_inbox`
-
-Update the display name of an email inbox in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox to update |
-| `displayName` | string | Yes | New display name for the inbox |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `inboxId` | string | Unique identifier for the inbox |
-| `email` | string | Email address of the inbox |
-| `displayName` | string | Display name of the inbox |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last updated timestamp |
-
-### `agentmail_update_message`
-
-Add or remove labels on an email message in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the message |
-| `messageId` | string | Yes | ID of the message to update |
-| `addLabels` | string | No | Comma-separated labels to add to the message |
-| `removeLabels` | string | No | Comma-separated labels to remove from the message |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `messageId` | string | Unique identifier for the message |
-| `labels` | array | Current labels on the message |
-
-### `agentmail_update_thread`
-
-Add or remove labels on an email thread in AgentMail
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | AgentMail API key |
-| `inboxId` | string | Yes | ID of the inbox containing the thread |
-| `threadId` | string | Yes | ID of the thread to update |
-| `addLabels` | string | No | Comma-separated labels to add to the thread |
-| `removeLabels` | string | No | Comma-separated labels to remove from the thread |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `threadId` | string | Unique identifier for the thread |
-| `labels` | array | Current labels on the thread |
-
-

apps/docs/content/docs/en/tools/ashby.mdx

@@ -30,50 +30,12 @@ In Sim, the Ashby integration enables your agents to programmatically manage you
 
 ## Usage Instructions
 
-Integrate Ashby into the workflow. Manage candidates (list, get, create, update, search, tag), applications (list, get, create, change stage), jobs (list, get), job postings (list, get), offers (list, get), notes (list, create), interviews (list), and reference data (sources, tags, archive reasons, custom fields, departments, locations, openings, users).
+Integrate Ashby into the workflow. Can list, search, create, and update candidates, list and get job details, create notes, list notes, list and get applications, create applications, and list offers.
 
 
 
 ## Tools
 
-### `ashby_add_candidate_tag`
-
-Adds a tag to a candidate in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `candidateId` | string | Yes | The UUID of the candidate to add the tag to |
-| `tagId` | string | Yes | The UUID of the tag to add |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the tag was successfully added |
-
-### `ashby_change_application_stage`
-
-Moves an application to a different interview stage. Requires an archive reason when moving to an Archived stage.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `applicationId` | string | Yes | The UUID of the application to update the stage of |
-| `interviewStageId` | string | Yes | The UUID of the interview stage to move the application to |
-| `archiveReasonId` | string | No | Archive reason UUID. Required when moving to an Archived stage, ignored otherwise |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `applicationId` | string | Application UUID |
-| `stageId` | string | New interview stage UUID |
-
 ### `ashby_create_application`
 
 Creates a new application for a candidate on a job. Optionally specify interview plan, stage, source, and credited user.
@@ -95,7 +57,23 @@ Creates a new application for a candidate on a job. Optionally specify interview
 
 | Parameter | Type | Description |
 | --------- | ---- | ----------- |
-| `applicationId` | string | Created application UUID |
+| `id` | string | Created application UUID |
+| `status` | string | Application status \(Active, Hired, Archived, Lead\) |
+| `candidate` | object | Associated candidate |
+|   ↳ `id` | string | Candidate UUID |
+|   ↳ `name` | string | Candidate name |
+| `job` | object | Associated job |
+|   ↳ `id` | string | Job UUID |
+|   ↳ `title` | string | Job title |
+| `currentInterviewStage` | object | Current interview stage |
+|   ↳ `id` | string | Stage UUID |
+|   ↳ `title` | string | Stage title |
+|   ↳ `type` | string | Stage type |
+| `source` | object | Application source |
+|   ↳ `id` | string | Source UUID |
+|   ↳ `title` | string | Source title |
+| `createdAt` | string | ISO 8601 creation timestamp |
+| `updatedAt` | string | ISO 8601 last update timestamp |
 
 ### `ashby_create_candidate`
 
@@ -107,8 +85,10 @@ Creates a new candidate record in Ashby.
 | --------- | ---- | -------- | ----------- |
 | `apiKey` | string | Yes | Ashby API Key |
 | `name` | string | Yes | The candidate full name |
-| `email` | string | Yes | Primary email address for the candidate |
+| `email` | string | No | Primary email address for the candidate |
+| `emailType` | string | No | Email address type: Personal, Work, or Other \(default Work\) |
 | `phoneNumber` | string | No | Primary phone number for the candidate |
+| `phoneType` | string | No | Phone number type: Personal, Work, or Other \(default Work\) |
 | `linkedInUrl` | string | No | LinkedIn profile URL |
 | `githubUrl` | string | No | GitHub profile URL |
 | `sourceId` | string | No | UUID of the source to attribute the candidate to |
@@ -147,7 +127,14 @@ Creates a note on a candidate in Ashby. Supports plain text and HTML content (bo
 
 | Parameter | Type | Description |
 | --------- | ---- | ----------- |
-| `noteId` | string | Created note UUID |
+| `id` | string | Created note UUID |
+| `content` | string | Note content as stored |
+| `author` | object | Note author |
+|   ↳ `id` | string | Author user UUID |
+|   ↳ `firstName` | string | First name |
+|   ↳ `lastName` | string | Last name |
+|   ↳ `email` | string | Email address |
+| `createdAt` | string | ISO 8601 creation timestamp |
 
 ### `ashby_get_application`
 
@@ -241,7 +228,7 @@ Retrieves full details about a single job by its ID.
 | --------- | ---- | ----------- |
 | `id` | string | Job UUID |
 | `title` | string | Job title |
-| `status` | string | Job status \(Open, Closed, Draft, Archived\) |
+| `status` | string | Job status \(Open, Closed, Draft, Archived, On Hold\) |
 | `employmentType` | string | Employment type \(FullTime, PartTime, Intern, Contract, Temporary\) |
 | `departmentId` | string | Department UUID |
 | `locationId` | string | Location UUID |
@@ -250,58 +237,6 @@ Retrieves full details about a single job by its ID.
 | `createdAt` | string | ISO 8601 creation timestamp |
 | `updatedAt` | string | ISO 8601 last update timestamp |
 
-### `ashby_get_job_posting`
-
-Retrieves full details about a single job posting by its ID.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `jobPostingId` | string | Yes | The UUID of the job posting to fetch |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Job posting UUID |
-| `title` | string | Job posting title |
-| `jobId` | string | Associated job UUID |
-| `locationName` | string | Location name |
-| `departmentName` | string | Department name |
-| `employmentType` | string | Employment type \(e.g. FullTime, PartTime, Contract\) |
-| `descriptionPlain` | string | Job posting description in plain text |
-| `isListed` | boolean | Whether the posting is publicly listed |
-| `publishedDate` | string | ISO 8601 published date |
-| `externalLink` | string | External link to the job posting |
-
-### `ashby_get_offer`
-
-Retrieves full details about a single offer by its ID.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `offerId` | string | Yes | The UUID of the offer to fetch |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Offer UUID |
-| `offerStatus` | string | Offer status \(e.g. WaitingOnCandidateResponse, CandidateAccepted\) |
-| `acceptanceStatus` | string | Acceptance status \(e.g. Accepted, Declined, Pending\) |
-| `applicationId` | string | Associated application UUID |
-| `startDate` | string | Offer start date |
-| `salary` | object | Salary details |
-|   ↳ `currencyCode` | string | ISO 4217 currency code |
-|   ↳ `value` | number | Salary amount |
-| `openingId` | string | Associated opening UUID |
-| `createdAt` | string | ISO 8601 creation timestamp \(from latest version\) |
-
 ### `ashby_list_applications`
 
 Lists all applications in an Ashby organization with pagination and optional filters for status, job, candidate, and creation date.
@@ -343,45 +278,6 @@ Lists all applications in an Ashby organization with pagination and optional fil
 | `moreDataAvailable` | boolean | Whether more pages of results exist |
 | `nextCursor` | string | Opaque cursor for fetching the next page |
 
-### `ashby_list_archive_reasons`
-
-Lists all archive reasons configured in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `archiveReasons` | array | List of archive reasons |
-|   ↳ `id` | string | Archive reason UUID |
-|   ↳ `text` | string | Archive reason text |
-|   ↳ `reasonType` | string | Reason type |
-|   ↳ `isArchived` | boolean | Whether the reason is archived |
-
-### `ashby_list_candidate_tags`
-
-Lists all candidate tags configured in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `tags` | array | List of candidate tags |
-|   ↳ `id` | string | Tag UUID |
-|   ↳ `title` | string | Tag title |
-|   ↳ `isArchived` | boolean | Whether the tag is archived |
-
 ### `ashby_list_candidates`
 
 Lists all candidates in an Ashby organization with cursor-based pagination.
@@ -414,98 +310,6 @@ Lists all candidates in an Ashby organization with cursor-based pagination.
 | `moreDataAvailable` | boolean | Whether more pages of results exist |
 | `nextCursor` | string | Opaque cursor for fetching the next page |
 
-### `ashby_list_custom_fields`
-
-Lists all custom field definitions configured in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `customFields` | array | List of custom field definitions |
-|   ↳ `id` | string | Custom field UUID |
-|   ↳ `title` | string | Custom field title |
-|   ↳ `fieldType` | string | Field type \(e.g. String, Number, Boolean\) |
-|   ↳ `objectType` | string | Object type the field applies to \(e.g. Candidate, Application, Job\) |
-|   ↳ `isArchived` | boolean | Whether the custom field is archived |
-
-### `ashby_list_departments`
-
-Lists all departments in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `departments` | array | List of departments |
-|   ↳ `id` | string | Department UUID |
-|   ↳ `name` | string | Department name |
-|   ↳ `isArchived` | boolean | Whether the department is archived |
-|   ↳ `parentId` | string | Parent department UUID |
-
-### `ashby_list_interviews`
-
-Lists interview schedules in Ashby, optionally filtered by application or interview stage.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `applicationId` | string | No | The UUID of the application to list interview schedules for |
-| `interviewStageId` | string | No | The UUID of the interview stage to list interview schedules for |
-| `cursor` | string | No | Opaque pagination cursor from a previous response nextCursor value |
-| `perPage` | number | No | Number of results per page \(default 100\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `interviewSchedules` | array | List of interview schedules |
-|   ↳ `id` | string | Interview schedule UUID |
-|   ↳ `applicationId` | string | Associated application UUID |
-|   ↳ `interviewStageId` | string | Interview stage UUID |
-|   ↳ `status` | string | Schedule status |
-|   ↳ `createdAt` | string | ISO 8601 creation timestamp |
-| `moreDataAvailable` | boolean | Whether more pages of results exist |
-| `nextCursor` | string | Opaque cursor for fetching the next page |
-
-### `ashby_list_job_postings`
-
-Lists all job postings in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `jobPostings` | array | List of job postings |
-|   ↳ `id` | string | Job posting UUID |
-|   ↳ `title` | string | Job posting title |
-|   ↳ `jobId` | string | Associated job UUID |
-|   ↳ `locationName` | string | Location name |
-|   ↳ `departmentName` | string | Department name |
-|   ↳ `employmentType` | string | Employment type \(e.g. FullTime, PartTime, Contract\) |
-|   ↳ `isListed` | boolean | Whether the posting is publicly listed |
-|   ↳ `publishedDate` | string | ISO 8601 published date |
-
 ### `ashby_list_jobs`
 
 Lists all jobs in an Ashby organization. By default returns Open, Closed, and Archived jobs. Specify status to filter.
@@ -535,30 +339,6 @@ Lists all jobs in an Ashby organization. By default returns Open, Closed, and Ar
 | `moreDataAvailable` | boolean | Whether more pages of results exist |
 | `nextCursor` | string | Opaque cursor for fetching the next page |
 
-### `ashby_list_locations`
-
-Lists all locations configured in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `locations` | array | List of locations |
-|   ↳ `id` | string | Location UUID |
-|   ↳ `name` | string | Location name |
-|   ↳ `isArchived` | boolean | Whether the location is archived |
-|   ↳ `isRemote` | boolean | Whether this is a remote location |
-|   ↳ `address` | object | Location address |
-|     ↳ `city` | string | City |
-|     ↳ `region` | string | State or region |
-|     ↳ `country` | string | Country |
-
 ### `ashby_list_notes`
 
 Lists all notes on a candidate with pagination support.
@@ -606,106 +386,18 @@ Lists all offers with their latest version in an Ashby organization.
 | --------- | ---- | ----------- |
 | `offers` | array | List of offers |
 |   ↳ `id` | string | Offer UUID |
-|   ↳ `offerStatus` | string | Offer status |
-|   ↳ `acceptanceStatus` | string | Acceptance status |
-|   ↳ `applicationId` | string | Associated application UUID |
-|   ↳ `startDate` | string | Offer start date |
-|   ↳ `salary` | object | Salary details |
-|     ↳ `currencyCode` | string | ISO 4217 currency code |
-|     ↳ `value` | number | Salary amount |
-|   ↳ `openingId` | string | Associated opening UUID |
+|   ↳ `status` | string | Offer status |
+|   ↳ `candidate` | object | Associated candidate |
+|     ↳ `id` | string | Candidate UUID |
+|     ↳ `name` | string | Candidate name |
+|   ↳ `job` | object | Associated job |
+|     ↳ `id` | string | Job UUID |
+|     ↳ `title` | string | Job title |
 |   ↳ `createdAt` | string | ISO 8601 creation timestamp |
+|   ↳ `updatedAt` | string | ISO 8601 last update timestamp |
 | `moreDataAvailable` | boolean | Whether more pages of results exist |
 | `nextCursor` | string | Opaque cursor for fetching the next page |
 
-### `ashby_list_openings`
-
-Lists all openings in Ashby with pagination.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `cursor` | string | No | Opaque pagination cursor from a previous response nextCursor value |
-| `perPage` | number | No | Number of results per page \(default 100\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `openings` | array | List of openings |
-|   ↳ `id` | string | Opening UUID |
-|   ↳ `openingState` | string | Opening state \(Approved, Closed, Draft, Filled, Open\) |
-|   ↳ `isArchived` | boolean | Whether the opening is archived |
-|   ↳ `openedAt` | string | ISO 8601 opened timestamp |
-|   ↳ `closedAt` | string | ISO 8601 closed timestamp |
-| `moreDataAvailable` | boolean | Whether more pages of results exist |
-| `nextCursor` | string | Opaque cursor for fetching the next page |
-
-### `ashby_list_sources`
-
-Lists all candidate sources configured in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `sources` | array | List of sources |
-|   ↳ `id` | string | Source UUID |
-|   ↳ `title` | string | Source title |
-|   ↳ `isArchived` | boolean | Whether the source is archived |
-
-### `ashby_list_users`
-
-Lists all users in Ashby with pagination.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `cursor` | string | No | Opaque pagination cursor from a previous response nextCursor value |
-| `perPage` | number | No | Number of results per page \(default 100\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `users` | array | List of users |
-|   ↳ `id` | string | User UUID |
-|   ↳ `firstName` | string | First name |
-|   ↳ `lastName` | string | Last name |
-|   ↳ `email` | string | Email address |
-|   ↳ `isEnabled` | boolean | Whether the user account is enabled |
-|   ↳ `globalRole` | string | User role \(Organization Admin, Elevated Access, Limited Access, External Recruiter\) |
-| `moreDataAvailable` | boolean | Whether more pages of results exist |
-| `nextCursor` | string | Opaque cursor for fetching the next page |
-
-### `ashby_remove_candidate_tag`
-
-Removes a tag from a candidate in Ashby.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Ashby API Key |
-| `candidateId` | string | Yes | The UUID of the candidate to remove the tag from |
-| `tagId` | string | Yes | The UUID of the tag to remove |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the tag was successfully removed |
-
 ### `ashby_search_candidates`
 
 Searches for candidates by name and/or email with AND logic. Results are limited to 100 matches. Use candidate.list for full pagination.
@@ -733,8 +425,6 @@ Searches for candidates by name and/or email with AND logic. Results are limited
 |     ↳ `value` | string | Phone number |
 |     ↳ `type` | string | Contact type \(Personal, Work, Other\) |
 |     ↳ `isPrimary` | boolean | Whether this is the primary phone |
-|   ↳ `createdAt` | string | ISO 8601 creation timestamp |
-|   ↳ `updatedAt` | string | ISO 8601 last update timestamp |
 
 ### `ashby_update_candidate`
 
@@ -748,7 +438,9 @@ Updates an existing candidate record in Ashby. Only provided fields are changed.
 | `candidateId` | string | Yes | The UUID of the candidate to update |
 | `name` | string | No | Updated full name |
 | `email` | string | No | Updated primary email address |
+| `emailType` | string | No | Email address type: Personal, Work, or Other \(default Work\) |
 | `phoneNumber` | string | No | Updated primary phone number |
+| `phoneType` | string | No | Phone number type: Personal, Work, or Other \(default Work\) |
 | `linkedInUrl` | string | No | LinkedIn profile URL |
 | `githubUrl` | string | No | GitHub profile URL |
 | `websiteUrl` | string | No | Personal website URL |

apps/docs/content/docs/en/tools/attio.mdx

@@ -359,35 +359,6 @@ List tasks in Attio, optionally filtered by record, assignee, or completion stat
 |   ↳ `createdAt` | string | When the task was created |
 | `count` | number | Number of tasks returned |
 
-### `attio_get_task`
-
-Get a single task by ID from Attio
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `taskId` | string | Yes | The ID of the task to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `taskId` | string | The task ID |
-| `content` | string | The task content |
-| `deadlineAt` | string | The task deadline |
-| `isCompleted` | boolean | Whether the task is completed |
-| `linkedRecords` | array | Records linked to this task |
-|   ↳ `targetObjectId` | string | The linked object ID |
-|   ↳ `targetRecordId` | string | The linked record ID |
-| `assignees` | array | Task assignees |
-|   ↳ `type` | string | The assignee actor type \(e.g. workspace-member\) |
-|   ↳ `id` | string | The assignee actor ID |
-| `createdByActor` | object | The actor who created this task |
-|   ↳ `type` | string | The actor type \(e.g. workspace-member, api-token, system\) |
-|   ↳ `id` | string | The actor ID |
-| `createdAt` | string | When the task was created |
-
 ### `attio_create_task`
 
 Create a task in Attio
@@ -1041,8 +1012,8 @@ Update a webhook in Attio (target URL and/or subscriptions)
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `webhookId` | string | Yes | The webhook ID to update |
-| `targetUrl` | string | No | HTTPS target URL for webhook delivery |
-| `subscriptions` | string | No | JSON array of subscriptions, e.g. \[\{"event_type":"note.created"\}\] |
+| `targetUrl` | string | Yes | HTTPS target URL for webhook delivery |
+| `subscriptions` | string | Yes | JSON array of subscriptions, e.g. \[\{"event_type":"note.created"\}\] |
 
 #### Output
 

apps/docs/content/docs/en/tools/box.mdx

@@ -1,440 +0,0 @@
----
-title: Box
-description: Manage files, folders, and e-signatures with Box
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="box"
-  color="#FFFFFF"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Box](https://www.box.com/) is a leading cloud content management and file sharing platform trusted by enterprises worldwide to securely store, manage, and collaborate on files. Box provides robust APIs for automating file operations and integrating with business workflows, including [Box Sign](https://www.box.com/esignature) for native e-signatures.
-
-With the Box integration in Sim, you can:
-
-- **Upload files**: Upload documents, images, and other files to any Box folder
-- **Download files**: Retrieve file content from Box for processing in your workflows
-- **Get file info**: Access detailed metadata including size, owner, timestamps, tags, and shared links
-- **List folder contents**: Browse files and folders with sorting and pagination support
-- **Create folders**: Organize your Box storage by creating new folders programmatically
-- **Delete files and folders**: Remove content with optional recursive deletion for folders
-- **Copy files**: Duplicate files across folders with optional renaming
-- **Search**: Find files and folders by name, content, extension, or location
-- **Update file metadata**: Rename, move, add descriptions, or tag files
-- **Create sign requests**: Send documents for e-signature with one or more signers
-- **Track signing status**: Monitor the progress of sign requests
-- **List sign requests**: View all sign requests with marker-based pagination
-- **Cancel sign requests**: Cancel pending sign requests that are no longer needed
-- **Resend sign reminders**: Send reminder notifications to signers who haven't completed signing
-
-These capabilities allow your Sim agents to automate Box operations directly within your workflows — from organizing documents and distributing content to processing uploaded files, managing e-signature workflows for offer letters and contracts, and maintaining structured cloud storage as part of your business processes.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Box into your workflow to manage files, folders, and e-signatures. Upload and download files, search content, create folders, send documents for e-signature, track signing status, and more.
-
-
-
-## Tools
-
-### `box_upload_file`
-
-Upload a file to a Box folder
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `parentFolderId` | string | Yes | The ID of the folder to upload the file to \(use "0" for root\) |
-| `file` | file | No | The file to upload \(UserFile object\) |
-| `fileContent` | string | No | Legacy: base64 encoded file content |
-| `fileName` | string | No | Optional filename override |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | File ID |
-| `name` | string | File name |
-| `size` | number | File size in bytes |
-| `sha1` | string | SHA1 hash of file content |
-| `createdAt` | string | Creation timestamp |
-| `modifiedAt` | string | Last modified timestamp |
-| `parentId` | string | Parent folder ID |
-| `parentName` | string | Parent folder name |
-
-### `box_download_file`
-
-Download a file from Box
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileId` | string | Yes | The ID of the file to download |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `file` | file | Downloaded file stored in execution files |
-| `content` | string | Base64 encoded file content |
-
-### `box_get_file_info`
-
-Get detailed information about a file in Box
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileId` | string | Yes | The ID of the file to get information about |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | File ID |
-| `name` | string | File name |
-| `description` | string | File description |
-| `size` | number | File size in bytes |
-| `sha1` | string | SHA1 hash of file content |
-| `createdAt` | string | Creation timestamp |
-| `modifiedAt` | string | Last modified timestamp |
-| `createdBy` | object | User who created the file |
-| `modifiedBy` | object | User who last modified the file |
-| `ownedBy` | object | User who owns the file |
-| `parentId` | string | Parent folder ID |
-| `parentName` | string | Parent folder name |
-| `sharedLink` | json | Shared link details |
-| `tags` | array | File tags |
-| `commentCount` | number | Number of comments |
-
-### `box_list_folder_items`
-
-List files and folders in a Box folder
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `folderId` | string | Yes | The ID of the folder to list items from \(use "0" for root\) |
-| `limit` | number | No | Maximum number of items to return per page |
-| `offset` | number | No | The offset for pagination |
-| `sort` | string | No | Sort field: id, name, date, or size |
-| `direction` | string | No | Sort direction: ASC or DESC |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `entries` | array | List of items in the folder |
-|   ↳ `type` | string | Item type \(file, folder, web_link\) |
-|   ↳ `id` | string | Item ID |
-|   ↳ `name` | string | Item name |
-|   ↳ `size` | number | Item size in bytes |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `modifiedAt` | string | Last modified timestamp |
-| `totalCount` | number | Total number of items in the folder |
-| `offset` | number | Current pagination offset |
-| `limit` | number | Current pagination limit |
-
-### `box_create_folder`
-
-Create a new folder in Box
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `name` | string | Yes | Name for the new folder |
-| `parentFolderId` | string | Yes | The ID of the parent folder \(use "0" for root\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Folder ID |
-| `name` | string | Folder name |
-| `createdAt` | string | Creation timestamp |
-| `modifiedAt` | string | Last modified timestamp |
-| `parentId` | string | Parent folder ID |
-| `parentName` | string | Parent folder name |
-
-### `box_delete_file`
-
-Delete a file from Box
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileId` | string | Yes | The ID of the file to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the file was successfully deleted |
-| `message` | string | Success confirmation message |
-
-### `box_delete_folder`
-
-Delete a folder from Box
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `folderId` | string | Yes | The ID of the folder to delete |
-| `recursive` | boolean | No | Delete folder and all its contents recursively |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the folder was successfully deleted |
-| `message` | string | Success confirmation message |
-
-### `box_copy_file`
-
-Copy a file to another folder in Box
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileId` | string | Yes | The ID of the file to copy |
-| `parentFolderId` | string | Yes | The ID of the destination folder |
-| `name` | string | No | Optional new name for the copied file |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | File ID |
-| `name` | string | File name |
-| `size` | number | File size in bytes |
-| `sha1` | string | SHA1 hash of file content |
-| `createdAt` | string | Creation timestamp |
-| `modifiedAt` | string | Last modified timestamp |
-| `parentId` | string | Parent folder ID |
-| `parentName` | string | Parent folder name |
-
-### `box_search`
-
-Search for files and folders in Box
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `query` | string | Yes | The search query string |
-| `limit` | number | No | Maximum number of results to return |
-| `offset` | number | No | The offset for pagination |
-| `ancestorFolderId` | string | No | Restrict search to a specific folder and its subfolders |
-| `fileExtensions` | string | No | Comma-separated file extensions to filter by \(e.g., pdf,docx\) |
-| `type` | string | No | Restrict to a specific content type: file, folder, or web_link |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `results` | array | Search results |
-|   ↳ `type` | string | Item type \(file, folder, web_link\) |
-|   ↳ `id` | string | Item ID |
-|   ↳ `name` | string | Item name |
-|   ↳ `size` | number | Item size in bytes |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `modifiedAt` | string | Last modified timestamp |
-|   ↳ `parentId` | string | Parent folder ID |
-|   ↳ `parentName` | string | Parent folder name |
-| `totalCount` | number | Total number of matching results |
-
-### `box_update_file`
-
-Update file info in Box (rename, move, change description, add tags)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileId` | string | Yes | The ID of the file to update |
-| `name` | string | No | New name for the file |
-| `description` | string | No | New description for the file \(max 256 characters\) |
-| `parentFolderId` | string | No | Move the file to a different folder by specifying the folder ID |
-| `tags` | string | No | Comma-separated tags to set on the file |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | File ID |
-| `name` | string | File name |
-| `description` | string | File description |
-| `size` | number | File size in bytes |
-| `sha1` | string | SHA1 hash of file content |
-| `createdAt` | string | Creation timestamp |
-| `modifiedAt` | string | Last modified timestamp |
-| `createdBy` | object | User who created the file |
-| `modifiedBy` | object | User who last modified the file |
-| `ownedBy` | object | User who owns the file |
-| `parentId` | string | Parent folder ID |
-| `parentName` | string | Parent folder name |
-| `sharedLink` | json | Shared link details |
-| `tags` | array | File tags |
-| `commentCount` | number | Number of comments |
-
-### `box_sign_create_request`
-
-Create a new Box Sign request to send documents for e-signature
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `sourceFileIds` | string | Yes | Comma-separated Box file IDs to send for signing |
-| `signerEmail` | string | Yes | Primary signer email address |
-| `signerRole` | string | No | Primary signer role: signer, approver, or final_copy_reader \(default: signer\) |
-| `additionalSigners` | string | No | JSON array of additional signers, e.g. \[\{"email":"user@example.com","role":"signer"\}\] |
-| `parentFolderId` | string | No | Box folder ID where signed documents will be stored \(default: user root\) |
-| `emailSubject` | string | No | Custom subject line for the signing email |
-| `emailMessage` | string | No | Custom message in the signing email body |
-| `name` | string | No | Name for the sign request |
-| `daysValid` | number | No | Number of days before the request expires \(0-730\) |
-| `areRemindersEnabled` | boolean | No | Whether to send automatic signing reminders |
-| `areTextSignaturesEnabled` | boolean | No | Whether to allow typed \(text\) signatures |
-| `signatureColor` | string | No | Signature color: blue, black, or red |
-| `redirectUrl` | string | No | URL to redirect signers to after signing |
-| `declinedRedirectUrl` | string | No | URL to redirect signers to after declining |
-| `isDocumentPreparationNeeded` | boolean | No | Whether document preparation is needed before sending |
-| `externalId` | string | No | External system reference ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Sign request ID |
-| `status` | string | Request status \(converting, created, sent, viewed, signed, cancelled, declined, expired, error_converting, error_sending, finalizing, error_finalizing\) |
-| `name` | string | Sign request name |
-| `shortId` | string | Human-readable short ID |
-| `signers` | array | List of signers |
-| `sourceFiles` | array | Source files for signing |
-| `emailSubject` | string | Custom email subject line |
-| `emailMessage` | string | Custom email message body |
-| `daysValid` | number | Number of days the request is valid |
-| `createdAt` | string | Creation timestamp |
-| `autoExpireAt` | string | Auto-expiration timestamp |
-| `prepareUrl` | string | URL for document preparation \(if preparation is needed\) |
-| `senderEmail` | string | Email of the sender |
-
-### `box_sign_get_request`
-
-Get the details and status of a Box Sign request
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `signRequestId` | string | Yes | The ID of the sign request to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Sign request ID |
-| `status` | string | Request status \(converting, created, sent, viewed, signed, cancelled, declined, expired, error_converting, error_sending, finalizing, error_finalizing\) |
-| `name` | string | Sign request name |
-| `shortId` | string | Human-readable short ID |
-| `signers` | array | List of signers |
-| `sourceFiles` | array | Source files for signing |
-| `emailSubject` | string | Custom email subject line |
-| `emailMessage` | string | Custom email message body |
-| `daysValid` | number | Number of days the request is valid |
-| `createdAt` | string | Creation timestamp |
-| `autoExpireAt` | string | Auto-expiration timestamp |
-| `prepareUrl` | string | URL for document preparation \(if preparation is needed\) |
-| `senderEmail` | string | Email of the sender |
-
-### `box_sign_list_requests`
-
-List all Box Sign requests
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | number | No | Maximum number of sign requests to return \(max 1000\) |
-| `marker` | string | No | Pagination marker from a previous response |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `signRequests` | array | List of sign requests |
-|   ↳ `id` | string | Sign request ID |
-|   ↳ `status` | string | Request status \(converting, created, sent, viewed, signed, cancelled, declined, expired, error_converting, error_sending, finalizing, error_finalizing\) |
-|   ↳ `name` | string | Sign request name |
-|   ↳ `shortId` | string | Human-readable short ID |
-|   ↳ `signers` | array | List of signers |
-|   ↳ `sourceFiles` | array | Source files for signing |
-|   ↳ `emailSubject` | string | Custom email subject line |
-|   ↳ `emailMessage` | string | Custom email message body |
-|   ↳ `daysValid` | number | Number of days the request is valid |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `autoExpireAt` | string | Auto-expiration timestamp |
-|   ↳ `prepareUrl` | string | URL for document preparation \(if preparation is needed\) |
-|   ↳ `senderEmail` | string | Email of the sender |
-| `count` | number | Number of sign requests returned in this page |
-| `nextMarker` | string | Marker for next page of results |
-
-### `box_sign_cancel_request`
-
-Cancel a pending Box Sign request
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `signRequestId` | string | Yes | The ID of the sign request to cancel |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Sign request ID |
-| `status` | string | Request status \(converting, created, sent, viewed, signed, cancelled, declined, expired, error_converting, error_sending, finalizing, error_finalizing\) |
-| `name` | string | Sign request name |
-| `shortId` | string | Human-readable short ID |
-| `signers` | array | List of signers |
-| `sourceFiles` | array | Source files for signing |
-| `emailSubject` | string | Custom email subject line |
-| `emailMessage` | string | Custom email message body |
-| `daysValid` | number | Number of days the request is valid |
-| `createdAt` | string | Creation timestamp |
-| `autoExpireAt` | string | Auto-expiration timestamp |
-| `prepareUrl` | string | URL for document preparation \(if preparation is needed\) |
-| `senderEmail` | string | Email of the sender |
-
-### `box_sign_resend_request`
-
-Resend a Box Sign request to signers who have not yet signed
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `signRequestId` | string | Yes | The ID of the sign request to resend |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Success confirmation message |
-
-

apps/docs/content/docs/en/tools/cloudformation.mdx

@@ -1,183 +0,0 @@
----
-title: CloudFormation
-description: Manage and inspect AWS CloudFormation stacks, resources, and drift
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="cloudformation"
-  color="linear-gradient(45deg, #B0084D 0%, #FF4F8B 100%)"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[AWS CloudFormation](https://aws.amazon.com/cloudformation/) is an infrastructure-as-code service that lets you model, provision, and manage AWS resources by treating infrastructure as code. CloudFormation uses templates to describe the resources you need and their dependencies, so you can launch and configure them together as a stack.
-
-With the CloudFormation integration, you can:
-
-- **Describe Stacks**: List all stacks in a region or get detailed information about a specific stack, including its status, outputs, tags, and drift information
-- **List Stack Resources**: Enumerate every resource in a stack with its logical ID, physical ID, type, status, and drift status
-- **Describe Stack Events**: View the full event history for a stack to understand what happened during create, update, or delete operations
-- **Detect Stack Drift**: Initiate drift detection to check whether any resources in a stack have been modified outside of CloudFormation
-- **Drift Detection Status**: Poll the results of a drift detection operation to see which resources have drifted and how many
-- **Get Template**: Retrieve the original template body (JSON or YAML) used to create or update a stack
-- **Validate Template**: Check a CloudFormation template for syntax errors, required capabilities, parameters, and declared transforms before deploying
-
-In Sim, the CloudFormation integration enables your agents to monitor infrastructure state, detect configuration drift, audit stack resources, and validate templates as part of automated SRE and DevOps workflows. This is especially powerful when combined with CloudWatch for observability and SNS for alerting, creating end-to-end infrastructure monitoring pipelines.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate AWS CloudFormation into workflows. Describe stacks, list resources, detect drift, view stack events, retrieve templates, and validate templates. Requires AWS access key and secret access key.
-
-
-
-## Tools
-
-### `cloudformation_describe_stacks`
-
-List and describe CloudFormation stacks
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `stackName` | string | No | Stack name or ID to describe \(omit to list all stacks\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `stacks` | array | List of CloudFormation stacks with status, outputs, and tags |
-
-### `cloudformation_list_stack_resources`
-
-List all resources in a CloudFormation stack
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `stackName` | string | Yes | Stack name or ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `resources` | array | List of stack resources with type, status, and drift information |
-
-### `cloudformation_detect_stack_drift`
-
-Initiate drift detection on a CloudFormation stack
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `stackName` | string | Yes | Stack name or ID to detect drift on |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `stackDriftDetectionId` | string | ID to use with Describe Stack Drift Detection Status to check results |
-
-### `cloudformation_describe_stack_drift_detection_status`
-
-Check the status of a stack drift detection operation
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `stackDriftDetectionId` | string | Yes | The drift detection ID returned by Detect Stack Drift |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `stackId` | string | The stack ID |
-| `stackDriftDetectionId` | string | The drift detection ID |
-| `stackDriftStatus` | string | Drift status \(DRIFTED, IN_SYNC, NOT_CHECKED\) |
-| `detectionStatus` | string | Detection status \(DETECTION_IN_PROGRESS, DETECTION_COMPLETE, DETECTION_FAILED\) |
-| `detectionStatusReason` | string | Reason if detection failed |
-| `driftedStackResourceCount` | number | Number of resources that have drifted |
-| `timestamp` | number | Timestamp of the detection |
-
-### `cloudformation_describe_stack_events`
-
-Get the event history for a CloudFormation stack
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `stackName` | string | Yes | Stack name or ID |
-| `limit` | number | No | Maximum number of events to return \(default: 50\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `events` | array | List of stack events with resource status and timestamps |
-
-### `cloudformation_get_template`
-
-Retrieve the template body for a CloudFormation stack
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `stackName` | string | Yes | Stack name or ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `templateBody` | string | The template body as a JSON or YAML string |
-| `stagesAvailable` | array | Available template stages |
-
-### `cloudformation_validate_template`
-
-Validate a CloudFormation template for syntax and structural correctness
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `templateBody` | string | Yes | The CloudFormation template body \(JSON or YAML\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `description` | string | Template description |
-| `parameters` | array | Template parameters with defaults and descriptions |
-| `capabilities` | array | Required capabilities \(e.g., CAPABILITY_IAM\) |
-| `capabilitiesReason` | string | Reason capabilities are required |
-| `declaredTransforms` | array | Transforms used in the template \(e.g., AWS::Serverless-2016-10-31\) |
-
-

apps/docs/content/docs/en/tools/cloudwatch.mdx

@@ -1,180 +0,0 @@
----
-title: CloudWatch
-description: Query and monitor AWS CloudWatch logs, metrics, and alarms
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="cloudwatch"
-  color="linear-gradient(45deg, #B0084D 0%, #FF4F8B 100%)"
-/>
-
-## Usage Instructions
-
-Integrate AWS CloudWatch into workflows. Run Log Insights queries, list log groups, retrieve log events, list and get metrics, and monitor alarms. Requires AWS access key and secret access key.
-
-
-
-## Tools
-
-### `cloudwatch_query_logs`
-
-Run a CloudWatch Log Insights query against one or more log groups
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `logGroupNames` | array | Yes | Log group names to query |
-| `queryString` | string | Yes | CloudWatch Log Insights query string |
-| `startTime` | number | Yes | Start time as Unix epoch seconds |
-| `endTime` | number | Yes | End time as Unix epoch seconds |
-| `limit` | number | No | Maximum number of results to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `results` | array | Query result rows |
-| `statistics` | object | Query statistics \(bytesScanned, recordsMatched, recordsScanned\) |
-| `status` | string | Query completion status |
-
-### `cloudwatch_describe_log_groups`
-
-List available CloudWatch log groups
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `prefix` | string | No | Filter log groups by name prefix |
-| `limit` | number | No | Maximum number of log groups to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `logGroups` | array | List of CloudWatch log groups with metadata |
-
-### `cloudwatch_get_log_events`
-
-Retrieve log events from a specific CloudWatch log stream
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `logGroupName` | string | Yes | CloudWatch log group name |
-| `logStreamName` | string | Yes | CloudWatch log stream name |
-| `startTime` | number | No | Start time as Unix epoch seconds |
-| `endTime` | number | No | End time as Unix epoch seconds |
-| `limit` | number | No | Maximum number of events to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `events` | array | Log events with timestamp, message, and ingestion time |
-
-### `cloudwatch_describe_log_streams`
-
-List log streams within a CloudWatch log group
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `logGroupName` | string | Yes | CloudWatch log group name |
-| `prefix` | string | No | Filter log streams by name prefix |
-| `limit` | number | No | Maximum number of log streams to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `logStreams` | array | List of log streams with metadata |
-
-### `cloudwatch_list_metrics`
-
-List available CloudWatch metrics
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `namespace` | string | No | Filter by namespace \(e.g., AWS/EC2, AWS/Lambda\) |
-| `metricName` | string | No | Filter by metric name |
-| `recentlyActive` | boolean | No | Only show metrics active in the last 3 hours |
-| `limit` | number | No | Maximum number of metrics to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `metrics` | array | List of metrics with namespace, name, and dimensions |
-
-### `cloudwatch_get_metric_statistics`
-
-Get statistics for a CloudWatch metric over a time range
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `namespace` | string | Yes | Metric namespace \(e.g., AWS/EC2, AWS/Lambda\) |
-| `metricName` | string | Yes | Metric name \(e.g., CPUUtilization, Invocations\) |
-| `startTime` | number | Yes | Start time as Unix epoch seconds |
-| `endTime` | number | Yes | End time as Unix epoch seconds |
-| `period` | number | Yes | Granularity in seconds \(e.g., 60, 300, 3600\) |
-| `statistics` | array | Yes | Statistics to retrieve \(Average, Sum, Minimum, Maximum, SampleCount\) |
-| `dimensions` | string | No | Dimensions as JSON \(e.g., \{"InstanceId": "i-1234"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `label` | string | Metric label |
-| `datapoints` | array | Datapoints with timestamp and statistics values |
-
-### `cloudwatch_describe_alarms`
-
-List and filter CloudWatch alarms
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `awsRegion` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `awsAccessKeyId` | string | Yes | AWS access key ID |
-| `awsSecretAccessKey` | string | Yes | AWS secret access key |
-| `alarmNamePrefix` | string | No | Filter alarms by name prefix |
-| `stateValue` | string | No | Filter by alarm state \(OK, ALARM, INSUFFICIENT_DATA\) |
-| `alarmType` | string | No | Filter by alarm type \(MetricAlarm, CompositeAlarm\) |
-| `limit` | number | No | Maximum number of alarms to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `alarms` | array | List of CloudWatch alarms with state and configuration |
-
-

apps/docs/content/docs/en/tools/cursor.mdx

@@ -45,7 +45,6 @@ List all cloud agents for the authenticated user with optional pagination. Retur
 | `apiKey` | string | Yes | Cursor API key |
 | `limit` | number | No | Number of agents to return \(default: 20, max: 100\) |
 | `cursor` | string | No | Pagination cursor from previous response |
-| `prUrl` | string | No | Filter agents by pull request URL |
 
 #### Output
 
@@ -174,41 +173,4 @@ Permanently delete a cloud agent. Returns API-aligned fields only.
 | --------- | ---- | ----------- |
 | `id` | string | Agent ID |
 
-### `cursor_list_artifacts`
-
-List generated artifact files for a cloud agent. Returns API-aligned fields only.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Cursor API key |
-| `agentId` | string | Yes | Unique identifier for the cloud agent \(e.g., bc_abc123\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `artifacts` | array | List of artifact files |
-|   ↳ `path` | string | Artifact file path |
-|   ↳ `size` | number | File size in bytes |
-
-### `cursor_download_artifact`
-
-Download a generated artifact file from a cloud agent. Returns the file for execution storage.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Cursor API key |
-| `agentId` | string | Yes | Unique identifier for the cloud agent \(e.g., bc_abc123\) |
-| `path` | string | Yes | Absolute path of the artifact to download \(e.g., /src/index.ts\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `file` | file | Downloaded artifact file stored in execution files |
-
 

apps/docs/content/docs/en/tools/docusign.mdx

@@ -1,230 +0,0 @@
----
-title: DocuSign
-description: Send documents for e-signature via DocuSign
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="docusign"
-  color="#FFFFFF"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[DocuSign](https://www.docusign.com) is the world's leading e-signature platform, enabling businesses to send, sign, and manage agreements digitally. With its powerful eSignature REST API, DocuSign supports the full document lifecycle from creation through completion.
-
-With the DocuSign integration in Sim, you can:
-
-- **Send envelopes**: Create and send documents for e-signature with custom recipients and signing tabs
-- **Use templates**: Send envelopes from pre-configured DocuSign templates with role assignments
-- **Track status**: Get envelope details including signing progress, timestamps, and recipient status
-- **List envelopes**: Search and filter envelopes by date range, status, and text
-- **Download documents**: Retrieve signed documents as base64-encoded files
-- **Manage recipients**: View signer and CC recipient details and signing status
-- **Void envelopes**: Cancel in-progress envelopes with a reason
-
-In Sim, the DocuSign integration enables your agents to automate document workflows end-to-end. Agents can generate agreements, send them for signature, monitor completion, and retrieve signed copies—powering contract management, HR onboarding, sales closings, and compliance processes.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Create and send envelopes for e-signature, use templates, check signing status, download signed documents, and manage recipients with DocuSign.
-
-
-
-## Tools
-
-### `docusign_send_envelope`
-
-Create and send a DocuSign envelope with a document for e-signature
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `emailSubject` | string | Yes | Email subject for the envelope |
-| `emailBody` | string | No | Email body message |
-| `signerEmail` | string | Yes | Email address of the signer |
-| `signerName` | string | Yes | Full name of the signer |
-| `ccEmail` | string | No | Email address of carbon copy recipient |
-| `ccName` | string | No | Full name of carbon copy recipient |
-| `file` | file | No | Document file to send for signature |
-| `status` | string | No | Envelope status: "sent" to send immediately, "created" for draft \(default: "sent"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `envelopeId` | string | Created envelope ID |
-| `status` | string | Envelope status |
-| `statusDateTime` | string | Status change datetime |
-| `uri` | string | Envelope URI |
-
-### `docusign_create_from_template`
-
-Create and send a DocuSign envelope using a pre-built template
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `templateId` | string | Yes | DocuSign template ID to use |
-| `emailSubject` | string | No | Override email subject \(uses template default if not set\) |
-| `emailBody` | string | No | Override email body message |
-| `templateRoles` | string | Yes | JSON array of template roles, e.g. \[\{"roleName":"Signer","name":"John","email":"john@example.com"\}\] |
-| `status` | string | No | Envelope status: "sent" to send immediately, "created" for draft \(default: "sent"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `envelopeId` | string | Created envelope ID |
-| `status` | string | Envelope status |
-| `statusDateTime` | string | Status change datetime |
-| `uri` | string | Envelope URI |
-
-### `docusign_get_envelope`
-
-Get the details and status of a DocuSign envelope
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `envelopeId` | string | Yes | The envelope ID to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `envelopeId` | string | Envelope ID |
-| `status` | string | Envelope status \(created, sent, delivered, completed, declined, voided\) |
-| `emailSubject` | string | Email subject line |
-| `sentDateTime` | string | When the envelope was sent |
-| `completedDateTime` | string | When all recipients completed signing |
-| `createdDateTime` | string | When the envelope was created |
-| `statusChangedDateTime` | string | When the status last changed |
-| `voidedReason` | string | Reason the envelope was voided |
-| `signerCount` | number | Number of signers |
-| `documentCount` | number | Number of documents |
-
-### `docusign_list_envelopes`
-
-List envelopes from your DocuSign account with optional filters
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fromDate` | string | No | Start date filter \(ISO 8601\). Defaults to 30 days ago |
-| `toDate` | string | No | End date filter \(ISO 8601\) |
-| `envelopeStatus` | string | No | Filter by status: created, sent, delivered, completed, declined, voided |
-| `searchText` | string | No | Search text to filter envelopes |
-| `count` | string | No | Maximum number of envelopes to return \(default: 25\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `envelopes` | array | Array of DocuSign envelopes |
-|   ↳ `envelopeId` | string | Unique envelope identifier |
-|   ↳ `status` | string | Envelope status \(created, sent, delivered, completed, declined, voided\) |
-|   ↳ `emailSubject` | string | Email subject line |
-|   ↳ `sentDateTime` | string | ISO 8601 datetime when envelope was sent |
-|   ↳ `completedDateTime` | string | ISO 8601 datetime when envelope was completed |
-|   ↳ `createdDateTime` | string | ISO 8601 datetime when envelope was created |
-|   ↳ `statusChangedDateTime` | string | ISO 8601 datetime of last status change |
-| `totalSetSize` | number | Total number of matching envelopes |
-| `resultSetSize` | number | Number of envelopes returned in this response |
-
-### `docusign_void_envelope`
-
-Void (cancel) a sent DocuSign envelope that has not yet been completed
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `envelopeId` | string | Yes | The envelope ID to void |
-| `voidedReason` | string | Yes | Reason for voiding the envelope |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `envelopeId` | string | Voided envelope ID |
-| `status` | string | Envelope status \(voided\) |
-
-### `docusign_download_document`
-
-Download a signed document from a completed DocuSign envelope
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `envelopeId` | string | Yes | The envelope ID containing the document |
-| `documentId` | string | No | Specific document ID to download, or "combined" for all documents merged \(default: "combined"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `base64Content` | string | Base64-encoded document content |
-| `mimeType` | string | MIME type of the document |
-| `fileName` | string | Original file name |
-
-### `docusign_list_templates`
-
-List available templates in your DocuSign account
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `searchText` | string | No | Search text to filter templates by name |
-| `count` | string | No | Maximum number of templates to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `templates` | array | Array of DocuSign templates |
-|   ↳ `templateId` | string | Template identifier |
-|   ↳ `name` | string | Template name |
-|   ↳ `description` | string | Template description |
-|   ↳ `shared` | boolean | Whether template is shared |
-|   ↳ `created` | string | ISO 8601 creation date |
-|   ↳ `lastModified` | string | ISO 8601 last modified date |
-| `totalSetSize` | number | Total number of matching templates |
-| `resultSetSize` | number | Number of templates returned in this response |
-
-### `docusign_list_recipients`
-
-Get the recipient status details for a DocuSign envelope
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `envelopeId` | string | Yes | The envelope ID to get recipients for |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `signers` | array | Array of DocuSign recipients |
-|   ↳ `recipientId` | string | Recipient identifier |
-|   ↳ `name` | string | Recipient name |
-|   ↳ `email` | string | Recipient email address |
-|   ↳ `status` | string | Recipient signing status \(sent, delivered, completed, declined\) |
-|   ↳ `signedDateTime` | string | ISO 8601 datetime when recipient signed |
-|   ↳ `deliveredDateTime` | string | ISO 8601 datetime when delivered to recipient |
-| `carbonCopies` | array | Array of carbon copy recipients |
-|   ↳ `recipientId` | string | Recipient ID |
-|   ↳ `name` | string | Recipient name |
-|   ↳ `email` | string | Recipient email |
-|   ↳ `status` | string | Recipient status |
-
-

apps/docs/content/docs/en/tools/extend.mdx

@@ -1,39 +0,0 @@
----
-title: Extend
-description: Parse and extract content from documents
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="extend_v2"
-  color="#000000"
-/>
-
-## Usage Instructions
-
-Integrate Extend AI into the workflow. Parse and extract structured content from documents or file references.
-
-
-
-## Tools
-
-### `extend_parser`
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `filePath` | string | No | URL to a document to be processed |
-| `file` | file | No | Document file to be processed |
-| `fileUpload` | object | No | File upload data from file-upload component |
-| `outputFormat` | string | No | Target output format \(markdown or spatial\). Defaults to markdown. |
-| `chunking` | string | No | Chunking strategy \(page, document, or section\). Defaults to page. |
-| `engine` | string | No | Parsing engine \(parse_performance or parse_light\). Defaults to parse_performance. |
-| `apiKey` | string | Yes | Extend API key |
-
-#### Output
-
-This tool does not produce any outputs.
-
-

apps/docs/content/docs/en/tools/file.mdx

@@ -1,6 +1,6 @@
 ---
 title: File
-description: Read and write workspace files
+description: Read and parse multiple files
 ---
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
@@ -27,7 +27,7 @@ The File Parser tool is particularly useful for scenarios where your agents need
 
 ## Usage Instructions
 
-Read and parse files from uploads or URLs, write new workspace files, or append content to existing files.
+Upload files directly or import from external URLs to get UserFile objects for use in other blocks.
 
 
 
@@ -52,45 +52,4 @@ Parse one or more uploaded files or files from URLs (text, PDF, CSV, images, etc
 | `files` | file[] | Parsed files as UserFile objects |
 | `combinedContent` | string | Combined content of all parsed files |
 
-### `file_write`
-
-Create a new workspace file. If a file with the same name already exists, a numeric suffix is added (e.g., 
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileName` | string | Yes | File name \(e.g., "data.csv"\). If a file with this name exists, a numeric suffix is added automatically. |
-| `content` | string | Yes | The text content to write to the file. |
-| `contentType` | string | No | MIME type for new files \(e.g., "text/plain"\). Auto-detected from file extension if omitted. |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | File ID |
-| `name` | string | File name |
-| `size` | number | File size in bytes |
-| `url` | string | URL to access the file |
-
-### `file_append`
-
-Append content to an existing workspace file. The file must already exist. Content is added to the end of the file.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileName` | string | Yes | Name of an existing workspace file to append to. |
-| `content` | string | Yes | The text content to append to the file. |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | File ID |
-| `name` | string | File name |
-| `size` | number | File size in bytes |
-| `url` | string | URL to access the file |
-
 

apps/docs/content/docs/en/tools/firecrawl.mdx

@@ -53,9 +53,6 @@ Extract structured content from web pages with comprehensive metadata support. C
 | `url` | string | Yes | The URL to scrape content from \(e.g., "https://example.com/page"\) |
 | `scrapeOptions` | json | No | Options for content scraping |
 | `apiKey` | string | Yes | Firecrawl API key |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -89,9 +86,6 @@ Search for information on the web using Firecrawl
 | --------- | ---- | -------- | ----------- |
 | `query` | string | Yes | The search query to use |
 | `apiKey` | string | Yes | Firecrawl API key |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -129,9 +123,6 @@ Crawl entire websites and extract structured content from all accessible pages
 | `includePaths` | json | No | URL paths to include in crawling \(e.g., \["/docs/*", "/api/*"\]\). Only these paths will be crawled |
 | `onlyMainContent` | boolean | No | Extract only main content from pages |
 | `apiKey` | string | Yes | Firecrawl API Key |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -151,6 +142,7 @@ Crawl entire websites and extract structured content from all accessible pages
 |     ↳ `statusCode` | number | HTTP status code |
 |     ↳ `ogLocaleAlternate` | array | Alternate locale versions |
 | `total` | number | Total number of pages found during crawl |
+| `creditsUsed` | number | Number of credits consumed by the crawl operation |
 
 ### `firecrawl_map`
 
@@ -169,9 +161,6 @@ Get a complete list of URLs from any website quickly and reliably. Useful for di
 | `timeout` | number | No | Request timeout in milliseconds |
 | `location` | json | No | Geographic context for proxying \(country, languages\) |
 | `apiKey` | string | Yes | Firecrawl API key |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -198,9 +187,6 @@ Extract structured data from entire webpages using natural language prompts and
 | `ignoreInvalidURLs` | boolean | No | Skip invalid URLs in the array \(default: true\) |
 | `scrapeOptions` | json | No | Advanced scraping configuration options |
 | `apiKey` | string | Yes | Firecrawl API key |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -231,6 +217,7 @@ Autonomous web data extraction agent. Searches and gathers information based on
 | `success` | boolean | Whether the agent operation was successful |
 | `status` | string | Current status of the agent job \(processing, completed, failed\) |
 | `data` | object | Extracted data from the agent |
+| `creditsUsed` | number | Number of credits consumed by this agent task |
 | `expiresAt` | string | Timestamp when the results expire \(24 hours\) |
 | `sources` | object | Array of source URLs used by the agent |
 

apps/docs/content/docs/en/tools/google_books.mdx

@@ -46,8 +46,6 @@ Search for books using the Google Books API
 | `startIndex` | number | No | Index of the first result to return \(for pagination\) |
 | `maxResults` | number | No | Maximum number of results to return \(1-40\) |
 | `langRestrict` | string | No | Restrict results to a specific language \(ISO 639-1 code\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -84,8 +82,6 @@ Get detailed information about a specific book volume
 | `apiKey` | string | Yes | Google Books API key |
 | `volumeId` | string | Yes | The ID of the volume to retrieve |
 | `projection` | string | No | Projection level \(full, lite\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 

apps/docs/content/docs/en/tools/google_maps.mdx

@@ -50,8 +50,6 @@ Get current air quality data for a location
 | `lat` | number | Yes | Latitude coordinate |
 | `lng` | number | Yes | Longitude coordinate |
 | `languageCode` | string | No | Language code for the response \(e.g., "en", "es"\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -93,8 +91,6 @@ Get directions and route information between two locations
 | `waypoints` | json | No | Array of intermediate waypoints |
 | `units` | string | No | Unit system: metric or imperial |
 | `language` | string | No | Language code for results \(e.g., en, es, fr\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -139,8 +135,6 @@ Calculate travel distance and time between multiple origins and destinations
 | `avoid` | string | No | Features to avoid: tolls, highways, or ferries |
 | `units` | string | No | Unit system: metric or imperial |
 | `language` | string | No | Language code for results \(e.g., en, es, fr\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -169,8 +163,6 @@ Get elevation data for a location
 | `apiKey` | string | Yes | Google Maps API key |
 | `lat` | number | Yes | Latitude coordinate |
 | `lng` | number | Yes | Longitude coordinate |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -193,8 +185,6 @@ Convert an address into geographic coordinates (latitude and longitude)
 | `address` | string | Yes | The address to geocode |
 | `language` | string | No | Language code for results \(e.g., en, es, fr\) |
 | `region` | string | No | Region bias as a ccTLD code \(e.g., us, uk\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -227,8 +217,6 @@ Geolocate a device using WiFi access points, cell towers, or IP address
 | `considerIp` | boolean | No | Whether to use IP address for geolocation \(default: true\) |
 | `cellTowers` | array | No | Array of cell tower objects with cellId, locationAreaCode, mobileCountryCode, mobileNetworkCode |
 | `wifiAccessPoints` | array | No | Array of WiFi access point objects with macAddress \(required\), signalStrength, etc. |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -250,8 +238,6 @@ Get detailed information about a specific place
 | `placeId` | string | Yes | Google Place ID |
 | `fields` | string | No | Comma-separated list of fields to return |
 | `language` | string | No | Language code for results \(e.g., en, es, fr\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -304,8 +290,6 @@ Search for places using a text query
 | `type` | string | No | Place type filter \(e.g., restaurant, cafe, hotel\) |
 | `language` | string | No | Language code for results \(e.g., en, es, fr\) |
 | `region` | string | No | Region bias as a ccTLD code \(e.g., us, uk\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -338,8 +322,6 @@ Convert geographic coordinates (latitude and longitude) into a human-readable ad
 | `lat` | number | Yes | Latitude coordinate |
 | `lng` | number | Yes | Longitude coordinate |
 | `language` | string | No | Language code for results \(e.g., en, es, fr\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -364,8 +346,6 @@ Snap GPS coordinates to the nearest road segment
 | `apiKey` | string | Yes | Google Maps API key with Roads API enabled |
 | `path` | string | Yes | Pipe-separated list of lat,lng coordinates \(e.g., "60.170880,24.942795\|60.170879,24.942796"\) |
 | `interpolate` | boolean | No | Whether to interpolate additional points along the road |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -419,8 +399,6 @@ Get timezone information for a location
 | `lng` | number | Yes | Longitude coordinate |
 | `timestamp` | number | No | Unix timestamp to determine DST offset \(defaults to current time\) |
 | `language` | string | No | Language code for timezone name \(e.g., en, es, fr\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -446,8 +424,6 @@ Validate and standardize a postal address
 | `regionCode` | string | No | ISO 3166-1 alpha-2 country code \(e.g., "US", "CA"\) |
 | `locality` | string | No | City or locality name |
 | `enableUspsCass` | boolean | No | Enable USPS CASS validation for US addresses |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 

apps/docs/content/docs/en/tools/google_pagespeed.mdx

@@ -55,8 +55,6 @@ Analyze a webpage for performance, accessibility, SEO, and best practices using
 | `category` | string | No | Lighthouse categories to analyze \(comma-separated\): performance, accessibility, best-practices, seo |
 | `strategy` | string | No | Analysis strategy: desktop or mobile |
 | `locale` | string | No | Locale for results \(e.g., en, fr, de\) |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 

apps/docs/content/docs/en/tools/google_translate.mdx

@@ -43,9 +43,6 @@ Translate text between languages using the Google Cloud Translation API. Support
 | `target` | string | Yes | Target language code \(e.g., "es", "fr", "de", "ja"\) |
 | `source` | string | No | Source language code. If omitted, the API will auto-detect the source language. |
 | `format` | string | No | Format of the text: "text" for plain text, "html" for HTML content |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -64,9 +61,6 @@ Detect the language of text using the Google Cloud Translation API.
 | --------- | ---- | -------- | ----------- |
 | `apiKey` | string | Yes | Google Cloud API key with Cloud Translation API enabled |
 | `text` | string | Yes | The text to detect the language of |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 

apps/docs/content/docs/en/tools/grain.mdx

@@ -138,26 +138,6 @@ Get the full transcript of a recording
 |   ↳ `end` | number | End timestamp in ms |
 |   ↳ `text` | string | Transcript text |
 
-### `grain_list_views`
-
-List available Grain views for webhook subscriptions
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Grain API key \(Personal Access Token\) |
-| `typeFilter` | string | No | Optional view type filter: recordings, highlights, or stories |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `views` | array | Array of Grain views |
-|   ↳ `id` | string | View UUID |
-|   ↳ `name` | string | View name |
-|   ↳ `type` | string | View type: recordings, highlights, or stories |
-
 ### `grain_list_teams`
 
 List all teams in the workspace
@@ -205,9 +185,15 @@ Create a webhook to receive recording events
 | --------- | ---- | -------- | ----------- |
 | `apiKey` | string | Yes | Grain API key \(Personal Access Token\) |
 | `hookUrl` | string | Yes | Webhook endpoint URL \(e.g., "https://example.com/webhooks/grain"\) |
-| `viewId` | string | Yes | Grain view ID from GET /_/public-api/views |
-| `actions` | array | No | Optional list of actions to subscribe to: added, updated, removed |
-| `items` | string | No | No description |
+| `hookType` | string | Yes | Type of webhook: "recording_added" or "upload_status" |
+| `filterBeforeDatetime` | string | No | Filter: recordings before this ISO8601 date \(e.g., "2024-01-15T00:00:00Z"\) |
+| `filterAfterDatetime` | string | No | Filter: recordings after this ISO8601 date \(e.g., "2024-01-01T00:00:00Z"\) |
+| `filterParticipantScope` | string | No | Filter: "internal" or "external" |
+| `filterTeamId` | string | No | Filter: specific team UUID \(e.g., "a1b2c3d4-e5f6-7890-abcd-ef1234567890"\) |
+| `filterMeetingTypeId` | string | No | Filter: specific meeting type UUID \(e.g., "a1b2c3d4-e5f6-7890-abcd-ef1234567890"\) |
+| `includeHighlights` | boolean | No | Include highlights in webhook payload |
+| `includeParticipants` | boolean | No | Include participants in webhook payload |
+| `includeAiSummary` | boolean | No | Include AI summary in webhook payload |
 
 #### Output
 
@@ -216,8 +202,9 @@ Create a webhook to receive recording events
 | `id` | string | Hook UUID |
 | `enabled` | boolean | Whether hook is active |
 | `hook_url` | string | The webhook URL |
-| `view_id` | string | Grain view ID for the webhook |
-| `actions` | array | Configured actions for the webhook |
+| `hook_type` | string | Type of hook: recording_added or upload_status |
+| `filter` | object | Applied filters |
+| `include` | object | Included fields |
 | `inserted_at` | string | ISO8601 creation timestamp |
 
 ### `grain_list_hooks`
@@ -238,8 +225,9 @@ List all webhooks for the account
 |   ↳ `id` | string | Hook UUID |
 |   ↳ `enabled` | boolean | Whether hook is active |
 |   ↳ `hook_url` | string | Webhook URL |
-|   ↳ `view_id` | string | Grain view ID |
-|   ↳ `actions` | array | Configured actions |
+|   ↳ `hook_type` | string | Type: recording_added or upload_status |
+|   ↳ `filter` | object | Applied filters |
+|   ↳ `include` | object | Included fields |
 |   ↳ `inserted_at` | string | Creation timestamp |
 
 ### `grain_delete_hook`

apps/docs/content/docs/en/tools/granola.mdx

@@ -1,92 +0,0 @@
----
-title: Granola
-description: Access meeting notes and transcripts from Granola
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="granola"
-  color="#B2C147"
-/>
-
-## Usage Instructions
-
-Integrate Granola into your workflow to retrieve meeting notes, summaries, attendees, and transcripts.
-
-
-
-## Tools
-
-### `granola_list_notes`
-
-Lists meeting notes from Granola with optional date filters and pagination.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Granola API key |
-| `createdBefore` | string | No | Return notes created before this date \(ISO 8601\) |
-| `createdAfter` | string | No | Return notes created after this date \(ISO 8601\) |
-| `updatedAfter` | string | No | Return notes updated after this date \(ISO 8601\) |
-| `cursor` | string | No | Pagination cursor from a previous response |
-| `pageSize` | number | No | Number of notes per page \(1-30, default 10\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `notes` | json | List of meeting notes |
-|   ↳ `id` | string | Note ID |
-|   ↳ `title` | string | Note title |
-|   ↳ `ownerName` | string | Note owner name |
-|   ↳ `ownerEmail` | string | Note owner email |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last update timestamp |
-| `hasMore` | boolean | Whether more notes are available |
-| `cursor` | string | Pagination cursor for the next page |
-
-### `granola_get_note`
-
-Retrieves a specific meeting note from Granola by ID, including summary, attendees, calendar event details, and optionally the transcript.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Granola API key |
-| `noteId` | string | Yes | The note ID \(e.g., not_1d3tmYTlCICgjy\) |
-| `includeTranscript` | string | No | Whether to include the meeting transcript |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Note ID |
-| `title` | string | Note title |
-| `ownerName` | string | Note owner name |
-| `ownerEmail` | string | Note owner email |
-| `createdAt` | string | Creation timestamp |
-| `updatedAt` | string | Last update timestamp |
-| `summaryText` | string | Plain text summary of the meeting |
-| `summaryMarkdown` | string | Markdown-formatted summary of the meeting |
-| `attendees` | json | Meeting attendees |
-|   ↳ `name` | string | Attendee name |
-|   ↳ `email` | string | Attendee email |
-| `folders` | json | Folders the note belongs to |
-|   ↳ `id` | string | Folder ID |
-|   ↳ `name` | string | Folder name |
-| `calendarEventTitle` | string | Calendar event title |
-| `calendarOrganiser` | string | Calendar event organiser email |
-| `calendarEventId` | string | Calendar event ID |
-| `scheduledStartTime` | string | Scheduled start time |
-| `scheduledEndTime` | string | Scheduled end time |
-| `invitees` | json | Calendar event invitee emails |
-| `transcript` | json | Meeting transcript entries \(only if requested\) |
-|   ↳ `speaker` | string | Speaker source \(microphone or speaker\) |
-|   ↳ `text` | string | Transcript text |
-|   ↳ `startTime` | string | Segment start time |
-|   ↳ `endTime` | string | Segment end time |
-
-

apps/docs/content/docs/en/tools/hubspot.mdx

@@ -41,7 +41,6 @@ Retrieve all users from HubSpot account
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `limit` | string | No | Number of results to return \(default: 100, max: 100\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
 
 #### Output
 
@@ -54,9 +53,6 @@ Retrieve all users from HubSpot account
 |   ↳ `primaryTeamId` | string | Primary team ID |
 |   ↳ `secondaryTeamIds` | array | Secondary team IDs |
 |   ↳ `superAdmin` | boolean | Whether user is a super admin |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
 | `totalItems` | number | Total number of users returned |
 | `success` | boolean | Operation success status |
 
@@ -234,7 +230,7 @@ Search for contacts in HubSpot using filters, sorting, and queries
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `filterGroups` | array | No | Array of filter groups as JSON. Each group contains "filters" array with objects having "propertyName", "operator" \(e.g., "EQ", "CONTAINS_TOKEN", "GT"\), and "value" |
+| `filterGroups` | array | No | Array of filter groups as JSON. Each group contains "filters" array with objects having "propertyName", "operator" \(e.g., "EQ", "CONTAINS"\), and "value" |
 | `sorts` | array | No | Array of sort objects as JSON with "propertyName" and "direction" \("ASCENDING" or "DESCENDING"\) |
 | `query` | string | No | Search query string to match against contact name, email, and other text fields |
 | `properties` | array | No | Array of HubSpot property names to return \(e.g., \["email", "firstname", "lastname", "phone"\]\) |
@@ -453,7 +449,7 @@ Search for companies in HubSpot using filters, sorting, and queries
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `filterGroups` | array | No | Array of filter groups as JSON. Each group contains "filters" array with objects having "propertyName", "operator" \(e.g., "EQ", "CONTAINS_TOKEN", "GT"\), and "value" |
+| `filterGroups` | array | No | Array of filter groups as JSON. Each group contains "filters" array with objects having "propertyName", "operator" \(e.g., "EQ", "CONTAINS"\), and "value" |
 | `sorts` | array | No | Array of sort objects as JSON with "propertyName" and "direction" \("ASCENDING" or "DESCENDING"\) |
 | `query` | string | No | Search query string to match against company name, domain, and other text fields |
 | `properties` | array | No | Array of HubSpot property names to return \(e.g., \["name", "domain", "industry"\]\) |
@@ -501,747 +497,30 @@ Retrieve all deals from HubSpot account with pagination support
 
 #### Input
 
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | string | No | Maximum number of results per page \(max 100, default 10\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "dealname,amount,dealstage"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "contacts,companies"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deals` | array | Array of HubSpot deal records |
-|   ↳ `dealname` | string | Deal name |
-|   ↳ `amount` | string | Deal amount |
-|   ↳ `dealstage` | string | Current deal stage |
-|   ↳ `pipeline` | string | Pipeline the deal is in |
-|   ↳ `closedate` | string | Expected close date \(ISO 8601\) |
-|   ↳ `dealtype` | string | Deal type \(New Business, Existing Business, etc.\) |
-|   ↳ `description` | string | Deal description |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Deal creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-|   ↳ `num_associated_contacts` | string | Number of associated contacts |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_deal`
-
-Retrieve a single deal by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `dealId` | string | Yes | The HubSpot deal ID to retrieve |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "dealname,amount,dealstage"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "contacts,companies"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deal` | object | HubSpot deal record |
-|   ↳ `dealname` | string | Deal name |
-|   ↳ `amount` | string | Deal amount |
-|   ↳ `dealstage` | string | Current deal stage |
-|   ↳ `pipeline` | string | Pipeline the deal is in |
-|   ↳ `closedate` | string | Expected close date \(ISO 8601\) |
-|   ↳ `dealtype` | string | Deal type \(New Business, Existing Business, etc.\) |
-|   ↳ `description` | string | Deal description |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Deal creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-|   ↳ `num_associated_contacts` | string | Number of associated contacts |
-| `dealId` | string | The retrieved deal ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_create_deal`
-
-Create a new deal in HubSpot. Requires at least a dealname property
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `properties` | object | Yes | Deal properties as JSON object. Must include dealname \(e.g., \{"dealname": "New Deal", "amount": "5000", "dealstage": "appointmentscheduled"\}\) |
-| `associations` | array | No | Array of associations to create with the deal as JSON. Each object should have "to.id" and "types" array with "associationCategory" and "associationTypeId" |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deal` | object | HubSpot deal record |
-|   ↳ `dealname` | string | Deal name |
-|   ↳ `amount` | string | Deal amount |
-|   ↳ `dealstage` | string | Current deal stage |
-|   ↳ `pipeline` | string | Pipeline the deal is in |
-|   ↳ `closedate` | string | Expected close date \(ISO 8601\) |
-|   ↳ `dealtype` | string | Deal type \(New Business, Existing Business, etc.\) |
-|   ↳ `description` | string | Deal description |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Deal creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-|   ↳ `num_associated_contacts` | string | Number of associated contacts |
-| `dealId` | string | The created deal ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_update_deal`
-
-Update an existing deal in HubSpot by ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `dealId` | string | Yes | The HubSpot deal ID to update |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | object | Yes | Deal properties to update as JSON object \(e.g., \{"amount": "10000", "dealstage": "closedwon"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deal` | object | HubSpot deal record |
-|   ↳ `dealname` | string | Deal name |
-|   ↳ `amount` | string | Deal amount |
-|   ↳ `dealstage` | string | Current deal stage |
-|   ↳ `pipeline` | string | Pipeline the deal is in |
-|   ↳ `closedate` | string | Expected close date \(ISO 8601\) |
-|   ↳ `dealtype` | string | Deal type \(New Business, Existing Business, etc.\) |
-|   ↳ `description` | string | Deal description |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Deal creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-|   ↳ `num_associated_contacts` | string | Number of associated contacts |
-| `dealId` | string | The updated deal ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_search_deals`
-
-Search for deals in HubSpot using filters, sorting, and queries
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `filterGroups` | array | No | Array of filter groups as JSON. Each group contains "filters" array with objects having "propertyName", "operator" \(e.g., "EQ", "NEQ", "CONTAINS_TOKEN", "NOT_CONTAINS_TOKEN"\), and "value" |
-| `sorts` | array | No | Array of sort objects as JSON with "propertyName" and "direction" \("ASCENDING" or "DESCENDING"\) |
-| `query` | string | No | Search query string to match against deal name and other text fields |
-| `properties` | array | No | Array of HubSpot property names to return \(e.g., \["dealname", "amount", "dealstage"\]\) |
-| `limit` | number | No | Maximum number of results to return \(max 200\) |
-| `after` | string | No | Pagination cursor for next page \(from previous response\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deals` | array | Array of HubSpot deal records |
-|   ↳ `dealname` | string | Deal name |
-|   ↳ `amount` | string | Deal amount |
-|   ↳ `dealstage` | string | Current deal stage |
-|   ↳ `pipeline` | string | Pipeline the deal is in |
-|   ↳ `closedate` | string | Expected close date \(ISO 8601\) |
-|   ↳ `dealtype` | string | Deal type \(New Business, Existing Business, etc.\) |
-|   ↳ `description` | string | Deal description |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Deal creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-|   ↳ `num_associated_contacts` | string | Number of associated contacts |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `total` | number | Total number of matching deals |
-| `success` | boolean | Operation success status |
-
-### `hubspot_list_tickets`
-
-Retrieve all tickets from HubSpot account with pagination support
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | string | No | Maximum number of results per page \(max 100, default 10\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "subject,content,hs_ticket_priority"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "contacts,companies"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `tickets` | array | Array of HubSpot ticket records |
-|   ↳ `subject` | string | Ticket subject/name |
-|   ↳ `content` | string | Ticket content/description |
-|   ↳ `hs_pipeline` | string | Pipeline the ticket is in |
-|   ↳ `hs_pipeline_stage` | string | Current pipeline stage |
-|   ↳ `hs_ticket_priority` | string | Ticket priority \(LOW, MEDIUM, HIGH\) |
-|   ↳ `hs_ticket_category` | string | Ticket category |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Ticket creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_ticket`
-
-Retrieve a single ticket by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `ticketId` | string | Yes | The HubSpot ticket ID to retrieve |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "subject,content,hs_ticket_priority"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "contacts,companies"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `ticket` | object | HubSpot ticket record |
-|   ↳ `subject` | string | Ticket subject/name |
-|   ↳ `content` | string | Ticket content/description |
-|   ↳ `hs_pipeline` | string | Pipeline the ticket is in |
-|   ↳ `hs_pipeline_stage` | string | Current pipeline stage |
-|   ↳ `hs_ticket_priority` | string | Ticket priority \(LOW, MEDIUM, HIGH\) |
-|   ↳ `hs_ticket_category` | string | Ticket category |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Ticket creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `ticketId` | string | The retrieved ticket ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_create_ticket`
-
-Create a new ticket in HubSpot. Requires subject and hs_pipeline_stage properties
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `properties` | object | Yes | Ticket properties as JSON object. Must include subject and hs_pipeline_stage \(e.g., \{"subject": "Support request", "hs_pipeline_stage": "1", "hs_ticket_priority": "HIGH"\}\) |
-| `associations` | array | No | Array of associations to create with the ticket as JSON. Each object should have "to.id" and "types" array with "associationCategory" and "associationTypeId" |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `ticket` | object | HubSpot ticket record |
-|   ↳ `subject` | string | Ticket subject/name |
-|   ↳ `content` | string | Ticket content/description |
-|   ↳ `hs_pipeline` | string | Pipeline the ticket is in |
-|   ↳ `hs_pipeline_stage` | string | Current pipeline stage |
-|   ↳ `hs_ticket_priority` | string | Ticket priority \(LOW, MEDIUM, HIGH\) |
-|   ↳ `hs_ticket_category` | string | Ticket category |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Ticket creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `ticketId` | string | The created ticket ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_update_ticket`
-
-Update an existing ticket in HubSpot by ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `ticketId` | string | Yes | The HubSpot ticket ID to update |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | object | Yes | Ticket properties to update as JSON object \(e.g., \{"subject": "Updated subject", "hs_ticket_priority": "HIGH"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `ticket` | object | HubSpot ticket record |
-|   ↳ `subject` | string | Ticket subject/name |
-|   ↳ `content` | string | Ticket content/description |
-|   ↳ `hs_pipeline` | string | Pipeline the ticket is in |
-|   ↳ `hs_pipeline_stage` | string | Current pipeline stage |
-|   ↳ `hs_ticket_priority` | string | Ticket priority \(LOW, MEDIUM, HIGH\) |
-|   ↳ `hs_ticket_category` | string | Ticket category |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Ticket creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `ticketId` | string | The updated ticket ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_search_tickets`
-
-Search for tickets in HubSpot using filters, sorting, and queries
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `filterGroups` | array | No | Array of filter groups as JSON. Each group contains "filters" array with objects having "propertyName", "operator" \(e.g., "EQ", "NEQ", "CONTAINS_TOKEN", "NOT_CONTAINS_TOKEN"\), and "value" |
-| `sorts` | array | No | Array of sort objects as JSON with "propertyName" and "direction" \("ASCENDING" or "DESCENDING"\) |
-| `query` | string | No | Search query string to match against ticket subject and other text fields |
-| `properties` | array | No | Array of HubSpot property names to return \(e.g., \["subject", "content", "hs_ticket_priority"\]\) |
-| `limit` | number | No | Maximum number of results to return \(max 200\) |
-| `after` | string | No | Pagination cursor for next page \(from previous response\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `tickets` | array | Array of HubSpot ticket records |
-|   ↳ `subject` | string | Ticket subject/name |
-|   ↳ `content` | string | Ticket content/description |
-|   ↳ `hs_pipeline` | string | Pipeline the ticket is in |
-|   ↳ `hs_pipeline_stage` | string | Current pipeline stage |
-|   ↳ `hs_ticket_priority` | string | Ticket priority \(LOW, MEDIUM, HIGH\) |
-|   ↳ `hs_ticket_category` | string | Ticket category |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Ticket creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `total` | number | Total number of matching tickets |
-| `success` | boolean | Operation success status |
-
-### `hubspot_list_line_items`
-
-Retrieve all line items from HubSpot account with pagination support
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | string | No | Maximum number of results per page \(max 100, default 10\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "name,quantity,price,amount"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "deals,quotes"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `lineItems` | array | Array of HubSpot line item records |
-|   ↳ `name` | string | Line item name |
-|   ↳ `description` | string | Full description of the product |
-|   ↳ `hs_sku` | string | Unique product identifier \(SKU\) |
-|   ↳ `quantity` | string | Number of units included |
-|   ↳ `price` | string | Unit price |
-|   ↳ `amount` | string | Total cost \(quantity * unit price\) |
-|   ↳ `hs_line_item_currency_code` | string | Currency code |
-|   ↳ `recurringbillingfrequency` | string | Recurring billing frequency |
-|   ↳ `hs_recurring_billing_start_date` | string | Recurring billing start date |
-|   ↳ `hs_recurring_billing_end_date` | string | Recurring billing end date |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_line_item`
-
-Retrieve a single line item by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `lineItemId` | string | Yes | The HubSpot line item ID to retrieve |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "name,quantity,price,amount"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "deals,quotes"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `lineItem` | object | HubSpot line item record |
-|   ↳ `name` | string | Line item name |
-|   ↳ `description` | string | Full description of the product |
-|   ↳ `hs_sku` | string | Unique product identifier \(SKU\) |
-|   ↳ `quantity` | string | Number of units included |
-|   ↳ `price` | string | Unit price |
-|   ↳ `amount` | string | Total cost \(quantity * unit price\) |
-|   ↳ `hs_line_item_currency_code` | string | Currency code |
-|   ↳ `recurringbillingfrequency` | string | Recurring billing frequency |
-|   ↳ `hs_recurring_billing_start_date` | string | Recurring billing start date |
-|   ↳ `hs_recurring_billing_end_date` | string | Recurring billing end date |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `lineItemId` | string | The retrieved line item ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_create_line_item`
-
-Create a new line item in HubSpot. Requires at least a name property
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `properties` | object | Yes | Line item properties as JSON object \(e.g., \{"name": "Product A", "quantity": "2", "price": "50.00", "hs_sku": "SKU-001"\}\) |
-| `associations` | array | No | Array of associations to create with the line item as JSON. Each object should have "to.id" and "types" array with "associationCategory" and "associationTypeId" |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `lineItem` | object | HubSpot line item record |
-|   ↳ `name` | string | Line item name |
-|   ↳ `description` | string | Full description of the product |
-|   ↳ `hs_sku` | string | Unique product identifier \(SKU\) |
-|   ↳ `quantity` | string | Number of units included |
-|   ↳ `price` | string | Unit price |
-|   ↳ `amount` | string | Total cost \(quantity * unit price\) |
-|   ↳ `hs_line_item_currency_code` | string | Currency code |
-|   ↳ `recurringbillingfrequency` | string | Recurring billing frequency |
-|   ↳ `hs_recurring_billing_start_date` | string | Recurring billing start date |
-|   ↳ `hs_recurring_billing_end_date` | string | Recurring billing end date |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `lineItemId` | string | The created line item ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_update_line_item`
-
-Update an existing line item in HubSpot by ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `lineItemId` | string | Yes | The HubSpot line item ID to update |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | object | Yes | Line item properties to update as JSON object \(e.g., \{"quantity": "5", "price": "25.00"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `lineItem` | object | HubSpot line item record |
-|   ↳ `name` | string | Line item name |
-|   ↳ `description` | string | Full description of the product |
-|   ↳ `hs_sku` | string | Unique product identifier \(SKU\) |
-|   ↳ `quantity` | string | Number of units included |
-|   ↳ `price` | string | Unit price |
-|   ↳ `amount` | string | Total cost \(quantity * unit price\) |
-|   ↳ `hs_line_item_currency_code` | string | Currency code |
-|   ↳ `recurringbillingfrequency` | string | Recurring billing frequency |
-|   ↳ `hs_recurring_billing_start_date` | string | Recurring billing start date |
-|   ↳ `hs_recurring_billing_end_date` | string | Recurring billing end date |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `lineItemId` | string | The updated line item ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_list_quotes`
-
-Retrieve all quotes from HubSpot account with pagination support
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | string | No | Maximum number of results per page \(max 100, default 10\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "hs_title,hs_expiration_date,hs_status"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "deals,line_items"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `quotes` | array | Array of HubSpot quote records |
-|   ↳ `hs_title` | string | Quote name/title |
-|   ↳ `hs_expiration_date` | string | Expiration date |
-|   ↳ `hs_status` | string | Quote status |
-|   ↳ `hs_esign_enabled` | string | Whether e-signatures are enabled |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_quote`
-
-Retrieve a single quote by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `quoteId` | string | Yes | The HubSpot quote ID to retrieve |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "hs_title,hs_expiration_date,hs_status"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "deals,line_items"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `quote` | object | HubSpot quote record |
-|   ↳ `hs_title` | string | Quote name/title |
-|   ↳ `hs_expiration_date` | string | Expiration date |
-|   ↳ `hs_status` | string | Quote status |
-|   ↳ `hs_esign_enabled` | string | Whether e-signatures are enabled |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `quoteId` | string | The retrieved quote ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_list_appointments`
-
-Retrieve all appointments from HubSpot account with pagination support
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | string | No | Maximum number of results per page \(max 100, default 10\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "hs_meeting_title,hs_meeting_start_time"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "contacts,companies"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `appointments` | array | Array of HubSpot appointment records |
-|   ↳ `hs_appointment_type` | string | Appointment type |
-|   ↳ `hs_meeting_title` | string | Meeting title |
-|   ↳ `hs_meeting_start_time` | string | Start time \(ISO 8601\) |
-|   ↳ `hs_meeting_end_time` | string | End time \(ISO 8601\) |
-|   ↳ `hs_meeting_location` | string | Meeting location |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `hs_createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_appointment`
-
-Retrieve a single appointment by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `appointmentId` | string | Yes | The HubSpot appointment ID to retrieve |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "hs_meeting_title,hs_meeting_start_time"\) |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "contacts,companies"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `appointment` | object | HubSpot appointment record |
-|   ↳ `hs_appointment_type` | string | Appointment type |
-|   ↳ `hs_meeting_title` | string | Meeting title |
-|   ↳ `hs_meeting_start_time` | string | Start time \(ISO 8601\) |
-|   ↳ `hs_meeting_end_time` | string | End time \(ISO 8601\) |
-|   ↳ `hs_meeting_location` | string | Meeting location |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `hs_createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `appointmentId` | string | The retrieved appointment ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_create_appointment`
-
-Create a new appointment in HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `properties` | object | Yes | Appointment properties as JSON object \(e.g., \{"hs_meeting_title": "Discovery Call", "hs_meeting_start_time": "2024-01-15T10:00:00Z", "hs_meeting_end_time": "2024-01-15T11:00:00Z"\}\) |
-| `associations` | array | No | Array of associations to create with the appointment as JSON. Each object should have "to.id" and "types" array with "associationCategory" and "associationTypeId" |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `appointment` | object | HubSpot appointment record |
-|   ↳ `hs_appointment_type` | string | Appointment type |
-|   ↳ `hs_meeting_title` | string | Meeting title |
-|   ↳ `hs_meeting_start_time` | string | Start time \(ISO 8601\) |
-|   ↳ `hs_meeting_end_time` | string | End time \(ISO 8601\) |
-|   ↳ `hs_meeting_location` | string | Meeting location |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `hs_createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `appointmentId` | string | The created appointment ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_update_appointment`
-
-Update an existing appointment in HubSpot by ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `appointmentId` | string | Yes | The HubSpot appointment ID to update |
-| `idProperty` | string | No | Property to use as unique identifier. If not specified, uses record ID |
-| `properties` | object | Yes | Appointment properties to update as JSON object \(e.g., \{"hs_meeting_title": "Updated Call", "hs_meeting_location": "Zoom"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `appointment` | object | HubSpot appointment record |
-|   ↳ `hs_appointment_type` | string | Appointment type |
-|   ↳ `hs_meeting_title` | string | Meeting title |
-|   ↳ `hs_meeting_start_time` | string | Start time \(ISO 8601\) |
-|   ↳ `hs_meeting_end_time` | string | End time \(ISO 8601\) |
-|   ↳ `hs_meeting_location` | string | Meeting location |
-|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
-|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
-|   ↳ `hs_createdate` | string | Creation date \(ISO 8601\) |
-|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
-| `appointmentId` | string | The updated appointment ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_list_carts`
-
-Retrieve all carts from HubSpot account with pagination support
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | string | No | Maximum number of results per page \(max 100, default 10\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `carts` | array | Array of HubSpot CRM records |
-|   ↳ `id` | string | Unique record ID \(hs_object_id\) |
-|   ↳ `createdAt` | string | Record creation timestamp \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Record last updated timestamp \(ISO 8601\) |
-|   ↳ `archived` | boolean | Whether the record is archived |
-|   ↳ `properties` | object | Record properties |
-|   ↳ `associations` | object | Associated records |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_cart`
-
-Retrieve a single cart by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `cartId` | string | Yes | The HubSpot cart ID to retrieve |
-| `properties` | string | No | Comma-separated list of HubSpot property names to return |
-| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `cart` | object | HubSpot CRM record |
-|   ↳ `id` | string | Unique record ID \(hs_object_id\) |
-|   ↳ `createdAt` | string | Record creation timestamp \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Record last updated timestamp \(ISO 8601\) |
-|   ↳ `archived` | boolean | Whether the record is archived |
-|   ↳ `properties` | object | Record properties |
-|   ↳ `associations` | object | Associated records |
-| `cartId` | string | The retrieved cart ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_list_owners`
-
-Retrieve all owners from HubSpot account with pagination support
-
-#### Input
-
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `limit` | string | No | Maximum number of results per page \(max 100, default 100\) |
 | `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-| `email` | string | No | Filter owners by email address |
+| `properties` | string | No | Comma-separated list of HubSpot property names to return \(e.g., "dealname,amount,dealstage"\) |
+| `associations` | string | No | Comma-separated list of object types to retrieve associated IDs for \(e.g., "contacts,companies"\) |
 
 #### Output
 
 | Parameter | Type | Description |
 | --------- | ---- | ----------- |
-| `owners` | array | Array of HubSpot owner objects |
-|   ↳ `id` | string | Owner ID |
-|   ↳ `email` | string | Owner email address |
-|   ↳ `firstName` | string | Owner first name |
-|   ↳ `lastName` | string | Owner last name |
-|   ↳ `userId` | number | Associated user ID |
-|   ↳ `teams` | array | Teams the owner belongs to |
-|     ↳ `id` | string | Team ID |
-|     ↳ `name` | string | Team name |
-|   ↳ `createdAt` | string | Creation date \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Last updated date \(ISO 8601\) |
-|   ↳ `archived` | boolean | Whether the owner is archived |
+| `deals` | array | Array of HubSpot deal records |
+|   ↳ `dealname` | string | Deal name |
+|   ↳ `amount` | string | Deal amount |
+|   ↳ `dealstage` | string | Current deal stage |
+|   ↳ `pipeline` | string | Pipeline the deal is in |
+|   ↳ `closedate` | string | Expected close date \(ISO 8601\) |
+|   ↳ `dealtype` | string | Deal type \(New Business, Existing Business, etc.\) |
+|   ↳ `description` | string | Deal description |
+|   ↳ `hubspot_owner_id` | string | HubSpot owner ID |
+|   ↳ `hs_object_id` | string | HubSpot object ID \(same as record ID\) |
+|   ↳ `createdate` | string | Deal creation date \(ISO 8601\) |
+|   ↳ `hs_lastmodifieddate` | string | Last modified date \(ISO 8601\) |
+|   ↳ `num_associated_contacts` | string | Number of associated contacts |
 | `paging` | object | Pagination information for fetching more results |
 |   ↳ `after` | string | Cursor for next page of results |
 |   ↳ `link` | string | Link to next page |
@@ -1250,170 +529,4 @@ Retrieve all owners from HubSpot account with pagination support
 |   ↳ `hasMore` | boolean | Whether more records are available |
 | `success` | boolean | Operation success status |
 
-### `hubspot_list_marketing_events`
-
-Retrieve all marketing events from HubSpot account with pagination support
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `limit` | string | No | Maximum number of results per page \(max 100, default 10\) |
-| `after` | string | No | Pagination cursor for next page of results \(from previous response\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `events` | array | Array of HubSpot marketing event objects |
-|   ↳ `objectId` | string | Unique event ID \(HubSpot internal\) |
-|   ↳ `eventName` | string | Event name |
-|   ↳ `eventType` | string | Event type |
-|   ↳ `eventStatus` | string | Event status |
-|   ↳ `eventDescription` | string | Event description |
-|   ↳ `eventUrl` | string | Event URL |
-|   ↳ `eventOrganizer` | string | Event organizer |
-|   ↳ `startDateTime` | string | Start date/time \(ISO 8601\) |
-|   ↳ `endDateTime` | string | End date/time \(ISO 8601\) |
-|   ↳ `eventCancelled` | boolean | Whether event is cancelled |
-|   ↳ `eventCompleted` | boolean | Whether event is completed |
-|   ↳ `registrants` | number | Number of registrants |
-|   ↳ `attendees` | number | Number of attendees |
-|   ↳ `cancellations` | number | Number of cancellations |
-|   ↳ `noShows` | number | Number of no-shows |
-|   ↳ `externalEventId` | string | External event ID |
-|   ↳ `createdAt` | string | Creation date \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Last updated date \(ISO 8601\) |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_marketing_event`
-
-Retrieve a single marketing event by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `eventId` | string | Yes | The HubSpot marketing event objectId to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `event` | object | HubSpot marketing event |
-|   ↳ `objectId` | string | Unique event ID \(HubSpot internal\) |
-|   ↳ `eventName` | string | Event name |
-|   ↳ `eventType` | string | Event type |
-|   ↳ `eventStatus` | string | Event status |
-|   ↳ `eventDescription` | string | Event description |
-|   ↳ `eventUrl` | string | Event URL |
-|   ↳ `eventOrganizer` | string | Event organizer |
-|   ↳ `startDateTime` | string | Start date/time \(ISO 8601\) |
-|   ↳ `endDateTime` | string | End date/time \(ISO 8601\) |
-|   ↳ `eventCancelled` | boolean | Whether event is cancelled |
-|   ↳ `eventCompleted` | boolean | Whether event is completed |
-|   ↳ `registrants` | number | Number of registrants |
-|   ↳ `attendees` | number | Number of attendees |
-|   ↳ `cancellations` | number | Number of cancellations |
-|   ↳ `noShows` | number | Number of no-shows |
-|   ↳ `externalEventId` | string | External event ID |
-|   ↳ `createdAt` | string | Creation date \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Last updated date \(ISO 8601\) |
-| `eventId` | string | The retrieved marketing event ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_list_lists`
-
-Search and retrieve lists from HubSpot account
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `query` | string | No | Search query to filter lists by name. Leave empty to return all lists. |
-| `count` | string | No | Maximum number of results to return \(default 20, max 500\) |
-| `offset` | string | No | Pagination offset for next page of results \(use the offset value from previous response\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `lists` | array | Array of HubSpot list objects |
-|   ↳ `listId` | string | List ID |
-|   ↳ `name` | string | List name |
-|   ↳ `objectTypeId` | string | Object type ID \(e.g., 0-1 for contacts\) |
-|   ↳ `processingType` | string | Processing type \(MANUAL, DYNAMIC, SNAPSHOT\) |
-|   ↳ `processingStatus` | string | Processing status \(COMPLETE, PROCESSING\) |
-|   ↳ `listVersion` | number | List version number |
-|   ↳ `createdAt` | string | Creation date \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Last updated date \(ISO 8601\) |
-| `paging` | object | Pagination information for fetching more results |
-|   ↳ `after` | string | Cursor for next page of results |
-|   ↳ `link` | string | Link to next page |
-| `metadata` | object | Response metadata |
-|   ↳ `totalReturned` | number | Number of records returned in this response |
-|   ↳ `hasMore` | boolean | Whether more records are available |
-|   ↳ `total` | number | Total number of lists matching the query |
-| `success` | boolean | Operation success status |
-
-### `hubspot_get_list`
-
-Retrieve a single list by ID from HubSpot
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `listId` | string | Yes | The HubSpot list ID to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `list` | object | HubSpot list |
-|   ↳ `listId` | string | List ID |
-|   ↳ `name` | string | List name |
-|   ↳ `objectTypeId` | string | Object type ID \(e.g., 0-1 for contacts\) |
-|   ↳ `processingType` | string | Processing type \(MANUAL, DYNAMIC, SNAPSHOT\) |
-|   ↳ `processingStatus` | string | Processing status \(COMPLETE, PROCESSING\) |
-|   ↳ `listVersion` | number | List version number |
-|   ↳ `createdAt` | string | Creation date \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Last updated date \(ISO 8601\) |
-| `listId` | string | The retrieved list ID |
-| `success` | boolean | Operation success status |
-
-### `hubspot_create_list`
-
-Create a new list in HubSpot. Specify the object type and processing type (MANUAL or DYNAMIC)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `name` | string | Yes | Name of the list |
-| `objectTypeId` | string | Yes | Object type ID \(e.g., "0-1" for contacts, "0-2" for companies\) |
-| `processingType` | string | Yes | Processing type: "MANUAL" for static lists or "DYNAMIC" for active lists |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `list` | object | HubSpot list |
-|   ↳ `listId` | string | List ID |
-|   ↳ `name` | string | List name |
-|   ↳ `objectTypeId` | string | Object type ID \(e.g., 0-1 for contacts\) |
-|   ↳ `processingType` | string | Processing type \(MANUAL, DYNAMIC, SNAPSHOT\) |
-|   ↳ `processingStatus` | string | Processing status \(COMPLETE, PROCESSING\) |
-|   ↳ `listVersion` | number | List version number |
-|   ↳ `createdAt` | string | Creation date \(ISO 8601\) |
-|   ↳ `updatedAt` | string | Last updated date \(ISO 8601\) |
-| `listId` | string | The created list ID |
-| `success` | boolean | Operation success status |
-
 

apps/docs/content/docs/en/tools/infisical.mdx

@@ -1,255 +0,0 @@
----
-title: Infisical
-description: Manage secrets with Infisical
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="infisical"
-  color="#F7FE62"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Infisical](https://infisical.com/) is an open-source secrets management platform that helps teams centralize and manage application secrets, environment variables, and sensitive configuration data across their infrastructure. This integration brings Infisical's secrets management capabilities directly into Sim workflows.
-
-With Infisical in Sim, you can:
-
-- **List secrets**: Retrieve all secrets from a project environment with filtering by path, tags, and recursive subdirectory support
-- **Get a secret**: Fetch a specific secret by name, with optional version pinning and secret reference expansion
-- **Create secrets**: Add new secrets to any project environment with support for comments, paths, and tag assignments
-- **Update secrets**: Modify existing secret values, comments, names, and tags
-- **Delete secrets**: Remove secrets from a project environment
-
-In Sim, the Infisical integration enables your agents to programmatically manage secrets as part of automated workflows — for example, rotating credentials, syncing environment variables across environments, or auditing secret usage. Simply configure the Infisical block with your API key, select the operation, and provide the project ID and environment slug to get started.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Infisical into your workflow. List, get, create, update, and delete secrets across project environments.
-
-
-
-## Tools
-
-### `infisical_list_secrets`
-
-List all secrets in a project environment. Returns secret keys, values, comments, tags, and metadata.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Infisical API token |
-| `baseUrl` | string | No | Infisical instance URL \(default: "https://us.infisical.com"\). Use "https://eu.infisical.com" for EU Cloud or your self-hosted URL. |
-| `projectId` | string | Yes | The ID of the project to list secrets from |
-| `environment` | string | Yes | The environment slug \(e.g., "dev", "staging", "prod"\) |
-| `secretPath` | string | No | The path of the secrets \(default: "/"\) |
-| `recursive` | boolean | No | Whether to fetch secrets recursively from subdirectories |
-| `expandSecretReferences` | boolean | No | Whether to expand secret references \(default: true\) |
-| `viewSecretValue` | boolean | No | Whether to include secret values in the response \(default: true\) |
-| `includeImports` | boolean | No | Whether to include imported secrets \(default: true\) |
-| `tagSlugs` | string | No | Comma-separated tag slugs to filter secrets by |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `secrets` | array | Array of secrets |
-|   ↳ `id` | string | Secret ID |
-|   ↳ `workspace` | string | Workspace/project ID |
-|   ↳ `secretKey` | string | Secret name/key |
-|   ↳ `secretValue` | string | Secret value |
-|   ↳ `secretComment` | string | Secret comment |
-|   ↳ `secretPath` | string | Secret path |
-|   ↳ `version` | number | Secret version |
-|   ↳ `type` | string | Secret type \(shared or personal\) |
-|   ↳ `environment` | string | Environment slug |
-|   ↳ `tags` | array | Tags attached to the secret |
-|     ↳ `id` | string | Tag ID |
-|     ↳ `slug` | string | Tag slug |
-|     ↳ `color` | string | Tag color |
-|     ↳ `name` | string | Tag name |
-|   ↳ `secretMetadata` | array | Custom metadata key-value pairs |
-|     ↳ `key` | string | Metadata key |
-|     ↳ `value` | string | Metadata value |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last update timestamp |
-| `count` | number | Total number of secrets returned |
-
-### `infisical_get_secret`
-
-Retrieve a single secret by name from a project environment.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Infisical API token |
-| `baseUrl` | string | No | Infisical instance URL \(default: "https://us.infisical.com"\). Use "https://eu.infisical.com" for EU Cloud or your self-hosted URL. |
-| `projectId` | string | Yes | The ID of the project |
-| `environment` | string | Yes | The environment slug \(e.g., "dev", "staging", "prod"\) |
-| `secretName` | string | Yes | The name of the secret to retrieve |
-| `secretPath` | string | No | The path of the secret \(default: "/"\) |
-| `version` | number | No | Specific version of the secret to retrieve |
-| `type` | string | No | Secret type: "shared" or "personal" \(default: "shared"\) |
-| `viewSecretValue` | boolean | No | Whether to include the secret value in the response \(default: true\) |
-| `expandSecretReferences` | boolean | No | Whether to expand secret references \(default: true\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `secret` | object | The retrieved secret |
-|   ↳ `id` | string | Secret ID |
-|   ↳ `workspace` | string | Workspace/project ID |
-|   ↳ `secretKey` | string | Secret name/key |
-|   ↳ `secretValue` | string | Secret value |
-|   ↳ `secretComment` | string | Secret comment |
-|   ↳ `secretPath` | string | Secret path |
-|   ↳ `version` | number | Secret version |
-|   ↳ `type` | string | Secret type \(shared or personal\) |
-|   ↳ `environment` | string | Environment slug |
-|   ↳ `tags` | array | Tags attached to the secret |
-|     ↳ `id` | string | Tag ID |
-|     ↳ `slug` | string | Tag slug |
-|     ↳ `color` | string | Tag color |
-|     ↳ `name` | string | Tag name |
-|   ↳ `secretMetadata` | array | Custom metadata key-value pairs |
-|     ↳ `key` | string | Metadata key |
-|     ↳ `value` | string | Metadata value |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last update timestamp |
-
-### `infisical_create_secret`
-
-Create a new secret in a project environment.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Infisical API token |
-| `baseUrl` | string | No | Infisical instance URL \(default: "https://us.infisical.com"\). Use "https://eu.infisical.com" for EU Cloud or your self-hosted URL. |
-| `projectId` | string | Yes | The ID of the project |
-| `environment` | string | Yes | The environment slug \(e.g., "dev", "staging", "prod"\) |
-| `secretName` | string | Yes | The name of the secret to create |
-| `secretValue` | string | Yes | The value of the secret |
-| `secretPath` | string | No | The path for the secret \(default: "/"\) |
-| `secretComment` | string | No | A comment for the secret |
-| `type` | string | No | Secret type: "shared" or "personal" \(default: "shared"\) |
-| `tagIds` | string | No | Comma-separated tag IDs to attach to the secret |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `secret` | object | The created secret |
-|   ↳ `id` | string | Secret ID |
-|   ↳ `workspace` | string | Workspace/project ID |
-|   ↳ `secretKey` | string | Secret name/key |
-|   ↳ `secretValue` | string | Secret value |
-|   ↳ `secretComment` | string | Secret comment |
-|   ↳ `secretPath` | string | Secret path |
-|   ↳ `version` | number | Secret version |
-|   ↳ `type` | string | Secret type \(shared or personal\) |
-|   ↳ `environment` | string | Environment slug |
-|   ↳ `tags` | array | Tags attached to the secret |
-|     ↳ `id` | string | Tag ID |
-|     ↳ `slug` | string | Tag slug |
-|     ↳ `color` | string | Tag color |
-|     ↳ `name` | string | Tag name |
-|   ↳ `secretMetadata` | array | Custom metadata key-value pairs |
-|     ↳ `key` | string | Metadata key |
-|     ↳ `value` | string | Metadata value |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last update timestamp |
-
-### `infisical_update_secret`
-
-Update an existing secret in a project environment.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Infisical API token |
-| `baseUrl` | string | No | Infisical instance URL \(default: "https://us.infisical.com"\). Use "https://eu.infisical.com" for EU Cloud or your self-hosted URL. |
-| `projectId` | string | Yes | The ID of the project |
-| `environment` | string | Yes | The environment slug \(e.g., "dev", "staging", "prod"\) |
-| `secretName` | string | Yes | The name of the secret to update |
-| `secretValue` | string | No | The new value for the secret |
-| `secretPath` | string | No | The path of the secret \(default: "/"\) |
-| `secretComment` | string | No | A comment for the secret |
-| `newSecretName` | string | No | New name for the secret \(to rename it\) |
-| `type` | string | No | Secret type: "shared" or "personal" \(default: "shared"\) |
-| `tagIds` | string | No | Comma-separated tag IDs to set on the secret |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `secret` | object | The updated secret |
-|   ↳ `id` | string | Secret ID |
-|   ↳ `workspace` | string | Workspace/project ID |
-|   ↳ `secretKey` | string | Secret name/key |
-|   ↳ `secretValue` | string | Secret value |
-|   ↳ `secretComment` | string | Secret comment |
-|   ↳ `secretPath` | string | Secret path |
-|   ↳ `version` | number | Secret version |
-|   ↳ `type` | string | Secret type \(shared or personal\) |
-|   ↳ `environment` | string | Environment slug |
-|   ↳ `tags` | array | Tags attached to the secret |
-|     ↳ `id` | string | Tag ID |
-|     ↳ `slug` | string | Tag slug |
-|     ↳ `color` | string | Tag color |
-|     ↳ `name` | string | Tag name |
-|   ↳ `secretMetadata` | array | Custom metadata key-value pairs |
-|     ↳ `key` | string | Metadata key |
-|     ↳ `value` | string | Metadata value |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last update timestamp |
-
-### `infisical_delete_secret`
-
-Delete a secret from a project environment.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Infisical API token |
-| `baseUrl` | string | No | Infisical instance URL \(default: "https://us.infisical.com"\). Use "https://eu.infisical.com" for EU Cloud or your self-hosted URL. |
-| `projectId` | string | Yes | The ID of the project |
-| `environment` | string | Yes | The environment slug \(e.g., "dev", "staging", "prod"\) |
-| `secretName` | string | Yes | The name of the secret to delete |
-| `secretPath` | string | No | The path of the secret \(default: "/"\) |
-| `type` | string | No | Secret type: "shared" or "personal" \(default: "shared"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `secret` | object | The deleted secret |
-|   ↳ `id` | string | Secret ID |
-|   ↳ `workspace` | string | Workspace/project ID |
-|   ↳ `secretKey` | string | Secret name/key |
-|   ↳ `secretValue` | string | Secret value |
-|   ↳ `secretComment` | string | Secret comment |
-|   ↳ `secretPath` | string | Secret path |
-|   ↳ `version` | number | Secret version |
-|   ↳ `type` | string | Secret type \(shared or personal\) |
-|   ↳ `environment` | string | Environment slug |
-|   ↳ `tags` | array | Tags attached to the secret |
-|     ↳ `id` | string | Tag ID |
-|     ↳ `slug` | string | Tag slug |
-|     ↳ `color` | string | Tag color |
-|     ↳ `name` | string | Tag name |
-|   ↳ `secretMetadata` | array | Custom metadata key-value pairs |
-|     ↳ `key` | string | Metadata key |
-|     ↳ `value` | string | Metadata value |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last update timestamp |
-
-

apps/docs/content/docs/en/tools/jina.mdx

@@ -64,7 +64,6 @@ Extract and process web content into clean, LLM-friendly text using Jina AI Read
 | Parameter | Type | Description |
 | --------- | ---- | ----------- |
 | `content` | string | The extracted content from the URL, processed into clean, LLM-friendly text |
-| `tokensUsed` | number | Number of Jina tokens consumed by this request |
 
 ### `jina_search`
 
@@ -98,6 +97,5 @@ Search the web and return top 5 results with LLM-friendly content. Each result i
 |   ↳ `content` | string | LLM-friendly extracted content |
 |   ↳ `usage` | object | Token usage information |
 |     ↳ `tokens` | number | Number of tokens consumed by this request |
-| `tokensUsed` | number | Number of Jina tokens consumed by this request |
 
 

apps/docs/content/docs/en/tools/ketch.mdx

@@ -1,149 +0,0 @@
----
-title: Ketch
-description: Manage privacy consent, subscriptions, and data subject rights
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="ketch"
-  color="#9B5CFF"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Ketch](https://www.ketch.com/) is an AI-powered privacy, consent, and data governance platform that helps organizations automate compliance with global privacy regulations. It provides tools for managing consent preferences, handling data subject rights requests, and controlling subscription communications.
-
-With Ketch, you can:
-
-- **Retrieve consent status**: Query the current consent preferences for any data subject across configured purposes and legal bases
-- **Update consent preferences**: Set or modify consent for specific purposes (e.g., analytics, marketing) with the appropriate legal basis (opt-in, opt-out, disclosure)
-- **Manage subscriptions**: Get and update subscription topic preferences and global controls across contact methods like email and SMS
-- **Invoke data subject rights**: Submit privacy rights requests including data access, deletion, correction, and processing restriction under regulations like GDPR and CCPA
-
-To use Ketch, drop the Ketch block into your workflow and provide your organization code, property code, and environment code. The Ketch Web API is a public API — no API key or OAuth credentials are required. Identity is determined by the organization and property codes along with the data subject's identity (e.g., email address).
-
-These capabilities let you automate privacy compliance workflows, respond to user consent changes in real time, and manage data subject rights requests as part of your broader automation pipelines.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Ketch into the workflow. Retrieve and update consent preferences, manage subscription topics and controls, and submit data subject rights requests for access, deletion, correction, or processing restriction.
-
-
-
-## Tools
-
-### `ketch_get_consent`
-
-Retrieve consent status for a data subject. Returns the current consent preferences for each configured purpose.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `organizationCode` | string | Yes | Ketch organization code |
-| `propertyCode` | string | Yes | Digital property code defined in Ketch |
-| `environmentCode` | string | Yes | Environment code defined in Ketch \(e.g., "production"\) |
-| `jurisdictionCode` | string | No | Jurisdiction code \(e.g., "gdpr", "ccpa"\) |
-| `identities` | json | Yes | Identity map \(e.g., \{"email": "user@example.com"\}\) |
-| `purposes` | json | No | Optional purposes to filter the consent query |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `purposes` | object | Map of purpose codes to consent status and legal basis |
-|   ↳ `allowed` | string | Consent status for the purpose: "granted" or "denied" |
-|   ↳ `legalBasisCode` | string | Legal basis code \(e.g., "consent_optin", "consent_optout", "disclosure", "other"\) |
-| `vendors` | object | Map of vendor consent statuses |
-
-### `ketch_set_consent`
-
-Update consent preferences for a data subject. Sets the consent status for specified purposes with the appropriate legal basis.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `organizationCode` | string | Yes | Ketch organization code |
-| `propertyCode` | string | Yes | Digital property code defined in Ketch |
-| `environmentCode` | string | Yes | Environment code defined in Ketch \(e.g., "production"\) |
-| `jurisdictionCode` | string | No | Jurisdiction code \(e.g., "gdpr", "ccpa"\) |
-| `identities` | json | Yes | Identity map \(e.g., \{"email": "user@example.com"\}\) |
-| `purposes` | json | Yes | Map of purpose codes to consent settings \(e.g., \{"analytics": \{"allowed": "granted", "legalBasisCode": "consent_optin"\}\}\) |
-| `collectedAt` | number | No | UNIX timestamp when consent was collected \(defaults to current time\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `purposes` | object | Updated consent status map of purpose codes to consent settings |
-|   ↳ `allowed` | string | Consent status for the purpose: "granted" or "denied" |
-|   ↳ `legalBasisCode` | string | Legal basis code \(e.g., "consent_optin", "consent_optout", "disclosure", "other"\) |
-
-### `ketch_get_subscriptions`
-
-Retrieve subscription preferences for a data subject. Returns the current subscription topic and control statuses.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `organizationCode` | string | Yes | Ketch organization code |
-| `propertyCode` | string | Yes | Digital property code defined in Ketch |
-| `environmentCode` | string | Yes | Environment code defined in Ketch \(e.g., "production"\) |
-| `identities` | json | Yes | Identity map \(e.g., \{"email": "user@example.com"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `topics` | object | Map of topic codes to contact method settings \(e.g., \{"newsletter": \{"email": \{"status": "granted"\}\}\}\) |
-| `controls` | object | Map of control codes to settings \(e.g., \{"global_unsubscribe": \{"status": "denied"\}\}\) |
-
-### `ketch_set_subscriptions`
-
-Update subscription preferences for a data subject. Sets topic and control statuses for email, SMS, and other contact methods.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `organizationCode` | string | Yes | Ketch organization code |
-| `propertyCode` | string | Yes | Digital property code defined in Ketch |
-| `environmentCode` | string | Yes | Environment code defined in Ketch \(e.g., "production"\) |
-| `identities` | json | Yes | Identity map \(e.g., \{"email": "user@example.com"\}\) |
-| `topics` | json | No | Map of topic codes to contact method settings \(e.g., \{"newsletter": \{"email": \{"status": "granted"\}, "sms": \{"status": "denied"\}\}\}\) |
-| `controls` | json | No | Map of control codes to settings \(e.g., \{"global_unsubscribe": \{"status": "denied"\}\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the subscription preferences were updated |
-
-### `ketch_invoke_right`
-
-Submit a data subject rights request (e.g., access, delete, correct, restrict processing). Initiates a privacy rights workflow in Ketch.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `organizationCode` | string | Yes | Ketch organization code |
-| `propertyCode` | string | Yes | Digital property code defined in Ketch |
-| `environmentCode` | string | Yes | Environment code defined in Ketch \(e.g., "production"\) |
-| `jurisdictionCode` | string | Yes | Jurisdiction code \(e.g., "gdpr", "ccpa"\) |
-| `rightCode` | string | Yes | Privacy right code to invoke \(e.g., "access", "delete", "correct", "restrict_processing"\) |
-| `identities` | json | Yes | Identity map \(e.g., \{"email": "user@example.com"\}\) |
-| `userData` | json | No | Optional data subject information \(e.g., \{"email": "user@example.com", "firstName": "John", "lastName": "Doe"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the rights request was submitted |
-| `message` | string | Response message from Ketch |
-
-

apps/docs/content/docs/en/tools/knowledge.mdx

@@ -122,37 +122,6 @@ Create a new document in a knowledge base
 | `message` | string | Success or error message describing the operation result |
 | `documentId` | string | ID of the created document |
 
-### `knowledge_upsert_document`
-
-Create or update a document in a knowledge base. If a document with the given ID or filename already exists, it will be replaced with the new content.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `knowledgeBaseId` | string | Yes | ID of the knowledge base containing the document |
-| `documentId` | string | No | Optional ID of an existing document to update. If not provided, lookup is done by filename. |
-| `name` | string | Yes | Name of the document |
-| `content` | string | Yes | Content of the document |
-| `documentTags` | json | No | Document tags |
-| `documentTags` | string | No | No description |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `data` | object | Information about the upserted document |
-|   ↳ `documentId` | string | Document ID |
-|   ↳ `documentName` | string | Document name |
-|   ↳ `type` | string | Document type |
-|   ↳ `enabled` | boolean | Whether the document is enabled |
-|   ↳ `isUpdate` | boolean | Whether an existing document was replaced |
-|   ↳ `previousDocumentId` | string | ID of the document that was replaced, if any |
-|   ↳ `createdAt` | string | Creation timestamp |
-|   ↳ `updatedAt` | string | Last update timestamp |
-| `message` | string | Success or error message describing the operation result |
-| `documentId` | string | ID of the upserted document |
-
 ### `knowledge_list_tags`
 
 List all tag definitions for a knowledge base

apps/docs/content/docs/en/tools/launchdarkly.mdx

@@ -1,388 +0,0 @@
----
-title: LaunchDarkly
-description: Manage feature flags with LaunchDarkly.
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="launchdarkly"
-  color="#191919"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[LaunchDarkly](https://launchdarkly.com/) is a feature management platform that enables teams to safely deploy, control, and measure their software features at scale.
-
-With the LaunchDarkly integration in Sim, you can:
-
-- **Feature flag management** — List, create, update, toggle, and delete feature flags programmatically. Toggle flags on or off in specific environments using LaunchDarkly's semantic patch API.
-- **Flag status monitoring** — Check whether a flag is active, inactive, new, or launched in a given environment. Track the last time a flag was evaluated.
-- **Project and environment management** — List all projects and their environments to understand your LaunchDarkly organization structure.
-- **User segments** — List user segments within a project and environment to understand how your audience is organized for targeting.
-- **Team visibility** — List account members and their roles for auditing and access management workflows.
-- **Audit log** — Retrieve recent audit log entries to track who changed what, when. Filter entries by resource type for targeted monitoring.
-
-In Sim, the LaunchDarkly integration enables your agents to automate feature flag operations as part of their workflows. This allows for automation scenarios such as toggling flags on/off based on deployment pipeline events, monitoring flag status and alerting on stale or unused flags, auditing flag changes by querying the audit log after deployments, syncing flag metadata with your project management tools, and listing all feature flags across projects for governance.
-
-## Authentication
-
-This integration uses a LaunchDarkly API key. You can create personal access tokens or service tokens in the LaunchDarkly dashboard under **Account Settings > Authorization**. The API key is passed directly in the `Authorization` header (no `Bearer` prefix).
-
-## Need Help?
-
-If you encounter issues with the LaunchDarkly integration, contact us at [help@sim.ai](mailto:help@sim.ai)
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate LaunchDarkly into your workflow. List, create, update, toggle, and delete feature flags. Manage projects, environments, segments, members, and audit logs. Requires API Key.
-
-
-
-## Tools
-
-### `launchdarkly_create_flag`
-
-Create a new feature flag in a LaunchDarkly project.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key to create the flag in |
-| `name` | string | Yes | Human-readable name for the feature flag |
-| `key` | string | Yes | Unique key for the feature flag \(used in code\) |
-| `description` | string | No | Description of the feature flag |
-| `tags` | string | No | Comma-separated list of tags |
-| `temporary` | boolean | No | Whether the flag is temporary \(default true\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `key` | string | The unique key of the feature flag |
-| `name` | string | The human-readable name of the feature flag |
-| `kind` | string | The type of flag \(boolean or multivariate\) |
-| `description` | string | Description of the feature flag |
-| `temporary` | boolean | Whether the flag is temporary |
-| `archived` | boolean | Whether the flag is archived |
-| `deprecated` | boolean | Whether the flag is deprecated |
-| `creationDate` | number | Unix timestamp in milliseconds when the flag was created |
-| `tags` | array | Tags applied to the flag |
-| `variations` | array | The variations for this feature flag |
-|   ↳ `value` | string | The variation value |
-|   ↳ `name` | string | The variation name |
-|   ↳ `description` | string | The variation description |
-| `maintainerId` | string | The ID of the member who maintains this flag |
-
-### `launchdarkly_delete_flag`
-
-Delete a feature flag from a LaunchDarkly project.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key |
-| `flagKey` | string | Yes | The feature flag key to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the flag was successfully deleted |
-
-### `launchdarkly_get_audit_log`
-
-List audit log entries from your LaunchDarkly account.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `limit` | number | No | Maximum number of entries to return \(default 10, max 20\) |
-| `spec` | string | No | Filter expression \(e.g., "resourceType:flag"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `entries` | array | List of audit log entries |
-|   ↳ `id` | string | The audit log entry ID |
-|   ↳ `date` | number | Unix timestamp in milliseconds |
-|   ↳ `kind` | string | The type of action performed |
-|   ↳ `name` | string | The name of the resource acted on |
-|   ↳ `description` | string | Full description of the action |
-|   ↳ `shortDescription` | string | Short description of the action |
-|   ↳ `memberEmail` | string | Email of the member who performed the action |
-|   ↳ `targetName` | string | Name of the target resource |
-|   ↳ `targetKind` | string | Kind of the target resource |
-| `totalCount` | number | Total number of audit log entries |
-
-### `launchdarkly_get_flag`
-
-Get a single feature flag by key from a LaunchDarkly project.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key |
-| `flagKey` | string | Yes | The feature flag key |
-| `environmentKey` | string | No | Filter flag configuration to a specific environment |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `key` | string | The unique key of the feature flag |
-| `name` | string | The human-readable name of the feature flag |
-| `kind` | string | The type of flag \(boolean or multivariate\) |
-| `description` | string | Description of the feature flag |
-| `temporary` | boolean | Whether the flag is temporary |
-| `archived` | boolean | Whether the flag is archived |
-| `deprecated` | boolean | Whether the flag is deprecated |
-| `creationDate` | number | Unix timestamp in milliseconds when the flag was created |
-| `tags` | array | Tags applied to the flag |
-| `variations` | array | The variations for this feature flag |
-|   ↳ `value` | string | The variation value |
-|   ↳ `name` | string | The variation name |
-|   ↳ `description` | string | The variation description |
-| `maintainerId` | string | The ID of the member who maintains this flag |
-| `on` | boolean | Whether the flag is on in the requested environment \(null if no single environment was specified\) |
-
-### `launchdarkly_get_flag_status`
-
-Get the status of a feature flag across environments (active, inactive, launched, etc.).
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key |
-| `flagKey` | string | Yes | The feature flag key |
-| `environmentKey` | string | Yes | The environment key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `name` | string | The flag status \(new, active, inactive, launched\) |
-| `lastRequested` | string | Timestamp of the last evaluation |
-| `defaultVal` | string | The default variation value |
-
-### `launchdarkly_list_environments`
-
-List environments in a LaunchDarkly project.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key to list environments for |
-| `limit` | number | No | Maximum number of environments to return \(default 20\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `environments` | array | List of environments |
-|   ↳ `id` | string | The environment ID |
-|   ↳ `key` | string | The unique environment key |
-|   ↳ `name` | string | The environment name |
-|   ↳ `color` | string | The color assigned to this environment |
-|   ↳ `apiKey` | string | The server-side SDK key for this environment |
-|   ↳ `mobileKey` | string | The mobile SDK key for this environment |
-|   ↳ `tags` | array | Tags applied to the environment |
-| `totalCount` | number | Total number of environments |
-
-### `launchdarkly_list_flags`
-
-List feature flags in a LaunchDarkly project.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key to list flags for |
-| `environmentKey` | string | No | Filter flag configurations to a specific environment |
-| `tag` | string | No | Filter flags by tag name |
-| `limit` | number | No | Maximum number of flags to return \(default 20\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `flags` | array | List of feature flags |
-|   ↳ `key` | string | The unique key of the feature flag |
-|   ↳ `name` | string | The human-readable name of the feature flag |
-|   ↳ `kind` | string | The type of flag \(boolean or multivariate\) |
-|   ↳ `description` | string | Description of the feature flag |
-|   ↳ `temporary` | boolean | Whether the flag is temporary |
-|   ↳ `archived` | boolean | Whether the flag is archived |
-|   ↳ `deprecated` | boolean | Whether the flag is deprecated |
-|   ↳ `creationDate` | number | Unix timestamp in milliseconds when the flag was created |
-|   ↳ `tags` | array | Tags applied to the flag |
-|   ↳ `variations` | array | The variations for this feature flag |
-|     ↳ `value` | string | The variation value |
-|     ↳ `name` | string | The variation name |
-|     ↳ `description` | string | The variation description |
-|   ↳ `maintainerId` | string | The ID of the member who maintains this flag |
-| `totalCount` | number | Total number of flags |
-
-### `launchdarkly_list_members`
-
-List account members in your LaunchDarkly organization.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `limit` | number | No | Maximum number of members to return \(default 20\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `members` | array | List of account members |
-|   ↳ `id` | string | The member ID |
-|   ↳ `email` | string | The member email address |
-|   ↳ `firstName` | string | The member first name |
-|   ↳ `lastName` | string | The member last name |
-|   ↳ `role` | string | The member role \(reader, writer, admin, owner\) |
-|   ↳ `lastSeen` | number | Unix timestamp of last activity |
-|   ↳ `creationDate` | number | Unix timestamp when the member was created |
-|   ↳ `verified` | boolean | Whether the member email is verified |
-| `totalCount` | number | Total number of members |
-
-### `launchdarkly_list_projects`
-
-List all projects in your LaunchDarkly account.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `limit` | number | No | Maximum number of projects to return \(default 20\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `projects` | array | List of projects |
-|   ↳ `id` | string | The project ID |
-|   ↳ `key` | string | The unique project key |
-|   ↳ `name` | string | The project name |
-|   ↳ `tags` | array | Tags applied to the project |
-| `totalCount` | number | Total number of projects |
-
-### `launchdarkly_list_segments`
-
-List user segments in a LaunchDarkly project and environment.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key |
-| `environmentKey` | string | Yes | The environment key |
-| `limit` | number | No | Maximum number of segments to return \(default 20\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `segments` | array | List of user segments |
-|   ↳ `key` | string | The unique segment key |
-|   ↳ `name` | string | The segment name |
-|   ↳ `description` | string | The segment description |
-|   ↳ `tags` | array | Tags applied to the segment |
-|   ↳ `creationDate` | number | Unix timestamp in milliseconds when the segment was created |
-|   ↳ `unbounded` | boolean | Whether this is an unbounded \(big\) segment |
-|   ↳ `included` | array | User keys explicitly included in the segment |
-|   ↳ `excluded` | array | User keys explicitly excluded from the segment |
-| `totalCount` | number | Total number of segments |
-
-### `launchdarkly_toggle_flag`
-
-Toggle a feature flag on or off in a specific LaunchDarkly environment.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key |
-| `flagKey` | string | Yes | The feature flag key to toggle |
-| `environmentKey` | string | Yes | The environment key to toggle the flag in |
-| `enabled` | boolean | Yes | Whether to turn the flag on \(true\) or off \(false\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `key` | string | The unique key of the feature flag |
-| `name` | string | The human-readable name of the feature flag |
-| `kind` | string | The type of flag \(boolean or multivariate\) |
-| `description` | string | Description of the feature flag |
-| `temporary` | boolean | Whether the flag is temporary |
-| `archived` | boolean | Whether the flag is archived |
-| `deprecated` | boolean | Whether the flag is deprecated |
-| `creationDate` | number | Unix timestamp in milliseconds when the flag was created |
-| `tags` | array | Tags applied to the flag |
-| `variations` | array | The variations for this feature flag |
-|   ↳ `value` | string | The variation value |
-|   ↳ `name` | string | The variation name |
-|   ↳ `description` | string | The variation description |
-| `maintainerId` | string | The ID of the member who maintains this flag |
-| `on` | boolean | Whether the flag is now on in the target environment |
-
-### `launchdarkly_update_flag`
-
-Update a feature flag metadata (name, description, tags, temporary, archived) using semantic patch.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | LaunchDarkly API key |
-| `projectKey` | string | Yes | The project key |
-| `flagKey` | string | Yes | The feature flag key to update |
-| `updateName` | string | No | New name for the flag |
-| `updateDescription` | string | No | New description for the flag |
-| `addTags` | string | No | Comma-separated tags to add |
-| `removeTags` | string | No | Comma-separated tags to remove |
-| `archive` | boolean | No | Set to true to archive, false to restore |
-| `comment` | string | No | Optional comment explaining the update |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `key` | string | The unique key of the feature flag |
-| `name` | string | The human-readable name of the feature flag |
-| `kind` | string | The type of flag \(boolean or multivariate\) |
-| `description` | string | Description of the feature flag |
-| `temporary` | boolean | Whether the flag is temporary |
-| `archived` | boolean | Whether the flag is archived |
-| `deprecated` | boolean | Whether the flag is deprecated |
-| `creationDate` | number | Unix timestamp in milliseconds when the flag was created |
-| `tags` | array | Tags applied to the flag |
-| `variations` | array | The variations for this feature flag |
-|   ↳ `value` | string | The variation value |
-|   ↳ `name` | string | The variation name |
-|   ↳ `description` | string | The variation description |
-| `maintainerId` | string | The ID of the member who maintains this flag |
-
-

apps/docs/content/docs/en/tools/linkup.mdx

@@ -51,9 +51,6 @@ Search the web for information using Linkup
 | `includeDomains` | string | No | Comma-separated list of domain names to restrict search results to |
 | `includeInlineCitations` | boolean | No | Add inline citations to answers \(only applies when outputType is "sourcedAnswer"\) |
 | `includeSources` | boolean | No | Include sources in response |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 

apps/docs/content/docs/en/tools/meta.json

@@ -2,7 +2,6 @@
   "pages": [
     "index",
     "a2a",
-    "agentmail",
     "ahrefs",
     "airtable",
     "airweave",
@@ -14,7 +13,6 @@
     "asana",
     "ashby",
     "attio",
-    "box",
     "brandfetch",
     "browser_use",
     "calcom",
@@ -23,15 +21,12 @@
     "clay",
     "clerk",
     "cloudflare",
-    "cloudformation",
-    "cloudwatch",
     "confluence",
     "cursor",
     "databricks",
     "datadog",
     "devin",
     "discord",
-    "docusign",
     "dropbox",
     "dspy",
     "dub",
@@ -42,7 +37,6 @@
     "enrich",
     "evernote",
     "exa",
-    "extend",
     "fathom",
     "file",
     "firecrawl",
@@ -72,7 +66,6 @@
     "google_vault",
     "grafana",
     "grain",
-    "granola",
     "greenhouse",
     "greptile",
     "hex",
@@ -82,16 +75,13 @@
     "image_generator",
     "imap",
     "incidentio",
-    "infisical",
     "intercom",
     "jina",
     "jira",
     "jira_service_management",
     "kalshi",
-    "ketch",
     "knowledge",
     "langsmith",
-    "launchdarkly",
     "lemlist",
     "linear",
     "linkedin",
@@ -102,7 +92,6 @@
     "mailgun",
     "mem0",
     "memory",
-    "microsoft_ad",
     "microsoft_dataverse",
     "microsoft_excel",
     "microsoft_planner",
@@ -113,7 +102,6 @@
     "neo4j",
     "notion",
     "obsidian",
-    "okta",
     "onedrive",
     "onepassword",
     "openai",
@@ -126,22 +114,17 @@
     "polymarket",
     "postgresql",
     "posthog",
-    "profound",
     "pulse",
     "qdrant",
-    "quiver",
     "rds",
     "reddit",
     "redis",
     "reducto",
     "resend",
     "revenuecat",
-    "rippling",
-    "rootly",
     "s3",
     "salesforce",
     "search",
-    "secrets_manager",
     "sendgrid",
     "sentry",
     "serper",
@@ -159,7 +142,6 @@
     "stt",
     "supabase",
     "table",
-    "tailscale",
     "tavily",
     "telegram",
     "textract",
@@ -179,7 +161,6 @@
     "whatsapp",
     "wikipedia",
     "wordpress",
-    "workday",
     "x",
     "youtube",
     "zendesk",

apps/docs/content/docs/en/tools/microsoft_ad.mdx

@@ -1,336 +0,0 @@
----
-title: Azure AD
-description: Manage users and groups in Azure AD (Microsoft Entra ID)
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="microsoft_ad"
-  color="#0078D4"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Azure Active Directory](https://entra.microsoft.com) (now Microsoft Entra ID) is Microsoft's cloud-based identity and access management service. It helps organizations manage users, groups, and access to applications and resources across cloud and on-premises environments.
-
-With the Azure AD integration in Sim, you can:
-
-- **Manage users**: List, create, update, and delete user accounts in your directory
-- **Manage groups**: Create and configure security groups and Microsoft 365 groups
-- **Control group membership**: Add and remove members from groups programmatically
-- **Query directory data**: Search and filter users and groups using OData expressions
-- **Automate onboarding/offboarding**: Create new user accounts with initial passwords and enable/disable accounts as part of HR workflows
-
-In Sim, the Azure AD integration enables your agents to programmatically manage your organization's identity infrastructure. This allows for automation scenarios such as provisioning new employees, updating user profiles in bulk, managing team group memberships, and auditing directory data. By connecting Sim with Azure AD, you can streamline identity lifecycle management and ensure your directory stays in sync with your organization's needs.
-
-## Need Help?
-
-If you encounter issues with the Azure AD integration, contact us at [help@sim.ai](mailto:help@sim.ai)
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Azure Active Directory into your workflows. List, create, update, and delete users and groups. Manage group memberships programmatically.
-
-
-
-## Tools
-
-### `microsoft_ad_list_users`
-
-List users in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `top` | number | No | Maximum number of users to return \(default 100, max 999\) |
-| `filter` | string | No | OData filter expression \(e.g., "department eq \'Sales\'"\) |
-| `search` | string | No | Search string to filter users by displayName or mail |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `users` | array | List of users |
-| `userCount` | number | Number of users returned |
-
-### `microsoft_ad_get_user`
-
-Get a user by ID or user principal name from Azure AD
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `userId` | string | Yes | User ID or user principal name \(e.g., "user@example.com"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `user` | object | User details |
-|   ↳ `id` | string | User ID |
-|   ↳ `displayName` | string | Display name |
-|   ↳ `givenName` | string | First name |
-|   ↳ `surname` | string | Last name |
-|   ↳ `userPrincipalName` | string | User principal name \(email\) |
-|   ↳ `mail` | string | Email address |
-|   ↳ `jobTitle` | string | Job title |
-|   ↳ `department` | string | Department |
-|   ↳ `officeLocation` | string | Office location |
-|   ↳ `mobilePhone` | string | Mobile phone number |
-|   ↳ `accountEnabled` | boolean | Whether the account is enabled |
-
-### `microsoft_ad_create_user`
-
-Create a new user in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `displayName` | string | Yes | Display name for the user |
-| `mailNickname` | string | Yes | Mail alias for the user |
-| `userPrincipalName` | string | Yes | User principal name \(e.g., "user@example.com"\) |
-| `password` | string | Yes | Initial password for the user |
-| `accountEnabled` | boolean | Yes | Whether the account is enabled |
-| `givenName` | string | No | First name |
-| `surname` | string | No | Last name |
-| `jobTitle` | string | No | Job title |
-| `department` | string | No | Department |
-| `officeLocation` | string | No | Office location |
-| `mobilePhone` | string | No | Mobile phone number |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `user` | object | Created user details |
-|   ↳ `id` | string | User ID |
-|   ↳ `displayName` | string | Display name |
-|   ↳ `givenName` | string | First name |
-|   ↳ `surname` | string | Last name |
-|   ↳ `userPrincipalName` | string | User principal name \(email\) |
-|   ↳ `mail` | string | Email address |
-|   ↳ `jobTitle` | string | Job title |
-|   ↳ `department` | string | Department |
-|   ↳ `officeLocation` | string | Office location |
-|   ↳ `mobilePhone` | string | Mobile phone number |
-|   ↳ `accountEnabled` | boolean | Whether the account is enabled |
-
-### `microsoft_ad_update_user`
-
-Update user properties in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `userId` | string | Yes | User ID or user principal name |
-| `displayName` | string | No | Display name |
-| `givenName` | string | No | First name |
-| `surname` | string | No | Last name |
-| `jobTitle` | string | No | Job title |
-| `department` | string | No | Department |
-| `officeLocation` | string | No | Office location |
-| `mobilePhone` | string | No | Mobile phone number |
-| `accountEnabled` | boolean | No | Whether the account is enabled |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `updated` | boolean | Whether the update was successful |
-| `userId` | string | ID of the updated user |
-
-### `microsoft_ad_delete_user`
-
-Delete a user from Azure AD (Microsoft Entra ID). The user is moved to a temporary container and can be restored within 30 days.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `userId` | string | Yes | User ID or user principal name |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the deletion was successful |
-| `userId` | string | ID of the deleted user |
-
-### `microsoft_ad_list_groups`
-
-List groups in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `top` | number | No | Maximum number of groups to return \(default 100, max 999\) |
-| `filter` | string | No | OData filter expression \(e.g., "securityEnabled eq true"\) |
-| `search` | string | No | Search string to filter groups by displayName or description |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `groups` | array | List of groups |
-| `groupCount` | number | Number of groups returned |
-
-### `microsoft_ad_get_group`
-
-Get a group by ID from Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `groupId` | string | Yes | Group ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `group` | object | Group details |
-|   ↳ `id` | string | Group ID |
-|   ↳ `displayName` | string | Display name |
-|   ↳ `description` | string | Group description |
-|   ↳ `mail` | string | Email address |
-|   ↳ `mailEnabled` | boolean | Whether mail is enabled |
-|   ↳ `mailNickname` | string | Mail nickname |
-|   ↳ `securityEnabled` | boolean | Whether security is enabled |
-|   ↳ `groupTypes` | array | Group types |
-|   ↳ `visibility` | string | Group visibility |
-|   ↳ `createdDateTime` | string | Creation date |
-
-### `microsoft_ad_create_group`
-
-Create a new group in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `displayName` | string | Yes | Display name for the group |
-| `mailNickname` | string | Yes | Mail alias for the group \(ASCII only, max 64 characters\) |
-| `description` | string | No | Group description |
-| `mailEnabled` | boolean | Yes | Whether mail is enabled \(true for Microsoft 365 groups\) |
-| `securityEnabled` | boolean | Yes | Whether security is enabled \(true for security groups\) |
-| `groupTypes` | string | No | Group type: "Unified" for Microsoft 365 group, leave empty for security group |
-| `visibility` | string | No | Group visibility: "Private" or "Public" |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `group` | object | Created group details |
-|   ↳ `id` | string | Group ID |
-|   ↳ `displayName` | string | Display name |
-|   ↳ `description` | string | Group description |
-|   ↳ `mail` | string | Email address |
-|   ↳ `mailEnabled` | boolean | Whether mail is enabled |
-|   ↳ `mailNickname` | string | Mail nickname |
-|   ↳ `securityEnabled` | boolean | Whether security is enabled |
-|   ↳ `groupTypes` | array | Group types |
-|   ↳ `visibility` | string | Group visibility |
-|   ↳ `createdDateTime` | string | Creation date |
-
-### `microsoft_ad_update_group`
-
-Update group properties in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `groupId` | string | Yes | Group ID |
-| `displayName` | string | No | Display name |
-| `description` | string | No | Group description |
-| `mailNickname` | string | No | Mail alias |
-| `visibility` | string | No | Group visibility: "Private" or "Public" |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `updated` | boolean | Whether the update was successful |
-| `groupId` | string | ID of the updated group |
-
-### `microsoft_ad_delete_group`
-
-Delete a group from Azure AD (Microsoft Entra ID). Microsoft 365 and security groups can be restored within 30 days.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `groupId` | string | Yes | Group ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `deleted` | boolean | Whether the deletion was successful |
-| `groupId` | string | ID of the deleted group |
-
-### `microsoft_ad_list_group_members`
-
-List members of a group in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `groupId` | string | Yes | Group ID |
-| `top` | number | No | Maximum number of members to return \(default 100, max 999\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `members` | array | List of group members |
-| `memberCount` | number | Number of members returned |
-
-### `microsoft_ad_add_group_member`
-
-Add a member to a group in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `groupId` | string | Yes | Group ID |
-| `memberId` | string | Yes | User ID of the member to add |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `added` | boolean | Whether the member was added successfully |
-| `groupId` | string | Group ID |
-| `memberId` | string | Member ID that was added |
-
-### `microsoft_ad_remove_group_member`
-
-Remove a member from a group in Azure AD (Microsoft Entra ID)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `groupId` | string | Yes | Group ID |
-| `memberId` | string | Yes | User ID of the member to remove |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `removed` | boolean | Whether the member was removed successfully |
-| `groupId` | string | Group ID |
-| `memberId` | string | Member ID that was removed |
-
-

apps/docs/content/docs/en/tools/okta.mdx

@@ -1,517 +0,0 @@
----
-title: Okta
-description: Manage users and groups in Okta
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="okta"
-  color="#191919"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Okta](https://www.okta.com/) is an identity and access management platform that provides secure authentication, authorization, and user management for organizations.
-
-With the Okta integration in Sim, you can:
-
-- **List and search users**: Retrieve users from your Okta org with SCIM search expressions and filters
-- **Manage user lifecycle**: Create, activate, deactivate, suspend, unsuspend, and delete users
-- **Update user profiles**: Modify user attributes like name, email, phone, title, and department
-- **Reset passwords**: Trigger password reset flows with optional email notification
-- **Manage groups**: Create, update, delete, and list groups in your organization
-- **Manage group membership**: Add or remove users from groups, and list group members
-
-In Sim, the Okta integration enables your agents to automate identity management tasks as part of their workflows. This allows for scenarios such as onboarding new employees, offboarding departing users, managing group-based access, auditing user status, and responding to security events by suspending or deactivating accounts.
-
-## Need Help?
-
-If you encounter issues with the Okta integration, contact us at [help@sim.ai](mailto:help@sim.ai)
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Okta identity management into your workflow. List, create, update, activate, suspend, and delete users. Reset passwords. Manage groups and group membership.
-
-
-
-## Tools
-
-### `okta_list_users`
-
-List all users in your Okta organization with optional search and filtering
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `search` | string | No | Okta search expression \(e.g., profile.firstName eq "John" or profile.email co "example.com"\) |
-| `filter` | string | No | Okta filter expression \(e.g., status eq "ACTIVE"\) |
-| `limit` | number | No | Maximum number of users to return \(default: 200, max: 200\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `users` | array | Array of Okta user objects |
-|   ↳ `id` | string | User ID |
-|   ↳ `status` | string | User status \(ACTIVE, STAGED, PROVISIONED, etc.\) |
-|   ↳ `firstName` | string | First name |
-|   ↳ `lastName` | string | Last name |
-|   ↳ `email` | string | Email address |
-|   ↳ `login` | string | Login \(usually email\) |
-|   ↳ `mobilePhone` | string | Mobile phone |
-|   ↳ `title` | string | Job title |
-|   ↳ `department` | string | Department |
-|   ↳ `created` | string | Creation timestamp |
-|   ↳ `lastLogin` | string | Last login timestamp |
-|   ↳ `lastUpdated` | string | Last update timestamp |
-|   ↳ `activated` | string | Activation timestamp |
-|   ↳ `statusChanged` | string | Status change timestamp |
-| `count` | number | Number of users returned |
-| `success` | boolean | Operation success status |
-
-### `okta_get_user`
-
-Get a specific user by ID or login from your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID or login \(email\) to look up |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | User ID |
-| `status` | string | User status |
-| `firstName` | string | First name |
-| `lastName` | string | Last name |
-| `email` | string | Email address |
-| `login` | string | Login \(usually email\) |
-| `mobilePhone` | string | Mobile phone |
-| `secondEmail` | string | Secondary email |
-| `displayName` | string | Display name |
-| `title` | string | Job title |
-| `department` | string | Department |
-| `organization` | string | Organization |
-| `manager` | string | Manager name |
-| `managerId` | string | Manager ID |
-| `division` | string | Division |
-| `employeeNumber` | string | Employee number |
-| `userType` | string | User type |
-| `created` | string | Creation timestamp |
-| `activated` | string | Activation timestamp |
-| `lastLogin` | string | Last login timestamp |
-| `lastUpdated` | string | Last update timestamp |
-| `statusChanged` | string | Status change timestamp |
-| `passwordChanged` | string | Password change timestamp |
-| `success` | boolean | Operation success status |
-
-### `okta_create_user`
-
-Create a new user in your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `firstName` | string | Yes | First name of the user |
-| `lastName` | string | Yes | Last name of the user |
-| `email` | string | Yes | Email address of the user |
-| `login` | string | No | Login for the user \(defaults to email if not provided\) |
-| `password` | string | No | Password for the user \(if not set, user will be emailed to set password\) |
-| `mobilePhone` | string | No | Mobile phone number |
-| `title` | string | No | Job title |
-| `department` | string | No | Department |
-| `activate` | boolean | No | Whether to activate the user immediately \(default: true\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Created user ID |
-| `status` | string | User status |
-| `firstName` | string | First name |
-| `lastName` | string | Last name |
-| `email` | string | Email address |
-| `login` | string | Login |
-| `created` | string | Creation timestamp |
-| `lastUpdated` | string | Last update timestamp |
-| `success` | boolean | Operation success status |
-
-### `okta_update_user`
-
-Update a user profile in your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID or login to update |
-| `firstName` | string | No | Updated first name |
-| `lastName` | string | No | Updated last name |
-| `email` | string | No | Updated email address |
-| `login` | string | No | Updated login |
-| `mobilePhone` | string | No | Updated mobile phone number |
-| `title` | string | No | Updated job title |
-| `department` | string | No | Updated department |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | User ID |
-| `status` | string | User status |
-| `firstName` | string | First name |
-| `lastName` | string | Last name |
-| `email` | string | Email address |
-| `login` | string | Login |
-| `created` | string | Creation timestamp |
-| `lastUpdated` | string | Last update timestamp |
-| `success` | boolean | Operation success status |
-
-### `okta_activate_user`
-
-Activate a user in your Okta organization. Can only be performed on users with STAGED or DEPROVISIONED status. Optionally sends an activation email.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID or login to activate |
-| `sendEmail` | boolean | No | Send activation email to the user \(default: true\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `userId` | string | Activated user ID |
-| `activated` | boolean | Whether the user was activated |
-| `activationUrl` | string | Activation URL \(only returned when sendEmail is false\) |
-| `activationToken` | string | Activation token \(only returned when sendEmail is false\) |
-| `success` | boolean | Operation success status |
-
-### `okta_deactivate_user`
-
-Deactivate a user in your Okta organization. This transitions the user to DEPROVISIONED status.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID or login to deactivate |
-| `sendEmail` | boolean | No | Send deactivation email to admin \(default: false\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `userId` | string | Deactivated user ID |
-| `deactivated` | boolean | Whether the user was deactivated |
-| `success` | boolean | Operation success status |
-
-### `okta_suspend_user`
-
-Suspend a user in your Okta organization. Only users with ACTIVE status can be suspended. Suspended users cannot log in but retain group and app assignments.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID or login to suspend |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `userId` | string | Suspended user ID |
-| `suspended` | boolean | Whether the user was suspended |
-| `success` | boolean | Operation success status |
-
-### `okta_unsuspend_user`
-
-Unsuspend a previously suspended user in your Okta organization. Returns the user to ACTIVE status.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID or login to unsuspend |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `userId` | string | Unsuspended user ID |
-| `unsuspended` | boolean | Whether the user was unsuspended |
-| `success` | boolean | Operation success status |
-
-### `okta_reset_password`
-
-Generate a one-time token to reset a user password. Can email the reset link to the user or return it directly. Transitions the user to RECOVERY status.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID or login to reset password for |
-| `sendEmail` | boolean | No | Send password reset email to the user \(default: true\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `userId` | string | User ID |
-| `resetPasswordUrl` | string | Password reset URL \(only returned when sendEmail is false\) |
-| `success` | boolean | Operation success status |
-
-### `okta_delete_user`
-
-Permanently delete a user from your Okta organization. Can only be performed on DEPROVISIONED users. If the user is active, this will first deactivate them and a second call is needed to delete.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `userId` | string | Yes | User ID to delete |
-| `sendEmail` | boolean | No | Send deactivation email to admin \(default: false\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `userId` | string | Deleted user ID |
-| `deleted` | boolean | Whether the user was deleted |
-| `success` | boolean | Operation success status |
-
-### `okta_list_groups`
-
-List all groups in your Okta organization with optional search and filtering
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `search` | string | No | Okta search expression for groups \(e.g., profile.name sw "Engineering" or type eq "OKTA_GROUP"\) |
-| `filter` | string | No | Okta filter expression \(e.g., type eq "OKTA_GROUP"\) |
-| `limit` | number | No | Maximum number of groups to return \(default: 10000, max: 10000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `groups` | array | Array of Okta group objects |
-|   ↳ `id` | string | Group ID |
-|   ↳ `name` | string | Group name |
-|   ↳ `description` | string | Group description |
-|   ↳ `type` | string | Group type \(OKTA_GROUP, APP_GROUP, BUILT_IN\) |
-|   ↳ `created` | string | Creation timestamp |
-|   ↳ `lastUpdated` | string | Last update timestamp |
-|   ↳ `lastMembershipUpdated` | string | Last membership change timestamp |
-| `count` | number | Number of groups returned |
-| `success` | boolean | Operation success status |
-
-### `okta_get_group`
-
-Get a specific group by ID from your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `groupId` | string | Yes | Group ID to look up |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Group ID |
-| `name` | string | Group name |
-| `description` | string | Group description |
-| `type` | string | Group type |
-| `created` | string | Creation timestamp |
-| `lastUpdated` | string | Last update timestamp |
-| `lastMembershipUpdated` | string | Last membership change timestamp |
-| `success` | boolean | Operation success status |
-
-### `okta_create_group`
-
-Create a new group in your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `name` | string | Yes | Name of the group |
-| `description` | string | No | Description of the group |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Created group ID |
-| `name` | string | Group name |
-| `description` | string | Group description |
-| `type` | string | Group type |
-| `created` | string | Creation timestamp |
-| `lastUpdated` | string | Last update timestamp |
-| `lastMembershipUpdated` | string | Last membership change timestamp |
-| `success` | boolean | Operation success status |
-
-### `okta_update_group`
-
-Update a group profile in your Okta organization. Only groups of OKTA_GROUP type can be updated. All profile properties must be specified (full replacement).
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `groupId` | string | Yes | Group ID to update |
-| `name` | string | Yes | Updated group name |
-| `description` | string | No | Updated group description |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Group ID |
-| `name` | string | Group name |
-| `description` | string | Group description |
-| `type` | string | Group type |
-| `created` | string | Creation timestamp |
-| `lastUpdated` | string | Last update timestamp |
-| `lastMembershipUpdated` | string | Last membership change timestamp |
-| `success` | boolean | Operation success status |
-
-### `okta_delete_group`
-
-Delete a group from your Okta organization. Groups of OKTA_GROUP or APP_GROUP type can be removed.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `groupId` | string | Yes | Group ID to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `groupId` | string | Deleted group ID |
-| `deleted` | boolean | Whether the group was deleted |
-| `success` | boolean | Operation success status |
-
-### `okta_add_user_to_group`
-
-Add a user to a group in your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `groupId` | string | Yes | Group ID to add the user to |
-| `userId` | string | Yes | User ID to add to the group |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `groupId` | string | Group ID |
-| `userId` | string | User ID added to the group |
-| `added` | boolean | Whether the user was added |
-| `success` | boolean | Operation success status |
-
-### `okta_remove_user_from_group`
-
-Remove a user from a group in your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `groupId` | string | Yes | Group ID to remove the user from |
-| `userId` | string | Yes | User ID to remove from the group |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `groupId` | string | Group ID |
-| `userId` | string | User ID removed from the group |
-| `removed` | boolean | Whether the user was removed |
-| `success` | boolean | Operation success status |
-
-### `okta_list_group_members`
-
-List all members of a specific group in your Okta organization
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Okta API token for authentication |
-| `domain` | string | Yes | Okta domain \(e.g., dev-123456.okta.com\) |
-| `groupId` | string | Yes | Group ID to list members for |
-| `limit` | number | No | Maximum number of members to return \(default: 1000, max: 1000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `members` | array | Array of group member user objects |
-|   ↳ `id` | string | User ID |
-|   ↳ `status` | string | User status |
-|   ↳ `firstName` | string | First name |
-|   ↳ `lastName` | string | Last name |
-|   ↳ `email` | string | Email address |
-|   ↳ `login` | string | Login |
-|   ↳ `mobilePhone` | string | Mobile phone |
-|   ↳ `title` | string | Job title |
-|   ↳ `department` | string | Department |
-|   ↳ `created` | string | Creation timestamp |
-|   ↳ `lastLogin` | string | Last login timestamp |
-|   ↳ `lastUpdated` | string | Last update timestamp |
-|   ↳ `activated` | string | Activation timestamp |
-|   ↳ `statusChanged` | string | Status change timestamp |
-| `count` | number | Number of members returned |
-| `success` | boolean | Operation success status |
-
-

apps/docs/content/docs/en/tools/perplexity.mdx

@@ -49,9 +49,6 @@ Generate completions using Perplexity AI chat models
 | `max_tokens` | number | No | Maximum number of tokens to generate \(e.g., 1024, 2048, 4096\) |
 | `temperature` | number | No | Sampling temperature between 0 and 1 \(e.g., 0.0 for deterministic, 0.7 for creative\) |
 | `apiKey` | string | Yes | Perplexity API key |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 
@@ -81,8 +78,6 @@ Get ranked search results from Perplexity
 | `search_after_date` | string | No | Include only content published after this date \(format: MM/DD/YYYY\) |
 | `search_before_date` | string | No | Include only content published before this date \(format: MM/DD/YYYY\) |
 | `apiKey` | string | Yes | Perplexity API key |
-| `pricing` | per_request | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 

apps/docs/content/docs/en/tools/profound.mdx

@@ -1,626 +0,0 @@
----
-title: Profound
-description: AI visibility and analytics with Profound
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="profound"
-  color="#000000"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Profound](https://tryprofound.com/) is an AI visibility and analytics platform that helps brands understand how they appear across AI-powered search engines, chatbots, and assistants. It tracks mentions, citations, sentiment, bot traffic, and referral patterns across platforms like ChatGPT, Perplexity, Google AI Overviews, and more.
-
-With the Profound integration in Sim, you can:
-
-- **Monitor AI Visibility**: Track share of voice, visibility scores, and mention counts across AI platforms for your brand and competitors.
-- **Analyze Sentiment**: Measure how positively or negatively your brand is discussed in AI-generated responses.
-- **Track Citations**: See which URLs are being cited by AI models and your citation share relative to competitors.
-- **Monitor Bot Traffic**: Analyze AI crawler activity on your domain, including GPTBot, ClaudeBot, and other AI agents, with hourly granularity.
-- **Track Referral Traffic**: Monitor human visits arriving from AI platforms to your website.
-- **Explore Prompt Data**: Access raw prompt-answer pairs, query fanouts, and prompt volume trends across AI platforms.
-- **Optimize Content**: Get AEO (Answer Engine Optimization) scores and actionable recommendations to improve how AI models reference your content.
-- **Manage Categories & Assets**: List and explore your tracked categories, assets (brands), topics, tags, personas, and regions.
-
-These tools let your agents automate AI visibility monitoring, competitive intelligence, and content optimization workflows. To use the Profound integration, you'll need a Profound account with API access.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Track how your brand appears across AI platforms. Monitor visibility scores, sentiment, citations, bot traffic, referrals, content optimization, and prompt volumes with Profound.
-
-
-
-## Tools
-
-### `profound_list_categories`
-
-List all organization categories in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `categories` | json | List of organization categories |
-|   ↳ `id` | string | Category ID |
-|   ↳ `name` | string | Category name |
-
-### `profound_list_regions`
-
-List all organization regions in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `regions` | json | List of organization regions |
-|   ↳ `id` | string | Region ID \(UUID\) |
-|   ↳ `name` | string | Region name |
-
-### `profound_list_models`
-
-List all AI models/platforms tracked in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `models` | json | List of AI models/platforms |
-|   ↳ `id` | string | Model ID \(UUID\) |
-|   ↳ `name` | string | Model/platform name |
-
-### `profound_list_domains`
-
-List all organization domains in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `domains` | json | List of organization domains |
-|   ↳ `id` | string | Domain ID \(UUID\) |
-|   ↳ `name` | string | Domain name |
-|   ↳ `createdAt` | string | When the domain was added |
-
-### `profound_list_assets`
-
-List all organization assets (companies/brands) across all categories in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `assets` | json | List of organization assets with category info |
-|   ↳ `id` | string | Asset ID |
-|   ↳ `name` | string | Asset/company name |
-|   ↳ `website` | string | Asset website URL |
-|   ↳ `alternateDomains` | json | Alternate domain names |
-|   ↳ `isOwned` | boolean | Whether this asset is owned by the organization |
-|   ↳ `createdAt` | string | When the asset was created |
-|   ↳ `logoUrl` | string | URL of the asset logo |
-|   ↳ `categoryId` | string | Category ID the asset belongs to |
-|   ↳ `categoryName` | string | Category name |
-
-### `profound_list_personas`
-
-List all organization personas across all categories in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `personas` | json | List of organization personas with profile details |
-|   ↳ `id` | string | Persona ID |
-|   ↳ `name` | string | Persona name |
-|   ↳ `categoryId` | string | Category ID |
-|   ↳ `categoryName` | string | Category name |
-|   ↳ `persona` | json | Persona profile with behavior, employment, and demographics |
-
-### `profound_category_topics`
-
-List topics for a specific category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `topics` | json | List of topics in the category |
-|   ↳ `id` | string | Topic ID \(UUID\) |
-|   ↳ `name` | string | Topic name |
-
-### `profound_category_tags`
-
-List tags for a specific category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `tags` | json | List of tags in the category |
-|   ↳ `id` | string | Tag ID \(UUID\) |
-|   ↳ `name` | string | Tag name |
-
-### `profound_category_prompts`
-
-List prompts for a specific category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-| `limit` | number | No | Maximum number of results \(default 10000, max 10000\) |
-| `cursor` | string | No | Pagination cursor from previous response |
-| `orderDir` | string | No | Sort direction: asc or desc \(default desc\) |
-| `promptType` | string | No | Comma-separated prompt types to filter: visibility, sentiment |
-| `topicId` | string | No | Comma-separated topic IDs \(UUIDs\) to filter by |
-| `tagId` | string | No | Comma-separated tag IDs \(UUIDs\) to filter by |
-| `regionId` | string | No | Comma-separated region IDs \(UUIDs\) to filter by |
-| `platformId` | string | No | Comma-separated platform IDs \(UUIDs\) to filter by |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of prompts |
-| `nextCursor` | string | Cursor for next page of results |
-| `prompts` | json | List of prompts |
-|   ↳ `id` | string | Prompt ID |
-|   ↳ `prompt` | string | Prompt text |
-|   ↳ `promptType` | string | Prompt type \(visibility or sentiment\) |
-|   ↳ `topicId` | string | Topic ID |
-|   ↳ `topicName` | string | Topic name |
-|   ↳ `tags` | json | Associated tags |
-|   ↳ `regions` | json | Associated regions |
-|   ↳ `platforms` | json | Associated platforms |
-|   ↳ `createdAt` | string | When the prompt was created |
-
-### `profound_category_assets`
-
-List assets (companies/brands) for a specific category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `assets` | json | List of assets in the category |
-|   ↳ `id` | string | Asset ID |
-|   ↳ `name` | string | Asset/company name |
-|   ↳ `website` | string | Website URL |
-|   ↳ `alternateDomains` | json | Alternate domain names |
-|   ↳ `isOwned` | boolean | Whether the asset is owned by the organization |
-|   ↳ `createdAt` | string | When the asset was created |
-|   ↳ `logoUrl` | string | URL of the asset logo |
-
-### `profound_category_personas`
-
-List personas for a specific category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `personas` | json | List of personas in the category |
-|   ↳ `id` | string | Persona ID |
-|   ↳ `name` | string | Persona name |
-|   ↳ `persona` | json | Persona profile with behavior, employment, and demographics |
-
-### `profound_visibility_report`
-
-Query AI visibility report for a category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | Yes | End date \(YYYY-MM-DD or ISO 8601\) |
-| `metrics` | string | Yes | Comma-separated metrics: share_of_voice, mentions_count, visibility_score, executions, average_position |
-| `dimensions` | string | No | Comma-separated dimensions: date, region, topic, model, asset_name, prompt, tag, persona |
-| `dateInterval` | string | No | Date interval: hour, day, week, month, year |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"asset_name","operator":"is","value":"Company"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of rows in the report |
-| `data` | json | Report data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values matching requested metrics order |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_sentiment_report`
-
-Query sentiment report for a category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | Yes | End date \(YYYY-MM-DD or ISO 8601\) |
-| `metrics` | string | Yes | Comma-separated metrics: positive, negative, occurrences |
-| `dimensions` | string | No | Comma-separated dimensions: theme, date, region, topic, model, asset_name, tag, prompt, sentiment_type, persona |
-| `dateInterval` | string | No | Date interval: hour, day, week, month, year |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"asset_name","operator":"is","value":"Company"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of rows in the report |
-| `data` | json | Report data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values matching requested metrics order |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_citations_report`
-
-Query citations report for a category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | Yes | End date \(YYYY-MM-DD or ISO 8601\) |
-| `metrics` | string | Yes | Comma-separated metrics: count, citation_share |
-| `dimensions` | string | No | Comma-separated dimensions: hostname, path, date, region, topic, model, tag, prompt, url, root_domain, persona, citation_category |
-| `dateInterval` | string | No | Date interval: hour, day, week, month, year |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"hostname","operator":"is","value":"example.com"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of rows in the report |
-| `data` | json | Report data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values matching requested metrics order |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_query_fanouts`
-
-Query fanout report showing how AI models expand prompts into sub-queries in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | Yes | End date \(YYYY-MM-DD or ISO 8601\) |
-| `metrics` | string | Yes | Comma-separated metrics: fanouts_per_execution, total_fanouts, share |
-| `dimensions` | string | No | Comma-separated dimensions: prompt, query, model, region, date |
-| `dateInterval` | string | No | Date interval: hour, day, week, month, year |
-| `filters` | string | No | JSON array of filter objects |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of rows in the report |
-| `data` | json | Report data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values matching requested metrics order |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_prompt_answers`
-
-Get raw prompt answers data for a category in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `categoryId` | string | Yes | Category ID \(UUID\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | Yes | End date \(YYYY-MM-DD or ISO 8601\) |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"prompt_type","operator":"is","value":"visibility"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of answer rows |
-| `data` | json | Raw prompt answer data |
-|   ↳ `prompt` | string | The prompt text |
-|   ↳ `promptType` | string | Prompt type \(visibility or sentiment\) |
-|   ↳ `response` | string | AI model response text |
-|   ↳ `mentions` | json | Companies/assets mentioned in the response |
-|   ↳ `citations` | json | URLs cited in the response |
-|   ↳ `topic` | string | Topic name |
-|   ↳ `region` | string | Region name |
-|   ↳ `model` | string | AI model/platform name |
-|   ↳ `asset` | string | Asset name |
-|   ↳ `createdAt` | string | Timestamp when the answer was collected |
-
-### `profound_bots_report`
-
-Query bot traffic report with hourly granularity for a domain in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `domain` | string | Yes | Domain to query bot traffic for \(e.g. example.com\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | No | End date \(YYYY-MM-DD or ISO 8601\). Defaults to now |
-| `metrics` | string | Yes | Comma-separated metrics: count, citations, indexing, training, last_visit |
-| `dimensions` | string | No | Comma-separated dimensions: date, hour, path, bot_name, bot_provider, bot_type |
-| `dateInterval` | string | No | Date interval: hour, day, week, month, year |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"bot_name","operator":"is","value":"GPTBot"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of rows in the report |
-| `data` | json | Report data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values matching requested metrics order |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_referrals_report`
-
-Query human referral traffic report with hourly granularity for a domain in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `domain` | string | Yes | Domain to query referral traffic for \(e.g. example.com\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | No | End date \(YYYY-MM-DD or ISO 8601\). Defaults to now |
-| `metrics` | string | Yes | Comma-separated metrics: visits, last_visit |
-| `dimensions` | string | No | Comma-separated dimensions: date, hour, path, referral_source, referral_type |
-| `dateInterval` | string | No | Date interval: hour, day, week, month, year |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"referral_source","operator":"is","value":"openai"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of rows in the report |
-| `data` | json | Report data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values matching requested metrics order |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_raw_logs`
-
-Get raw traffic logs with filters for a domain in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `domain` | string | Yes | Domain to query logs for \(e.g. example.com\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | No | End date \(YYYY-MM-DD or ISO 8601\). Defaults to now |
-| `dimensions` | string | No | Comma-separated dimensions: timestamp, method, host, path, status_code, ip, user_agent, referer, bytes_sent, duration_ms, query_params |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"path","operator":"contains","value":"/blog"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of log entries |
-| `data` | json | Log data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values \(count\) |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_bot_logs`
-
-Get identified bot visit logs with filters for a domain in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `domain` | string | Yes | Domain to query bot logs for \(e.g. example.com\) |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | No | End date \(YYYY-MM-DD or ISO 8601\). Defaults to now |
-| `dimensions` | string | No | Comma-separated dimensions: timestamp, method, host, path, status_code, ip, user_agent, referer, bytes_sent, duration_ms, query_params, bot_name, bot_provider, bot_types |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"bot_name","operator":"is","value":"GPTBot"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of bot log entries |
-| `data` | json | Bot log data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values \(count\) |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_list_optimizations`
-
-List content optimization entries for an asset in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `assetId` | string | Yes | Asset ID \(UUID\) |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-| `offset` | number | No | Offset for pagination \(default 0\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of optimization entries |
-| `optimizations` | json | List of content optimization entries |
-|   ↳ `id` | string | Optimization ID \(UUID\) |
-|   ↳ `title` | string | Content title |
-|   ↳ `createdAt` | string | When the optimization was created |
-|   ↳ `extractedInput` | string | Extracted input text |
-|   ↳ `type` | string | Content type: file, text, or url |
-|   ↳ `status` | string | Optimization status |
-
-### `profound_optimization_analysis`
-
-Get detailed content optimization analysis for a specific content item in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `assetId` | string | Yes | Asset ID \(UUID\) |
-| `contentId` | string | Yes | Content/optimization ID \(UUID\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `content` | json | The analyzed content |
-|   ↳ `format` | string | Content format: markdown or html |
-|   ↳ `value` | string | Content text |
-| `aeoContentScore` | json | AEO content score with target zone |
-|   ↳ `value` | number | AEO score value |
-|   ↳ `targetZone` | json | Target zone range |
-|     ↳ `low` | number | Low end of target range |
-|     ↳ `high` | number | High end of target range |
-| `analysis` | json | Analysis breakdown by category |
-|   ↳ `breakdown` | json | Array of scoring breakdowns |
-|     ↳ `title` | string | Category title |
-|     ↳ `weight` | number | Category weight |
-|     ↳ `score` | number | Category score |
-| `recommendations` | json | Content optimization recommendations |
-|   ↳ `title` | string | Recommendation title |
-|   ↳ `status` | string | Status: done or pending |
-|   ↳ `impact` | json | Impact details with section and score |
-|   ↳ `suggestion` | json | Suggestion text and rationale |
-|     ↳ `text` | string | Suggestion text |
-|     ↳ `rationale` | string | Why this recommendation matters |
-
-### `profound_prompt_volume`
-
-Query prompt volume data to understand search demand across AI platforms in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `startDate` | string | Yes | Start date \(YYYY-MM-DD or ISO 8601\) |
-| `endDate` | string | Yes | End date \(YYYY-MM-DD or ISO 8601\) |
-| `metrics` | string | Yes | Comma-separated metrics: volume, change |
-| `dimensions` | string | No | Comma-separated dimensions: keyword, date, platform, country_code, matching_type, frequency |
-| `dateInterval` | string | No | Date interval: hour, day, week, month, year |
-| `filters` | string | No | JSON array of filter objects, e.g. \[\{"field":"keyword","operator":"contains","value":"best"\}\] |
-| `limit` | number | No | Maximum number of results \(default 10000, max 50000\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `totalRows` | number | Total number of rows in the report |
-| `data` | json | Volume data rows with metrics and dimension values |
-|   ↳ `metrics` | json | Array of metric values matching requested metrics order |
-|   ↳ `dimensions` | json | Array of dimension values matching requested dimensions order |
-
-### `profound_citation_prompts`
-
-Get prompts that cite a specific domain across AI platforms in Profound
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Profound API Key |
-| `inputDomain` | string | Yes | Domain to look up citations for \(e.g. ramp.com\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `data` | json | Citation prompt data for the queried domain |
-
-

apps/docs/content/docs/en/tools/quiver.mdx

@@ -1,132 +0,0 @@
----
-title: Quiver
-description: Generate and vectorize SVGs
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="quiver"
-  color="#000000"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[QuiverAI](https://quiver.ai/) is an AI-powered SVG generation platform that creates high-quality, scalable vector graphics from text descriptions or by vectorizing raster images. It produces clean, resolution-independent SVGs that are ideal for icons, illustrations, logos, and UI elements.
-
-With Quiver, you can:
-
-- **Generate SVGs from text prompts**: Describe the vector graphic you need and get production-ready SVG output
-- **Vectorize raster images**: Convert PNG, JPG, and other raster images into clean SVG vector format
-- **Provide reference images**: Upload up to 4 reference images to guide the style and composition of generated SVGs
-- **Control generation parameters**: Adjust temperature, number of outputs, and token limits to fine-tune results
-- **List available models**: Query available QuiverAI models to discover supported operations and capabilities
-- **Get clean SVG markup**: Receive raw SVG content alongside downloadable files for easy embedding
-
-In Sim, the Quiver integration enables your workflows to generate and vectorize graphics on demand. This is useful for creating dynamic illustrations, converting raster assets to scalable vectors, generating icons for applications, producing visual assets for content pipelines, or building design automation workflows. The generated SVGs are returned as files that can be passed to downstream blocks for further processing, storage, or delivery.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Generate SVG images from text prompts or vectorize raster images into SVGs using QuiverAI. Supports reference images, style instructions, and multiple output generation.
-
-
-
-## Tools
-
-### `quiver_text_to_svg`
-
-Generate SVG images from text prompts using QuiverAI
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | QuiverAI API key |
-| `prompt` | string | Yes | A text description of the desired SVG |
-| `model` | string | Yes | The model to use for SVG generation \(e.g., "arrow-preview"\) |
-| `instructions` | string | No | Style or formatting guidance for the SVG output |
-| `references` | file | No | Reference images to guide SVG generation \(up to 4\) |
-| `n` | number | No | Number of SVGs to generate \(1-16, default 1\) |
-| `temperature` | number | No | Sampling temperature \(0-2, default 1\) |
-| `top_p` | number | No | Nucleus sampling probability \(0-1, default 1\) |
-| `max_output_tokens` | number | No | Maximum output tokens \(1-131072\) |
-| `presence_penalty` | number | No | Token penalty for prior output \(-2 to 2, default 0\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the SVG generation succeeded |
-| `output` | object | Generated SVG output |
-|   ↳ `file` | file | First generated SVG file |
-|   ↳ `files` | json | All generated SVG files \(when n &gt; 1\) |
-|   ↳ `svgContent` | string | Raw SVG markup content of the first result |
-|   ↳ `id` | string | Generation request ID |
-|   ↳ `usage` | json | Token usage statistics |
-|     ↳ `totalTokens` | number | Total tokens used |
-|     ↳ `inputTokens` | number | Input tokens used |
-|     ↳ `outputTokens` | number | Output tokens used |
-
-### `quiver_image_to_svg`
-
-Convert raster images into vector SVG format using QuiverAI
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | QuiverAI API key |
-| `model` | string | Yes | The model to use for vectorization \(e.g., "arrow-preview"\) |
-| `image` | file | Yes | The raster image to vectorize into SVG |
-| `temperature` | number | No | Sampling temperature \(0-2, default 1\) |
-| `top_p` | number | No | Nucleus sampling probability \(0-1, default 1\) |
-| `max_output_tokens` | number | No | Maximum output tokens \(1-131072\) |
-| `presence_penalty` | number | No | Token penalty for prior output \(-2 to 2, default 0\) |
-| `auto_crop` | boolean | No | Automatically crop the image before vectorizing |
-| `target_size` | number | No | Square resize target in pixels \(128-4096\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the vectorization succeeded |
-| `output` | object | Vectorized SVG output |
-|   ↳ `file` | file | Generated SVG file |
-|   ↳ `svgContent` | string | Raw SVG markup content |
-|   ↳ `id` | string | Vectorization request ID |
-|   ↳ `usage` | json | Token usage statistics |
-|     ↳ `totalTokens` | number | Total tokens used |
-|     ↳ `inputTokens` | number | Input tokens used |
-|     ↳ `outputTokens` | number | Output tokens used |
-
-### `quiver_list_models`
-
-List all available QuiverAI models
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | QuiverAI API key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the request succeeded |
-| `output` | object | Available models |
-|   ↳ `models` | json | List of available QuiverAI models |
-|     ↳ `id` | string | Model identifier |
-|     ↳ `name` | string | Human-readable model name |
-|     ↳ `description` | string | Model capabilities summary |
-|     ↳ `created` | number | Unix timestamp of creation |
-|     ↳ `ownedBy` | string | Organization that owns the model |
-|     ↳ `inputModalities` | json | Supported input types \(text, image, svg\) |
-|     ↳ `outputModalities` | json | Supported output types \(text, image, svg\) |
-|     ↳ `contextLength` | number | Maximum context window |
-|     ↳ `maxOutputLength` | number | Maximum generation length |
-|     ↳ `supportedOperations` | json | Available operations \(svg_generate, svg_edit, svg_animate, svg_vectorize, chat_completions\) |
-|     ↳ `supportedSamplingParameters` | json | Supported sampling parameters \(temperature, top_p, top_k, repetition_penalty, presence_penalty, stop\) |
-
-

apps/docs/content/docs/en/tools/rootly.mdx

@@ -1,891 +0,0 @@
----
-title: Rootly
-description: Manage incidents, alerts, and on-call with Rootly
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="rootly"
-  color="#6C72C8"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Rootly](https://rootly.com/) is an incident management platform that helps teams respond to, mitigate, and learn from incidents — all without leaving Slack or your existing tools. Rootly automates on-call alerting, incident workflows, status page updates, and retrospectives so engineering teams can resolve issues faster and reduce toil.
-
-**Why Rootly?**
-- **End-to-End Incident Management:** Create, track, update, and resolve incidents with full lifecycle support — from initial triage through retrospective.
-- **On-Call Alerting:** Create and manage alerts with deduplication, routing, and escalation to ensure the right people are notified immediately.
-- **Timeline Events:** Add structured timeline events to incidents for clear, auditable incident narratives.
-- **Service Catalog:** Maintain a catalog of services and map them to incidents for precise impact tracking.
-- **Severity & Prioritization:** Use configurable severity levels to prioritize incidents and drive appropriate response urgency.
-- **Retrospectives:** Access post-incident retrospectives to identify root causes, capture learnings, and drive reliability improvements.
-
-**Using Rootly in Sim**
-
-Sim's Rootly integration connects your agentic workflows directly to your Rootly account using an API key. With operations spanning incidents, alerts, services, severities, teams, environments, functionalities, incident types, and retrospectives, you can build powerful incident management automations without writing backend code.
-
-**Key benefits of using Rootly in Sim:**
-- **Automated incident creation:** Trigger incident creation from monitoring alerts, customer reports, or anomaly detection workflows with full metadata including severity, services, and teams.
-- **Incident lifecycle automation:** Automatically update incident status, add timeline events, and attach mitigation or resolution messages as your response progresses.
-- **Alert management:** Create and list alerts with deduplication support to integrate Rootly into your existing monitoring and notification pipelines.
-- **Organizational awareness:** Query services, severities, teams, environments, functionalities, and incident types to build context-aware incident workflows.
-- **Retrospective insights:** List and filter retrospectives to feed post-incident learnings into continuous improvement workflows.
-
-Whether you're automating incident response, building on-call alerting pipelines, or driving post-incident learning, Rootly in Sim gives you direct, secure access to the Rootly API — no middleware required. Simply configure your API key, select the operation you need, and let Sim handle the rest.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Rootly incident management into workflows. Create and manage incidents, alerts, services, severities, and retrospectives.
-
-
-
-## Tools
-
-### `rootly_create_incident`
-
-Create a new incident in Rootly with optional severity, services, and teams.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `title` | string | No | The title of the incident \(auto-generated if not provided\) |
-| `summary` | string | No | A summary of the incident |
-| `severityId` | string | No | Severity ID to attach to the incident |
-| `status` | string | No | Incident status \(in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed\) |
-| `kind` | string | No | Incident kind \(normal, normal_sub, test, test_sub, example, example_sub, backfilled, scheduled, scheduled_sub\) |
-| `serviceIds` | string | No | Comma-separated service IDs to attach |
-| `environmentIds` | string | No | Comma-separated environment IDs to attach |
-| `groupIds` | string | No | Comma-separated team/group IDs to attach |
-| `incidentTypeIds` | string | No | Comma-separated incident type IDs to attach |
-| `functionalityIds` | string | No | Comma-separated functionality IDs to attach |
-| `labels` | string | No | Labels as JSON object, e.g. \{"platform":"osx","version":"1.29"\} |
-| `private` | boolean | No | Create as a private incident \(cannot be undone\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `incident` | object | The created incident |
-|   ↳ `id` | string | Unique incident ID |
-|   ↳ `sequentialId` | number | Sequential incident number |
-|   ↳ `title` | string | Incident title |
-|   ↳ `slug` | string | Incident slug |
-|   ↳ `kind` | string | Incident kind |
-|   ↳ `summary` | string | Incident summary |
-|   ↳ `status` | string | Incident status |
-|   ↳ `private` | boolean | Whether the incident is private |
-|   ↳ `url` | string | URL to the incident |
-|   ↳ `shortUrl` | string | Short URL to the incident |
-|   ↳ `severityName` | string | Severity name |
-|   ↳ `severityId` | string | Severity ID |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `mitigatedAt` | string | Mitigation date |
-|   ↳ `resolvedAt` | string | Resolution date |
-|   ↳ `closedAt` | string | Closed date |
-
-### `rootly_get_incident`
-
-Retrieve a single incident by ID from Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `incidentId` | string | Yes | The ID of the incident to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `incident` | object | The incident details |
-|   ↳ `id` | string | Unique incident ID |
-|   ↳ `sequentialId` | number | Sequential incident number |
-|   ↳ `title` | string | Incident title |
-|   ↳ `slug` | string | Incident slug |
-|   ↳ `kind` | string | Incident kind |
-|   ↳ `summary` | string | Incident summary |
-|   ↳ `status` | string | Incident status |
-|   ↳ `private` | boolean | Whether the incident is private |
-|   ↳ `url` | string | URL to the incident |
-|   ↳ `shortUrl` | string | Short URL to the incident |
-|   ↳ `severityName` | string | Severity name |
-|   ↳ `severityId` | string | Severity ID |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `mitigatedAt` | string | Mitigation date |
-|   ↳ `resolvedAt` | string | Resolution date |
-|   ↳ `closedAt` | string | Closed date |
-
-### `rootly_update_incident`
-
-Update an existing incident in Rootly (status, severity, summary, etc.).
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `incidentId` | string | Yes | The ID of the incident to update |
-| `title` | string | No | Updated incident title |
-| `summary` | string | No | Updated incident summary |
-| `severityId` | string | No | Updated severity ID |
-| `status` | string | No | Updated status \(in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed\) |
-| `kind` | string | No | Incident kind \(normal, normal_sub, test, test_sub, example, example_sub, backfilled, scheduled, scheduled_sub\) |
-| `private` | boolean | No | Set incident as private \(cannot be undone\) |
-| `serviceIds` | string | No | Comma-separated service IDs |
-| `environmentIds` | string | No | Comma-separated environment IDs |
-| `groupIds` | string | No | Comma-separated team/group IDs |
-| `incidentTypeIds` | string | No | Comma-separated incident type IDs to attach |
-| `functionalityIds` | string | No | Comma-separated functionality IDs to attach |
-| `labels` | string | No | Labels as JSON object, e.g. \{"platform":"osx","version":"1.29"\} |
-| `mitigationMessage` | string | No | How was the incident mitigated? |
-| `resolutionMessage` | string | No | How was the incident resolved? |
-| `cancellationMessage` | string | No | Why was the incident cancelled? |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `incident` | object | The updated incident |
-|   ↳ `id` | string | Unique incident ID |
-|   ↳ `sequentialId` | number | Sequential incident number |
-|   ↳ `title` | string | Incident title |
-|   ↳ `slug` | string | Incident slug |
-|   ↳ `kind` | string | Incident kind |
-|   ↳ `summary` | string | Incident summary |
-|   ↳ `status` | string | Incident status |
-|   ↳ `private` | boolean | Whether the incident is private |
-|   ↳ `url` | string | URL to the incident |
-|   ↳ `shortUrl` | string | Short URL to the incident |
-|   ↳ `severityName` | string | Severity name |
-|   ↳ `severityId` | string | Severity ID |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `mitigatedAt` | string | Mitigation date |
-|   ↳ `resolvedAt` | string | Resolution date |
-|   ↳ `closedAt` | string | Closed date |
-
-### `rootly_list_incidents`
-
-List incidents from Rootly with optional filtering by status, severity, and more.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `status` | string | No | Filter by status \(in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed\) |
-| `severity` | string | No | Filter by severity slug |
-| `search` | string | No | Search term to filter incidents |
-| `services` | string | No | Filter by service slugs \(comma-separated\) |
-| `teams` | string | No | Filter by team slugs \(comma-separated\) |
-| `environments` | string | No | Filter by environment slugs \(comma-separated\) |
-| `sort` | string | No | Sort order \(e.g., -created_at, created_at, -started_at\) |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `incidents` | array | List of incidents |
-|   ↳ `id` | string | Unique incident ID |
-|   ↳ `sequentialId` | number | Sequential incident number |
-|   ↳ `title` | string | Incident title |
-|   ↳ `slug` | string | Incident slug |
-|   ↳ `kind` | string | Incident kind |
-|   ↳ `summary` | string | Incident summary |
-|   ↳ `status` | string | Incident status |
-|   ↳ `private` | boolean | Whether the incident is private |
-|   ↳ `url` | string | URL to the incident |
-|   ↳ `shortUrl` | string | Short URL to the incident |
-|   ↳ `severityName` | string | Severity name |
-|   ↳ `severityId` | string | Severity ID |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `mitigatedAt` | string | Mitigation date |
-|   ↳ `resolvedAt` | string | Resolution date |
-|   ↳ `closedAt` | string | Closed date |
-| `totalCount` | number | Total number of incidents returned |
-
-### `rootly_create_alert`
-
-Create a new alert in Rootly for on-call notification and routing.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `summary` | string | Yes | The summary of the alert |
-| `description` | string | No | A detailed description of the alert |
-| `source` | string | Yes | The source of the alert \(e.g., api, manual, datadog, pagerduty\) |
-| `status` | string | No | Alert status on creation \(open, triggered\) |
-| `serviceIds` | string | No | Comma-separated service IDs to attach |
-| `groupIds` | string | No | Comma-separated team/group IDs to attach |
-| `environmentIds` | string | No | Comma-separated environment IDs to attach |
-| `externalId` | string | No | External ID for the alert |
-| `externalUrl` | string | No | External URL for the alert |
-| `deduplicationKey` | string | No | Alerts sharing the same deduplication key are treated as a single alert |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `alert` | object | The created alert |
-|   ↳ `id` | string | Unique alert ID |
-|   ↳ `shortId` | string | Short alert ID |
-|   ↳ `summary` | string | Alert summary |
-|   ↳ `description` | string | Alert description |
-|   ↳ `source` | string | Alert source |
-|   ↳ `status` | string | Alert status |
-|   ↳ `externalId` | string | External ID |
-|   ↳ `externalUrl` | string | External URL |
-|   ↳ `deduplicationKey` | string | Deduplication key |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `endedAt` | string | End date |
-
-### `rootly_list_alerts`
-
-List alerts from Rootly with optional filtering by status, source, and services.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `status` | string | No | Filter by status \(open, triggered, acknowledged, resolved\) |
-| `source` | string | No | Filter by source \(e.g., api, datadog, pagerduty\) |
-| `services` | string | No | Filter by service slugs \(comma-separated\) |
-| `environments` | string | No | Filter by environment slugs \(comma-separated\) |
-| `groups` | string | No | Filter by team/group slugs \(comma-separated\) |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `alerts` | array | List of alerts |
-|   ↳ `id` | string | Unique alert ID |
-|   ↳ `shortId` | string | Short alert ID |
-|   ↳ `summary` | string | Alert summary |
-|   ↳ `description` | string | Alert description |
-|   ↳ `source` | string | Alert source |
-|   ↳ `status` | string | Alert status |
-|   ↳ `externalId` | string | External ID |
-|   ↳ `externalUrl` | string | External URL |
-|   ↳ `deduplicationKey` | string | Deduplication key |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `endedAt` | string | End date |
-| `totalCount` | number | Total number of alerts returned |
-
-### `rootly_add_incident_event`
-
-Add a timeline event to an existing incident in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `incidentId` | string | Yes | The ID of the incident to add the event to |
-| `event` | string | Yes | The summary/description of the event |
-| `visibility` | string | No | Event visibility \(internal or external\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `eventId` | string | The ID of the created event |
-| `event` | string | The event summary |
-| `visibility` | string | Event visibility \(internal or external\) |
-| `occurredAt` | string | When the event occurred |
-| `createdAt` | string | Creation date |
-| `updatedAt` | string | Last update date |
-
-### `rootly_list_services`
-
-List services from Rootly with optional search filtering.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter services |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `services` | array | List of services |
-|   ↳ `id` | string | Unique service ID |
-|   ↳ `name` | string | Service name |
-|   ↳ `slug` | string | Service slug |
-|   ↳ `description` | string | Service description |
-|   ↳ `color` | string | Service color |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of services returned |
-
-### `rootly_list_severities`
-
-List severity levels configured in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter severities |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `severities` | array | List of severity levels |
-|   ↳ `id` | string | Unique severity ID |
-|   ↳ `name` | string | Severity name |
-|   ↳ `slug` | string | Severity slug |
-|   ↳ `description` | string | Severity description |
-|   ↳ `severity` | string | Severity level \(critical, high, medium, low\) |
-|   ↳ `color` | string | Severity color |
-|   ↳ `position` | number | Display position |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of severities returned |
-
-### `rootly_list_teams`
-
-List teams (groups) configured in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter teams |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `teams` | array | List of teams |
-|   ↳ `id` | string | Unique team ID |
-|   ↳ `name` | string | Team name |
-|   ↳ `slug` | string | Team slug |
-|   ↳ `description` | string | Team description |
-|   ↳ `color` | string | Team color |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of teams returned |
-
-### `rootly_list_environments`
-
-List environments configured in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter environments |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `environments` | array | List of environments |
-|   ↳ `id` | string | Unique environment ID |
-|   ↳ `name` | string | Environment name |
-|   ↳ `slug` | string | Environment slug |
-|   ↳ `description` | string | Environment description |
-|   ↳ `color` | string | Environment color |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of environments returned |
-
-### `rootly_list_incident_types`
-
-List incident types configured in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Filter incident types by name |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `incidentTypes` | array | List of incident types |
-|   ↳ `id` | string | Unique incident type ID |
-|   ↳ `name` | string | Incident type name |
-|   ↳ `slug` | string | Incident type slug |
-|   ↳ `description` | string | Incident type description |
-|   ↳ `color` | string | Incident type color |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of incident types returned |
-
-### `rootly_list_functionalities`
-
-List functionalities configured in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter functionalities |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `functionalities` | array | List of functionalities |
-|   ↳ `id` | string | Unique functionality ID |
-|   ↳ `name` | string | Functionality name |
-|   ↳ `slug` | string | Functionality slug |
-|   ↳ `description` | string | Functionality description |
-|   ↳ `color` | string | Functionality color |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of functionalities returned |
-
-### `rootly_list_retrospectives`
-
-List incident retrospectives (post-mortems) from Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `status` | string | No | Filter by status \(draft, published\) |
-| `search` | string | No | Search term to filter retrospectives |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `retrospectives` | array | List of retrospectives |
-|   ↳ `id` | string | Unique retrospective ID |
-|   ↳ `title` | string | Retrospective title |
-|   ↳ `status` | string | Status \(draft or published\) |
-|   ↳ `url` | string | URL to the retrospective |
-|   ↳ `startedAt` | string | Incident start date |
-|   ↳ `mitigatedAt` | string | Mitigation date |
-|   ↳ `resolvedAt` | string | Resolution date |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of retrospectives returned |
-
-### `rootly_delete_incident`
-
-Delete an incident by ID from Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `incidentId` | string | Yes | The ID of the incident to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the deletion succeeded |
-| `message` | string | Result message |
-
-### `rootly_get_alert`
-
-Retrieve a single alert by ID from Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `alertId` | string | Yes | The ID of the alert to retrieve |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `alert` | object | The alert details |
-|   ↳ `id` | string | Unique alert ID |
-|   ↳ `shortId` | string | Short alert ID |
-|   ↳ `summary` | string | Alert summary |
-|   ↳ `description` | string | Alert description |
-|   ↳ `source` | string | Alert source |
-|   ↳ `status` | string | Alert status |
-|   ↳ `externalId` | string | External ID |
-|   ↳ `externalUrl` | string | External URL |
-|   ↳ `deduplicationKey` | string | Deduplication key |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `endedAt` | string | End date |
-
-### `rootly_update_alert`
-
-Update an existing alert in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `alertId` | string | Yes | The ID of the alert to update |
-| `summary` | string | No | Updated alert summary |
-| `description` | string | No | Updated alert description |
-| `source` | string | No | Updated alert source |
-| `serviceIds` | string | No | Comma-separated service IDs to attach |
-| `groupIds` | string | No | Comma-separated team/group IDs to attach |
-| `environmentIds` | string | No | Comma-separated environment IDs to attach |
-| `externalId` | string | No | Updated external ID |
-| `externalUrl` | string | No | Updated external URL |
-| `deduplicationKey` | string | No | Updated deduplication key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `alert` | object | The updated alert |
-|   ↳ `id` | string | Unique alert ID |
-|   ↳ `shortId` | string | Short alert ID |
-|   ↳ `summary` | string | Alert summary |
-|   ↳ `description` | string | Alert description |
-|   ↳ `source` | string | Alert source |
-|   ↳ `status` | string | Alert status |
-|   ↳ `externalId` | string | External ID |
-|   ↳ `externalUrl` | string | External URL |
-|   ↳ `deduplicationKey` | string | Deduplication key |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `endedAt` | string | End date |
-
-### `rootly_acknowledge_alert`
-
-Acknowledge an alert in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `alertId` | string | Yes | The ID of the alert to acknowledge |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `alert` | object | The acknowledged alert |
-|   ↳ `id` | string | Unique alert ID |
-|   ↳ `shortId` | string | Short alert ID |
-|   ↳ `summary` | string | Alert summary |
-|   ↳ `description` | string | Alert description |
-|   ↳ `source` | string | Alert source |
-|   ↳ `status` | string | Alert status |
-|   ↳ `externalId` | string | External ID |
-|   ↳ `externalUrl` | string | External URL |
-|   ↳ `deduplicationKey` | string | Deduplication key |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `endedAt` | string | End date |
-
-### `rootly_resolve_alert`
-
-Resolve an alert in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `alertId` | string | Yes | The ID of the alert to resolve |
-| `resolutionMessage` | string | No | Message describing how the alert was resolved |
-| `resolveRelatedIncidents` | boolean | No | Whether to also resolve related incidents |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `alert` | object | The resolved alert |
-|   ↳ `id` | string | Unique alert ID |
-|   ↳ `shortId` | string | Short alert ID |
-|   ↳ `summary` | string | Alert summary |
-|   ↳ `description` | string | Alert description |
-|   ↳ `source` | string | Alert source |
-|   ↳ `status` | string | Alert status |
-|   ↳ `externalId` | string | External ID |
-|   ↳ `externalUrl` | string | External URL |
-|   ↳ `deduplicationKey` | string | Deduplication key |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-|   ↳ `startedAt` | string | Start date |
-|   ↳ `endedAt` | string | End date |
-
-### `rootly_create_action_item`
-
-Create a new action item for an incident in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `incidentId` | string | Yes | The ID of the incident to add the action item to |
-| `summary` | string | Yes | The title of the action item |
-| `description` | string | No | A detailed description of the action item |
-| `kind` | string | No | The kind of action item \(task, follow_up\) |
-| `priority` | string | No | Priority level \(high, medium, low\) |
-| `status` | string | No | Action item status \(open, in_progress, cancelled, done\) |
-| `assignedToUserId` | string | No | The user ID to assign the action item to |
-| `dueDate` | string | No | Due date for the action item |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `actionItem` | object | The created action item |
-|   ↳ `id` | string | Unique action item ID |
-|   ↳ `summary` | string | Action item title |
-|   ↳ `description` | string | Action item description |
-|   ↳ `kind` | string | Action item kind \(task, follow_up\) |
-|   ↳ `priority` | string | Priority level |
-|   ↳ `status` | string | Action item status |
-|   ↳ `dueDate` | string | Due date |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-
-### `rootly_list_action_items`
-
-List action items for an incident in Rootly.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `incidentId` | string | Yes | The ID of the incident to list action items for |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `actionItems` | array | List of action items |
-|   ↳ `id` | string | Unique action item ID |
-|   ↳ `summary` | string | Action item title |
-|   ↳ `description` | string | Action item description |
-|   ↳ `kind` | string | Action item kind \(task, follow_up\) |
-|   ↳ `priority` | string | Priority level |
-|   ↳ `status` | string | Action item status |
-|   ↳ `dueDate` | string | Due date |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of action items returned |
-
-### `rootly_list_users`
-
-List users from Rootly with optional search and email filtering.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter users |
-| `email` | string | No | Filter users by email address |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `users` | array | List of users |
-|   ↳ `id` | string | Unique user ID |
-|   ↳ `email` | string | User email address |
-|   ↳ `firstName` | string | User first name |
-|   ↳ `lastName` | string | User last name |
-|   ↳ `fullName` | string | User full name |
-|   ↳ `timeZone` | string | User time zone |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of users returned |
-
-### `rootly_list_on_calls`
-
-List current on-call entries from Rootly with optional filtering.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `scheduleIds` | string | No | Comma-separated schedule IDs to filter by |
-| `escalationPolicyIds` | string | No | Comma-separated escalation policy IDs to filter by |
-| `userIds` | string | No | Comma-separated user IDs to filter by |
-| `serviceIds` | string | No | Comma-separated service IDs to filter by |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `onCalls` | array | List of on-call entries |
-|   ↳ `id` | string | Unique on-call entry ID |
-|   ↳ `userId` | string | ID of the on-call user |
-|   ↳ `userName` | string | Name of the on-call user |
-|   ↳ `scheduleId` | string | ID of the associated schedule |
-|   ↳ `scheduleName` | string | Name of the associated schedule |
-|   ↳ `escalationPolicyId` | string | ID of the associated escalation policy |
-|   ↳ `startTime` | string | On-call start time |
-|   ↳ `endTime` | string | On-call end time |
-| `totalCount` | number | Total number of on-call entries returned |
-
-### `rootly_list_schedules`
-
-List on-call schedules from Rootly with optional search filtering.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter schedules |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `schedules` | array | List of schedules |
-|   ↳ `id` | string | Unique schedule ID |
-|   ↳ `name` | string | Schedule name |
-|   ↳ `description` | string | Schedule description |
-|   ↳ `allTimeCoverage` | boolean | Whether schedule provides 24/7 coverage |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of schedules returned |
-
-### `rootly_list_escalation_policies`
-
-List escalation policies from Rootly with optional search filtering.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter escalation policies |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `escalationPolicies` | array | List of escalation policies |
-|   ↳ `id` | string | Unique escalation policy ID |
-|   ↳ `name` | string | Escalation policy name |
-|   ↳ `description` | string | Escalation policy description |
-|   ↳ `repeatCount` | number | Number of times to repeat escalation |
-|   ↳ `groupIds` | array | Associated group IDs |
-|   ↳ `serviceIds` | array | Associated service IDs |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of escalation policies returned |
-
-### `rootly_list_causes`
-
-List causes from Rootly with optional search filtering.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `search` | string | No | Search term to filter causes |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `causes` | array | List of causes |
-|   ↳ `id` | string | Unique cause ID |
-|   ↳ `name` | string | Cause name |
-|   ↳ `slug` | string | Cause slug |
-|   ↳ `description` | string | Cause description |
-|   ↳ `position` | number | Cause position |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of causes returned |
-
-### `rootly_list_playbooks`
-
-List playbooks from Rootly with pagination support.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Rootly API key |
-| `pageSize` | number | No | Number of items per page \(default: 20\) |
-| `pageNumber` | number | No | Page number for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `playbooks` | array | List of playbooks |
-|   ↳ `id` | string | Unique playbook ID |
-|   ↳ `title` | string | Playbook title |
-|   ↳ `summary` | string | Playbook summary |
-|   ↳ `externalUrl` | string | External URL |
-|   ↳ `createdAt` | string | Creation date |
-|   ↳ `updatedAt` | string | Last update date |
-| `totalCount` | number | Total number of playbooks returned |
-
-

apps/docs/content/docs/en/tools/secrets_manager.mdx

@@ -1,157 +0,0 @@
----
-title: AWS Secrets Manager
-description: Connect to AWS Secrets Manager
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="secrets_manager"
-  color="linear-gradient(45deg, #BD0816 0%, #FF5252 100%)"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) is a secrets management service that helps you protect access to your applications, services, and IT resources. It enables you to rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle.
-
-With AWS Secrets Manager, you can:
-
-- **Securely store secrets**: Encrypt secrets at rest using AWS KMS encryption keys
-- **Retrieve secrets programmatically**: Access secrets from your applications and workflows without hardcoding credentials
-- **Rotate secrets automatically**: Configure automatic rotation for supported services like RDS, Redshift, and DocumentDB
-- **Audit access**: Track secret access and changes through AWS CloudTrail integration
-- **Control access with IAM**: Use fine-grained IAM policies to manage who can access which secrets
-- **Replicate across regions**: Automatically replicate secrets to multiple AWS regions for disaster recovery
-
-In Sim, the AWS Secrets Manager integration allows your workflows to securely retrieve credentials and configuration values at runtime, create and manage secrets as part of automation pipelines, and maintain a centralized secrets store that your agents can access. This is particularly useful for workflows that need to authenticate with external services, rotate credentials, or manage sensitive configuration across environments — all without exposing secrets in your workflow definitions.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate AWS Secrets Manager into the workflow. Can retrieve, create, update, list, and delete secrets.
-
-
-
-## Tools
-
-### `secrets_manager_get_secret`
-
-Retrieve a secret value from AWS Secrets Manager
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `region` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `accessKeyId` | string | Yes | AWS access key ID |
-| `secretAccessKey` | string | Yes | AWS secret access key |
-| `secretId` | string | Yes | The name or ARN of the secret to retrieve |
-| `versionId` | string | No | The unique identifier of the version to retrieve |
-| `versionStage` | string | No | The staging label of the version to retrieve \(e.g., AWSCURRENT, AWSPREVIOUS\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `name` | string | Name of the secret |
-| `secretValue` | string | The decrypted secret value |
-| `arn` | string | ARN of the secret |
-| `versionId` | string | Version ID of the secret |
-| `versionStages` | array | Staging labels attached to this version |
-| `createdDate` | string | Date the secret was created |
-
-### `secrets_manager_list_secrets`
-
-List secrets stored in AWS Secrets Manager
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `region` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `accessKeyId` | string | Yes | AWS access key ID |
-| `secretAccessKey` | string | Yes | AWS secret access key |
-| `maxResults` | number | No | Maximum number of secrets to return \(1-100, default 100\) |
-| `nextToken` | string | No | Pagination token from a previous request |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `secrets` | json | List of secrets with name, ARN, description, and dates |
-| `nextToken` | string | Pagination token for the next page of results |
-| `count` | number | Number of secrets returned |
-
-### `secrets_manager_create_secret`
-
-Create a new secret in AWS Secrets Manager
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `region` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `accessKeyId` | string | Yes | AWS access key ID |
-| `secretAccessKey` | string | Yes | AWS secret access key |
-| `name` | string | Yes | Name of the secret to create |
-| `secretValue` | string | Yes | The secret value \(plain text or JSON string\) |
-| `description` | string | No | Description of the secret |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `name` | string | Name of the created secret |
-| `arn` | string | ARN of the created secret |
-| `versionId` | string | Version ID of the created secret |
-
-### `secrets_manager_update_secret`
-
-Update the value of an existing secret in AWS Secrets Manager
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `region` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `accessKeyId` | string | Yes | AWS access key ID |
-| `secretAccessKey` | string | Yes | AWS secret access key |
-| `secretId` | string | Yes | The name or ARN of the secret to update |
-| `secretValue` | string | Yes | The new secret value \(plain text or JSON string\) |
-| `description` | string | No | Updated description of the secret |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `name` | string | Name of the updated secret |
-| `arn` | string | ARN of the updated secret |
-| `versionId` | string | Version ID of the updated secret |
-
-### `secrets_manager_delete_secret`
-
-Delete a secret from AWS Secrets Manager
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `region` | string | Yes | AWS region \(e.g., us-east-1\) |
-| `accessKeyId` | string | Yes | AWS access key ID |
-| `secretAccessKey` | string | Yes | AWS secret access key |
-| `secretId` | string | Yes | The name or ARN of the secret to delete |
-| `recoveryWindowInDays` | number | No | Number of days before permanent deletion \(7-30, default 30\) |
-| `forceDelete` | boolean | No | If true, immediately delete without recovery window |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `name` | string | Name of the deleted secret |
-| `arn` | string | ARN of the deleted secret |
-| `deletionDate` | string | Scheduled deletion date |
-
-

apps/docs/content/docs/en/tools/serper.mdx

@@ -47,9 +47,6 @@ A powerful web search tool that provides access to Google search results through
 | `hl` | string | No | Language code for search results \(e.g., "en", "es", "de", "fr"\) |
 | `type` | string | No | Type of search to perform \(e.g., "search", "news", "images", "videos", "places", "shopping"\) |
 | `apiKey` | string | Yes | Serper API Key |
-| `pricing` | custom | No | No description |
-| `metadata` | string | No | No description |
-| `rateLimit` | string | No | No description |
 
 #### Output
 

apps/docs/content/docs/en/tools/slack.mdx

@@ -925,82 +925,6 @@ Create a canvas pinned to a Slack channel as its resource hub
 | --------- | ---- | ----------- |
 | `canvas_id` | string | ID of the created channel canvas |
 
-### `slack_create_conversation`
-
-Create a new public or private channel in a Slack workspace.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `authMethod` | string | No | Authentication method: oauth or bot_token |
-| `botToken` | string | No | Bot token for Custom Bot |
-| `name` | string | Yes | Name of the channel to create \(lowercase, numbers, hyphens, underscores only; max 80 characters\) |
-| `isPrivate` | boolean | No | Create a private channel instead of a public one \(default: false\) |
-| `teamId` | string | No | Encoded team ID to create the channel in \(required if using an org token\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `channelInfo` | object | The newly created channel object |
-|   ↳ `id` | string | Channel ID \(e.g., C1234567890\) |
-|   ↳ `name` | string | Channel name without # prefix |
-|   ↳ `is_channel` | boolean | Whether this is a channel |
-|   ↳ `is_private` | boolean | Whether channel is private |
-|   ↳ `is_archived` | boolean | Whether channel is archived |
-|   ↳ `is_general` | boolean | Whether this is the general channel |
-|   ↳ `is_member` | boolean | Whether the bot/user is a member |
-|   ↳ `is_shared` | boolean | Whether channel is shared across workspaces |
-|   ↳ `is_ext_shared` | boolean | Whether channel is externally shared |
-|   ↳ `is_org_shared` | boolean | Whether channel is org-wide shared |
-|   ↳ `num_members` | number | Number of members in the channel |
-|   ↳ `topic` | string | Channel topic |
-|   ↳ `purpose` | string | Channel purpose/description |
-|   ↳ `created` | number | Unix timestamp when channel was created |
-|   ↳ `creator` | string | User ID of channel creator |
-|   ↳ `updated` | number | Unix timestamp of last update |
-
-### `slack_invite_to_conversation`
-
-Invite one or more users to a Slack channel. Supports up to 100 users at a time.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `authMethod` | string | No | Authentication method: oauth or bot_token |
-| `botToken` | string | No | Bot token for Custom Bot |
-| `channel` | string | Yes | The ID of the channel to invite users to |
-| `users` | string | Yes | Comma-separated list of user IDs to invite \(up to 100\) |
-| `force` | boolean | No | When true, continues inviting valid users while skipping invalid ones \(default: false\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `channelInfo` | object | The channel object after inviting users |
-|   ↳ `id` | string | Channel ID \(e.g., C1234567890\) |
-|   ↳ `name` | string | Channel name without # prefix |
-|   ↳ `is_channel` | boolean | Whether this is a channel |
-|   ↳ `is_private` | boolean | Whether channel is private |
-|   ↳ `is_archived` | boolean | Whether channel is archived |
-|   ↳ `is_general` | boolean | Whether this is the general channel |
-|   ↳ `is_member` | boolean | Whether the bot/user is a member |
-|   ↳ `is_shared` | boolean | Whether channel is shared across workspaces |
-|   ↳ `is_ext_shared` | boolean | Whether channel is externally shared |
-|   ↳ `is_org_shared` | boolean | Whether channel is org-wide shared |
-|   ↳ `num_members` | number | Number of members in the channel |
-|   ↳ `topic` | string | Channel topic |
-|   ↳ `purpose` | string | Channel purpose/description |
-|   ↳ `created` | number | Unix timestamp when channel was created |
-|   ↳ `creator` | string | User ID of channel creator |
-|   ↳ `updated` | number | Unix timestamp of last update |
-| `errors` | array | Per-user errors when force is true and some invitations failed |
-|   ↳ `user` | string | User ID that failed |
-|   ↳ `ok` | boolean | Always false for error entries |
-|   ↳ `error` | string | Error code for this user |
-
 ### `slack_open_view`
 
 Open a modal view in Slack using a trigger_id from an interaction payload. Used to display forms, confirmations, and other interactive modals.

apps/docs/content/docs/en/tools/tailscale.mdx

@@ -1,498 +0,0 @@
----
-title: Tailscale
-description: Manage devices and network settings in your Tailscale tailnet
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="tailscale"
-  color="#2E2D2D"
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-## Overview
-
-[Tailscale](https://tailscale.com) is a zero-config mesh VPN built on WireGuard that makes it easy to connect devices, services, and users across any network. The Tailscale block lets you automate network management tasks like device provisioning, access control, route management, and DNS configuration directly from your Sim workflows.
-
-## Authentication
-
-The Tailscale block uses API key authentication. To get an API key:
-
-1. Go to the [Tailscale admin console](https://login.tailscale.com/admin/settings/keys)
-2. Navigate to **Settings > Keys**
-3. Click **Generate API key**
-4. Set an expiry (1-90 days) and copy the key (starts with `tskey-api-`)
-
-You must have an **Owner**, **Admin**, **IT admin**, or **Network admin** role to generate API keys.
-
-## Tailnet Identifier
-
-Every operation requires a **tailnet** parameter. This is typically your organization's domain name (e.g., `example.com`). You can also use `"-"` to refer to your default tailnet.
-
-## Common Use Cases
-
-- **Device inventory**: List and monitor all devices connected to your network
-- **Automated provisioning**: Create and manage auth keys to pre-authorize new devices
-- **Access control**: Authorize or deauthorize devices, manage device tags for ACL policies
-- **Route management**: View and enable subnet routes for devices acting as subnet routers
-- **DNS management**: Configure nameservers, MagicDNS, and search paths
-- **Key lifecycle**: Create, list, inspect, and revoke auth keys
-- **User auditing**: List all users in the tailnet and their roles
-- **Policy review**: Retrieve the current ACL policy for inspection or backup
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Interact with the Tailscale API to manage devices, DNS, ACLs, auth keys, users, and routes across your tailnet.
-
-
-
-## Tools
-
-### `tailscale_list_devices`
-
-List all devices in the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `devices` | array | List of devices in the tailnet |
-|   ↳ `id` | string | Device ID |
-|   ↳ `name` | string | Device name |
-|   ↳ `hostname` | string | Device hostname |
-|   ↳ `user` | string | Associated user |
-|   ↳ `os` | string | Operating system |
-|   ↳ `clientVersion` | string | Tailscale client version |
-|   ↳ `addresses` | array | Tailscale IP addresses |
-|   ↳ `tags` | array | Device tags |
-|   ↳ `authorized` | boolean | Whether the device is authorized |
-|   ↳ `blocksIncomingConnections` | boolean | Whether the device blocks incoming connections |
-|   ↳ `lastSeen` | string | Last seen timestamp |
-|   ↳ `created` | string | Creation timestamp |
-| `count` | number | Total number of devices |
-
-### `tailscale_get_device`
-
-Get details of a specific device by ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `deviceId` | string | Yes | Device ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Device ID |
-| `name` | string | Device name |
-| `hostname` | string | Device hostname |
-| `user` | string | Associated user |
-| `os` | string | Operating system |
-| `clientVersion` | string | Tailscale client version |
-| `addresses` | array | Tailscale IP addresses |
-| `tags` | array | Device tags |
-| `authorized` | boolean | Whether the device is authorized |
-| `blocksIncomingConnections` | boolean | Whether the device blocks incoming connections |
-| `lastSeen` | string | Last seen timestamp |
-| `created` | string | Creation timestamp |
-| `isExternal` | boolean | Whether the device is external |
-| `updateAvailable` | boolean | Whether an update is available |
-| `machineKey` | string | Machine key |
-| `nodeKey` | string | Node key |
-
-### `tailscale_delete_device`
-
-Remove a device from the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `deviceId` | string | Yes | Device ID to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the device was successfully deleted |
-| `deviceId` | string | ID of the deleted device |
-
-### `tailscale_authorize_device`
-
-Authorize or deauthorize a device on the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `deviceId` | string | Yes | Device ID to authorize |
-| `authorized` | boolean | Yes | Whether to authorize \(true\) or deauthorize \(false\) the device |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the operation succeeded |
-| `deviceId` | string | Device ID |
-| `authorized` | boolean | Authorization status after the operation |
-
-### `tailscale_set_device_tags`
-
-Set tags on a device in the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `deviceId` | string | Yes | Device ID |
-| `tags` | string | Yes | Comma-separated list of tags \(e.g., "tag:server,tag:production"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the tags were successfully set |
-| `deviceId` | string | Device ID |
-| `tags` | array | Tags set on the device |
-
-### `tailscale_get_device_routes`
-
-Get the subnet routes for a device
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `deviceId` | string | Yes | Device ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `advertisedRoutes` | array | Subnet routes the device is advertising |
-| `enabledRoutes` | array | Subnet routes that are approved/enabled |
-
-### `tailscale_set_device_routes`
-
-Set the enabled subnet routes for a device
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `deviceId` | string | Yes | Device ID |
-| `routes` | string | Yes | Comma-separated list of subnet routes to enable \(e.g., "10.0.0.0/24,192.168.1.0/24"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `advertisedRoutes` | array | Subnet routes the device is advertising |
-| `enabledRoutes` | array | Subnet routes that are now enabled |
-
-### `tailscale_update_device_key`
-
-Enable or disable key expiry on a device
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `deviceId` | string | Yes | Device ID |
-| `keyExpiryDisabled` | boolean | Yes | Whether to disable key expiry \(true\) or enable it \(false\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the operation succeeded |
-| `deviceId` | string | Device ID |
-| `keyExpiryDisabled` | boolean | Whether key expiry is now disabled |
-
-### `tailscale_list_dns_nameservers`
-
-Get the DNS nameservers configured for the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `dns` | array | List of DNS nameserver addresses |
-| `magicDNS` | boolean | Whether MagicDNS is enabled |
-
-### `tailscale_set_dns_nameservers`
-
-Set the DNS nameservers for the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `dns` | string | Yes | Comma-separated list of DNS nameserver IP addresses \(e.g., "8.8.8.8,8.8.4.4"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `dns` | array | Updated list of DNS nameserver addresses |
-| `magicDNS` | boolean | Whether MagicDNS is enabled |
-
-### `tailscale_get_dns_preferences`
-
-Get the DNS preferences for the tailnet including MagicDNS status
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `magicDNS` | boolean | Whether MagicDNS is enabled |
-
-### `tailscale_set_dns_preferences`
-
-Set DNS preferences for the tailnet (enable/disable MagicDNS)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `magicDNS` | boolean | Yes | Whether to enable \(true\) or disable \(false\) MagicDNS |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `magicDNS` | boolean | Updated MagicDNS status |
-
-### `tailscale_get_dns_searchpaths`
-
-Get the DNS search paths configured for the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `searchPaths` | array | List of DNS search path domains |
-
-### `tailscale_set_dns_searchpaths`
-
-Set the DNS search paths for the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `searchPaths` | string | Yes | Comma-separated list of DNS search path domains \(e.g., "corp.example.com,internal.example.com"\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `searchPaths` | array | Updated list of DNS search path domains |
-
-### `tailscale_list_users`
-
-List all users in the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `users` | array | List of users in the tailnet |
-|   ↳ `id` | string | User ID |
-|   ↳ `displayName` | string | Display name |
-|   ↳ `loginName` | string | Login name / email |
-|   ↳ `profilePicURL` | string | Profile picture URL |
-|   ↳ `role` | string | User role \(owner, admin, member, etc.\) |
-|   ↳ `status` | string | User status \(active, suspended, etc.\) |
-|   ↳ `type` | string | User type \(member, shared, tagged\) |
-|   ↳ `created` | string | Creation timestamp |
-|   ↳ `lastSeen` | string | Last seen timestamp |
-|   ↳ `deviceCount` | number | Number of devices owned by user |
-| `count` | number | Total number of users |
-
-### `tailscale_create_auth_key`
-
-Create a new auth key for the tailnet to pre-authorize devices
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `reusable` | boolean | No | Whether the key can be used more than once |
-| `ephemeral` | boolean | No | Whether devices authenticated with this key are ephemeral |
-| `preauthorized` | boolean | No | Whether devices are pre-authorized \(skip manual approval\) |
-| `tags` | string | No | Comma-separated list of tags for devices using this key \(e.g., "tag:server,tag:prod"\) |
-| `description` | string | No | Description for the auth key |
-| `expirySeconds` | number | No | Key expiry time in seconds \(default: 90 days\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Auth key ID |
-| `key` | string | The auth key value \(only shown once at creation\) |
-| `description` | string | Key description |
-| `created` | string | Creation timestamp |
-| `expires` | string | Expiration timestamp |
-| `revoked` | string | Revocation timestamp \(empty if not revoked\) |
-| `capabilities` | object | Key capabilities |
-|   ↳ `reusable` | boolean | Whether the key is reusable |
-|   ↳ `ephemeral` | boolean | Whether devices are ephemeral |
-|   ↳ `preauthorized` | boolean | Whether devices are pre-authorized |
-|   ↳ `tags` | array | Tags applied to devices using this key |
-
-### `tailscale_list_auth_keys`
-
-List all auth keys in the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `keys` | array | List of auth keys |
-|   ↳ `id` | string | Auth key ID |
-|   ↳ `description` | string | Key description |
-|   ↳ `created` | string | Creation timestamp |
-|   ↳ `expires` | string | Expiration timestamp |
-|   ↳ `revoked` | string | Revocation timestamp |
-|   ↳ `capabilities` | object | Key capabilities |
-|     ↳ `reusable` | boolean | Whether the key is reusable |
-|     ↳ `ephemeral` | boolean | Whether devices are ephemeral |
-|     ↳ `preauthorized` | boolean | Whether devices are pre-authorized |
-|     ↳ `tags` | array | Tags applied to devices |
-| `count` | number | Total number of auth keys |
-
-### `tailscale_get_auth_key`
-
-Get details of a specific auth key
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `keyId` | string | Yes | Auth key ID |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `id` | string | Auth key ID |
-| `description` | string | Key description |
-| `created` | string | Creation timestamp |
-| `expires` | string | Expiration timestamp |
-| `revoked` | string | Revocation timestamp |
-| `capabilities` | object | Key capabilities |
-|   ↳ `reusable` | boolean | Whether the key is reusable |
-|   ↳ `ephemeral` | boolean | Whether devices are ephemeral |
-|   ↳ `preauthorized` | boolean | Whether devices are pre-authorized |
-|   ↳ `tags` | array | Tags applied to devices using this key |
-
-### `tailscale_delete_auth_key`
-
-Revoke and delete an auth key
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-| `keyId` | string | Yes | Auth key ID to delete |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the auth key was successfully deleted |
-| `keyId` | string | ID of the deleted auth key |
-
-### `tailscale_get_acl`
-
-Get the current ACL policy for the tailnet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Tailscale API key |
-| `tailnet` | string | Yes | Tailnet name \(e.g., example.com\) or "-" for default |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `acl` | string | ACL policy as JSON string |
-| `etag` | string | ETag for the current ACL version \(use with If-Match header for updates\) |
-
-

apps/docs/content/docs/en/tools/workday.mdx

@@ -1,262 +0,0 @@
----
-title: Workday
-description: Manage workers, hiring, onboarding, and HR operations in Workday
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="workday"
-  color="#F5F0EB"
-/>
-
-## Usage Instructions
-
-Integrate Workday HRIS into your workflow. Create pre-hires, hire employees, manage worker profiles, assign onboarding plans, handle job changes, retrieve compensation data, and process terminations.
-
-
-
-## Tools
-
-### `workday_get_worker`
-
-Retrieve a specific worker profile including personal, employment, and organization data.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `workerId` | string | Yes | Worker ID to retrieve \(e.g., 3aa5550b7fe348b98d7b5741afc65534\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `worker` | json | Worker profile with personal, employment, and organization data |
-
-### `workday_list_workers`
-
-List or search workers with optional filtering and pagination.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `limit` | number | No | Maximum number of workers to return \(default: 20\) |
-| `offset` | number | No | Number of records to skip for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `workers` | array | Array of worker profiles |
-| `total` | number | Total number of matching workers |
-
-### `workday_create_prehire`
-
-Create a new pre-hire (applicant) record in Workday. This is typically the first step before hiring an employee.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `legalName` | string | Yes | Full legal name of the pre-hire \(e.g., "Jane Doe"\) |
-| `email` | string | No | Email address of the pre-hire |
-| `phoneNumber` | string | No | Phone number of the pre-hire |
-| `address` | string | No | Address of the pre-hire |
-| `countryCode` | string | No | ISO 3166-1 Alpha-2 country code \(defaults to US\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `preHireId` | string | ID of the created pre-hire record |
-| `descriptor` | string | Display name of the pre-hire |
-
-### `workday_hire_employee`
-
-Hire a pre-hire into an employee position. Converts an applicant into an active employee record with position, start date, and manager assignment.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `preHireId` | string | Yes | Pre-hire \(applicant\) ID to convert into an employee |
-| `positionId` | string | Yes | Position ID to assign the new hire to |
-| `hireDate` | string | Yes | Hire date in ISO 8601 format \(e.g., 2025-06-01\) |
-| `employeeType` | string | No | Employee type \(e.g., Regular, Temporary, Contractor\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `workerId` | string | Worker ID of the newly hired employee |
-| `employeeId` | string | Employee ID assigned to the new hire |
-| `eventId` | string | Event ID of the hire business process |
-| `hireDate` | string | Effective hire date |
-
-### `workday_update_worker`
-
-Update fields on an existing worker record in Workday.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `workerId` | string | Yes | Worker ID to update |
-| `fields` | json | Yes | Fields to update as JSON \(e.g., \{"businessTitle": "Senior Engineer", "primaryWorkEmail": "new@company.com"\}\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `eventId` | string | Event ID of the change personal information business process |
-| `workerId` | string | Worker ID that was updated |
-
-### `workday_assign_onboarding`
-
-Create or update an onboarding plan assignment for a worker. Sets up onboarding stages and manages the assignment lifecycle.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `workerId` | string | Yes | Worker ID to assign the onboarding plan to |
-| `onboardingPlanId` | string | Yes | Onboarding plan ID to assign |
-| `actionEventId` | string | Yes | Action event ID that enables the onboarding plan \(e.g., the hiring event ID\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `assignmentId` | string | Onboarding plan assignment ID |
-| `workerId` | string | Worker ID the plan was assigned to |
-| `planId` | string | Onboarding plan ID that was assigned |
-
-### `workday_get_organizations`
-
-Retrieve organizations, departments, and cost centers from Workday.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `type` | string | No | Organization type filter \(e.g., Supervisory, Cost_Center, Company, Region\) |
-| `limit` | number | No | Maximum number of organizations to return \(default: 20\) |
-| `offset` | number | No | Number of records to skip for pagination |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `organizations` | array | Array of organization records |
-| `total` | number | Total number of matching organizations |
-
-### `workday_change_job`
-
-Perform a job change for a worker including transfers, promotions, demotions, and lateral moves.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `workerId` | string | Yes | Worker ID for the job change |
-| `effectiveDate` | string | Yes | Effective date for the job change in ISO 8601 format \(e.g., 2025-06-01\) |
-| `newPositionId` | string | No | New position ID \(for transfers\) |
-| `newJobProfileId` | string | No | New job profile ID \(for role changes\) |
-| `newLocationId` | string | No | New work location ID \(for relocations\) |
-| `newSupervisoryOrgId` | string | No | Target supervisory organization ID \(for org transfers\) |
-| `reason` | string | Yes | Reason for the job change \(e.g., Promotion, Transfer, Reorganization\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `eventId` | string | Job change event ID |
-| `workerId` | string | Worker ID the job change was applied to |
-| `effectiveDate` | string | Effective date of the job change |
-
-### `workday_get_compensation`
-
-Retrieve compensation plan details for a specific worker.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `workerId` | string | Yes | Worker ID to retrieve compensation data for |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `compensationPlans` | array | Array of compensation plan details |
-|   ↳ `id` | string | Compensation plan ID |
-|   ↳ `planName` | string | Name of the compensation plan |
-|   ↳ `amount` | number | Compensation amount |
-|   ↳ `currency` | string | Currency code |
-|   ↳ `frequency` | string | Pay frequency |
-
-### `workday_terminate_worker`
-
-Initiate a worker termination in Workday. Triggers the Terminate Employee business process.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `tenantUrl` | string | Yes | Workday instance URL \(e.g., https://wd5-impl-services1.workday.com\) |
-| `tenant` | string | Yes | Workday tenant name |
-| `username` | string | Yes | Integration System User username |
-| `password` | string | Yes | Integration System User password |
-| `workerId` | string | Yes | Worker ID to terminate |
-| `terminationDate` | string | Yes | Termination date in ISO 8601 format \(e.g., 2025-06-01\) |
-| `reason` | string | Yes | Termination reason \(e.g., Resignation, End_of_Contract, Retirement\) |
-| `notificationDate` | string | No | Date the termination was communicated in ISO 8601 format |
-| `lastDayOfWork` | string | No | Last day of work in ISO 8601 format \(defaults to termination date\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `eventId` | string | Termination event ID |
-| `workerId` | string | Worker ID that was terminated |
-| `terminationDate` | string | Effective termination date |
-
-

apps/docs/content/docs/es/blocks/guardrails.mdx

@@ -131,7 +131,7 @@ Detecta información de identificación personal utilizando Microsoft Presidio.
 **Casos de uso:**
 - Bloquear contenido que contiene información personal sensible
 - Enmascarar PII antes de registrar o almacenar datos
-- Cumplimiento de GDPR y otras regulaciones de privacidad
+- Cumplimiento de GDPR, HIPAA y otras regulaciones de privacidad
 - Sanear entradas de usuario antes del procesamiento
 
 ## Configuración

apps/docs/content/docs/fr/blocks/guardrails.mdx

@@ -131,7 +131,7 @@ Détecte les informations personnelles identifiables à l'aide de Microsoft Pres
 **Cas d'utilisation :**
 - Bloquer le contenu contenant des informations personnelles sensibles
 - Masquer les PII avant de journaliser ou stocker des données
-- Conformité avec le RGPD et autres réglementations sur la confidentialité
+- Conformité avec le RGPD, HIPAA et autres réglementations sur la confidentialité
 - Assainir les entrées utilisateur avant traitement
 
 ## Configuration

apps/docs/content/docs/ja/blocks/guardrails.mdx

@@ -131,7 +131,7 @@ Microsoft Presidioを使用して個人を特定できる情報を検出しま
 **ユースケース:**
 - 機密性の高い個人情報を含むコンテンツをブロック
 - データのログ記録や保存前にPIIをマスク
-- GDPR、その他のプライバシー規制への準拠
+- GDPR、HIPAA、その他のプライバシー規制への準拠
 - 処理前のユーザー入力のサニタイズ
 
 ## 設定

apps/docs/content/docs/zh/blocks/guardrails.mdx

@@ -131,7 +131,7 @@ Guardrails 模块通过针对多种验证类型检查内容，验证并保护您
 **使用场景：**
 - 阻止包含敏感个人信息的内容
 - 在记录或存储数据之前屏蔽 PII
-- 符合 GDPR 和其他隐私法规
+- 符合 GDPR、HIPAA 和其他隐私法规
 - 在处理之前清理用户输入
 
 ## 配置

apps/docs/package.json

@@ -29,8 +29,8 @@
     "next": "16.1.6",
     "next-themes": "^0.4.6",
     "postgres": "^3.4.5",
-    "react": "19.2.4",
-    "react-dom": "19.2.4",
+    "react": "19.2.1",
+    "react-dom": "19.2.1",
     "shiki": "4.0.0",
     "tailwind-merge": "^3.0.2"
   },

apps/docs/public/favicon/site.webmanifest

@@ -1,42 +1,21 @@
 {
-  "name": "Sim Documentation — Build AI Agents & Run Your Agentic Workforce",
-  "short_name": "Sim Docs",
-  "description": "Documentation for Sim — the open-source platform to build AI agents and run your agentic workforce. Connect 1,000+ integrations and LLMs to deploy and orchestrate agentic workflows.",
-  "start_url": "/",
-  "scope": "/",
+  "name": "MyWebSite",
+  "short_name": "MySite",
   "icons": [
     {
-      "src": "/favicon/web-app-manifest-192x192.png",
+      "src": "/web-app-manifest-192x192.png",
       "sizes": "192x192",
       "type": "image/png",
       "purpose": "maskable"
     },
     {
-      "src": "/favicon/web-app-manifest-512x512.png",
+      "src": "/web-app-manifest-512x512.png",
       "sizes": "512x512",
       "type": "image/png",
       "purpose": "maskable"
-    },
-    {
-      "src": "/favicon/android-chrome-192x192.png",
-      "sizes": "192x192",
-      "type": "image/png"
-    },
-    {
-      "src": "/favicon/android-chrome-512x512.png",
-      "sizes": "512x512",
-      "type": "image/png"
-    },
-    {
-      "src": "/favicon/apple-touch-icon.png",
-      "sizes": "180x180",
-      "type": "image/png"
     }
   ],
-  "theme_color": "#33C482",
+  "theme_color": "#ffffff",
   "background_color": "#ffffff",
-  "display": "standalone",
-  "categories": ["productivity", "developer", "business"],
-  "lang": "en-US",
-  "dir": "ltr"
+  "display": "standalone"
 }

apps/docs/public/icon.svg

@@ -1 +0,0 @@
-<svg height="16" viewBox="0 0 16 16" width="16" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><linearGradient id="a" gradientUnits="userSpaceOnUse" x1="129.434" x2="185.629" y1="129.266" y2="185.33"><stop offset="0"/><stop offset="1" stop-opacity="0"/></linearGradient><rect fill="#0b0b0b" height="16" rx="3" width="16"/><g transform="matrix(.0473 0 0 .0473 2.75 2.75)"><path clip-rule="evenodd" d="m107.822 93.7612c0 3.5869-1.419 7.0308-3.938 9.5668l-.361.364c-2.517 2.544-5.9375 3.966-9.4994 3.966h-80.5781c-7.42094 0-13.4455 6.06-13.4455 13.533v87.141c0 7.474 6.02456 13.534 13.4455 13.534h86.5167c7.4208 0 13.4378-6.06 13.4378-13.534v-81.587c0-3.326 1.31-6.517 3.647-8.871 2.33-2.347 5.499-3.667 8.802-3.667h81.928c7.421 0 13.437-6.059 13.437-13.533v-87.1407c0-7.47374-6.016-13.5333-13.437-13.5333h-86.517c-7.421 0-13.438 6.05956-13.438 13.5333zm26.256-75.2112h60.874c4.337 0 7.844 3.5393 7.844 7.9003v61.3071c0 4.3604-3.507 7.9003-7.844 7.9003h-60.874c-4.33 0-7.845-3.5399-7.845-7.9003v-61.3071c0-4.361 3.515-7.9003 7.845-7.9003z" fill="#33c482" fill-rule="evenodd"/><path d="m207.878 129.57h-64.324c-7.798 0-14.12 6.367-14.12 14.221v63.993c0 7.854 6.322 14.221 14.12 14.221h64.324c7.799 0 14.121-6.367 14.121-14.221v-63.993c0-7.854-6.322-14.221-14.121-14.221z" fill="#33c482"/><path d="m207.878 129.266h-64.324c-7.798 0-14.12 6.366-14.12 14.221v63.992c0 7.854 6.322 14.22 14.12 14.22h64.324c7.799 0 14.121-6.366 14.121-14.22v-63.992c0-7.855-6.322-14.221-14.121-14.221z" fill="url(#a)" fill-opacity=".2"/></g></svg>