v0.3.43: added additional parsers, mysql block improvements, billing fixes, permission fixes

* fix md, pptx, html

* consolidate consts

.devcontainer/.bashrc

@@ -1,4 +1,4 @@
-# Sim Studio Development Environment Bashrc
+# Sim Development Environment Bashrc
 # This gets sourced by post-create.sh
 
 # Enhanced prompt with git branch info
@@ -17,7 +17,7 @@ alias ...="cd ../.."
 alias pgc="PGPASSWORD=postgres psql -h db -U postgres -d simstudio"
 alias check-db="PGPASSWORD=postgres psql -h db -U postgres -c '\l'"
 
-# Sim Studio specific aliases
+# Sim specific aliases
 alias logs="cd /workspace/apps/sim && tail -f logs/*.log 2>/dev/null || echo 'No log files found'"
 alias sim-start="cd /workspace && bun run dev"
 alias sim-migrate="cd /workspace/apps/sim && bunx drizzle-kit push"
@@ -45,7 +45,7 @@ if [ -z "$SIM_WELCOME_SHOWN" ]; then
   
   echo ""
   echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo "🚀 Welcome to Sim Studio development environment!"
+  echo "🚀 Welcome to Sim development environment!"
   echo ""
   echo "Available commands:"
   echo "  sim-start    - Start all apps in development mode"

.devcontainer/README.md

@@ -1,4 +1,4 @@
-# Sim Studio Development Container
+# Sim Development Container
 
 This directory contains configuration files for Visual Studio Code Dev Containers / GitHub Codespaces. Dev containers provide a consistent, isolated development environment for this project.
 

.devcontainer/devcontainer.json

@@ -1,5 +1,5 @@
 {
-  "name": "Sim Studio Dev Environment",
+  "name": "Sim Dev Environment",
   "dockerComposeFile": "docker-compose.yml",
   "service": "app",
   "workspaceFolder": "/workspace",

.devcontainer/docker-compose.yml

@@ -77,7 +77,7 @@ services:
       - POSTGRES_PASSWORD=postgres
       - POSTGRES_DB=simstudio
     ports:
-      - "5432:5432"
+      - "${POSTGRES_PORT:-5432}:5432"
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U postgres"]
       interval: 5s

.devcontainer/post-create.sh

@@ -3,7 +3,7 @@
 # Exit on error, but with some error handling
 set -e
 
-echo "🔧 Setting up Sim Studio development environment..."
+echo "🔧 Setting up Sim development environment..."
 
 # Change to the workspace root directory
 cd /workspace
@@ -85,7 +85,7 @@ echo "Waiting for database to be ready..."
 # Add additional helpful aliases to .bashrc
 cat << EOF >> ~/.bashrc
 
-# Additional Sim Studio Development Aliases
+# Additional Sim Development Aliases
 alias migrate="cd /workspace/apps/sim && DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio bunx drizzle-kit push"
 alias generate="cd /workspace/apps/sim && bunx drizzle-kit generate"
 alias dev="cd /workspace && bun run dev"
@@ -104,7 +104,7 @@ unset SIM_WELCOME_SHOWN
 
 echo ""
 echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "✅ Sim Studio development environment setup complete!"
+echo "✅ Sim development environment setup complete!"
 echo ""
 echo "Your environment is now ready. A new terminal session will show"
 echo "available commands. You can start the development server with:"

.github/CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
-# Code of Conduct - Sim Studio
+# Code of Conduct - Sim
 
 ## Our Pledge
 
@@ -55,7 +55,7 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behaviour may be
-reported to the community leaders responsible for enforcement at <waleed@simstudio.ai>.
+reported to the community leaders responsible for enforcement at <waleed@sim.ai>.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

.github/CONTRIBUTING.md

@@ -1,9 +1,9 @@
-# Contributing to Sim Studio
+# Contributing to Sim
 
-Thank you for your interest in contributing to Sim Studio! Our goal is to provide developers with a powerful, user-friendly platform for building, testing, and optimizing agentic workflows. We welcome contributions in all forms—from bug fixes and design improvements to brand-new features.
+Thank you for your interest in contributing to Sim! Our goal is to provide developers with a powerful, user-friendly platform for building, testing, and optimizing agentic workflows. We welcome contributions in all forms—from bug fixes and design improvements to brand-new features.
 
 > **Project Overview:**  
-> Sim Studio is a monorepo using Turborepo, containing the main application (`apps/sim/`), documentation (`apps/docs/`), and shared packages (`packages/`). The main application is built with Next.js (app router), ReactFlow, Zustand, Shadcn, and Tailwind CSS. Please ensure your contributions follow our best practices for clarity, maintainability, and consistency.
+> Sim is a monorepo using Turborepo, containing the main application (`apps/sim/`), documentation (`apps/docs/`), and shared packages (`packages/`). The main application is built with Next.js (app router), ReactFlow, Zustand, Shadcn, and Tailwind CSS. Please ensure your contributions follow our best practices for clarity, maintainability, and consistency.
 
 ---
 
@@ -15,8 +15,6 @@ Thank you for your interest in contributing to Sim Studio! Our goal is to provid
 - [Commit Message Guidelines](#commit-message-guidelines)
 - [Local Development Setup](#local-development-setup)
 - [Adding New Blocks and Tools](#adding-new-blocks-and-tools)
-- [Local Storage Mode](#local-storage-mode)
-- [Standalone Build](#standalone-build)
 - [License](#license)
 - [Contributor License Agreement (CLA)](#contributor-license-agreement-cla)
 
@@ -57,7 +55,7 @@ We strive to keep our workflow as simple as possible. To contribute:
    ```
 
 7. **Create a Pull Request**  
-   Open a pull request against the `main` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
+   Open a pull request against the `staging` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
 
 ---
 
@@ -85,7 +83,7 @@ If you discover a bug or have a feature request, please open an issue in our Git
 Before creating a pull request:
 
 - **Ensure Your Branch Is Up-to-Date:**  
-  Rebase your branch onto the latest `main` branch to prevent merge conflicts.
+  Rebase your branch onto the latest `staging` branch to prevent merge conflicts.
 - **Follow the Guidelines:**  
   Make sure your changes are well-tested, follow our coding standards, and include relevant documentation if necessary.
 
@@ -132,7 +130,7 @@ To set up your local development environment:
 
 ### Option 1: Using NPM Package (Simplest)
 
-The easiest way to run Sim Studio locally is using our NPM package:
+The easiest way to run Sim locally is using our NPM package:
 
 ```bash
 npx simstudio
@@ -142,7 +140,7 @@ After running this command, open [http://localhost:3000/](http://localhost:3000/
 
 #### Options
 
-- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
+- `-p, --port <port>`: Specify the port to run Sim on (default: 3000)
 - `--no-pull`: Skip pulling the latest Docker images
 
 #### Requirements
@@ -156,7 +154,7 @@ After running this command, open [http://localhost:3000/](http://localhost:3000/
 git clone https://github.com/<your-username>/sim.git
 cd sim
 
-# Start Sim Studio
+# Start Sim
 docker compose -f docker-compose.prod.yml up -d
 ```
 
@@ -164,15 +162,19 @@ Access the application at [http://localhost:3000/](http://localhost:3000/)
 
 #### Using Local Models
 
-To use local models with Sim Studio:
+To use local models with Sim:
 
-1. Pull models using our helper script:
+1. Install Ollama and pull models:
 
 ```bash
-./apps/sim/scripts/ollama_docker.sh pull <model_name>
+# Install Ollama (if not already installed)
+curl -fsSL https://ollama.ai/install.sh | sh
+
+# Pull a model (e.g., gemma3:4b)
+ollama pull gemma3:4b
 ```
 
-2. Start Sim Studio with local model support:
+2. Start Sim with local model support:
 
 ```bash
 # With NVIDIA GPU support
@@ -209,13 +211,14 @@ Dev Containers provide a consistent and easy-to-use development environment:
 
 3. **Start Developing:**
 
-   - Run `bun run dev` in the terminal or use the `sim-start` alias
+   - 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
    - All dependencies and configurations are automatically set up
    - Your changes will be automatically hot-reloaded
 
 4. **GitHub Codespaces:**
    - This setup also works with GitHub Codespaces if you prefer development in the browser
-   - Just click "Code" → "Codespaces" → "Create codespace on main"
+   - Just click "Code" → "Codespaces" → "Create codespace on staging"
 
 ### Option 4: Manual Setup
 
@@ -246,9 +249,11 @@ If you prefer not to use Docker or Dev Containers:
 4. **Run the Development Server:**
 
    ```bash
-   bun run dev
+   bun run dev:full
    ```
 
+   This command starts both the main application and the realtime socket server required for full functionality.
+
 5. **Make Your Changes and Test Locally.**
 
 ### Email Template Development
@@ -275,7 +280,7 @@ When working on email templates, you can preview them using a local email previe
 
 ## Adding New Blocks and Tools
 
-Sim Studio is built in a modular fashion where blocks and tools extend the platform's functionality. To maintain consistency and quality, please follow the guidelines below when adding a new block or tool.
+Sim is built in a modular fashion where blocks and tools extend the platform's functionality. To maintain consistency and quality, please follow the guidelines below when adding a new block or tool.
 
 ### Where to Add Your Code
 
@@ -300,8 +305,8 @@ In addition, you will need to update the registries:
 
    ```typescript:/apps/sim/blocks/blocks/pinecone.ts
    import { PineconeIcon } from '@/components/icons'
-   import { PineconeResponse } from '@/tools/pinecone/types'
-   import { BlockConfig } from '../types'
+   import type { BlockConfig } from '@/blocks/types'
+   import type { PineconeResponse } from '@/tools/pinecone/types'
 
    export const PineconeBlock: BlockConfig<PineconeResponse> = {
      type: 'pinecone',
@@ -312,13 +317,58 @@ In addition, you will need to update the registries:
      bgColor: '#123456',
      icon: PineconeIcon,
 
-     // If this block requires OAuth authentication
-     provider: 'pinecone',
-
-     // Define subBlocks for the UI configuration
      subBlocks: [
-       // Block configuration options
+       {
+         id: 'operation',
+         title: 'Operation',
+         type: 'dropdown',
+         layout: 'full',
+         required: true,
+         options: [
+           { label: 'Generate Embeddings', id: 'generate' },
+           { label: 'Search Text', id: 'search_text' },
+         ],
+         value: () => 'generate',
+       },
+       {
+         id: 'apiKey',
+         title: 'API Key',
+         type: 'short-input',
+         layout: 'full',
+         placeholder: 'Your Pinecone API key',
+         password: true,
+         required: true,
+       },
      ],
+
+     tools: {
+       access: ['pinecone_generate_embeddings', 'pinecone_search_text'],
+       config: {
+         tool: (params: Record<string, any>) => {
+           switch (params.operation) {
+             case 'generate':
+               return 'pinecone_generate_embeddings'
+             case 'search_text':
+               return 'pinecone_search_text'
+             default:
+               throw new Error('Invalid operation selected')
+           }
+         },
+       },
+     },
+
+     inputs: {
+       operation: { type: 'string', description: 'Operation to perform' },
+       apiKey: { type: 'string', description: 'Pinecone API key' },
+       searchQuery: { type: 'string', description: 'Search query text' },
+       topK: { type: 'string', description: 'Number of results to return' },
+     },
+
+     outputs: {
+       matches: { type: 'any', description: 'Search results or generated embeddings' },
+       data: { type: 'any', description: 'Response data from Pinecone' },
+       usage: { type: 'any', description: 'API usage statistics' },
+     },
    }
    ```
 
@@ -366,8 +416,8 @@ In addition, you will need to update the registries:
    Your tool should export a constant with a naming convention of `{toolName}Tool`. The tool ID should follow the format `{provider}_{tool_name}`. For example:
 
    ```typescript:/apps/sim/tools/pinecone/fetch.ts
-   import { ToolConfig, ToolResponse } from '../types'
-   import { PineconeParams, PineconeResponse } from './types'
+   import { ToolConfig, ToolResponse } from '@/tools/types'
+   import { PineconeParams, PineconeResponse } from '@/tools/pinecone/types'
 
    export const fetchTool: ToolConfig<PineconeParams, PineconeResponse> = {
      id: 'pinecone_fetch', // Follow the {provider}_{tool_name} format
@@ -379,7 +429,18 @@ In addition, you will need to update the registries:
      provider: 'pinecone', // ID of the OAuth provider
 
      params: {
-       // Tool parameters
+       parameterName: {
+         type: 'string',
+         required: true,
+         visibility: 'user-or-llm', // Controls parameter visibility
+         description: 'Description of the parameter',
+       },
+       optionalParam: {
+         type: 'string',
+         required: false,
+         visibility: 'user-only',
+         description: 'Optional parameter only user can set',
+       },
      },
      request: {
        // Request configuration
@@ -387,9 +448,6 @@ In addition, you will need to update the registries:
      transformResponse: async (response: Response) => {
        // Transform response
      },
-     transformError: (error) => {
-       // Handle errors
-     },
    }
    ```
 
@@ -397,7 +455,7 @@ In addition, you will need to update the registries:
    Update the tools registry in `/apps/sim/tools/index.ts` to include your new tool:
 
    ```typescript:/apps/sim/tools/index.ts
-   import { fetchTool, generateEmbeddingsTool, searchTextTool } from './pinecone'
+   import { fetchTool, generateEmbeddingsTool, searchTextTool } from '/@tools/pinecone'
    // ... other imports
 
    export const tools: Record<string, ToolConfig> = {
@@ -429,11 +487,57 @@ Maintaining consistent naming across the codebase is critical for auto-generatio
 - **Tool Exports:** Should be named `{toolName}Tool` (e.g., `fetchTool`)
 - **Tool IDs:** Should follow the format `{provider}_{tool_name}` (e.g., `pinecone_fetch`)
 
+### Parameter Visibility System
+
+Sim implements a sophisticated parameter visibility system that controls how parameters are exposed to users and LLMs in agent workflows. Each parameter can have one of four visibility levels:
+
+| Visibility  | User Sees | LLM Sees | How It Gets Set                |
+|-------------|-----------|----------|--------------------------------|
+| `user-only` | ✅ Yes     | ❌ No     | User provides in UI            |
+| `user-or-llm` | ✅ Yes     | ✅ Yes    | User provides OR LLM generates |
+| `llm-only`  | ❌ No      | ✅ Yes    | LLM generates only             |
+| `hidden`    | ❌ No      | ❌ No     | Application injects at runtime |
+
+#### Visibility Guidelines
+
+- **`user-or-llm`**: Use for core parameters that can be provided by users or intelligently filled by the LLM (e.g., search queries, email subjects)
+- **`user-only`**: Use for configuration parameters, API keys, and settings that only users should control (e.g., number of results, authentication credentials)
+- **`llm-only`**: Use for computed values that the LLM should handle internally (e.g., dynamic calculations, contextual data)
+- **`hidden`**: Use for system-level parameters injected at runtime (e.g., OAuth tokens, internal identifiers)
+
+#### Example Implementation
+
+```typescript
+params: {
+  query: {
+    type: 'string',
+    required: true,
+    visibility: 'user-or-llm', // User can provide or LLM can generate
+    description: 'Search query to execute',
+  },
+  apiKey: {
+    type: 'string',
+    required: true,
+    visibility: 'user-only', // Only user provides this
+    description: 'API key for authentication',
+  },
+  internalId: {
+    type: 'string',
+    required: false,
+    visibility: 'hidden', // System provides this at runtime
+    description: 'Internal tracking identifier',
+  },
+}
+```
+
+This visibility system ensures clean user interfaces while maintaining full flexibility for LLM-driven workflows.
+
 ### Guidelines & Best Practices
 
-- **Code Style:** Follow the project's ESLint and Prettier configurations. Use meaningful variable names and small, focused functions.
+- **Code Style:** Follow the project's Biome configurations. Use meaningful variable names and small, focused functions.
 - **Documentation:** Clearly document the purpose, inputs, outputs, and any special behavior for your block/tool.
 - **Error Handling:** Implement robust error handling and provide user-friendly error messages.
+- **Parameter Visibility:** Always specify the appropriate visibility level for each parameter to ensure proper UI behavior and LLM integration.
 - **Testing:** Add unit or integration tests to verify your changes when possible.
 - **Commit Changes:** Update all related components and registries, and describe your changes in your pull request.
 
@@ -451,7 +555,7 @@ This project is licensed under the Apache License 2.0. By contributing, you agre
 
 By contributing to this repository, you agree that your contributions are provided under the terms of the Apache License Version 2.0, as included in the LICENSE file of this repository.
 
-In addition, by submitting your contributions, you grant Sim Studio, Inc. ("The Licensor") a perpetual, irrevocable, worldwide, royalty-free, sublicensable right and license to:
+In addition, by submitting your contributions, you grant Sim, Inc. ("The Licensor") a perpetual, irrevocable, worldwide, royalty-free, sublicensable right and license to:
 
 - Use, copy, modify, distribute, publicly display, publicly perform, and prepare derivative works of your contributions.
 - Incorporate your contributions into other works or products.
@@ -463,4 +567,4 @@ If you do not agree with these terms, you must not contribute your work to this
 
 ---
 
-Thank you for taking the time to contribute to Sim Studio. We truly appreciate your efforts and look forward to collaborating with you!
+Thank you for taking the time to contribute to Sim. We truly appreciate your efforts and look forward to collaborating with you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,42 +1,25 @@
-## Description
+## Summary
+Brief description of what this PR does and why.
 
-Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
+Fixes #(issue)
 
-Fixes # (issue)
+## Type of Change
+- [ ] Bug fix
+- [ ] New feature  
+- [ ] Breaking change
+- [ ] Documentation
+- [ ] Other: ___________
 
-## Type of change
+## Testing
+How has this been tested? What should reviewers focus on?
 
-Please delete options that are not relevant.
-
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] Documentation update
-- [ ] Security enhancement
-- [ ] Performance improvement
-- [ ] Code refactoring (no functional changes)
-
-## How Has This Been Tested?
-
-Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
-
-## Checklist:
-
-- [ ] My code follows the style guidelines of this project
-- [ ] I have performed a self-review of my own code
-- [ ] I have commented my code, particularly in hard-to-understand areas
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] All tests pass locally and in CI (`bun run test`)
-- [ ] My changes generate no new warnings
-- [ ] Any dependent changes have been merged and published in downstream modules
-- [ ] I have updated version numbers as needed (if needed)
+## Checklist
+- [ ] Code follows project style guidelines
+- [ ] Self-reviewed my changes
+- [ ] Tests added/updated and passing
+- [ ] No new warnings introduced
 - [ ] I confirm that I have read and agree to the terms outlined in the [Contributor License Agreement (CLA)](./CONTRIBUTING.md#contributor-license-agreement-cla)
 
-## Security Considerations:
-
-- [ ] My changes do not introduce any new security vulnerabilities
-- [ ] I have considered the security implications of my changes
-
-## Additional Information:
-
-Any additional information, configuration or data that might be necessary to reproduce the issue or use the feature.
+## Screenshots/Videos
+<!-- If applicable, add screenshots or videos to help explain your changes -->
+<!-- For UI changes, before/after screenshots are especially helpful -->

.github/SECURITY.md

@@ -8,11 +8,11 @@
 
 ## Reporting a Vulnerability
 
-We take the security of Sim Studio seriously. If you believe you've found a security vulnerability, please follow these steps:
+We take the security of Sim seriously. If you believe you've found a security vulnerability, please follow these steps:
 
 1. **Do not disclose the vulnerability publicly** or to any third parties.
 
-2. **Email us directly** at security@simstudio.ai with details of the vulnerability.
+2. **Email us directly** at security@sim.ai with details of the vulnerability.
 
 3. **Include the following information** in your report:
 

.github/workflows/build.yml

@@ -7,17 +7,43 @@ on:
 
 jobs:
   build-and-push:
-    runs-on: ubuntu-latest
     strategy:
       fail-fast: false
       matrix:
         include:
+          # AMD64 builds on x86 runners
           - dockerfile: ./docker/app.Dockerfile
             image: ghcr.io/simstudioai/simstudio
+            platform: linux/amd64
+            arch: amd64
+            runner: linux-x64-8-core
           - dockerfile: ./docker/db.Dockerfile
             image: ghcr.io/simstudioai/migrations
+            platform: linux/amd64
+            arch: amd64
+            runner: linux-x64-8-core
           - dockerfile: ./docker/realtime.Dockerfile
             image: ghcr.io/simstudioai/realtime
+            platform: linux/amd64
+            arch: amd64
+            runner: linux-x64-8-core
+          # ARM64 builds on native ARM64 runners
+          - dockerfile: ./docker/app.Dockerfile
+            image: ghcr.io/simstudioai/simstudio
+            platform: linux/arm64
+            arch: arm64
+            runner: linux-arm64-8-core
+          - dockerfile: ./docker/db.Dockerfile
+            image: ghcr.io/simstudioai/migrations
+            platform: linux/arm64
+            arch: arm64
+            runner: linux-arm64-8-core
+          - dockerfile: ./docker/realtime.Dockerfile
+            image: ghcr.io/simstudioai/realtime
+            platform: linux/arm64
+            arch: arm64
+            runner: linux-arm64-8-core
+    runs-on: ${{ matrix.runner }}
     permissions:
       contents: read
       packages: write
@@ -26,9 +52,6 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v4
 
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3
-
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
 
@@ -41,6 +64,55 @@ jobs:
           password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ matrix.image }}
+          tags: |
+            type=raw,value=latest-${{ matrix.arch }},enable=${{ github.ref == 'refs/heads/main' }}
+            type=ref,event=pr,suffix=-${{ matrix.arch }}
+            type=semver,pattern={{version}},suffix=-${{ matrix.arch }}
+            type=semver,pattern={{major}}.{{minor}},suffix=-${{ matrix.arch }}
+            type=semver,pattern={{major}}.{{minor}}.{{patch}},suffix=-${{ matrix.arch }}
+            type=sha,format=long,suffix=-${{ matrix.arch }}
+
+      - name: Build and push Docker image
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          file: ${{ matrix.dockerfile }}
+          platforms: ${{ matrix.platform }}
+          push: ${{ github.event_name != 'pull_request' }}
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha,scope=build-v3
+          cache-to: type=gha,mode=max,scope=build-v3
+          provenance: false
+          sbom: false
+
+  create-manifests:
+    runs-on: ubuntu-latest
+    needs: build-and-push
+    if: github.event_name != 'pull_request'
+    strategy:
+      matrix:
+        include:
+          - image: ghcr.io/simstudioai/simstudio
+          - image: ghcr.io/simstudioai/migrations
+          - image: ghcr.io/simstudioai/realtime
+    permissions:
+      contents: read
+      packages: write
+
+    steps:
+      - name: Log in to the Container registry
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.repository_owner }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract metadata for manifest
         id: meta
         uses: docker/metadata-action@v5
         with:
@@ -53,14 +125,35 @@ jobs:
             type=semver,pattern={{major}}.{{minor}}.{{patch}}
             type=sha,format=long
 
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          file: ${{ matrix.dockerfile }}
-          platforms: linux/amd64,linux/arm64
-          push: ${{ github.event_name != 'pull_request' }}
-          tags: ${{ steps.meta.outputs.tags }}
-          labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
+      - name: Create and push manifest
+        run: |
+          # Extract the tags from metadata (these are the final manifest tags we want)
+          MANIFEST_TAGS="${{ steps.meta.outputs.tags }}"
+
+          # Create manifest for each tag
+          for manifest_tag in $MANIFEST_TAGS; do
+            echo "Creating manifest for $manifest_tag"
+
+            # The architecture-specific images have -amd64 and -arm64 suffixes
+            amd64_image="${manifest_tag}-amd64"
+            arm64_image="${manifest_tag}-arm64"
+
+            echo "Looking for images: $amd64_image and $arm64_image"
+
+            # Check if both architecture images exist
+            if docker manifest inspect "$amd64_image" >/dev/null 2>&1 && docker manifest inspect "$arm64_image" >/dev/null 2>&1; then
+              echo "Both images found, creating manifest..."
+              docker manifest create "$manifest_tag" \
+                "$amd64_image" \
+                "$arm64_image"
+              docker manifest push "$manifest_tag"
+              echo "Successfully created and pushed manifest for $manifest_tag"
+            else
+              echo "Error: One or both architecture images not found"
+              echo "Checking AMD64 image: $amd64_image"
+              docker manifest inspect "$amd64_image" || echo "AMD64 image not found"
+              echo "Checking ARM64 image: $arm64_image"
+              docker manifest inspect "$arm64_image" || echo "ARM64 image not found"
+              exit 1
+            fi
+          done

.github/workflows/ci.yml

@@ -26,19 +26,19 @@ jobs:
           node-version: latest
 
       - name: Install dependencies
-        run: bun install
+        run: bun install --frozen-lockfile
 
       - name: Run tests with coverage
         env:
           NODE_OPTIONS: '--no-warnings'
-          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.ai'
+          NEXT_PUBLIC_APP_URL: 'https://www.sim.ai'
           ENCRYPTION_KEY: '7cf672e460e430c1fba707575c2b0e2ad5a99dddf9b7b7e3b5646e630861db1c' # dummy key for CI only
         run: bun run test
 
       - name: Build application
         env:
           NODE_OPTIONS: '--no-warnings'
-          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.ai'
+          NEXT_PUBLIC_APP_URL: 'https://www.sim.ai'
           STRIPE_SECRET_KEY: 'dummy_key_for_ci_only'
           STRIPE_WEBHOOK_SECRET: 'dummy_secret_for_ci_only'
           RESEND_API_KEY: 'dummy_key_for_ci_only'
@@ -74,4 +74,4 @@ jobs:
         working-directory: ./apps/sim
         env:
           DATABASE_URL: ${{ github.ref == 'refs/heads/main' && secrets.DATABASE_URL || secrets.STAGING_DATABASE_URL }}
-        run: bunx drizzle-kit push
+        run: bunx drizzle-kit migrate

.github/workflows/docs-embeddings.yml

@@ -0,0 +1,38 @@
+name: Process Docs Embeddings
+
+on:
+  push:
+    branches: [main, staging]
+    paths:
+      - 'apps/docs/**'
+  workflow_dispatch: # Allow manual triggering
+
+jobs:
+  process-docs-embeddings:
+    name: Process Documentation Embeddings
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/staging'
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Process docs embeddings
+        working-directory: ./apps/sim
+        env:
+          DATABASE_URL: ${{ github.ref == 'refs/heads/main' && secrets.DATABASE_URL || secrets.STAGING_DATABASE_URL }}
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+        run: bun run scripts/process-docs-embeddings.ts --clear 

.github/workflows/trigger-deploy.yml

@@ -0,0 +1,44 @@
+name: Trigger.dev Deploy
+
+on:
+  push:
+    branches:
+      - main
+      - staging
+
+jobs:
+  deploy:
+    name: Trigger.dev Deploy
+    runs-on: ubuntu-latest
+    concurrency:
+      group: trigger-deploy-${{ github.ref }}
+      cancel-in-progress: false
+    env:
+      TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 'lts/*'
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Deploy to Staging
+        if: github.ref == 'refs/heads/staging'
+        working-directory: ./apps/sim
+        run: npx --yes trigger.dev@4.0.1 deploy -e staging
+
+      - name: Deploy to Production
+        if: github.ref == 'refs/heads/main'
+        working-directory: ./apps/sim
+        run: npx --yes trigger.dev@4.0.1 deploy
+

.gitignore

@@ -65,4 +65,7 @@ start-collector.sh
 .turbo
 
 # VSCode
-.vscode
+.vscode
+
+## Helm Chart Tests
+helm/sim/test

.husky/pre-commit

@@ -1 +1 @@
-bun lint
+bunx lint-staged

NOTICE

@@ -1,4 +1,4 @@
 Sim Studio
 Copyright 2025 Sim Studio
 
-This product includes software developed for the Sim Studio project. 
+This product includes software developed for the Sim project. 

README.md

@@ -1,50 +1,46 @@
 <p align="center">
-  <img src="apps/sim/public/static/sim.png" alt="Sim Studio Logo" width="500"/>
+  <a href="https://sim.ai" target="_blank" rel="noopener noreferrer">
+    <img src="apps/sim/public/logo/reverse/text/large.png" alt="Sim Logo" width="500"/>
+  </a>
+</p>
+
+<p align="center">Build and deploy AI agent workflows in minutes.</p>
+
+<p align="center">
+  <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/simstudioai?style=social" alt="Twitter"></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">
-  <a href="https://www.apache.org/licenses/LICENSE-2.0"><img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg" alt="License: Apache-2.0"></a>
-  <a href="https://discord.gg/Hr4UWYEcTT"><img src="https://img.shields.io/badge/Discord-Join%20Server-7289DA?logo=discord&logoColor=white" alt="Discord"></a>
-  <a href="https://x.com/simstudioai"><img src="https://img.shields.io/twitter/follow/simstudioai?style=social" alt="Twitter"></a>
-  <a href="https://github.com/simstudioai/sim/pulls"><img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs welcome"></a>
-  <a href="https://docs.simstudio.ai"><img src="https://img.shields.io/badge/Docs-visit%20documentation-blue.svg" alt="Documentation"></a>
+  <img src="apps/sim/public/static/demo.gif" alt="Sim Demo" width="800"/>
 </p>
 
-<p align="center">
-  <strong>Sim Studio</strong> is a lightweight, user-friendly platform for building AI agent workflows.
-</p>
+## Quickstart
 
-<p align="center">
-  <img src="apps/sim/public/static/demo.gif" alt="Sim Studio Demo" width="800"/>
-</p>
+### Cloud-hosted: [sim.ai](https://sim.ai)
 
-## Getting Started
+<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>
 
-1. Use our [cloud-hosted version](https://simstudio.ai)
-2. Self-host using one of the methods below
-
-## Self-Hosting Options
-
-### Option 1: NPM Package (Simplest)
-
-The easiest way to run Sim Studio locally is using our [NPM package](https://www.npmjs.com/package/simstudio?activeTab=readme):
+### Self-hosted: NPM Package
 
 ```bash
 npx simstudio
 ```
+→ http://localhost:3000
 
-After running these commands, open [http://localhost:3000/](http://localhost:3000/) in your browser.
+#### Note
+Docker must be installed and running on your machine.
 
 #### Options
 
-- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
-- `--no-pull`: Skip pulling the latest Docker images
+| Flag | Description |
+|------|-------------|
+| `-p, --port <port>` | Port to run Sim on (default `3000`) |
+| `--no-pull` | Skip pulling latest Docker images |
 
-#### Requirements
-
-- Docker must be installed and running on your machine
-
-### Option 2: Docker Compose
+### Self-hosted: Docker Compose
 
 ```bash
 # Clone the repository
@@ -53,42 +49,43 @@ git clone https://github.com/simstudioai/sim.git
 # Navigate to the project directory
 cd sim
 
-# Start Sim Studio
+# Start Sim
 docker compose -f docker-compose.prod.yml up -d
 ```
 
 Access the application at [http://localhost:3000/](http://localhost:3000/)
 
-#### Using Local Models
+#### Using Local Models with Ollama
 
-To use local models with Sim Studio:
-
-1. Pull models using our helper script:
+Run Sim with local AI models using [Ollama](https://ollama.ai) - no external APIs required:
 
 ```bash
-./apps/sim/scripts/ollama_docker.sh pull <model_name>
+# 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
 ```
 
-2. Start Sim Studio with local model support:
-
+Wait for the model to download, then visit [http://localhost:3000](http://localhost:3000). Add more models with:
 ```bash
-# With NVIDIA GPU support
-docker compose --profile local-gpu -f docker-compose.ollama.yml up -d
-
-# Without GPU (CPU only)
-docker compose --profile local-cpu -f docker-compose.ollama.yml up -d
-
-# If hosting on a server, update the environment variables in the docker-compose.prod.yml file to include the server's public IP then start again (OLLAMA_URL to i.e. http://1.1.1.1:11434)
-docker compose -f docker-compose.prod.yml up -d
+docker compose -f docker-compose.ollama.yml exec ollama ollama pull llama3.1:8b
 ```
 
-### Option 3: Dev Containers
+### 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
 
-### Option 4: Manual Setup
+### Self-hosted: Manual Setup
+
+**Requirements:**
+- [Bun](https://bun.sh/) runtime
+- PostgreSQL 12+ with [pgvector extension](https://github.com/pgvector/pgvector) (required for AI embeddings)
+
+**Note:** Sim uses vector embeddings for AI features like knowledge bases and semantic search, which requires the `pgvector` PostgreSQL extension.
 
 1. Clone and install dependencies:
 
@@ -98,39 +95,72 @@ cd sim
 bun install
 ```
 
-2. Set up environment:
+2. Set up PostgreSQL with pgvector:
+
+You need PostgreSQL with the `vector` extension for embedding support. Choose one option:
+
+**Option A: Using Docker (Recommended)**
+```bash
+# Start PostgreSQL with pgvector extension
+docker run --name simstudio-db \
+  -e POSTGRES_PASSWORD=your_password \
+  -e POSTGRES_DB=simstudio \
+  -p 5432:5432 -d \
+  pgvector/pgvector:pg17
+```
+
+**Option B: Manual Installation**
+- Install PostgreSQL 12+ and the pgvector extension
+- See [pgvector installation guide](https://github.com/pgvector/pgvector#installation)
+
+3. Set up environment:
 
 ```bash
 cd apps/sim
 cp .env.example .env  # Configure with required variables (DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL)
 ```
 
-3. Set up the database:
-
+Update your `.env` file with the database URL:
 ```bash
-bunx drizzle-kit push
+DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio"
 ```
 
-4. Start the development servers:
-
-Next.js app:
+4. Set up the database:
 
 ```bash
-bun run dev
+bunx drizzle-kit migrate 
 ```
 
-Start the realtime server:
+5. Start the development servers:
 
-```bash
-bun run dev:sockets
-```
-
-Run both together (recommended):
+**Recommended approach - run both servers together (from project root):**
 
 ```bash
 bun run dev:full
 ```
 
+This starts both the main Next.js application and the realtime socket server required for full functionality.
+
+**Alternative - run servers separately:**
+
+Next.js app (from project root):
+```bash
+bun run dev
+```
+
+Realtime socket server (from `apps/sim` directory in a separate terminal):
+```bash
+cd apps/sim
+bun run dev:sockets
+```
+
+## Copilot API Keys
+
+Copilot is a Sim-managed service. To use Copilot on a self-hosted instance:
+
+- Go to https://sim.ai → Settings → Copilot and generate a Copilot API key
+- Set `COPILOT_API_KEY` in your self-hosted environment to that value
+
 ## Tech Stack
 
 - **Framework**: [Next.js](https://nextjs.org/) (App Router)
@@ -143,6 +173,7 @@ bun run dev:full
 - **Docs**: [Fumadocs](https://fumadocs.vercel.app/)
 - **Monorepo**: [Turborepo](https://turborepo.org/)
 - **Realtime**: [Socket.io](https://socket.io/)
+- **Background Jobs**: [Trigger.dev](https://trigger.dev/)
 
 ## Contributing
 
@@ -152,4 +183,4 @@ We welcome contributions! Please see our [Contributing Guide](.github/CONTRIBUTI
 
 This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
 
-<p align="center">Made with ❤️ by the Sim Studio Team</p>
+<p align="center">Made with ❤️ by the Sim Team</p>

apps/docs/app/(docs)/layout.tsx

@@ -23,12 +23,12 @@ export default function Layout({ children }: { children: ReactNode }) {
       <DocsLayout
         tree={source.pageTree}
         nav={{
-          title: <div className='flex items-center font-medium'>Sim Studio</div>,
+          title: <div className='flex items-center font-medium'>Sim</div>,
         }}
         links={[
           {
-            text: 'Visit Sim Studio',
-            url: 'https://simstudio.ai',
+            text: 'Visit Sim',
+            url: 'https://sim.ai',
             icon: <ExternalLink className='h-4 w-4' />,
           },
         ]}

apps/docs/app/global.css

@@ -1,7 +1,8 @@
 @import "tailwindcss";
 @import "fumadocs-ui/css/neutral.css";
 @import "fumadocs-ui/css/preset.css";
-:root {
+
+@theme {
   --color-fd-primary: #802fff; /* Purple from control-bar component */
 }
 
@@ -15,4 +16,9 @@
   color: var(--color-fd-primary);
 }
 
+/* Tailwind v4 content sources */
+@source '../app/**/*.{js,ts,jsx,tsx,mdx}';
+@source '../components/**/*.{js,ts,jsx,tsx,mdx}';
+@source '../content/**/*.{js,ts,jsx,tsx,mdx}';
+@source '../mdx-components.tsx';
 @source '../node_modules/fumadocs-ui/dist/**/*.js';

apps/docs/app/layout.tsx

@@ -22,7 +22,7 @@ export default function Layout({ children }: { children: ReactNode }) {
 }
 
 export const metadata = {
-  title: 'Sim Studio',
+  title: 'Sim',
   description:
     'Build agents in seconds with a drag and drop workflow builder. Access comprehensive documentation to help you create efficient workflows and maximize your automation capabilities.',
   manifest: '/favicon/site.webmanifest',
@@ -37,6 +37,6 @@ export const metadata = {
   appleWebApp: {
     capable: true,
     statusBarStyle: 'default',
-    title: 'Sim Studio Docs',
+    title: 'Sim Docs',
   },
 }

apps/docs/components/icons.tsx

@@ -270,3 +270,26 @@ export const ResponseIcon = (props: SVGProps<SVGSVGElement>) => (
     <path d='m9 17-5-5 5-5' />
   </svg>
 )
+
+export const StarterIcon = (props: SVGProps<SVGSVGElement>) => (
+  <svg viewBox='0 0 24 24' fill='none' xmlns='http://www.w3.org/2000/svg' {...props}>
+    <path d='M8 5v14l11-7z' fill='currentColor' />
+  </svg>
+)
+
+export const LoopIcon = (props: SVGProps<SVGSVGElement>) => (
+  <svg viewBox='0 0 24 24' fill='none' xmlns='http://www.w3.org/2000/svg' {...props}>
+    <path
+      d='M4 12a8 8 0 018-8V2.5L16 6l-4 3.5V8a6 6 0 00-6 6 6 6 0 006 6 6 6 0 006-6h2a8 8 0 01-8 8 8 8 0 01-8-8z'
+      fill='currentColor'
+    />
+  </svg>
+)
+
+export const ParallelIcon = (props: SVGProps<SVGSVGElement>) => (
+  <svg viewBox='0 0 24 24' fill='none' xmlns='http://www.w3.org/2000/svg' {...props}>
+    <rect x='3' y='3' width='18' height='6' rx='1' stroke='currentColor' strokeWidth='2' />
+    <rect x='3' y='15' width='18' height='6' rx='1' stroke='currentColor' strokeWidth='2' />
+    <path d='M12 9v6' stroke='currentColor' strokeWidth='2' strokeLinecap='round' />
+  </svg>
+)

apps/docs/components/ui/block-types.tsx

@@ -1,4 +1,3 @@
-import { cn } from '@/lib/utils'
 import {
   AgentIcon,
   ApiIcon,
@@ -7,7 +6,8 @@ import {
   ConditionalIcon,
   ConnectIcon,
   ResponseIcon,
-} from '../icons'
+} from '@/components/icons'
+import { cn } from '@/lib/utils'
 
 // Custom Feature component specifically for BlockTypes to handle the 6-item layout
 const BlockFeature = ({

apps/docs/components/ui/video.tsx

@@ -0,0 +1,30 @@
+import { getVideoUrl } from '@/lib/utils'
+
+interface VideoProps {
+  src: string
+  className?: string
+  autoPlay?: boolean
+  loop?: boolean
+  muted?: boolean
+  playsInline?: boolean
+}
+
+export function Video({
+  src,
+  className = 'w-full -mb-2 rounded-lg',
+  autoPlay = true,
+  loop = true,
+  muted = true,
+  playsInline = true,
+}: VideoProps) {
+  return (
+    <video
+      autoPlay={autoPlay}
+      loop={loop}
+      muted={muted}
+      playsInline={playsInline}
+      className={className}
+      src={getVideoUrl(src)}
+    />
+  )
+}

apps/docs/content/docs/blocks/agent.mdx

@@ -8,47 +8,40 @@ import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 import { ThemeImage } from '@/components/ui/theme-image'
 
-The Agent block is a fundamental component in Sim Studio that allows you to create powerful AI agents using various LLM providers. These agents can process inputs based on customizable system prompts and utilize integrated tools to enhance their capabilities.
+The Agent block serves as the interface between your workflow and Large Language Models (LLMs). It executes inference requests against various AI providers, processes natural language inputs according to defined instructions, and generates structured or unstructured outputs for downstream consumption.
 
 <ThemeImage
   lightSrc="/static/light/agent-light.png"
   darkSrc="/static/dark/agent-dark.png"
-  alt="Agent Block"
-  width={300}
+  alt="Agent Block Configuration"
+  width={350}
   height={175}
 />
 
-<Callout type="info">
-  Agent blocks serve as interfaces to Large Language Models, enabling your workflow to leverage
-  state-of-the-art AI capabilities.
-</Callout>
-
 ## Overview
 
-The Agent block serves as an interface to Large Language Models (LLMs), enabling you to create agents that can:
+The Agent block enables you to:
 
 <Steps>
   <Step>
-    <strong>Respond to user inputs</strong>: Generate natural language responses based on provided
-    inputs
+    <strong>Process natural language</strong>: Analyze user input and generate contextual responses
   </Step>
   <Step>
-    <strong>Follow instructions</strong>: Adhere to specific instructions defined in the system
-    prompt
+    <strong>Execute AI-powered tasks</strong>: Perform content analysis, generation, and decision-making
   </Step>
   <Step>
-    <strong>Use specialized tools</strong>: Interact with integrated tools to extend capabilities
+    <strong>Call external tools</strong>: Access APIs, databases, and services during processing
   </Step>
   <Step>
-    <strong>Structure output</strong>: Generate responses in structured formats when needed
+    <strong>Generate structured output</strong>: Return JSON data that matches your schema requirements
   </Step>
-</Steps>
+</Steps> 
 
 ## Configuration Options
 
 ### System Prompt
 
-The system prompt defines the agent's behavior, capabilities, and limitations. It's the primary way to instruct the agent on how to respond to inputs.
+The system prompt establishes the agent's operational parameters and behavioral constraints. This configuration defines the agent's role, response methodology, and processing boundaries for all incoming requests.
 
 ```markdown
 You are a helpful assistant that specializes in financial analysis.
@@ -58,22 +51,25 @@ When responding to questions about investments, include risk disclaimers.
 
 ### User Prompt
 
-The user prompt or context is the specific input or question that the agent should respond to. This can be:
+The user prompt represents the primary input data for inference processing. This parameter accepts natural language text or structured data that the agent will analyze and respond to. Input sources include:
 
-- Directly provided in the block configuration
-- Connected from another block's output
-- Dynamically generated during workflow execution
+- **Static Configuration**: Direct text input specified in the block configuration
+- **Dynamic Input**: Data passed from upstream blocks through connection interfaces
+- **Runtime Generation**: Programmatically generated content during workflow execution
 
 ### Model Selection
 
-Choose from a variety of LLM providers:
+The Agent block supports multiple LLM providers through a unified inference interface. Available models include:
 
-- OpenAI (GPT-4o, o1, o3, o4-mini, gpt-4.1)
-- Anthropic (Claude 3.7 Sonnet)
-- Google (Gemini 2.5 Pro, Gemini 2.0 Flash)
-- Groq, Cerebras
-- Ollama Local Models
-- And more
+**OpenAI Models**: GPT-5, GPT-4o, o1, o3, o4-mini, gpt-4.1 (API-based inference)
+**Anthropic Models**: Claude 3.7 Sonnet (API-based inference)
+**Google Models**: Gemini 2.5 Pro, Gemini 2.0 Flash (API-based inference)
+**Alternative Providers**: Groq, Cerebras, xAI, DeepSeek (API-based inference)
+**Local Deployment**: Ollama-compatible models (self-hosted inference)
+
+<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
+  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/models.mp4"></video>
+</div>
 
 ### Temperature
 
@@ -81,22 +77,16 @@ Control the creativity and randomness of responses:
 
 <Tabs items={['Low (0-0.3)', 'Medium (0.3-0.7)', 'High (0.7-2.0)']}>
   <Tab>
-    <p>
-      More deterministic, focused responses. Best for factual tasks, customer support, and
-      situations where accuracy is critical.
-    </p>
+    More deterministic, focused responses. Best for factual tasks, customer support, and
+    situations where accuracy is critical.
   </Tab>
   <Tab>
-    <p>
-      Balanced creativity and focus. Suitable for general purpose applications that require both
-      accuracy and some creativity.
-    </p>
+    Balanced creativity and focus. Suitable for general purpose applications that require both
+    accuracy and some creativity.
   </Tab>
   <Tab>
-    <p>
-      More creative, varied responses. Ideal for creative writing, brainstorming, and generating
-      diverse ideas.
-    </p>
+    More creative, varied responses. Ideal for creative writing, brainstorming, and generating
+    diverse ideas.
   </Tab>
 </Tabs>
 
@@ -110,103 +100,204 @@ Your API key for the selected LLM provider. This is securely stored and used for
 
 ### Tools
 
-Integrate specialized tools to enhance the agent's capabilities. You can add tools to your agent by:
+Tools extend the agent's capabilities through external API integrations and service connections. The tool system enables function calling, allowing the agent to execute operations beyond text generation.
 
-1. Clicking the Tools section in the Agent configuration
-2. Selecting from the tools dropdown menu
-3. Choosing an existing tool or creating a new one
+**Tool Integration Process**:
+1. Access the Tools configuration section within the Agent block
+2. Select from 60+ pre-built integrations or define custom functions
+3. Configure authentication parameters and operational constraints
 
-<ThemeImage
-  lightSrc="/static/light/tooldropdown-light.png"
-  darkSrc="/static/dark/tooldropdown-dark.png"
-  alt="Tools Dropdown"
-  width={150}
-  height={125}
-/>
+<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
+  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/tools.mp4"></video>
+</div>
 
-Available tools include:
+**Available Tool Categories**:
+- **Communication**: Gmail, Slack, Telegram, WhatsApp, Microsoft Teams
+- **Data Sources**: Notion, Google Sheets, Airtable, Supabase, Pinecone
+- **Web Services**: Firecrawl, Google Search, Exa AI, browser automation
+- **Development**: GitHub, Jira, Linear repository and issue management
+- **AI Services**: OpenAI, Perplexity, Hugging Face, ElevenLabs
 
-- **Confluence**: Access and query Confluence knowledge bases
-- **Evaluator**: Use evaluation metrics to assess content
-- **GitHub**: Interact with GitHub repositories and issues
-- **Gmail**: Process and respond to emails
-- **Firecrawl**: Web search and content retrieval
-- And many, many more pre-built integrations
+**Tool Execution Control**:
+- **Auto**: Model determines tool invocation based on context and necessity
+- **Required**: Tool must be called during every inference request
+- **None**: Tool definition available but excluded from model context
 
-You can also create custom tools to meet specific requirements for your agent's capabilities.
-
-<Callout type="info">
-  Tools significantly expand what your agent can do, allowing it to access external systems,
-  retrieve information, and take actions beyond simple text generation.
-</Callout>
+<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
+  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/granular-tool-control.mp4"></video>
+</div>
 
 ### Response Format
 
-Define a structured format for the agent's response when needed, using JSON or other formats.
+The Response Format parameter enforces structured output generation through JSON Schema validation. This ensures consistent, machine-readable responses that conform to predefined data structures:
+
+```json
+{
+  "name": "user_analysis",
+  "schema": {
+    "type": "object",
+    "properties": {
+      "sentiment": {
+        "type": "string",
+        "enum": ["positive", "negative", "neutral"]
+      },
+      "confidence": {
+        "type": "number",
+        "minimum": 0,
+        "maximum": 1
+      }
+    },
+    "required": ["sentiment", "confidence"]
+  }
+}
+```
+
+This configuration constrains the model's output to comply with the specified schema, preventing free-form text responses and ensuring structured data generation.
+
+### Accessing Results
+
+After an agent completes, you can access its outputs:
+
+- **`<agent.content>`**: The agent's response text or structured data
+- **`<agent.tokens>`**: Token usage statistics (prompt, completion, total)
+- **`<agent.tool_calls>`**: Details of any tools the agent used during execution
+- **`<agent.cost>`**: Estimated cost of the API call (if available)
+
+## Advanced Features
+
+### Memory Integration
+
+Agents can maintain context across interactions using the memory system:
+
+```javascript
+// In a Function block before the agent
+const memory = {
+  conversation_history: previousMessages,
+  user_preferences: userProfile,
+  session_data: currentSession
+};
+```
+
+### Structured Output Validation
+
+Use JSON Schema to ensure consistent, machine-readable responses:
+
+```json
+{
+  "type": "object",
+  "properties": {
+    "analysis": {"type": "string"},
+    "confidence": {"type": "number", "minimum": 0, "maximum": 1},
+    "categories": {"type": "array", "items": {"type": "string"}}
+  },
+  "required": ["analysis", "confidence"]
+}
+```
+
+### Error Handling
+
+Agents automatically handle common errors:
+- API rate limits with exponential backoff
+- Invalid tool calls with retry logic
+- Network failures with connection recovery
+- Schema validation errors with fallback responses
 
 ## Inputs and Outputs
 
-<Tabs items={['Inputs', 'Outputs']}>
+<Tabs items={['Configuration', 'Variables', 'Results']}>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>User Prompt</strong>: The user's query or context for the agent
+        <strong>System Prompt</strong>: Instructions defining agent behavior and role
       </li>
       <li>
-        <strong>System Prompt</strong>: Instructions for the agent (optional)
+        <strong>User Prompt</strong>: Input text or data to process
       </li>
       <li>
-        <strong>Tools</strong>: Optional tool connections that the agent can use
+        <strong>Model</strong>: AI model selection (OpenAI, Anthropic, Google, etc.)
+      </li>
+      <li>
+        <strong>Temperature</strong>: Response randomness control (0-2)
+      </li>
+      <li>
+        <strong>Tools</strong>: Array of available tools for function calling
+      </li>
+      <li>
+        <strong>Response Format</strong>: JSON Schema for structured output
       </li>
     </ul>
   </Tab>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>Content</strong>: The agent's response text
+        <strong>agent.content</strong>: Agent's response text or structured data
       </li>
       <li>
-        <strong>Model</strong>: The model used for generation
+        <strong>agent.tokens</strong>: Token usage statistics object
       </li>
       <li>
-        <strong>Tokens</strong>: Usage statistics (prompt, completion, total)
+        <strong>agent.tool_calls</strong>: Array of tool execution details
       </li>
       <li>
-        <strong>Tool Calls</strong>: Details of any tools used during processing
+        <strong>agent.cost</strong>: Estimated API call cost (if available)
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Content</strong>: Primary response output from the agent
       </li>
       <li>
-        <strong>Cost</strong>: Cost of the response
+        <strong>Metadata</strong>: Usage statistics and execution details
       </li>
       <li>
-        <strong>Usage</strong>: Usage statistics (prompt, completion, total)
+        <strong>Access</strong>: Available in blocks after the agent
       </li>
     </ul>
   </Tab>
 </Tabs>
 
-## Example Usage
+## Example Use Cases
 
-Here's an example of how an Agent block might be configured for a customer support workflow:
+### Customer Support Automation
 
-```yaml
-# Example Agent Configuration
-systemPrompt: |
-  You are a customer support agent for TechCorp.
-  Always maintain a professional, friendly tone.
-  If you don't know an answer, direct the customer to email support@techcorp.com.
-  Never make up information about products or policies.
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Handle customer inquiries with database access</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>User submits support ticket via API block</li>
+    <li>Agent processes inquiry with product database tools</li>
+    <li>Agent generates response and creates follow-up ticket</li>
+    <li>Response block sends reply to customer</li>
+  </ol>
+</div>
 
-model: OpenAI/gpt-4
-temperature: 0.2
-tools:
-  - ProductDatabase
-  - OrderHistory
-  - SupportTicketCreator
-```
+### Multi-Model Content Analysis
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Analyze content with different AI models</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Function block processes uploaded document</li>
+    <li>Agent with GPT-4o performs technical analysis</li>
+    <li>Agent with Claude analyzes sentiment and tone</li>
+    <li>Function block combines results for final report</li>
+  </ol>
+</div>
+
+### Tool-Powered Research Assistant
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Research assistant with web search and document access</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>User query received via input</li>
+    <li>Agent searches web using Google Search tool</li>
+    <li>Agent accesses Notion database for internal docs</li>
+    <li>Agent compiles comprehensive research report</li>
+  </ol>
+</div>
 
 ## Best Practices
 
 - **Be specific in system prompts**: Clearly define the agent's role, tone, and limitations. The more specific your instructions are, the better the agent will be able to fulfill its intended purpose.
 - **Choose the right temperature setting**: Use lower temperature settings (0-0.3) when accuracy is important, or increase temperature (0.7-2.0) for more creative or varied responses
-- **Combine with Evaluator blocks**: Use Evaluator blocks to assess agent responses and ensure quality. This allows you to create feedback loops and implement quality control measures.
-- **Leverage tools effectively**: Integrate tools that complement the agent's purpose and enhance its capabilities. Be selective about which tools you provide to avoid overwhelming the agent.
+- **Leverage tools effectively**: Integrate tools that complement the agent's purpose and enhance its capabilities. Be selective about which tools you provide to avoid overwhelming the agent. For tasks with little overlap, use another Agent block for the best results.

apps/docs/content/docs/blocks/api.mdx

@@ -14,7 +14,7 @@ The API block enables you to connect your workflow to external services through
   lightSrc="/static/light/api-light.png"
   darkSrc="/static/dark/api-dark.png"
   alt="API Block"
-  width={300}
+  width={350}
   height={175}
 />
 
@@ -22,11 +22,20 @@ The API block enables you to connect your workflow to external services through
 
 The API block enables you to:
 
-- Make HTTP requests to external services and APIs
-- Process and transform data from external sources
-- Send data to external systems
-- Integrate with third-party platforms and services
-- Create webhooks and callbacks
+<Steps>
+  <Step>
+    <strong>Connect to external services</strong>: Make HTTP requests to REST APIs and web services
+  </Step>
+  <Step>
+    <strong>Send and receive data</strong>: Process responses and transform data from external sources
+  </Step>
+  <Step>
+    <strong>Integrate third-party platforms</strong>: Connect with services like Stripe, Slack, or custom APIs
+  </Step>
+  <Step>
+    <strong>Handle authentication</strong>: Support various auth methods including Bearer tokens and API keys
+  </Step>
+</Steps>
 
 ## Configuration Options
 
@@ -82,42 +91,140 @@ For methods that support a request body (POST, PUT, PATCH), you can define the d
 - Data connected from another block's output
 - Dynamically generated during workflow execution
 
+### Accessing Results
+
+After an API request completes, you can access its outputs:
+
+- **`<api.data>`**: The response body data from the API
+- **`<api.status>`**: HTTP status code (200, 404, 500, etc.)
+- **`<api.headers>`**: Response headers from the server
+- **`<api.error>`**: Error details if the request failed
+
+## Advanced Features
+
+### Dynamic URL Construction
+
+Build URLs dynamically using variables from previous blocks:
+
+```javascript
+// In a Function block before the API
+const userId = <start.userId>;
+const apiUrl = `https://api.example.com/users/${userId}/profile`;
+```
+
+### Request Retries
+
+The API block automatically handles:
+- Network timeouts with exponential backoff
+- Rate limit responses (429 status codes)
+- Server errors (5xx status codes) with retry logic
+- Connection failures with reconnection attempts
+
+### Response Validation
+
+Validate API responses before processing:
+
+```javascript
+// In a Function block after the API
+if (<api.status> === 200) {
+  const data = <api.data>;
+  // Process successful response
+} else {
+  // Handle error response
+  console.error(`API Error: ${<api.status>}`);
+}
+```
+
 ## Inputs and Outputs
 
-### Inputs
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>URL</strong>: The endpoint to send the request to
+      </li>
+      <li>
+        <strong>Method</strong>: HTTP method (GET, POST, PUT, DELETE, PATCH)
+      </li>
+      <li>
+        <strong>Query Parameters</strong>: Key-value pairs for URL parameters
+      </li>
+      <li>
+        <strong>Headers</strong>: HTTP headers for authentication and content type
+      </li>
+      <li>
+        <strong>Body</strong>: Request payload for POST/PUT/PATCH methods
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>api.data</strong>: Response body data from the API call
+      </li>
+      <li>
+        <strong>api.status</strong>: HTTP status code returned by server
+      </li>
+      <li>
+        <strong>api.headers</strong>: Response headers from the server
+      </li>
+      <li>
+        <strong>api.error</strong>: Error details if request failed
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Response Data</strong>: Primary API response content
+      </li>
+      <li>
+        <strong>Status Information</strong>: HTTP status and error details
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the API call
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
 
-- **URL**: The endpoint to send the request to
-- **Method**: The HTTP method to use
-- **Query Parameters**: Key-value pairs for URL parameters
-- **Headers**: HTTP headers for the request
-- **Body**: Data to send with the request (for applicable methods)
+## Example Use Cases
 
-### Outputs
+### Fetch User Profile Data
 
-- **Status Code**: The HTTP status code returned by the server
-- **Response Body**: The data returned by the server
-- **Headers**: Response headers from the server
-- **Error**: Any error information if the request fails
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Retrieve user information from external service</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Function block constructs user ID from input</li>
+    <li>API block calls GET /users/&#123;id&#125; endpoint</li>
+    <li>Function block processes and formats user data</li>
+    <li>Response block returns formatted profile</li>
+  </ol>
+</div>
 
-## Example Usage
+### Create Support Ticket
 
-Here's an example of how an API block might be configured to fetch weather data:
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Submit support request to ticketing system</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Agent analyzes user issue and generates ticket data</li>
+    <li>API block POSTs ticket to support system</li>
+    <li>Condition block checks if ticket was created successfully</li>
+    <li>Response block confirms ticket creation with ID</li>
+  </ol>
+</div>
 
-```yaml
-# Example API Configuration
-url: https://api.weatherapi.com/v1/current.json
-method: GET
-params:
-  - key: key
-    value: your_api_key_here
-  - key: q
-    value: London
-  - key: aqi
-    value: no
-headers:
-  - key: Accept
-    value: application/json
-```
+### Payment Processing
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Process payment through Stripe API</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Function block validates payment data</li>
+    <li>API block creates payment intent via Stripe</li>
+    <li>Condition block handles payment success/failure</li>
+    <li>Function block updates order status in database</li>
+  </ol>
+</div>
 
 ## Best Practices
 
@@ -125,4 +232,3 @@ headers:
 - **Handle errors gracefully**: Connect error handling logic for failed requests
 - **Validate responses**: Check status codes and response formats before processing data
 - **Respect rate limits**: Be mindful of API rate limits and implement appropriate throttling
-- **Cache responses when appropriate**: For frequently accessed data that doesn't change often

apps/docs/content/docs/blocks/condition.mdx

@@ -4,9 +4,9 @@ description: Create conditional logic and branching in your workflows
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
-import { File, Files, Folder } from 'fumadocs-ui/components/files'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
 import { ThemeImage } from '@/components/ui/theme-image'
 
 The Condition block allows you to branch your workflow execution path based on boolean expressions. It evaluates conditions and routes the workflow accordingly, enabling you to create dynamic, responsive workflows with different execution paths.
@@ -15,7 +15,7 @@ The Condition block allows you to branch your workflow execution path based on b
   lightSrc="/static/light/condition-light.png"
   darkSrc="/static/dark/condition-dark.png"
   alt="Condition Block"
-  width={300}
+  width={350}
   height={175}
 />
 
@@ -26,57 +26,32 @@ The Condition block allows you to branch your workflow execution path based on b
 
 ## Overview
 
-The Condition block serves as a decision point in your workflow, enabling:
-
-<div className="my-6 grid grid-cols-1 gap-4 md:grid-cols-2">
-  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
-    <h3 className="mb-2 text-lg font-medium">Branching Logic</h3>
-    <div className="text-sm text-gray-600 dark:text-gray-400">
-      Create different execution paths based on specific conditions
-    </div>
-  </div>
-
-  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
-    <h3 className="mb-2 text-lg font-medium">Rule-Based Routing</h3>
-    <div className="text-sm text-gray-600 dark:text-gray-400">
-      Route workflows deterministically without needing an LLM
-    </div>
-  </div>
-
-  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
-    <h3 className="mb-2 text-lg font-medium">Data-Driven Decisions</h3>
-    <div className="text-sm text-gray-600 dark:text-gray-400">
-      Create workflow paths based on structured data values
-    </div>
-  </div>
-
-  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
-    <h3 className="mb-2 text-lg font-medium">If-Then-Else Logic</h3>
-    <div className="text-sm text-gray-600 dark:text-gray-400">
-      Implement conditional programming paradigms in your workflows
-    </div>
-  </div>
-</div>
-
-## How It Works
-
-The Condition block:
+The Condition block enables you to:
 
 <Steps>
   <Step>
-    <strong>Evaluate Expression</strong>: Evaluates a boolean expression or condition
+    <strong>Create branching logic</strong>: Route workflows based on boolean expressions
   </Step>
   <Step>
-    <strong>Determine Result</strong>: Determines whether the condition evaluates to true or false
+    <strong>Make data-driven decisions</strong>: Evaluate conditions using previous block outputs
   </Step>
   <Step>
-    <strong>Route Workflow</strong>: Routes the workflow to the appropriate path based on the result
+    <strong>Handle multiple scenarios</strong>: Define multiple conditions with different paths
   </Step>
   <Step>
-    <strong>Provide Context</strong>: Provides context about the decision made
+    <strong>Provide deterministic routing</strong>: Make decisions without requiring an LLM
   </Step>
 </Steps>
 
+## How It Works
+
+The Condition block operates through a sequential evaluation process:
+
+1. **Evaluate Expression** - Processes the JavaScript/TypeScript boolean expression using current workflow data
+2. **Determine Result** - Returns true or false based on the expression evaluation
+3. **Route Workflow** - Directs execution to the appropriate destination block based on the result  
+4. **Provide Context** - Generates metadata about the decision for debugging and monitoring
+
 ## Configuration Options
 
 ### Conditions
@@ -97,95 +72,165 @@ Conditions use JavaScript syntax and can reference input values from previous bl
   <Tab>
     ```javascript
     // Check if a score is above a threshold
-    input.score > 75
+    <agent.score> > 75
     ```
   </Tab>
   <Tab>
     ```javascript
     // Check if a text contains specific keywords
-    input.text.includes('urgent') || input.text.includes('emergency')
+    <agent.text>.includes('urgent') || <agent.text>.includes('emergency')
     ```
   </Tab>
   <Tab>
     ```javascript
     // Check multiple conditions
-    input.age >= 18 && input.country === 'US'
+    <agent.age> >= 18 && <agent.country> === 'US'
     ```
   </Tab>
 </Tabs>
 
+
+### Accessing Results
+
+After a condition evaluates, you can access its outputs:
+
+- **`<condition.result>`**: Boolean result of the condition evaluation
+- **`<condition.matched_condition>`**: ID of the condition that was matched
+- **`<condition.content>`**: Description of the evaluation result
+- **`<condition.path>`**: Details of the chosen routing destination
+
+## Advanced Features
+
+### Complex Expressions
+
+Use JavaScript operators and functions in conditions:
+
+```javascript
+// String operations
+<user.email>.endsWith('@company.com')
+
+// Array operations
+<api.tags>.includes('urgent')
+
+// Mathematical operations
+<agent.confidence> * 100 > 85
+
+// Date comparisons
+new Date(<api.created_at>) > new Date('2024-01-01')
+```
+
+### Multiple Condition Evaluation
+
+Conditions are evaluated in order until one matches:
+
+```javascript
+// Condition 1: Check for high priority
+<ticket.priority> === 'high'
+
+// Condition 2: Check for urgent keywords
+<ticket.subject>.toLowerCase().includes('urgent')
+
+// Condition 3: Default fallback
+true
+```
+
+### Error Handling
+
+Conditions automatically handle:
+- Undefined or null values with safe evaluation
+- Type mismatches with appropriate fallbacks
+- Invalid expressions with error logging
+- Missing variables with default values
+
 ## Inputs and Outputs
 
-<Tabs items={['Inputs', 'Outputs']}>
+<Tabs items={['Configuration', 'Variables', 'Results']}>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>Variables</strong>: Values from previous blocks that can be referenced in conditions
+        <strong>Conditions</strong>: Array of boolean expressions to evaluate
       </li>
       <li>
-        <strong>Conditions</strong>: Boolean expressions to evaluate
+        <strong>Expressions</strong>: JavaScript/TypeScript conditions using block outputs
+      </li>
+      <li>
+        <strong>Routing Paths</strong>: Destination blocks for each condition result
       </li>
     </ul>
   </Tab>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>Content</strong>: A description of the evaluation result
+        <strong>condition.result</strong>: Boolean result of condition evaluation
       </li>
       <li>
-        <strong>Condition Result</strong>: The boolean result of the condition evaluation
+        <strong>condition.matched_condition</strong>: ID of the matched condition
       </li>
       <li>
-        <strong>Selected Path</strong>: Details of the chosen routing destination
+        <strong>condition.content</strong>: Description of evaluation result
       </li>
       <li>
-        <strong>Selected Condition ID</strong>: Identifier of the condition that was matched
+        <strong>condition.path</strong>: Details of chosen routing destination
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Boolean Result</strong>: Primary condition evaluation outcome
+      </li>
+      <li>
+        <strong>Routing Information</strong>: Path selection and condition details
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the condition
       </li>
     </ul>
   </Tab>
 </Tabs>
 
-## Example Usage
+## Example Use Cases
 
-Here's an example of how a Condition block might be used in a customer satisfaction workflow:
+### Customer Support Routing
 
-```yaml
-# Example Condition Configuration
-conditions:
-  - id: 'high_satisfaction'
-    expression: 'input.satisfactionScore >= 8'
-    description: 'Customer is highly satisfied'
-    path: 'positive_feedback_block'
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Route support tickets based on priority</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>API block fetches support ticket data</li>
+    <li>Condition checks if `<api.priority>` equals 'high'</li>
+    <li>High priority tickets → Agent with escalation tools</li>
+    <li>Normal priority tickets → Standard support agent</li>
+  </ol>
+</div>
 
-  - id: 'medium_satisfaction'
-    expression: 'input.satisfactionScore >= 5'
-    description: 'Customer is moderately satisfied'
-    path: 'neutral_feedback_block'
+### Content Moderation
 
-  - id: 'default'
-    expression: 'true'
-    description: 'Customer is not satisfied'
-    path: 'improvement_feedback_block'
-```
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Filter content based on analysis results</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Agent analyzes user-generated content</li>
+    <li>Condition checks if `<agent.toxicity_score>` > 0.7</li>
+    <li>Toxic content → Moderation workflow</li>
+    <li>Clean content → Publishing workflow</li>
+  </ol>
+</div>
+
+### User Onboarding Flow
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Personalize onboarding based on user type</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Function block processes user registration data</li>
+    <li>Condition checks if `<user.account_type>` === 'enterprise'</li>
+    <li>Enterprise users → Advanced setup workflow</li>
+    <li>Individual users → Simple onboarding workflow</li>
+  </ol>
+</div>
 
 ## Best Practices
 
-### Order conditions correctly
-
-Conditions are evaluated in order, so place more specific conditions before general ones. This ensures that more specific logic takes precedence over general fallbacks.
-
-### Include a default condition
-
-Add a catch-all condition (e.g., `true`) as the last condition to handle cases when no other conditions match. This prevents workflow execution from getting stuck.
-
-### Keep expressions simple
-
-Use clear, straightforward boolean expressions for better readability. Complex expressions can be difficult to debug and maintain.
-
-### Document your conditions
-
-Add descriptions to explain the purpose of each condition. This helps other team members understand the logic and makes maintenance easier.
-
-### Test edge cases
-
-Ensure your conditions handle boundary values correctly. Test with values at the edges of your condition ranges to verify correct behavior.
+- **Order conditions correctly**: Place more specific conditions before general ones to ensure specific logic takes precedence over fallbacks
+- **Include a default condition**: Add a catch-all condition (`true`) as the last condition to handle unmatched cases and prevent workflow execution from getting stuck
+- **Keep expressions simple**: Use clear, straightforward boolean expressions for better readability and easier debugging
+- **Document your conditions**: Add descriptions to explain the purpose of each condition for better team collaboration and maintenance
+- **Test edge cases**: Verify conditions handle boundary values correctly by testing with values at the edges of your condition ranges

apps/docs/content/docs/blocks/evaluator.mdx

@@ -7,25 +7,25 @@ import { Callout } from 'fumadocs-ui/components/callout'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 import { ThemeImage } from '@/components/ui/theme-image'
+import { Video } from '@/components/ui/video'
 
-The Evaluator block allows you to assess the quality of content using customizable evaluation metrics. This is particularly useful for evaluating AI-generated text, ensuring outputs meet specific criteria, and building quality-control mechanisms into your workflows.
+The Evaluator block uses AI to score and assess content quality based on metrics you define. Perfect for quality control, A/B testing, and ensuring your AI outputs meet specific standards.
 
 <ThemeImage
   lightSrc="/static/light/evaluator-light.png"
   darkSrc="/static/dark/evaluator-dark.png"
-  alt="Evaluator Block"
-  width={300}
+  alt="Evaluator Block Configuration"
+  width={350}
   height={175}
 />
 
-## Overview
+## What You Can Evaluate
 
-The Evaluator block utilizes LLMs to objectively evaluate content based on custom metrics you define. This is especially useful for:
-
-- Assessing the quality of AI-generated content
-- Evaluating responses against specific criteria
-- Creating scoring frameworks for different types of content
-- Building objective feedback loops in your workflows
+**AI-Generated Content**: Score chatbot responses, generated articles, or marketing copy
+**User Input**: Evaluate customer feedback, survey responses, or form submissions  
+**Content Quality**: Assess clarity, accuracy, relevance, and tone
+**Performance Metrics**: Track improvements over time with consistent scoring
+**A/B Testing**: Compare different approaches with objective metrics
 
 ## Configuration Options
 
@@ -55,16 +55,19 @@ The content to be evaluated. This can be:
 
 ### Model Selection
 
-Choose an LLM provider to perform the evaluation:
+Choose an AI model to perform the evaluation:
 
-- OpenAI (GPT-4o, o1, o3, , gpt-4.1)
-- Anthropic (Claude 3.7 Sonnet)
-- Google (Gemini 2.5 Pro, Gemini 2.0 Flash)
-- Groq, Cerebras
-- Ollama Local Models
-- And more
+**OpenAI**: GPT-4o, o1, o3, o4-mini, gpt-4.1
+**Anthropic**: Claude 3.7 Sonnet
+**Google**: Gemini 2.5 Pro, Gemini 2.0 Flash
+**Other Providers**: Groq, Cerebras, xAI, DeepSeek
+**Local Models**: Any model running on Ollama
 
-The chosen model should have strong reasoning capabilities to provide accurate evaluations.
+<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
+  <Video src="models.mp4" />
+</div>
+
+**Recommendation**: Use models with strong reasoning capabilities like GPT-4o or Claude 3.7 Sonnet for more accurate evaluations.
 
 ### API Key
 

apps/docs/content/docs/blocks/function.mdx

@@ -8,100 +8,281 @@ import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 import { ThemeImage } from '@/components/ui/theme-image'
 
-The Function block allows you to write and execute custom JavaScript or TypeScript code directly within your workflow. This powerful feature enables you to implement complex logic, data transformations, and integration with external libraries.
+The Function block lets you run custom JavaScript or TypeScript code in your workflow. Use it to transform data, perform calculations, or implement custom logic that isn't available in other blocks.
 
 <ThemeImage
   lightSrc="/static/light/function-light.png"
   darkSrc="/static/dark/function-dark.png"
-  alt="Function Block"
-  width={300}
+  alt="Function Block with Code Editor"
+  width={350}
   height={175}
 />
 
 ## Overview
 
-The Function block brings the full power of JavaScript/TypeScript to your workflows, allowing for:
+The Function block enables you to:
 
-- Custom data transformation and manipulation
-- Complex conditional logic
-- Mathematical calculations and algorithms
-- Integration with external libraries
-- Creation of reusable utility functions
+<Steps>
+  <Step>
+    <strong>Transform data</strong>: Convert formats, parse text, manipulate arrays and objects
+  </Step>
+  <Step>
+    <strong>Perform calculations</strong>: Math operations, statistics, financial calculations
+  </Step>
+  <Step>
+    <strong>Implement custom logic</strong>: Complex conditionals, loops, and algorithms
+  </Step>
+  <Step>
+    <strong>Process external data</strong>: Parse responses, format requests, handle authentication
+  </Step>
+</Steps>
 
 ## How It Works
 
-The Function block:
+The Function block runs your code in a secure, isolated environment:
 
-1. Takes your custom JavaScript/TypeScript code
-2. Executes it in a secure, isolated environment
-3. Processes any inputs provided from previous blocks
-4. Returns the result for use in subsequent blocks
+1. **Receive Input**: Access data from previous blocks via the `input` object
+2. **Execute Code**: Run your JavaScript/TypeScript code 
+3. **Return Results**: Use `return` to pass data to the next block
+4. **Handle Errors**: Built-in error handling and logging
 
 ## Configuration Options
 
 ### Code Editor
 
-A full-featured code editor where you can write your JavaScript/TypeScript code. The editor supports:
+Write your JavaScript/TypeScript code in a full-featured editor with:
+- Syntax highlighting and error checking
+- Line numbers and bracket matching
+- Support for modern JavaScript features
+- Native support for `fetch` 
 
-- Syntax highlighting
-- Code completion
-- Error checking
-- Multiple lines of code
+### Accessing Input Data
 
-### Inputs
-
-Your function can access inputs from previous blocks through an `input` object. For example:
+Use the `input` object to access data from previous blocks:
 
 ```javascript
-// Access data from a previous block
-const customerName = input.customerData.name;
-const orderTotal = input.orderData.total;
+// Access data from connected blocks
+const userData = <agent.userData>;
+const orderData = <agent.orderData>;
 
-// Process the data
-const discount = orderTotal > 100 ? 0.1 : 0;
-const finalPrice = orderTotal * (1 - discount);
-
-// Return the result
-return {
-  customerName,
-  originalTotal: orderTotal,
-  discount: discount * 100 + '%',
-  finalPrice
-};
+// Access specific fields
+const customerName = <agent.customer.name>;
+const total = <agent.order.total>;
 ```
 
-## Safety and Limitations
+### Common Examples
 
-For security and performance reasons, function execution has certain limitations:
+**Data Transformation**:
+```javascript
+// Convert and format data
+const formatted = {
+  name: <agent.user.firstName> + ' ' + <agent.user.lastName>,
+  email: <agent.user.email>.toLowerCase(),
+  joinDate: new Date(<agent.user.created>).toLocaleDateString()
+};
+return formatted;
+```
 
-- **Execution Time**: Functions have a maximum execution time to prevent infinite loops
-- **Memory Usage**: Memory is limited to prevent excessive resource usage
-- **Network Access**: Network calls are restricted to prevent unauthorized access
-- **Available APIs**: Only a subset of browser APIs are available
+**Calculations**:
+```javascript
+// Calculate discounts and totals
+const subtotal = <agent.items>.reduce((sum, item) => sum + item.price, 0);
+const discount = subtotal > 100 ? 0.1 : 0;
+const total = subtotal * (1 - discount);
+
+return { subtotal, discount, total };
+```
+
+**Data Validation**:
+```javascript
+// Validate email format
+const email = <agent.email>;
+const isValid = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email);
+
+if (!isValid) {
+  throw new Error('Invalid email format');
+}
+return { email, isValid };
+```
+
+### Accessing Results
+
+After a function executes, you can access its outputs:
+
+- **`<function.result>`**: The value returned from your function
+- **`<function.stdout>`**: Any console.log() output from your code
+
+## Advanced Features
+
+### Async/Await Support
+
+Use async functions for complex operations:
+
+```javascript
+// Async function example
+const processData = async () => {
+  const data = <api.response>;
+  
+  // Process data with async operations
+  const processed = await Promise.all(
+    data.map(async (item) => {
+      return {
+        id: item.id,
+        processed: true,
+        timestamp: new Date().toISOString()
+      };
+    })
+  );
+  
+  return processed;
+};
+
+return await processData();
+```
+
+### Error Handling
+
+Implement robust error handling:
+
+```javascript
+try {
+  const result = <api.data>;
+  
+  if (!result || !result.length) {
+    throw new Error('No data received');
+  }
+  
+  return result.map(item => ({
+    id: item.id,
+    name: item.name.trim(),
+    valid: true
+  }));
+} catch (error) {
+  console.error('Processing failed:', error.message);
+  return { error: error.message, valid: false };
+}
+```
+
+### Performance Optimization
+
+Optimize for large datasets:
+
+```javascript
+// Efficient data processing
+const data = <api.large_dataset>;
+
+// Use efficient array methods
+const processed = data
+  .filter(item => item.status === 'active')
+  .map(item => ({
+    id: item.id,
+    summary: item.description.substring(0, 100)
+  }))
+  .slice(0, 1000); // Limit results
+
+return processed;
+```
+
+## Security and Limitations
+
+<Callout type="warning">
+  Functions run in a secure environment with these restrictions:
+  - **Execution timeout**: 30 seconds maximum to prevent infinite loops
+  - **Memory limits**: Limited memory to prevent resource exhaustion
+  - **No network access**: Cannot make HTTP requests (use API blocks instead)
+  - **Limited APIs**: Only safe JavaScript APIs are available
+</Callout>
 
 ## Inputs and Outputs
 
-### Inputs
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Code</strong>: Your JavaScript/TypeScript code to execute
+      </li>
+      <li>
+        <strong>Timeout</strong>: Maximum execution time (defaults to 30 seconds)
+      </li>
+      <li>
+        <strong>Input Data</strong>: All connected block outputs available via variables
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>function.result</strong>: The value returned from your function
+      </li>
+      <li>
+        <strong>function.stdout</strong>: Console.log() output from your code
+      </li>
+      <li>
+        <strong>function.error</strong>: Error details if function failed
+      </li>
+      <li>
+        <strong>function.execution_time</strong>: Time taken to execute
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Function Result</strong>: Primary output from your code
+      </li>
+      <li>
+        <strong>Debug Information</strong>: Logs and execution details
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the function
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
 
-- **Code**: Your JavaScript/TypeScript code to execute
-- **Input Data**: Values from previous blocks that can be accessed in your code
+## Example Use Cases
 
-### Outputs
+### Data Processing Pipeline
 
-- **Result**: The value returned by your function
-- **Standard Output**: Any console output from your function
-- **Execution Time**: The time taken to execute your function (in milliseconds)
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Transform API response into structured data</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>API block fetches raw customer data</li>
+    <li>Function block processes and validates data</li>
+    <li>Function block calculates derived metrics</li>
+    <li>Response block returns formatted results</li>
+  </ol>
+</div>
 
-## Example Usage
+### Business Logic Implementation
 
-Here's an example of a Function block that processes customer data and calculates a loyalty score:
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Calculate loyalty scores and tiers</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Agent retrieves customer purchase history</li>
+    <li>Function block calculates loyalty metrics</li>
+    <li>Function block determines customer tier</li>
+    <li>Condition block routes based on tier level</li>
+  </ol>
+</div>
 
-```javascript
-// Example Function Block Code
+### Data Validation and Sanitization
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Validate and clean user input</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>User input received from form submission</li>
+    <li>Function block validates email format and phone numbers</li>
+    <li>Function block sanitizes and normalizes data</li>
+    <li>API block saves validated data to database</li>
+  </ol>
+</div>
+
+### Example: Loyalty Score Calculator
+
+```javascript title="loyalty-calculator.js"
 // Process customer data and calculate loyalty score
-
-// Access input from previous blocks
-const { purchaseHistory, accountAge, supportTickets } = input;
+const { purchaseHistory, accountAge, supportTickets } = <agent>;
 
 // Calculate metrics
 const totalSpent = purchaseHistory.reduce((sum, purchase) => sum + purchase.amount, 0);
@@ -115,23 +296,18 @@ const supportScore = ticketRatio * 30;
 
 const loyaltyScore = Math.round(spendScore + frequencyScore + supportScore);
 
-// Return results
 return {
-  customer: input.name,
+  customer: <agent.name>,
   loyaltyScore,
-  loyaltyTier: loyaltyScore >= 80 ? "Platinum" : loyaltyScore >= 60 ? "Gold" : loyaltyScore >= 40 ? "Silver" : "Bronze",
-  metrics: {
-    spendScore,
-    frequencyScore,
-    supportScore
-  }
+  loyaltyTier: loyaltyScore >= 80 ? "Platinum" : loyaltyScore >= 60 ? "Gold" : "Silver",
+  metrics: { spendScore, frequencyScore, supportScore }
 };
 ```
 
 ## Best Practices
 
-- **Keep functions focused**: Write functions that do one thing well
-- **Handle errors gracefully**: Use try/catch blocks to handle potential errors
-- **Document your code**: Add comments to explain complex logic
-- **Test edge cases**: Ensure your code handles unusual inputs correctly
-- **Optimize for performance**: Be mindful of computational complexity for large datasets
+- **Keep functions focused**: Write functions that do one thing well to improve maintainability and debugging
+- **Handle errors gracefully**: Use try/catch blocks to handle potential errors and provide meaningful error messages
+- **Test edge cases**: Ensure your code handles unusual inputs, null values, and boundary conditions correctly
+- **Optimize for performance**: Be mindful of computational complexity and memory usage for large datasets
+- **Use console.log() for debugging**: Leverage stdout output to debug and monitor function execution

apps/docs/content/docs/blocks/index.mdx

@@ -1,54 +1,129 @@
 ---
 title: Blocks
-description: Building blocks for your agentic workflows
+description: The building components of your AI workflows
 ---
 
 import { Card, Cards } from 'fumadocs-ui/components/card'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 import { BlockTypes } from '@/components/ui/block-types'
+import { Video } from '@/components/ui/video'
 
-Blocks are the fundamental building components of Sim Studio workflows. Each block has a specific purpose and can be connected to other blocks to create sophisticated workflows.
+Blocks are the building components you connect together to create AI workflows. Think of them as specialized modules that each handle a specific task—from chatting with AI models to making API calls or processing data.
 
-## What is a Block?
+<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
+  <Video src="connections.mp4" />
+</div>
 
-A block is a reusable, configurable component that performs a specific function within your workflow. Blocks have inputs and outputs that allow them to communicate with other blocks. They can process data, make decisions, interact with external systems, or perform computations.
+## Core Block Types
 
-## Primary Block Types
+Sim provides seven core block types that handle the essential functions of AI workflows:
 
-Sim Studio provides six powerful block types that form the foundation of any workflow. Each block is designed to handle specific aspects of your agentic applications, from AI-powered reasoning to conditional logic and external integrations.
+### Processing Blocks
+- **[Agent](/blocks/agent)** - Chat with AI models (OpenAI, Anthropic, Google, local models)
+- **[Function](/blocks/function)** - Run custom JavaScript/TypeScript code
+- **[API](/blocks/api)** - Connect to external services via HTTP requests
+
+### Logic Blocks
+- **[Condition](/blocks/condition)** - Branch workflow paths based on boolean expressions
+- **[Router](/blocks/router)** - Use AI to intelligently route requests to different paths
+- **[Evaluator](/blocks/evaluator)** - Score and assess content quality using AI
+
+### Output Blocks
+- **[Response](/blocks/response)** - Format and return final results from your workflow
 
 <BlockTypes />
 
-## Block Connections
+## How Blocks Work
 
-Blocks can be connected to form a directed graph representing your workflow. Each connection represents the flow of data from one block to another:
+Each block has three main components:
+
+**Inputs**: Data coming into the block from other blocks or user input
+**Configuration**: Settings that control how the block behaves
+**Outputs**: Data the block produces for other blocks to use
 
 <Steps>
   <Step>
-    <strong>Outputs to Inputs</strong>: A block's outputs can be connected to another block's
-    inputs.
+    <strong>Receive Input</strong>: Block receives data from connected blocks or user input
   </Step>
   <Step>
-    <strong>Multiple Connections</strong>: A block can have multiple incoming and outgoing
-    connections.
+    <strong>Process</strong>: Block processes the input according to its configuration
   </Step>
   <Step>
-    <strong>Conditional Flows</strong>: Some blocks (like Router and Condition) can have multiple
-    output paths based on conditions.
+    <strong>Output Results</strong>: Block produces output data for the next blocks in the workflow
   </Step>
 </Steps>
 
+## Connecting Blocks
+
+You create workflows by connecting blocks together. The output of one block becomes the input of another:
+
+- **Drag to connect**: Drag from an output port to an input port
+- **Multiple connections**: One output can connect to multiple inputs
+- **Branching paths**: Some blocks can route to different paths based on conditions
+
+<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
+  <Video src="connections.mp4" />
+</div>
+
+## Common Patterns
+
+### Sequential Processing
+Connect blocks in a chain where each block processes the output of the previous one:
+```
+User Input → Agent → Function → Response
+```
+
+### Conditional Branching
+Use Condition or Router blocks to create different paths:
+```
+User Input → Router → Agent A (for questions)
+                   → Agent B (for commands)
+```
+
+### Quality Control
+Use Evaluator blocks to assess and filter outputs:
+```
+Agent → Evaluator → Condition → Response (if good)
+                              → Agent (retry if bad)
+```
+
 ## Block Configuration
 
-Each block type has its own configuration options allowing you to customize its behavior.
+Each block type has specific configuration options:
 
-### Common Configuration Options
+**All Blocks**:
+- Input/output connections
+- Error handling behavior
+- Execution timeout settings
 
-- **Input/output definitions**: Define how data flows in and out of the block
-- **Processing instructions**: Configure how the block processes its inputs
-- **API keys or authentication details**: Provide necessary credentials for external services
-- **Retry policies**: Configure how the block handles failures
-- **Error handling behavior**: Define how errors are managed and reported
+**AI Blocks** (Agent, Router, Evaluator):
+- Model selection (OpenAI, Anthropic, Google, local)
+- API keys and authentication
+- Temperature and other model parameters
+- System prompts and instructions
 
-See the specific documentation for each block type to learn about its configuration options.
+**Logic Blocks** (Condition, Function):
+- Custom expressions or code
+- Variable references
+- Execution environment settings
+
+**Integration Blocks** (API, Response):
+- Endpoint configuration
+- Headers and authentication
+- Request/response formatting
+
+<Cards>
+  <Card title="Agent Block" href="/blocks/agent">
+    Connect to AI models and create intelligent responses
+  </Card>
+  <Card title="Function Block" href="/blocks/function">
+    Run custom code to process and transform data
+  </Card>
+  <Card title="API Block" href="/blocks/api">
+    Integrate with external services and APIs
+  </Card>
+  <Card title="Condition Block" href="/blocks/condition">
+    Create branching logic based on data evaluation
+  </Card>
+</Cards>

apps/docs/content/docs/blocks/loop.mdx

@@ -0,0 +1,175 @@
+---
+title: Loop
+description: Create iterative workflows with loops that execute blocks repeatedly
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Loop block is a container block in Sim that allows you to execute a group of blocks repeatedly. Loops enable iterative processing in your workflows.
+
+<ThemeImage
+  lightSrc="/static/light/loop-light.png"
+  darkSrc="/static/dark/loop-dark.png"
+  alt="Loop Block"
+  width={500}
+  height={300}
+/>
+
+<Callout type="info">
+  Loop blocks are container nodes that can hold other blocks inside them. The blocks inside a loop will execute multiple times based on your configuration.
+</Callout>
+
+## Overview
+
+The Loop block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Iterate over collections</strong>: Process arrays or objects one item at a time
+  </Step>
+  <Step>
+    <strong>Repeat operations</strong>: Execute blocks a fixed number of times
+  </Step>
+</Steps>
+
+## Configuration Options
+
+### Loop Type
+
+Choose between two types of loops:
+
+<Tabs items={['For Loop', 'ForEach Loop']}>
+  <Tab>
+    A numeric loop that executes a fixed number of times. Use this when you need to repeat an operation a specific number of times.
+    
+    ```
+    Example: Run 5 times
+    - Iteration 1
+    - Iteration 2
+    - Iteration 3
+    - Iteration 4
+    - Iteration 5
+    ```
+  </Tab>
+  <Tab>
+    A collection-based loop that iterates over each item in an array or object. Use this when you need to process a collection of items.
+    
+    ```
+    Example: Process ["apple", "banana", "orange"]
+    - Iteration 1: Process "apple"
+    - Iteration 2: Process "banana"
+    - Iteration 3: Process "orange"
+    ```
+  </Tab>
+</Tabs>
+
+## How to Use Loops
+
+### Creating a Loop
+
+1. Drag a Loop block from the toolbar onto your canvas
+2. Configure the loop type and parameters
+3. Drag other blocks inside the loop container
+4. Connect the blocks as needed
+
+### Accessing Results
+
+After a loop completes, you can access aggregated results:
+
+- **`<loop.results>`**: Array of results from all loop iterations
+
+## Example Use Cases
+
+### Processing API Results
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Process multiple customer records</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>API block fetches customer list</li>
+    <li>ForEach loop iterates over each customer</li>
+    <li>Inside loop: Agent analyzes customer data</li>
+    <li>Inside loop: Function stores analysis results</li>
+  </ol>
+</div>
+
+### Iterative Content Generation
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Generate multiple variations</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Set For loop to 5 iterations</li>
+    <li>Inside loop: Agent generates content variation</li>
+    <li>Inside loop: Evaluator scores the content</li>
+    <li>After loop: Function selects best variation</li>
+  </ol>
+</div>
+
+## Advanced Features
+
+### Limitations
+
+<Callout type="warning">
+  Container blocks (Loops and Parallels) cannot be nested inside each other. This means:
+  - You cannot place a Loop block inside another Loop block
+  - You cannot place a Parallel block inside a Loop block
+  - You cannot place any container block inside another container block
+  
+  If you need multi-dimensional iteration, consider restructuring your workflow to use sequential loops or process data in stages.
+</Callout>
+
+<Callout type="info">
+  Loops execute sequentially, not in parallel. If you need concurrent execution, use the Parallel block instead.
+</Callout>
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Loop Type</strong>: Choose between 'for' or 'forEach'
+      </li>
+      <li>
+        <strong>Iterations</strong>: Number of times to execute (for loops)
+      </li>
+      <li>
+        <strong>Collection</strong>: Array or object to iterate over (forEach loops)
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>loop.currentItem</strong>: Current item being processed
+      </li>
+      <li>
+        <strong>loop.index</strong>: Current iteration number (0-based)
+      </li>
+      <li>
+        <strong>loop.items</strong>: Full collection (forEach loops)
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>loop.results</strong>: Array of all iteration results
+      </li>
+      <li>
+        <strong>Structure</strong>: Results maintain iteration order
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the loop
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Best Practices
+
+- **Set reasonable limits**: Keep iteration counts reasonable to avoid long execution times
+- **Use ForEach for collections**: When processing arrays or objects, use ForEach instead of For loops
+- **Handle errors gracefully**: Consider adding error handling inside loops for robust workflows

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

@@ -1,4 +1,15 @@
 {
   "title": "Blocks",
-  "pages": ["agent", "api", "condition", "function", "evaluator", "router", "response", "workflow"]
+  "pages": [
+    "agent",
+    "api",
+    "condition",
+    "evaluator",
+    "function",
+    "loop",
+    "parallel",
+    "response",
+    "router",
+    "workflow"
+  ]
 }

apps/docs/content/docs/blocks/parallel.mdx

@@ -0,0 +1,210 @@
+---
+title: Parallel
+description: Execute multiple blocks concurrently for faster workflow processing
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Parallel block is a container block in Sim that allows you to execute multiple instances of blocks concurrently.
+
+<ThemeImage
+  lightSrc="/static/light/parallel-light.png"
+  darkSrc="/static/dark/parallel-dark.png"
+  alt="Parallel Block"
+  width={500}
+  height={300}
+/>
+
+<Callout type="info">
+  Parallel blocks are container nodes that execute their contents multiple times simultaneously, unlike loops which execute sequentially.
+</Callout>
+
+## Overview
+
+The Parallel block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Distribute work</strong>: Process multiple items concurrently
+  </Step>
+  <Step>
+    <strong>Speed up execution</strong>: Run independent operations simultaneously
+  </Step>
+  <Step>
+    <strong>Handle bulk operations</strong>: Process large datasets efficiently
+  </Step>
+  <Step>
+    <strong>Aggregate results</strong>: Collect outputs from all parallel executions
+  </Step>
+</Steps>
+
+## Configuration Options
+
+### Parallel Type
+
+Choose between two types of parallel execution:
+
+<Tabs items={['Count-based', 'Collection-based']}>
+  <Tab>
+    Execute a fixed number of parallel instances. Use this when you need to run the same operation multiple times concurrently.
+    
+    ```
+    Example: Run 5 parallel instances
+    - Instance 1 ┐
+    - Instance 2 ├─ All execute simultaneously
+    - Instance 3 │
+    - Instance 4 │
+    - Instance 5 ┘
+    ```
+  </Tab>
+  <Tab>
+    Distribute a collection across parallel instances. Each instance processes one item from the collection simultaneously.
+    
+    ```
+    Example: Process ["task1", "task2", "task3"] in parallel
+    - Instance 1: Process "task1" ┐
+    - Instance 2: Process "task2" ├─ All execute simultaneously
+    - Instance 3: Process "task3" ┘
+    ```
+  </Tab>
+</Tabs>
+
+## How to Use Parallel Blocks
+
+### Creating a Parallel Block
+
+1. Drag a Parallel block from the toolbar onto your canvas
+2. Configure the parallel type and parameters
+3. Drag a single block inside the parallel container
+4. Connect the block as needed
+
+### Accessing Results
+
+After a parallel block completes, you can access aggregated results:
+
+- **`<parallel.results>`**: Array of results from all parallel instances
+
+## Example Use Cases
+
+### Batch API Processing
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Process multiple API calls simultaneously</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Parallel block with collection of API endpoints</li>
+    <li>Inside parallel: API block calls each endpoint</li>
+    <li>After parallel: Process all responses together</li>
+  </ol>
+</div>
+
+### Multi-Model AI Processing
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Get responses from multiple AI models</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Count-based parallel set to 3 instances</li>
+    <li>Inside parallel: Agent configured with different model per instance</li>
+    <li>After parallel: Compare and select best response</li>
+  </ol>
+</div>
+
+## Advanced Features
+
+### Result Aggregation
+
+Results from all parallel instances are automatically collected:
+
+```javascript
+// In a Function block after the parallel
+const allResults = input.parallel.results;
+// Returns: [result1, result2, result3, ...]
+```
+
+### Instance Isolation
+
+Each parallel instance runs independently:
+- Separate variable scopes
+- No shared state between instances
+- Failures in one instance don't affect others
+
+### Limitations
+
+<Callout type="warning">
+  Container blocks (Loops and Parallels) cannot be nested inside each other. This means:
+  - You cannot place a Loop block inside a Parallel block
+  - You cannot place another Parallel block inside a Parallel block
+  - You cannot place any container block inside another container block
+</Callout>
+
+<Callout type="warning">
+  Parallel blocks can only contain a single block. You cannot have multiple blocks connected to each other inside a parallel - only the first block would execute in that case.
+</Callout>
+
+<Callout type="info">
+  While parallel execution is faster, be mindful of:
+  - API rate limits when making concurrent requests
+  - Memory usage with large datasets
+  - Maximum of 20 concurrent instances to prevent resource exhaustion
+</Callout>
+
+## Parallel vs Loop
+
+Understanding when to use each:
+
+| Feature | Parallel | Loop |
+|---------|----------|------|
+| Execution | Concurrent | Sequential |
+| Speed | Faster for independent operations | Slower but ordered |
+| Order | No guaranteed order | Maintains order |
+| Use case | Independent operations | Dependent operations |
+| Resource usage | Higher | Lower |
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Parallel Type</strong>: Choose between 'count' or 'collection'
+      </li>
+      <li>
+        <strong>Count</strong>: Number of instances to run (count-based)
+      </li>
+      <li>
+        <strong>Collection</strong>: Array or object to distribute (collection-based)
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>parallel.currentItem</strong>: Item for this instance
+      </li>
+      <li>
+        <strong>parallel.index</strong>: Instance number (0-based)
+      </li>
+      <li>
+        <strong>parallel.items</strong>: Full collection (collection-based)
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>parallel.results</strong>: Array of all instance results
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the parallel
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Best Practices
+
+- **Independent operations only**: Ensure operations don't depend on each other
+- **Handle rate limits**: Add delays or throttling for API-heavy workflows
+- **Error handling**: Each instance should handle its own errors gracefully

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

@@ -8,38 +8,40 @@ import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 import { ThemeImage } from '@/components/ui/theme-image'
 
-The Response block is the final component in API-enabled workflows that transforms your workflow's variables into a structured HTTP response. This block serves as the endpoint that returns data, status codes, and headers back to API callers.
+The Response block is the final step in your workflow that formats and returns data to whoever called your workflow. It's like the "return" statement for your entire workflow—it packages up results and sends them back.
 
 <ThemeImage
   lightSrc="/static/light/response-light.png"
   darkSrc="/static/dark/response-dark.png"
-  alt="Response Block"
-  width={430}
-  height={784}
+  alt="Response Block Configuration"
+  width={350}
+  height={175}
 />
 
 <Callout type="info">
-  Response blocks are terminal blocks - they mark the end of a workflow execution and cannot have further connections.
+  Response blocks are terminal blocks - they end the workflow execution and cannot connect to other blocks.
 </Callout>
 
-## Overview
+## When You Need Response Blocks
 
-The Response block serves as the final output mechanism for API workflows, enabling you to:
+**API Endpoints**: When your workflow is called via API, Response blocks format the return data
+**Webhooks**: Return confirmation or data back to the calling system
+**Testing**: See formatted results when testing your workflow
+**Data Export**: Structure data for external systems or reports
 
-<Steps>
-  <Step>
-    <strong>Return structured data</strong>: Transform workflow variables into JSON responses
-  </Step>
-  <Step>
-    <strong>Set HTTP status codes</strong>: Control the response status (200, 400, 500, etc.)
-  </Step>
-  <Step>
-    <strong>Configure headers</strong>: Add custom HTTP headers to the response
-  </Step>
-  <Step>
-    <strong>Reference variables</strong>: Use workflow variables dynamically in the response
-  </Step>
-</Steps>
+## Two Ways to Build Responses
+
+### Builder Mode (Recommended)
+Visual interface for building response structure:
+- Drag and drop fields
+- Reference workflow variables easily
+- Visual preview of response structure
+
+### Editor Mode (Advanced)
+Write JSON directly:
+- Full control over response format
+- Support for complex nested structures
+- Use `<variable.name>` syntax for dynamic values
 
 ## Configuration Options
 
@@ -115,14 +117,9 @@ Headers are configured as key-value pairs:
   </Tab>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>response</strong>: Complete response object containing:
-        <ul className="list-disc space-y-1 pl-6 mt-2">
-          <li><strong>data</strong>: The response body data</li>
-          <li><strong>status</strong>: HTTP status code</li>
-          <li><strong>headers</strong>: Response headers</li>
-        </ul>
-      </li>
+      <li><strong>data</strong>: The response body data</li>
+      <li><strong>status</strong>: HTTP status code</li>
+      <li><strong>headers</strong>: Response headers</li>
     </ul>
   </Tab>
 </Tabs>
@@ -185,4 +182,5 @@ headers:
 - **Structure your responses consistently**: Maintain a consistent JSON structure across all your API endpoints for better developer experience
 - **Include relevant metadata**: Add timestamps and version information to help with debugging and monitoring
 - **Handle errors gracefully**: Use conditional logic in your workflow to set appropriate error responses with descriptive messages
-- **Validate variable references**: Ensure all referenced variables exist and contain the expected data types before the Response block executes
+- **Validate variable references**: Ensure all referenced variables exist and contain the expected data types before the Response block executes
+

apps/docs/content/docs/blocks/router.mdx

@@ -6,35 +6,74 @@ description: Route workflow execution based on specific conditions or logic
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
 import { ThemeImage } from '@/components/ui/theme-image'
+import { Video } from '@/components/ui/video'
 
-The Router block is a powerful component in Sim Studio that intelligently routes workflow execution based on content analysis, user input, or predefined conditions. It acts as a decision-making junction in your workflow, directing the flow to different paths based on various criteria.
+The Router block uses AI to intelligently decide which path your workflow should take next. Unlike Condition blocks that use simple rules, Router blocks can understand context and make smart routing decisions based on content analysis.
 
 <ThemeImage
   lightSrc="/static/light/router-light.png"
   darkSrc="/static/dark/router-dark.png"
-  alt="Router Block"
-  width={300}
+  alt="Router Block with Multiple Paths"
+  width={350}
   height={175}
 />
 
 ## Overview
 
-The Router block uses LLMs to analyze input content and determine the most appropriate next step in your workflow. This allows for:
+The Router block enables you to:
 
-- Creating dynamic, adaptable workflows
-- Implementing complex decision trees
-- Routing user requests to specialized components
-- Building conversational systems that can handle diverse inputs
+<Steps>
+  <Step>
+    <strong>Intelligent content routing</strong>: Use AI to understand intent and context
+  </Step>
+  <Step>
+    <strong>Dynamic path selection</strong>: Route workflows based on unstructured content analysis
+  </Step>
+  <Step>
+    <strong>Context-aware decisions</strong>: Make smart routing choices beyond simple rules
+  </Step>
+  <Step>
+    <strong>Multi-path management</strong>: Handle complex workflows with multiple potential destinations
+  </Step>
+</Steps>
+
+## Router vs Condition Blocks
+
+<Accordions>
+  <Accordion title="When to Use Router">
+    - AI-powered content analysis needed
+    - Unstructured or varying content types
+    - Intent-based routing (e.g., "route support tickets to departments")
+    - Context-aware decision making required
+  </Accordion>
+  <Accordion title="When to Use Condition">
+    - Simple, rule-based decisions
+    - Structured data or numeric comparisons
+    - Fast, deterministic routing needed
+    - Boolean logic sufficient
+  </Accordion>
+</Accordions>
 
 ## How It Works
 
 The Router block:
 
-1. Analyzes the input content using an LLM
-2. Evaluates the content against the available target blocks in your workflow
-3. Identifies the most appropriate destination based on the content's intent or requirements
-4. Routes the workflow execution to the selected block
+<Steps>
+  <Step>
+    <strong>Analyze content</strong>: Uses an LLM to understand input content and context
+  </Step>
+  <Step>
+    <strong>Evaluate targets</strong>: Compares content against available destination blocks
+  </Step>
+  <Step>
+    <strong>Select destination</strong>: Identifies the most appropriate path based on intent
+  </Step>
+  <Step>
+    <strong>Route execution</strong>: Directs workflow to the selected block
+  </Step>
+</Steps>
 
 ## Configuration Options
 
@@ -56,65 +95,165 @@ The possible destination blocks that the Router can select from. The Router will
 
 ### Model Selection
 
-Choose an LLM provider to power the routing decision:
+Choose an AI model to power the routing decision:
 
-- OpenAI (GPT-4o, o1, o3, o4-mini)
-- Anthropic (Claude 3.7 Sonnet)
-- Google (Gemini 2.5 Pro, Gemini 2.0 Flash)
-- Groq, Cerebras
-- Ollama Local Models
-- And more
+**OpenAI**: GPT-4o, o1, o3, o4-mini, gpt-4.1  \
+**Anthropic**: Claude 3.7 Sonnet \
+**Google**: Gemini 2.5 Pro, Gemini 2.0 Flash \
+**Other Providers**: Groq, Cerebras, xAI, DeepSeek \
+**Local Models**: Any model running on Ollama 
 
-Select a model with strong reasoning capabilities for more accurate routing decisions.
+<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
+  <Video src="router-model-dropdown.mp4" />
+</div>
+
+**Recommendation**: Use models with strong reasoning capabilities like GPT-4o or Claude 3.7 Sonnet for more accurate routing decisions.
 
 ### API Key
 
 Your API key for the selected LLM provider. This is securely stored and used for authentication.
 
-## Inputs and Outputs
+### Accessing Results
 
-### Inputs
+After a router makes a decision, you can access its outputs:
 
-- **Content/Prompt**: The text to analyze for routing decisions
-- **Target Blocks**: Connected blocks that are potential routing destinations
-- **Model Settings**: LLM provider and parameters
+- **`<router.content>`**: Summary of the routing decision made
+- **`<router.selected_path>`**: Details of the chosen destination block
+- **`<router.tokens>`**: Token usage statistics from the LLM
+- **`<router.model>`**: The model used for decision-making
 
-### Outputs
+## Advanced Features
 
-- **Content**: A summary of the routing decision
-- **Model**: The model used for decision-making
-- **Tokens**: Usage statistics
-- **Selected Path**: Details of the chosen routing destination, including:
-  - Block ID
-  - Block Type
-  - Block Title
+### Custom Routing Criteria
 
-## Example Usage
+Define specific criteria for each target block:
 
-Here's an example of how a Router block might be used in a customer support workflow:
-
-```yaml
-# Example Router Configuration
-prompt: |
-  Analyze the user query and route to the most appropriate department.
-  Choose ONE destination based on the query content and intent.
-
-model: OpenAI/gpt-4
+```javascript
+// Example routing descriptions
+Target Block 1: "Technical support issues, API problems, integration questions"
+Target Block 2: "Billing inquiries, subscription changes, payment issues"
+Target Block 3: "General questions, feedback, feature requests"
 ```
 
-In this example, the Router might be connected to:
+### Multi-Model Routing
 
-- A product support block
-- A billing inquiries block
-- A technical support block
-- A general inquiries block
+Use different models for different routing scenarios:
+
+```javascript
+// Fast routing for simple cases
+Model: GPT-4o-mini
+Criteria: Simple, common routing patterns
+
+// Complex routing for nuanced decisions
+Model: Claude 3.7 Sonnet
+Criteria: Complex content analysis required
+```
+
+### Fallback Handling
+
+Implement robust fallback mechanisms:
+
+```javascript
+// Router configuration
+Primary Targets: ["Support", "Sales", "Technical"]
+Fallback Target: "General" // Default when no specific match
+Confidence Threshold: 0.7 // Minimum confidence for routing
+```
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Content/Prompt</strong>: Text to analyze for routing decisions
+      </li>
+      <li>
+        <strong>Target Blocks</strong>: Connected blocks as potential destinations
+      </li>
+      <li>
+        <strong>Model</strong>: AI model for routing analysis
+      </li>
+      <li>
+        <strong>API Key</strong>: Authentication for selected LLM provider
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>router.content</strong>: Summary of routing decision
+      </li>
+      <li>
+        <strong>router.selected_path</strong>: Details of chosen destination
+      </li>
+      <li>
+        <strong>router.tokens</strong>: Token usage statistics
+      </li>
+      <li>
+        <strong>router.model</strong>: Model used for decision-making
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Routing Decision</strong>: Primary path selection result
+      </li>
+      <li>
+        <strong>Decision Context</strong>: Analysis summary and reasoning
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the router
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Example Use Cases
+
+### Customer Support Triage
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Route support tickets to specialized departments</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>User submits support request via form</li>
+    <li>Router analyzes ticket content and context</li>
+    <li>Technical issues → Engineering support agent</li>
+    <li>Billing questions → Finance support agent</li>
+  </ol>
+</div>
+
+### Content Classification
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Classify and route user-generated content</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>User submits content or feedback</li>
+    <li>Router analyzes content type and sentiment</li>
+    <li>Feature requests → Product team workflow</li>
+    <li>Bug reports → Technical support workflow</li>
+  </ol>
+</div>
+
+### Lead Qualification
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Route leads based on qualification criteria</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Lead information captured from form</li>
+    <li>Router analyzes company size, industry, and needs</li>
+    <li>Enterprise leads → Sales team with custom pricing</li>
+    <li>SMB leads → Self-service onboarding flow</li>
+  </ol>
+</div>
 
-Based on the user's query, the Router would analyze the content and direct it to the most appropriate specialized support block.
 
 ## Best Practices
 
-- **Provide clear descriptions for target blocks**: Help the Router understand when to select each destination
-- **Use specific routing criteria**: Define clear conditions for selecting each path
-- **Consider fallback paths**: Connect a default destination for when no specific path is appropriate
-- **Test with diverse inputs**: Ensure the Router handles various input types correctly
-- **Review routing decisions**: Monitor the Router's performance and refine as needed
+- **Provide clear target descriptions**: Help the Router understand when to select each destination with specific, detailed descriptions
+- **Use specific routing criteria**: Define clear conditions and examples for each path to improve accuracy
+- **Implement fallback paths**: Connect a default destination for when no specific path is appropriate
+- **Test with diverse inputs**: Ensure the Router handles various input types, edge cases, and unexpected content
+- **Monitor routing performance**: Review routing decisions regularly and refine criteria based on actual usage patterns
+- **Choose appropriate models**: Use models with strong reasoning capabilities for complex routing decisions

apps/docs/content/docs/blocks/workflow.mdx

@@ -71,12 +71,15 @@ Define the data to pass to the child workflow:
 - **Optional**: The input field is optional - child workflows can run without input data
 - **Type Preservation**: Variable types (strings, numbers, objects, etc.) are preserved when passed to the child workflow
 
-### Examples of Input References
+### Accessing Results
 
-- `<variable.customerData>` - Pass a workflow variable
-- `<dataProcessor.result>` - Pass the result from a previous block
-- `<start.input>` - Pass the original workflow input
-- `<apiCall.data.user>` - Pass a specific field from an API response
+After a workflow executes, you can access its outputs:
+
+- **`<workflow.response>`**: The complete output from the child workflow
+- **`<workflow.name>`**: The name of the executed child workflow
+- **`<workflow.success>`**: Boolean indicating successful completion
+- **`<workflow.error>`**: Error details if the workflow failed
+- **`<workflow.execution_time>`**: Time taken to execute the workflow
 
 ### Execution Context
 
@@ -100,132 +103,157 @@ To prevent infinite recursion and ensure system stability, the Workflow block in
 - **Timeout Protection**: Child workflows inherit timeout settings to prevent indefinite execution
 - **Resource Limits**: Memory and execution time limits apply to prevent resource exhaustion
 
+## Advanced Features
+
+### Dynamic Workflow Selection
+
+Select workflows dynamically based on runtime conditions:
+
+```javascript
+// In a Function block before the Workflow block
+const workflowId = <condition.result> ? 'premium-workflow' : 'standard-workflow';
+return { selectedWorkflow: workflowId };
+```
+
+### Error Handling and Fallbacks
+
+Implement robust error handling for child workflows:
+
+```javascript
+// In a Function block after the Workflow block
+if (!<workflow.success>) {
+  console.error('Child workflow failed:', <workflow.error>);
+  // Implement fallback logic
+  return { fallback: true, error: <workflow.error> };
+}
+return <workflow.response>;
+```
+
+### Workflow Chaining
+
+Chain multiple workflows together:
+
+```javascript
+// Pass output from one workflow to another
+Workflow 1 Input: <start.input>
+Workflow 2 Input: <workflow1.response>
+Workflow 3 Input: <workflow2.response>
+```
+
 ## Inputs and Outputs
 
-<Tabs items={['Inputs', 'Outputs']}>
+<Tabs items={['Configuration', 'Variables', 'Results']}>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>Workflow ID</strong>: The identifier of the workflow to execute
+        <strong>Workflow Selection</strong>: Choose which workflow to execute
       </li>
       <li>
-        <strong>Input Variable</strong>: Variable or block reference to pass to the child workflow (e.g., `<variable.name>` or `<block.field>`)
+        <strong>Input Data</strong>: Variable or block reference to pass to child workflow
+      </li>
+      <li>
+        <strong>Execution Context</strong>: Isolated environment with workspace resources
       </li>
     </ul>
   </Tab>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>Response</strong>: The complete output from the child workflow execution
+        <strong>workflow.response</strong>: Complete output from child workflow
       </li>
       <li>
-        <strong>Child Workflow Name</strong>: The name of the executed child workflow
+        <strong>workflow.name</strong>: Name of executed child workflow
       </li>
       <li>
-        <strong>Success Status</strong>: Boolean indicating whether the child workflow completed successfully
+        <strong>workflow.success</strong>: Boolean indicating completion status
       </li>
       <li>
-        <strong>Error Information</strong>: Details about any errors that occurred during execution
+        <strong>workflow.error</strong>: Error details if workflow failed
       </li>
       <li>
-        <strong>Execution Metadata</strong>: Information about execution time, resource usage, and performance
+        <strong>workflow.execution_time</strong>: Time taken to execute
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Workflow Response</strong>: Primary output from child workflow
+      </li>
+      <li>
+        <strong>Execution Status</strong>: Success status and error information
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the workflow
       </li>
     </ul>
   </Tab>
 </Tabs>
 
-## Example Usage
+## Example Use Cases
 
-Here's an example of how a Workflow block might be used to create a modular customer onboarding process:
+### Modular Customer Onboarding
 
-### Parent Workflow: Customer Onboarding
-```yaml
-# Main customer onboarding workflow
-blocks:
-  - type: workflow
-    name: "Validate Customer Data"
-    workflowId: "customer-validation-workflow"
-    input: "<variable.newCustomer>"
-  
-  - type: workflow
-    name: "Setup Customer Account"
-    workflowId: "account-setup-workflow"
-    input: "<Validate Customer Data.result>"
-  
-  - type: workflow
-    name: "Send Welcome Email"
-    workflowId: "welcome-email-workflow"
-    input: "<Setup Customer Account.result.accountDetails>"
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Break down complex onboarding into reusable components</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Main workflow receives customer data</li>
+    <li>Workflow block executes validation workflow</li>
+    <li>Workflow block executes account setup workflow</li>
+    <li>Workflow block executes welcome email workflow</li>
+  </ol>
+</div>
+
+### Microservice Architecture
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Create independent service workflows</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Payment processing workflow handles transactions</li>
+    <li>Inventory management workflow updates stock</li>
+    <li>Notification workflow sends confirmations</li>
+    <li>Main workflow orchestrates all services</li>
+  </ol>
+</div>
+
+### Conditional Processing
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Execute different workflows based on conditions</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Condition block evaluates user type</li>
+    <li>Enterprise users → Complex approval workflow</li>
+    <li>Standard users → Simple approval workflow</li>
+    <li>Free users → Basic processing workflow</li>
+  </ol>
+</div>
+
+### Example: Customer Validation Workflow
+
+```javascript title="validation-workflow.js"
+// Main workflow passes customer data to validation workflow
+const customerData = <start.input>;
+
+// Validation workflow processes the data
+const emailValid = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(customerData.email);
+const phoneValid = /^\+?[1-9]\d{1,14}$/.test(customerData.phone);
+
+return {
+  customer: customerData,
+  validation: {
+    email: emailValid,
+    phone: phoneValid,
+    overall: emailValid && phoneValid
+  }
+};
 ```
 
-### Child Workflow: Customer Validation
-```yaml
-# Reusable customer validation workflow
-# Access the input data using: start.input
-blocks:
-  - type: function
-    name: "Validate Email"
-    code: |
-      const customerData = start.input;
-      const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
-      return emailRegex.test(customerData.email);
-  
-  - type: api
-    name: "Check Credit Score"
-    url: "https://api.creditcheck.com/score"
-    method: "POST"
-    body: "<start.input>"
-```
-
-### Variable Reference Examples
-
-```yaml
-# Using workflow variables
-input: "<variable.customerInfo>"
-
-# Using block outputs
-  input: "<dataProcessor.cleanedData>"
-
-# Using nested object properties
-  input: "<apiCall.data.user.profile>"
-
-# Using array elements (if supported by the resolver)
-  input: "<listProcessor.items[0]>"
-```
-
-## Access Control and Permissions
-
-The Workflow block respects workspace permissions and access controls:
-
-- **Workspace Membership**: Only workflows within the same workspace can be executed
-- **Permission Inheritance**: Child workflows inherit the execution permissions of the parent workflow
-- **API Key Access**: Child workflows have access to the same API keys and environment variables as the parent
-- **User Context**: The execution maintains the original user context for audit and logging purposes
-
 ## Best Practices
 
-- **Keep workflows focused**: Design child workflows to handle specific, well-defined tasks
-- **Minimize nesting depth**: Avoid deeply nested workflow hierarchies for better maintainability
-- **Handle errors gracefully**: Implement proper error handling for child workflow failures
-- **Document dependencies**: Clearly document which workflows depend on others
-- **Version control**: Consider versioning strategies for workflows that are used as components
-- **Test independently**: Ensure child workflows can be tested and validated independently
-- **Monitor performance**: Be aware that nested workflows can impact overall execution time
-
-## Common Patterns
-
-### Microservice Architecture
-Break down complex business processes into smaller, focused workflows that can be developed and maintained independently.
-
-### Reusable Components
-Create library workflows for common operations like data validation, email sending, or API integrations that can be reused across multiple projects.
-
-### Conditional Execution
-Use workflow blocks within conditional logic to execute different business processes based on runtime conditions.
-
-### Parallel Processing
-Combine workflow blocks with parallel execution to run multiple child workflows simultaneously for improved performance.
-
-<Callout type="tip">
-  When designing modular workflows, think of each workflow as a function with clear inputs, outputs, and a single responsibility.
-</Callout> 
+- **Keep workflows focused**: Design child workflows to handle specific, well-defined tasks with clear inputs and outputs
+- **Minimize nesting depth**: Avoid deeply nested workflow hierarchies for better maintainability and performance
+- **Handle errors gracefully**: Implement proper error handling for child workflow failures and provide fallback mechanisms
+- **Document dependencies**: Clearly document which workflows depend on others and maintain dependency maps
+- **Test independently**: Ensure child workflows can be tested and validated independently from parent workflows
+- **Monitor performance**: Be aware that nested workflows can impact overall execution time and resource usage
+- **Use semantic naming**: Give workflows descriptive names that clearly indicate their purpose and functionality

apps/docs/content/docs/connections/basics.mdx

@@ -1,6 +1,6 @@
 ---
 title: Connection Basics
-description: Learn how connections work in Sim Studio
+description: Learn how connections work in Sim
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,7 +8,7 @@ import { Step, Steps } from 'fumadocs-ui/components/steps'
 
 ## How Connections Work
 
-Connections are the pathways that allow data to flow between blocks in your workflow. When you connect two blocks in Sim Studio, you're establishing a data flow relationship that defines how information passes from one block to another.
+Connections are the pathways that allow data to flow between blocks in your workflow. When you connect two blocks in Sim, you're establishing a data flow relationship that defines how information passes from one block to another.
 
 <Callout type="info">
   Each connection represents a directed relationship where data flows from a source block's output

apps/docs/content/docs/connections/data-structure.mdx

@@ -71,7 +71,6 @@ Different block types produce different output structures. Here's what you can e
     {
       "result": "Function return value",
       "stdout": "Console output",
-      "executionTime": 45
     }
     ```
 
@@ -79,14 +78,13 @@ Different block types produce different output structures. Here's what you can e
 
     - **result**: The return value of the function (can be any type)
     - **stdout**: Console output captured during function execution
-    - **executionTime**: Time taken to execute the function (in milliseconds)
 
   </Tab>
   <Tab>
     ```json
     {
       "content": "Evaluation summary",
-      "model": "gpt-4o",
+      "model": "gpt-5",
       "tokens": {
         "prompt": 120,
         "completion": 85,

apps/docs/content/docs/connections/index.mdx

@@ -6,6 +6,7 @@ description: Connect your blocks to one another.
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Card, Cards } from 'fumadocs-ui/components/card'
 import { ConnectIcon } from '@/components/icons'
+import { Video } from '@/components/ui/video'
 
 Connections are the pathways that allow data to flow between blocks in your workflow. They define how information is passed from one block to another, enabling you to create sophisticated, multi-step processes.
 
@@ -14,13 +15,13 @@ Connections are the pathways that allow data to flow between blocks in your work
   data moves through your system and how blocks interact with each other.
 </Callout>
 
-<div>
-  <video autoPlay loop muted playsInline className="w-full" src="/connections.mp4"></video>
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="connections.mp4" />
 </div>
 
 ## Connection Types
 
-Sim Studio supports different types of connections that enable various workflow patterns:
+Sim supports different types of connections that enable various workflow patterns:
 
 <Cards>
   <Card title="Connection Basics" href="/connections/basics">

apps/docs/content/docs/connections/tags.mdx

@@ -4,11 +4,12 @@ description: Using connection tags to reference data between blocks
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
+import { Video } from '@/components/ui/video'
 
 Connection tags are visual representations of the data available from connected blocks. They provide an easy way to reference outputs from previous blocks in your workflow.
 
-<div>
-  <video autoPlay loop muted playsInline className="w-full" src="/connections.mp4"></video>
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="connections.mp4" />
 </div>
 
 ### What Are Connection Tags?

apps/docs/content/docs/copilot/index.mdx

@@ -0,0 +1,94 @@
+---
+title: Copilot
+description: Build and edit workflows with Sim Copilot
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Card, Cards } from 'fumadocs-ui/components/card'
+import { MessageCircle, Package, Zap, Infinity as InfinityIcon, Brain, BrainCircuit } from 'lucide-react'
+
+Copilot is your in-editor assistant that helps you build, understand, and improve workflows. It can:
+
+- **Explain**: Answer questions about Sim and your current workflow
+- **Guide**: Suggest edits and best practices
+- **Edit**: Make changes to blocks, connections, and settings when you approve
+
+<Callout type="info">
+  Copilot is a Sim-managed service. For self-hosted deployments, generate a Copilot API key in the hosted app (sim.ai → Settings → Copilot)
+  1. Go to [sim.ai](https://sim.ai) → Settings → Copilot and generate a Copilot API key
+  2. Set `COPILOT_API_KEY` in your self-hosted environment to that value
+</Callout>
+
+## Modes
+
+<Cards>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <MessageCircle className="h-4 w-4 text-muted-foreground" />
+        Ask
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">
+      Q&A mode for explanations, guidance, and suggestions without making changes to your workflow.
+    </div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <Package className="h-4 w-4 text-muted-foreground" />
+        Agent
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">
+      Build-and-edit mode. Copilot proposes specific edits (add blocks, wire variables, tweak settings) and applies them when you approve.
+    </div>
+  </Card>
+</Cards>
+
+## Depth Levels
+
+<Cards>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <Zap className="h-4 w-4 text-muted-foreground" />
+        Fast
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">Quickest and cheapest. Best for small edits, simple workflows, and minor tweaks.</div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <InfinityIcon className="h-4 w-4 text-muted-foreground" />
+        Auto
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">Balanced speed and reasoning. Recommended default for most tasks.</div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <Brain className="h-4 w-4 text-muted-foreground" />
+        Advanced
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">More reasoning for larger workflows and complex edits while staying performant.</div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <BrainCircuit className="h-4 w-4 text-muted-foreground" />
+        Behemoth
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">Maximum reasoning for deep planning, debugging, and complex architectural changes.</div>
+  </Card>
+</Cards> 

apps/docs/content/docs/copilot/meta.json

@@ -0,0 +1,4 @@
+{
+  "title": "Copilot",
+  "pages": ["index"]
+}

apps/docs/content/docs/execution/advanced.mdx

@@ -1,280 +1,214 @@
 ---
-title: Advanced Execution Features
-description: Master advanced execution capabilities in Sim Studio
+title: Logging and Cost Calculation
+description: Understanding workflow logs and how execution costs are calculated in Sim
 ---
 
 import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
 
-Sim Studio provides several advanced features that give you more control over workflow execution, error handling, and performance optimization.
+Sim provides comprehensive logging for workflow executions and automatic cost calculation for AI model usage.
 
-## Error Handling
+## Logging System
 
-The execution engine includes built-in error handling mechanisms to make your workflows more robust:
+Sim offers two complementary logging interfaces:
 
-### Block-Level Error Handling
+### Real-Time Console (Manual Executions)
 
-Errors in one block don't necessarily stop the entire workflow execution:
+During manual workflow execution, logs appear in real-time in the Console panel on the right side of the workflow editor:
 
-```javascript
-// Example of error handling in a Function block
-try {
-  // Potentially risky operation
-  const result = JSON.parse(input.apiBlock.data);
-  return { success: true, data: result };
-} catch (error) {
-  // Handle the error gracefully
-  console.error("Failed to parse JSON:", error.message);
-  return {
-    success: false,
-    error: error.message,
-    fallbackData: { status: "error", message: "Could not process data" }
-  };
-}
-```
+<ThemeImage
+  lightSrc="/static/light/console-panel-light.png"
+  darkSrc="/static/dark/console-panel-dark.png"
+  alt="Real-time Console Panel"
+  width={600}
+  height={400}
+/>
 
-### Error Logging
+The console shows:
+- Block execution progress with active block highlighting
+- Real-time outputs as blocks complete
+- Execution timing for each block
+- Success/error status indicators
 
-Comprehensive error information is captured in the execution logs:
+### Logs Page (All Executions)
 
-- **Error Messages**: Clear descriptions of what went wrong
-- **Stack Traces**: Detailed information about where errors occurred
-- **Context Data**: The inputs that led to the error
-- **Timestamps**: When the error occurred
+All workflow executions—whether triggered manually, via API, Chat, Schedule, or Webhook—are logged to the dedicated Logs page:
 
-<Callout type="info">
-  Error logs are invaluable for debugging workflows. Always check the logs first when
-  troubleshooting execution issues.
-</Callout>
+<ThemeImage
+  lightSrc="/static/light/logs-page-light.png"
+  darkSrc="/static/dark/logs-page-dark.png"
+  alt="Logs Page"
+  width={600}
+  height={400}
+/>
 
-### Fallback Mechanisms
+The Logs page provides:
+- Comprehensive filtering by time range, status, trigger type, folder, and workflow
+- Search functionality across all logs
+- Live mode for real-time updates
+- 7-day log retention (upgradeable for longer retention)
 
-For certain operations, the system provides automatic fallbacks:
+## Log Details Sidebar
 
-- **Function Execution**: Freestyle execution first, then VM execution if needed
-- **API Requests**: Automatic retries for transient network errors
-- **Model Calls**: Fallback to alternative models if primary model is unavailable
+Clicking on any log entry opens a detailed sidebar view:
 
-### Recovery Options
+<ThemeImage
+  lightSrc="/static/light/logs-sidebar-light.png"
+  darkSrc="/static/dark/logs-sidebar-dark.png"
+  alt="Logs Sidebar Details"
+  width={600}
+  height={400}
+/>
 
-Configure blocks to handle failures gracefully:
+### Block Input/Output
 
-- **Retry Logic**: Automatically retry failed operations
-- **Default Values**: Provide fallback values when operations fail
-- **Alternative Paths**: Use conditional blocks to create error handling paths
-- **Graceful Degradation**: Continue execution with partial results
+View the complete data flow for each block with tabs to switch between:
 
-## Environment Variables
-
-Environment variables provide a secure way to store and access configuration values:
-
-### Types of Environment Variables
-
-<Tabs items={['API Keys', 'Configuration Values', 'Secrets']}>
+<Tabs items={['Output', 'Input']}>
   <Tab>
-    Store API credentials securely: ``` OPENAI_API_KEY=sk-... ANTHROPIC_API_KEY=sk-...
-    GOOGLE_API_KEY=AIza... ``` These are automatically available to blocks that need them, without
-    hardcoding sensitive values in your workflow.
+    **Output Tab** shows the block's execution result:
+    - Structured data with JSON formatting
+    - Markdown rendering for AI-generated content
+    - Copy button for easy data extraction
   </Tab>
-
-<Tab>
-  Manage environment-specific configuration: ``` MAX_RETRIES=3 DEFAULT_MODEL=gpt-4o LOG_LEVEL=info
-  BASE_URL=https://api.example.com ``` These values can be referenced in blocks to control behavior
-  without modifying the workflow itself.
-</Tab>
-
+  
   <Tab>
-    Store sensitive information securely: ``` DATABASE_PASSWORD=... JWT_SECRET=...
-    ENCRYPTION_KEY=... ``` These values are encrypted at rest and only decrypted during execution,
-    providing an extra layer of security.
+    **Input Tab** displays what was passed to the block:
+    - Resolved variable values
+    - Referenced outputs from other blocks
+    - Environment variables used
+    - API keys are automatically redacted for security
   </Tab>
 </Tabs>
 
-### Using Environment Variables
+### Execution Timeline
 
-Environment variables can be accessed in different ways depending on the block type:
+For workflow-level logs, view detailed execution metrics:
+- Start and end timestamps
+- Total workflow duration
+- Individual block execution times
+- Performance bottleneck identification
 
-```javascript
-// In Function blocks
-const apiKey = process.env.MY_API_KEY
-const maxRetries = parseInt(process.env.MAX_RETRIES || '3')
+### Model Breakdown
 
-// In API blocks (via connection tags)
-// URL: https://api.example.com?key=<env.MY_API_KEY>
+For workflows using AI blocks, expand the Model Breakdown section to see:
 
-// In Agent blocks (via connection tags)
-// System prompt: Use the model <env.DEFAULT_MODEL> for this task.
-```
+<ThemeImage
+  lightSrc="/static/light/model-breakdown-light.png"
+  darkSrc="/static/dark/model-breakdown-dark.png"
+  alt="Model Breakdown"
+  width={600}
+  height={400}
+/>
 
-<Callout type="warning">
-  Never hardcode sensitive information like API keys directly in your workflows. Always use
-  environment variables instead.
+- **Token Usage**: Input and output token counts for each model
+- **Cost Breakdown**: Individual costs per model and operation
+- **Model Distribution**: Which models were used and how many times
+- **Total Cost**: Aggregate cost for the entire workflow execution
+
+### Workflow Snapshot
+
+For any logged execution, click "View Snapshot" to see the exact workflow state at execution time:
+
+<ThemeImage
+  lightSrc="/static/light/workflow-snapshot-light.png"
+  darkSrc="/static/dark/workflow-snapshot-dark.png"
+  alt="Workflow Snapshot"
+  width={600}
+  height={400}
+/>
+
+The snapshot provides:
+- Frozen canvas showing the workflow structure
+- Block states and connections as they were during execution
+- Click any block to see its inputs and outputs
+- Useful for debugging workflows that have since been modified
+
+<Callout type="info">
+  Workflow snapshots are only available for executions after the enhanced logging system was introduced. Older migrated logs show a "Logged State Not Found" message.
 </Callout>
 
-## Real-Time Monitoring
+## Cost Calculation
 
-Sim Studio provides powerful real-time monitoring capabilities:
+Sim automatically calculates costs for all AI model usage:
+
+### How Costs Are Calculated
+
+Every workflow execution includes two cost components:
+
+**Base Execution Charge**: $0.001 per execution
+
+**AI Model Usage**: Variable cost based on token consumption
+```javascript
+modelCost = (inputTokens × inputPrice + outputTokens × outputPrice) / 1,000,000
+totalCost = baseExecutionCharge + modelCost
+```
+
+<Callout type="info">
+  AI model prices are per million tokens. The calculation divides by 1,000,000 to get the actual cost. Workflows without AI blocks only incur the base execution charge.
+</Callout>
+
+### Pricing Options
+
+<Tabs items={['Hosted Models', 'Bring Your Own API Key']}>
+  <Tab>
+    **Hosted Models** - Sim provides API keys with a 2.5x pricing multiplier:
+    
+    | Model | Base Price (Input/Output) | Hosted Price (Input/Output) |
+    |-------|---------------------------|----------------------------|
+    | GPT-4o | $2.50 / $10.00 | $6.25 / $25.00 |
+    | GPT-4.1 | $2.00 / $8.00 | $5.00 / $20.00 |
+    | o1 | $15.00 / $60.00 | $37.50 / $150.00 |
+    | o3 | $2.00 / $8.00 | $5.00 / $20.00 |
+    | Claude 3.5 Sonnet | $3.00 / $15.00 | $7.50 / $37.50 |
+    | Claude Opus 4.0 | $15.00 / $75.00 | $37.50 / $187.50 |
+    
+    *The 2.5x multiplier covers infrastructure and API management costs.*
+  </Tab>
+  
+  <Tab>
+    **Your Own API Keys** - Use any model at base pricing:
+    
+    | Provider | Models | Input / Output |
+    |----------|---------|----------------|
+    | Google | Gemini 2.5 | $0.15 / $0.60 |
+    | Deepseek | V3, R1 | $0.75 / $1.00 |
+    | xAI | Grok 4, Grok 3 | $5.00 / $25.00 |
+    | Groq | Llama 4 Scout | $0.40 / $0.60 |
+    | Cerebras | Llama 3.3 70B | $0.94 / $0.94 |
+    | Ollama | Local models | Free |
+    
+    *Pay providers directly with no markup*
+  </Tab>
+</Tabs>
+
+<Callout type="warning">
+  Pricing shown reflects rates as of July 14, 2025. Check provider documentation for current pricing.
+</Callout>
+
+### Cost Optimization
 
 <Accordions>
-  <Accordion title="Active Block Indicator">
-    The currently executing block is highlighted in the workflow editor, making it easy to follow
-    the execution flow in real-time. This visual indicator helps you understand exactly where in
-    your workflow the execution is currently happening.
+  <Accordion title="Model Selection">
+    Choose models based on task complexity. Simple tasks can use GPT-4.1-nano ($0.10/$0.40) while complex reasoning might need o1 or Claude Opus.
   </Accordion>
-
-<Accordion title="Live Logs Panel">
-  Execution logs appear in real-time in the logs panel on the right side. These logs include
-  detailed information about each block's execution, including inputs, outputs, execution time, and
-  any errors that occur. You can use these logs to debug your workflow and understand how data flows
-  between blocks.
-</Accordion>
-
-<Accordion title="Block States">
-  Each block's state (pending, executing, completed, or error) is visually indicated in the workflow
-  editor. This helps you quickly identify which blocks have executed successfully and which may have
-  encountered issues.
-</Accordion>
-
-  <Accordion title="Performance Metrics">
-    Detailed timing information shows how long each block takes to execute, helping you identify
-    performance bottlenecks in your workflow. The execution engine tracks start time, end time, and
-    total duration for both individual blocks and the entire workflow.
+  
+  <Accordion title="Prompt Engineering">
+    Well-structured, concise prompts reduce token usage without sacrificing quality.
+  </Accordion>
+  
+  <Accordion title="Local Models">
+    Use Ollama for non-critical tasks to eliminate API costs entirely.
   </Accordion>
 </Accordions>
 
-## Performance Optimization
+## Usage Monitoring
 
-Optimize your workflows for better performance:
+Monitor your usage and billing in Settings → Subscription:
 
-### Block Optimization
-
-- **Break Down Complex Blocks**: Split complex operations into multiple simpler blocks
-- **Minimize External Calls**: Batch API requests where possible
-- **Cache Results**: Use Memory blocks to store and reuse results
-- **Optimize Function Code**: Write efficient JavaScript/TypeScript code
-
-### Data Flow Optimization
-
-- **Filter Data Early**: Process only the data you need as early as possible
-- **Minimize Data Transfer**: Pass only necessary fields between blocks
-- **Use Appropriate Data Structures**: Choose efficient data structures for your use case
-- **Avoid Redundant Computations**: Don't recalculate values that haven't changed
-
-### Execution Configuration
-
-- **Set Appropriate Timeouts**: Configure timeouts based on expected execution time
-- **Limit Parallel Executions**: Control how many workflows can run simultaneously
-- **Schedule During Off-Peak Hours**: Run resource-intensive workflows when system load is lower
-- **Monitor Resource Usage**: Keep an eye on memory and CPU usage
-
-<Callout type="info">
-  Performance optimization is especially important for workflows that run frequently or process
-  large amounts of data.
-</Callout>
-
-## Advanced Execution Context
-
-The execution context maintains detailed information about the workflow execution:
-
-```javascript
-// Example of execution context structure (simplified)
-{
-  // Block states indexed by block ID
-  blockStates: {
-    "block-1": { output: { content: "..." }, status: "completed" },
-    "block-2": { output: { data: { ... } }, status: "completed" },
-    "block-3": { status: "pending" }
-  },
-
-  // Active execution path
-  activeExecutionPath: Set(["block-1", "block-2", "block-5"]),
-
-  // Routing decisions
-  decisions: {
-    router: Map(["router-1" => "block-5"]),
-    condition: Map(["condition-1" => "condition-true"])
-  },
-
-  // Loop iterations
-  loopIterations: Map(["loop-1" => 2]),
-
-  // Environment variables
-  env: { "API_KEY": "...", "MAX_RETRIES": "3" },
-
-  // Execution logs
-  logs: [
-    { blockId: "block-1", timestamp: "...", status: "completed", duration: 120 },
-    { blockId: "block-2", timestamp: "...", status: "completed", duration: 85 }
-  ]
-}
-```
-
-This context is used internally by the execution engine but understanding its structure can help you debug complex workflows.
-
-## Debugging Techniques
-
-Advanced techniques for debugging workflow execution:
-
-### Console Logging
-
-Add strategic console.log statements in Function blocks:
-
-```javascript
-console.log('Input to processData:', JSON.stringify(input, null, 2))
-console.log('Processing step 1 complete:', intermediateResult)
-console.log('Final result:', finalResult)
-```
-
-### State Inspection
-
-Use Function blocks to inspect the current state:
-
-```javascript
-function debugState() {
-  // Log all inputs
-  console.log('All inputs:', input)
-
-  // Return a debug object with relevant information
-  return {
-    debug: true,
-    inputSummary: {
-      hasUserData: !!input.userBlock,
-      apiStatus: input.apiBlock?.status,
-      itemCount: input.dataBlock?.items?.length || 0,
-    },
-    timestamp: new Date().toISOString(),
-  }
-}
-```
-
-### Execution Tracing
-
-Enable detailed execution tracing for complex workflows:
-
-1. Add a Memory block to accumulate trace information
-2. Add trace logging in key Function blocks
-3. Review the trace after execution to understand the flow
-
-### Performance Profiling
-
-Identify performance bottlenecks:
-
-```javascript
-function profileOperation() {
-  const start = performance.now()
-
-  // Perform the operation
-  const result = performExpensiveOperation()
-
-  const end = performance.now()
-  console.log(`Operation took ${end - start}ms`)
-
-  return {
-    result,
-    executionTime: end - start,
-  }
-}
-```
-
-By mastering these advanced execution features, you can create more robust, efficient, and sophisticated workflows in Sim Studio.
+- **Current Usage**: Real-time usage and costs for the current period
+- **Usage Limits**: Plan limits with visual progress indicators
+- **Billing Details**: Projected charges and minimum commitments
+- **Plan Management**: Upgrade options and billing history

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

@@ -1,12 +1,13 @@
 ---
 title: Execution Basics
-description: Understanding the fundamental execution flow in Sim Studio
+description: Understanding the fundamental execution flow in Sim
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
 import { File, Files, Folder } from 'fumadocs-ui/components/files'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
 import {
   AgentIcon,
   ApiIcon,
@@ -14,44 +15,38 @@ import {
   CodeIcon,
   ConditionalIcon,
   ConnectIcon,
+  ResponseIcon,
+  StarterIcon,
+  LoopIcon,
+  ParallelIcon,
 } from '@/components/icons'
+import { Video } from '@/components/ui/video'
 
-When you run a workflow in Sim Studio, the execution engine follows a systematic process to ensure blocks are executed in the correct order and data flows properly between them.
+When you run a workflow in Sim, the execution engine follows a systematic process to ensure blocks are executed in the correct order with proper data flow.
 
 ## Execution Flow
 
-The execution of a workflow follows these key steps:
+The execution engine runs workflows in layers, processing blocks based on their dependencies:
 
 <Steps>
   <Step>
-    ### Validation Before execution begins, the workflow is validated to ensure it has: - An enabled
-    starter block with no incoming connections - Properly connected blocks with valid configurations
-    - No circular dependencies (except in intentional loops) - Valid input and output types between
-    connected blocks
+    <strong>Validation</strong>: Ensures the workflow has a starter block with no incoming connections and all blocks are properly connected.
   </Step>
 
-<Step>
-  ### Initialization The execution context is created, which includes: - Environment variables for
-  the workflow - Input values from the starter block - Initial state for all blocks - Execution path
-  tracking - Loop iteration counters
-</Step>
-
-<Step>
-  ### Block Execution Blocks are executed in topological order (based on dependencies): - The system
-  identifies which blocks can be executed next - Inputs for each block are resolved from previous
-  block outputs - Each block is executed by its specialized handler - Outputs are stored in the
-  execution context
-</Step>
-
-<Step>
-  ### Path Determination As execution progresses, the system determines which paths to follow: -
-  Router and conditional blocks make decisions about execution paths - Only blocks on active paths
-  are executed - The path tracker maintains the current execution state
-</Step>
+  <Step>
+    <strong>Layer-based Execution</strong>: Identifies which blocks can execute next based on completed dependencies and executes them in parallel.
+  </Step>
 
   <Step>
-    ### Result Collection After all blocks have executed: - Final outputs are collected - Execution
-    logs are compiled - Performance metrics are calculated - Results are presented in the UI
+    <strong>Path Updates</strong>: Router and Condition blocks update the active execution path, determining which blocks execute next.
+  </Step>
+
+  <Step>
+    <strong>Iteration Processing</strong>: Loop and Parallel blocks manage iterations and create virtual instances for concurrent execution.
+  </Step>
+
+  <Step>
+    <strong>Result Collection</strong>: Outputs from the final blocks are collected and returned as the workflow result.
   </Step>
 </Steps>
 
@@ -66,7 +61,7 @@ Different block types have different execution behaviors:
       <Files>
         <File
           name="Starter Block"
-          icon={<ConnectIcon className="h-4 w-4" />}
+          icon={<StarterIcon className="h-4 w-4" />}
           annotation="Initiates workflow execution and provides initial input values. Every workflow must have exactly one starter block."
         />
         <File
@@ -79,6 +74,16 @@ Different block types have different execution behaviors:
           icon={<ConditionalIcon className="h-4 w-4" />}
           annotation="Executes different paths based on conditional logic. Evaluates JavaScript expressions to determine which path to follow."
         />
+        <File
+          name="Loop Block"
+          icon={<LoopIcon className="h-4 w-4" />}
+          annotation="Executes blocks repeatedly for a fixed number of iterations or over a collection. Manages iteration state and provides access to current item."
+        />
+        <File
+          name="Parallel Block"
+          icon={<ParallelIcon className="h-4 w-4" />}
+          annotation="Executes blocks concurrently across multiple instances. Distributes work based on count or collection for faster processing."
+        />
       </Files>
     </Card>
   </Tab>
@@ -102,6 +107,11 @@ Different block types have different execution behaviors:
         icon={<ChartBarIcon className="h-4 w-4" />}
         annotation="Assesses outputs against defined criteria. Uses AI to evaluate content based on custom metrics."
       />
+      <File
+        name="Workflow Block"
+        icon={<ConnectIcon className="h-4 w-4" />}
+        annotation="Execute nested workflows as a single block. Allows modular workflow design by embedding one workflow inside another."
+      />
     </Files>
   </Card>
 </Tab>
@@ -115,6 +125,21 @@ Different block types have different execution behaviors:
           icon={<ApiIcon className="h-4 w-4" />}
           annotation="Makes HTTP requests to external services. Configurable with headers, body, and authentication."
         />
+        <File
+          name="Knowledge Base Block"
+          icon={
+            <svg className="h-4 w-4" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
+              <path d="M12 2L3 9V20C3 20.55 3.45 21 4 21H9V14H15V21H20C20.55 21 21 20.55 21 20V9L12 2Z" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round"/>
+              <circle cx="12" cy="10" r="2" stroke="currentColor" strokeWidth="2"/>
+            </svg>
+          }
+          annotation="Search and interact with knowledge bases. Performs semantic search, retrieves documents, and manages knowledge data."
+        />
+        <File
+          name="Response Block"
+          icon={<ResponseIcon className="h-4 w-4" />}
+          annotation="Format and return responses from workflows. Configure response data, status codes, and headers."
+        />
         <File
           name="Tool Blocks"
           icon={<CodeIcon className="h-4 w-4" />}
@@ -127,16 +152,20 @@ Different block types have different execution behaviors:
 
 ## Execution Methods
 
-Sim Studio offers multiple ways to trigger workflow execution:
+Sim offers multiple ways to trigger workflow execution:
 
 ### Manual Execution
 
-Run workflows on-demand through the Sim Studio interface by clicking the "Run" button. This is perfect for:
+Run workflows on-demand through the Sim interface by clicking the "Run" button. This is perfect for:
 
 - Testing during development
 - One-off tasks
 - Workflows that need human supervision
 
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="input-format.mp4" />
+</div>
+
 ### Scheduled Execution
 
 Configure workflows to run automatically on a specified schedule:
@@ -146,6 +175,10 @@ Configure workflows to run automatically on a specified schedule:
 - Configure timezone settings
 - Set minimum and maximum execution intervals
 
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="configure-schedule.mp4" />
+</div>
+
 ### API Endpoints
 
 Each workflow can be exposed as an API endpoint:
@@ -155,6 +188,20 @@ Each workflow can be exposed as an API endpoint:
 - Send custom inputs via POST requests
 - Receive execution results as JSON responses
 
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="api-deployment.mp4" />
+</div>
+
+#### Viewing Deployed APIs
+
+Monitor your deployed workflow APIs and their current state:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="api-redeployment.mp4" />
+</div>
+
+This shows how to view the deployed state and compare with the original deployed API configuration.
+
 ### Webhooks
 
 Configure workflows to execute in response to external events:
@@ -164,6 +211,10 @@ Configure workflows to execute in response to external events:
 - Configure webhook security settings
 - Support for specialized webhooks (GitHub, Stripe, etc.)
 
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="webhooks.mp4" />
+</div>
+
 <Callout type="info">
   The execution method you choose depends on your workflow's purpose. Manual execution is great for
   development, while scheduled execution, API endpoints, and webhooks are better for production use
@@ -172,29 +223,21 @@ Configure workflows to execute in response to external events:
 
 ## Execution Context
 
-Each workflow execution maintains a detailed context that includes:
+Each workflow execution maintains a context that tracks:
 
 - **Block States**: Outputs and execution status of each block
-- **Execution Path**: The active path through the workflow
-- **Routing Decisions**: Records of which paths were selected
-- **Environment Variables**: Configuration values for the workflow
-- **Execution Logs**: Detailed records of each step in the execution
+- **Execution Path**: Active blocks based on routing decisions
+- **Loop/Parallel State**: Current iterations and distribution items
+- **Environment Variables**: Configuration values available during execution
+- **Execution Logs**: Detailed records of each block's execution
 
-This context is maintained throughout the execution and is used to:
+## Real-Time Monitoring
 
-- Resolve inputs for blocks
-- Determine which blocks to execute next
-- Track the progress of execution
-- Provide debugging information
-- Store intermediate results
+Monitor your workflow execution in real-time:
 
-## Real-Time Execution Monitoring
+- **Active Block Highlighting**: Currently executing blocks pulse with animation
+- **Live Logs**: Execution logs appear instantly in the logs panel
+- **Block States**: Visual indicators show success, error, or pending states
+- **Performance Metrics**: Execution time for each block
 
-As your workflow executes, you can monitor its progress in real-time:
-
-- **Active Block Highlighting**: The currently executing block is highlighted
-- **Live Logs**: Execution logs appear in real-time in the logs panel
-- **Block States**: Visual indicators show each block's execution state
-- **Performance Metrics**: Timing information for each block's execution
-
-These monitoring features help you understand how your workflow is executing and identify any issues that arise.
+These monitoring features help you understand workflow behavior and quickly identify any issues.

apps/docs/content/docs/execution/index.mdx

@@ -1,41 +1,18 @@
 ---
 title: Execution
-description: Understand how workflows are executed in Sim Studio
+description: Understand how workflows are executed in Sim
 ---
 
-import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Card, Cards } from 'fumadocs-ui/components/card'
-import { File, Files, Folder } from 'fumadocs-ui/components/files'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import {
-  AgentIcon,
-  ApiIcon,
-  ChartBarIcon,
-  CodeIcon,
-  ConditionalIcon,
-  ConnectIcon,
-  ExaAIIcon,
-  FirecrawlIcon,
-  GmailIcon,
-  NotionIcon,
-  PerplexityIcon,
-  SlackIcon,
-} from '@/components/icons'
 
-Sim Studio provides a powerful execution engine that brings your workflows to life. Understanding how execution works will help you design more effective workflows and troubleshoot any issues that arise.
-
-<div>
-  <video autoPlay loop muted playsInline className="w-full" src="/loops.mp4"></video>
-</div>
+Sim's execution engine brings your workflows to life by processing blocks in the correct order, managing data flow, and handling errors gracefully.
 
 <Callout type="info">
-  The execution engine handles everything from block execution order to data flow, error handling,
-  and loop management. It ensures your workflows run efficiently and predictably.
+  Every workflow execution follows a deterministic path based on your block connections and logic, ensuring predictable and reliable results.
 </Callout>
 
-## Execution Documentation
+## Documentation Overview
 
 <Cards>
   <Card title="Execution Basics" href="/execution/basics">
@@ -43,223 +20,109 @@ Sim Studio provides a powerful execution engine that brings your workflows to li
     workflow
   </Card>
 
-<Card title="Loops" href="/execution/loops">
-  Master the powerful loop functionality to create iterative processes and feedback mechanisms
-</Card>
-
-  <Card title="Advanced Features" href="/execution/advanced">
-    Discover advanced capabilities like error handling, environment variables, and performance
-    optimization
+  <Card title="Logging and Cost Calculation" href="/execution/advanced">
+    Understand workflow logs and how execution costs are calculated in Sim
   </Card>
 </Cards>
 
-## Key Execution Concepts
+## Key Concepts
 
-- **Topological Execution** - Blocks are executed in dependency order, ensuring data flows correctly
-- **Path Tracking** - The system tracks active execution paths based on routing decisions
-- **Loop Management** - Sophisticated loop handling allows for iterative processing with safeguards
-- **Real-time Monitoring** - Watch your workflow execute with detailed logs and visual indicators
-- **Error Handling** - Robust error management keeps your workflows resilient
+### Topological Execution
+Blocks execute in dependency order, similar to how a spreadsheet recalculates cells. The execution engine automatically determines which blocks can run based on completed dependencies.
 
-Whether you're building simple automations or complex AI workflows, understanding execution is key to creating effective solutions in Sim Studio.
+### Path Tracking
+The engine actively tracks execution paths through your workflow. Router and Condition blocks dynamically update these paths, ensuring only relevant blocks execute.
 
-## Execution Flow
+### Layer-Based Processing
+Instead of executing blocks one-by-one, the engine identifies layers of blocks that can run in parallel, optimizing performance for complex workflows.
 
-When you execute a workflow in Sim Studio, the system follows a predictable pattern:
+### Execution Context
+Each workflow maintains a rich context during execution containing:
+- Block outputs and states
+- Active execution paths
+- Loop and parallel iteration tracking
+- Environment variables
+- Routing decisions
 
-<Steps>
-  <Step>
-    ### Validation The workflow is validated to ensure it has an enabled starter block and proper
-    connections. This includes checking that: - The starter block has no incoming connections - All
-    required blocks are present and properly connected - Loop configurations are valid with
-    appropriate iteration limits
-  </Step>
+## Execution Triggers
 
-<Step>
-  ### Initialization The execution context is created with environment variables and input values.
-  This context maintains the state of the workflow throughout execution, including: - Block outputs
-  and states - Execution path tracking - Routing decisions - Loop iteration counters
-</Step>
+Workflows can be executed through multiple channels:
 
-<Step>
-  ### Block Execution Blocks are executed in topological order, with each block's outputs feeding
-  into subsequent blocks. The executor: - Determines the next layer of blocks to execute based on
-  dependencies - Resolves inputs for each block from previous outputs - Dispatches execution to
-  specialized handlers for each block type
-</Step>
+- **Manual**: Test and debug directly in the editor
+- **Deploy as API**: Create an HTTP endpoint secured with API keys
+- **Deploy as Chat**: Create a conversational interface on a custom subdomain
+- **Webhooks**: Respond to external events from third-party services
+- **Scheduled**: Run on a recurring schedule using cron expressions
 
-<Step>
-  ### Path Determination Router and conditional blocks make routing decisions that determine which
-  execution paths to follow. The path tracker: - Updates the active execution path based on these
-  decisions - Ensures that only blocks on active paths are executed - Handles complex branching
-  logic in your workflow
-</Step>
+### Deploy as API
 
-  <Step>
-    ### Result Collection The final output and execution logs are collected and presented in the UI.
-    You'll see: - Complete execution logs for each block - Performance metrics and timing
-    information - Any errors that occurred during execution - The final workflow output
-  </Step>
-</Steps>
+When you deploy a workflow as an API, Sim:
+- Creates a unique HTTP endpoint: `https://sim.ai/api/workflows/{workflowId}/execute`
+- Generates an API key for authentication
+- Accepts POST requests with JSON payloads
+- Returns workflow execution results as JSON
 
-## Block Types
+Example API call:
+```bash
+curl -X POST https://sim.ai/api/workflows/your-workflow-id/execute \
+  -H "X-API-Key: your-api-key" \
+  -H "Content-Type: application/json" \
+  -d '{"input": "your data here"}'
+```
 
-Sim Studio has two main categories of blocks in workflows:
+### Deploy as Chat
 
-<Tabs items={['Orchestration Blocks', 'Output Blocks']}>
-  <Tab value="Orchestration Blocks">
-    <Card>
-      Orchestration blocks control the flow of execution through your workflow.
-      <Files>
-        <File
-          name="Router Blocks"
-          icon={<ConnectIcon className="h-4 w-4" />}
-          annotation="Direct the workflow along specific paths based on dynamic decisions. The router evaluates inputs and selects one of multiple possible paths."
-        />
-        <File
-          name="Conditional Blocks"
-          icon={<ConditionalIcon className="h-4 w-4" />}
-          annotation="Execute different paths based on conditional logic. Conditions are evaluated to true or false, determining which path to follow."
-        />
-      </Files>
-    </Card>
-  </Tab>
+Chat deployment creates a conversational interface for your workflow:
+- Hosted on a custom subdomain: `https://your-name.sim.ai`
+- Optional authentication (public, password, or email-based)
+- Customizable UI with your branding
+- Streaming responses for real-time interaction
+- Perfect for AI assistants, support bots, or interactive tools
 
-  <Tab value="Output Blocks">
-    <Card>
-      Output blocks perform operations and generate results that can be used by downstream blocks.
-      <Files>
-        <File
-          name="Agent Block"
-          icon={<AgentIcon className="h-4 w-4" />}
-          annotation="Interact with AI models to generate content. Supports various LLM providers with optional tool calling capabilities."
-        />
-        <File
-          name="Function Blocks"
-          icon={<CodeIcon className="h-4 w-4" />}
-          annotation="Execute custom JavaScript/TypeScript code to process data. Runs in a secure sandbox environment with appropriate timeout limits."
-        />
-        <File
-          name="API Blocks"
-          icon={<ApiIcon className="h-4 w-4" />}
-          annotation="Make HTTP requests to external services. Configure headers, body, and authentication for REST API interactions."
-        />
-        <File
-          name="Evaluator Blocks"
-          icon={<ChartBarIcon className="h-4 w-4" />}
-          annotation="Assess outputs against defined criteria with customizable scoring logic."
-        />
-      </Files>
-    </Card>
-  </Tab>
-</Tabs>
+Each deployment method passes data to your workflow's starter block, beginning the execution flow.
 
-## Real-Time Monitoring
+## Programmatic Execution
 
-As your workflow executes, Sim Studio provides powerful real-time monitoring capabilities:
+Execute workflows from your applications using our official SDKs:
 
-<Accordions>
-  <Accordion title="Active Block Indicator">
-    The currently executing block is highlighted in the workflow editor, making it easy to follow
-    the execution flow in real-time. This visual indicator helps you understand exactly where in
-    your workflow the execution is currently happening.
-  </Accordion>
+```bash
+# TypeScript/JavaScript
+npm install simstudio-ts-sdk
 
-<Accordion title="Live Logs Panel">
-  Execution logs appear in real-time in the logs panel on the right side. These logs include
-  detailed information about each block's execution, including inputs, outputs, execution time, and
-  any errors that occur. You can use these logs to debug your workflow and understand how data flows
-  between blocks.
-</Accordion>
+# Python
+pip install simstudio-sdk
+```
 
-<Accordion title="Block States">
-  Each block's state (pending, executing, completed, or error) is visually indicated in the workflow
-  editor. This helps you quickly identify which blocks have executed successfully and which may have
-  encountered issues.
-</Accordion>
+```typescript
+// TypeScript Example
+import { SimStudioClient } from 'simstudio-ts-sdk';
 
-  <Accordion title="Performance Metrics">
-    Detailed timing information shows how long each block takes to execute, helping you identify
-    performance bottlenecks in your workflow. The execution engine tracks start time, end time, and
-    total duration for both individual blocks and the entire workflow.
-  </Accordion>
-</Accordions>
+const client = new SimStudioClient({ 
+  apiKey: 'your-api-key' 
+});
 
-## Execution Methods
+const result = await client.executeWorkflow('workflow-id', {
+  input: { message: 'Hello' }
+});
+```
 
-Sim Studio offers multiple ways to trigger workflow execution:
+## Best Practices
 
-<Cards>
-  <Card title="Manual Execution" href="#">
-    Run workflows on-demand through the Sim Studio interface. This is perfect for testing and
-    development, allowing you to iteratively refine your workflow with immediate feedback.
-  </Card>
+### Design for Reliability
+- Handle errors gracefully with appropriate fallback paths
+- Use environment variables for sensitive data
+- Add logging to Function blocks for debugging
 
-<Card title="Scheduled Execution" href="#">
-  Configure workflows to run automatically on a specified schedule using cron expressions. Ideal for
-  regular data processing, reporting tasks, or any workflow that needs to run periodically without
-  manual intervention.
-</Card>
+### Optimize Performance
+- Minimize external API calls where possible
+- Use parallel execution for independent operations
+- Cache results with Memory blocks when appropriate
 
-<Card title="API Endpoints" href="#">
-  Each workflow can be exposed as an API endpoint with authentication, allowing external systems to
-  trigger execution with custom inputs. This enables seamless integration with your existing
-  applications and services.
-</Card>
+### Monitor Executions
+- Review logs regularly to understand performance patterns
+- Track costs for AI model usage
+- Use workflow snapshots to debug issues
 
-  <Card title="Webhooks" href="#">
-    Configure workflows to execute in response to external events via webhook triggers. This allows
-    your workflows to react to events from third-party services like GitHub, Stripe, or any platform
-    that supports webhooks.
-  </Card>
-</Cards>
+## What's Next?
 
-## Advanced Execution Features
-
-### Loops
-
-Sim Studio supports sophisticated loop constructs, allowing parts of your workflow to execute repeatedly:
-
-- **Iteration Limits** - Configure maximum iterations (default: 5) to prevent infinite loops and minimum iterations to ensure the loop executes a certain number of times.
-- **Conditional Looping** - Continue looping until specific conditions are met, with the loop manager tracking iteration counts.
-- **Loop Reset** - Automatically resets block states between iterations, allowing blocks to be re-executed with updated inputs.
-- **Feedback Paths** - Create feedback loops where outputs from later blocks feed back into earlier blocks in the workflow.
-
-### Error Handling
-
-The execution engine includes built-in error handling mechanisms:
-
-- **Block-Level Errors** - Errors in one block don't necessarily stop the entire workflow execution.
-- **Detailed Error Logs** - Comprehensive error information is captured in the execution logs, including error messages, stack traces, and relevant context.
-- **Fallback Mechanisms** - For function execution, the system tries Freestyle execution first, then falls back to VM execution if needed.
-- **Recovery Options** - Configure blocks to retry on failure or implement custom error handling logic.
-
-### Environment Variables
-
-Use environment variables to securely store and access sensitive information:
-
-- **API Keys** - Store API credentials securely without hardcoding them in your workflow.
-- **Configuration Values** - Manage environment-specific configuration values.
-- **Runtime Availability** - All environment variables are available to blocks during execution.
-- **Secure Storage** - Values are encrypted at rest and only decrypted during execution.
-
-## Execution Context
-
-Each workflow execution maintains a detailed context that includes:
-
-- **Block States** - Outputs and execution status of each block, indexed by block ID.
-- **Execution Path** - The active path through the workflow based on routing decisions.
-- **Routing Decisions** - Records which paths were selected by router and conditional blocks.
-- **Loop Iterations** - Tracks current iteration count for each loop in the workflow.
-- **Environment Variables** - Configuration values available to all blocks during execution.
-- **Execution Logs** - A chronological record of block executions with timing information.
-
-## Performance Considerations
-
-- **Block Complexity** - Complex blocks with heavy computation may take longer to execute. Consider breaking complex operations into multiple blocks.
-- **External Dependencies** - Blocks that rely on external services may be affected by network latency or service availability.
-- **Execution Layers** - The executor processes blocks in layers based on dependencies, which can affect overall execution time.
-- **Code Optimization** - For function blocks, optimize your code to reduce execution time and resource usage.
-- **Timeout Limits** - Function blocks have configurable timeout limits to prevent long-running operations from blocking execution.
-
-By understanding these execution principles, you can design more efficient and effective workflows in Sim Studio.
+Start with [Execution Basics](/execution/basics) to understand how workflows run, then explore [Logging and Cost Calculation](/execution/advanced) to monitor and optimize your executions.

apps/docs/content/docs/execution/loops.mdx

@@ -1,214 +0,0 @@
----
-title: Loops
-description: Creating iterative processes with loops in Sim Studio
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-
-Loops are a powerful feature in Sim Studio that allow you to create iterative processes, implement feedback mechanisms, and build more sophisticated workflows.
-
-<div>
-  <video autoPlay loop muted playsInline className="w-full" src="/loops.mp4"></video>
-</div>
-
-## What Are Loops?
-
-Loops in Sim Studio allow a group of blocks to execute repeatedly, with each iteration building on the results of the previous one. This enables:
-
-- **Iterative Refinement**: Progressively improve outputs through multiple passes
-- **Batch Processing**: Process collections of items one at a time
-- **Feedback Mechanisms**: Create systems that learn from their own outputs
-- **Conditional Processing**: Continue execution until specific criteria are met
-
-<Callout type="info">
-  Loops are particularly powerful for AI workflows, allowing you to implement techniques like
-  chain-of-thought reasoning, recursive refinement, and multi-step problem solving.
-</Callout>
-
-## Creating Loops
-
-To create a loop in your workflow:
-
-<Steps>
-  <Step>
-    <strong>Select Blocks</strong>: Choose the blocks you want to include in the loop
-  </Step>
-  <Step>
-    <strong>Create Loop</strong>: Use the "Create Loop" option in the editor
-  </Step>
-  <Step>
-    <strong>Configure Loop Settings</strong>: Set iteration limits and conditions
-  </Step>
-  <Step>
-    <strong>Create Feedback Connections</strong>: Connect outputs from later blocks back to earlier
-    blocks
-  </Step>
-</Steps>
-
-## Loop Configuration
-
-When configuring a loop, you can set several important parameters:
-
-### Iteration Limits
-
-- **Maximum Iterations**: The maximum number of times the loop can execute (default: 5)
-- **Minimum Iterations**: The minimum number of times the loop must execute before checking conditions
-
-<Callout type="warning">
-  Always set a reasonable maximum iteration limit to prevent infinite loops. The default limit of 5
-  iterations is a good starting point for most workflows.
-</Callout>
-
-### Loop Conditions
-
-Loops can continue based on different types of conditions:
-
-<Tabs items={['Conditional Block', 'Function Block', 'Fixed Iterations']}>
-  <Tab>
-    Use a Condition block to determine whether the loop should continue:
-    
-    ```javascript
-    // Example condition in a Condition block
-    function shouldContinueLoop() {
-      // Get the current score from an evaluator block
-      const score = input.evaluatorBlock.score;
-      
-      // Continue looping if score is below threshold
-      return score < 0.8;
-    }
-    ```
-    
-    The loop will continue executing as long as the condition returns true and the maximum iteration limit hasn't been reached.
-  </Tab>
-  
-  <Tab>
-    Use a Function block to implement complex loop conditions:
-    
-    ```javascript
-    // Example condition in a Function block
-    function processAndCheckContinuation() {
-      // Process data from previous blocks
-      const currentResult = input.agentBlock.content;
-      const previousResults = input.memoryBlock.results || [];
-      
-      // Store results for comparison
-      const allResults = [...previousResults, currentResult];
-      
-      // Check if we've converged (results not changing significantly)
-      const shouldContinue = previousResults.length === 0 || 
-        currentResult !== previousResults[previousResults.length - 1];
-      
-      return {
-        results: allResults,
-        shouldContinue: shouldContinue
-      };
-    }
-    ```
-    
-    Connect this Function block's output to a Condition block to control the loop.
-  </Tab>
-  
-  <Tab>
-    Execute the loop for a fixed number of iterations:
-    
-    ```
-    // Set in loop configuration
-    Minimum Iterations: 3
-    Maximum Iterations: 3
-    ```
-    
-    This will run the loop exactly 3 times, regardless of any conditions.
-  </Tab>
-</Tabs>
-
-## Loop Execution
-
-When a workflow with loops executes, the loop manager handles the iteration process:
-
-1. **First Pass**: All blocks in the loop execute normally
-2. **Iteration Check**: The system checks if another iteration should occur
-3. **State Reset**: If continuing, block states within the loop are reset
-4. **Next Iteration**: The loop blocks execute again with updated inputs
-5. **Termination**: The loop stops when either:
-   - The maximum iteration count is reached
-   - A loop condition evaluates to false (after minimum iterations)
-
-## Loop Use Cases
-
-Loops enable powerful workflow patterns:
-
-### Iterative Refinement
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Example: Content Refinement</h4>
-  <div className="mb-2 text-sm text-gray-600 dark:text-gray-400">
-    Create a loop where an Agent block generates content, an Evaluator block assesses it, and a
-    Function block decides whether to continue refining.
-  </div>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Agent generates initial content</li>
-    <li>Evaluator scores the content</li>
-    <li>Function analyzes score and provides feedback</li>
-    <li>Loop back to Agent with feedback for improvement</li>
-    <li>Continue until quality threshold is reached</li>
-  </ol>
-</div>
-
-### Batch Processing
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Example: Data Processing Pipeline</h4>
-  <div className="mb-2 text-sm text-gray-600 dark:text-gray-400">
-    Process a collection of items one at a time through a series of blocks.
-  </div>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Function block extracts the next item from a collection</li>
-    <li>Processing blocks operate on the single item</li>
-    <li>Results are accumulated in a Memory block</li>
-    <li>Loop continues until all items are processed</li>
-  </ol>
-</div>
-
-### Recursive Problem Solving
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Example: Multi-step Reasoning</h4>
-  <div className="mb-2 text-sm text-gray-600 dark:text-gray-400">
-    Implement a recursive approach to complex problem solving.
-  </div>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Agent analyzes the current problem state</li>
-    <li>Function block implements a step in the solution</li>
-    <li>Condition block checks if the problem is solved</li>
-    <li>Loop continues until solution is found or maximum steps reached</li>
-  </ol>
-</div>
-
-## Best Practices for Loops
-
-To use loops effectively in your workflows:
-
-- **Set Appropriate Limits**: Always configure reasonable iteration limits
-- **Use Memory Blocks**: Store state between iterations with Memory blocks
-- **Include Exit Conditions**: Define clear conditions for when loops should terminate
-- **Monitor Performance**: Watch for performance impacts with many iterations
-- **Test Thoroughly**: Verify that loops terminate as expected in all scenarios
-
-<Callout type="warning">
-  Loops with many blocks or complex operations can impact performance. Consider optimizing
-  individual blocks if your loops need many iterations.
-</Callout>
-
-## Loop Debugging
-
-When debugging loops in your workflows:
-
-- **Check Iteration Counts**: Verify the loop is executing the expected number of times
-- **Inspect Block Inputs/Outputs**: Look at how data changes between iterations
-- **Review Loop Conditions**: Ensure conditions are evaluating as expected
-- **Use Console Logging**: Add console.log statements in Function blocks to track loop progress
-- **Monitor Memory Usage**: Watch for growing data structures that might cause performance issues
-
-By mastering loops, you can create much more sophisticated and powerful workflows in Sim Studio.

apps/docs/content/docs/execution/meta.json

@@ -1,4 +1,4 @@
 {
   "title": "Execution",
-  "pages": ["basics", "loops", "advanced"]
+  "pages": ["basics", "advanced"]
 }

apps/docs/content/docs/getting-started/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Getting Started
-description: Build, test, and optimize your agentic workflows
+description: Build your first AI workflow in 5 minutes
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,6 +8,7 @@ import { Card, Cards } from 'fumadocs-ui/components/card'
 import { File, Files, Folder } from 'fumadocs-ui/components/files'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
 import {
   AgentIcon,
   ApiIcon,
@@ -22,80 +23,173 @@ import {
   PerplexityIcon,
   SlackIcon,
 } from '@/components/icons'
+import { Video } from '@/components/ui/video'
 
-Sim Studio is a powerful, user-friendly platform for building, testing, and optimizing your agentic workflows. This documentation will help you understand how to use the various components of Sim Studio to create sophisticated agent-based applications.
+This tutorial will guide you through building your first AI workflow in Sim. We'll create a people research agent that can find information about individuals using state-of-the-art LLM-Search tools.
 
 <Callout type="info">
-  This guide will walk you through the essential concepts and help you get started building your
-  first workflow.
+  This tutorial takes about 10 minutes and covers the essential concepts of building workflows in Sim.
 </Callout>
 
-## Core Components
+## What We're Building
 
-Sim Studio is built around two primary components:
+A people research agent that:
+1. Receives a person's name via chat interface
+2. Uses an AI agent with advanced search capabilities
+3. Searches the web using state-of-the-art LLM-Search tools (Exa and Linkup)
+4. Extracts structured information using a response format
+5. Returns comprehensive data about the person
 
-### Blocks
+<ThemeImage
+  lightSrc="/static/examples/started/started-1.png"
+  darkSrc="/static/examples/started/started-1.png"
+  alt="Getting Started Example"
+  width={800}
+  height={500}
+/>
 
-Blocks are the fundamental building elements of your workflows. Each block serves a specific purpose:
+## Step-by-Step Tutorial
+
+<Steps>
+  <Step title="Create workflow and add AI agent">
+    Open Sim and click "New Workflow" in the dashboard. Name it "Getting Started".
+    
+    When you create a new workflow, it automatically includes a **Start block** - this is the entry point that receives input from users. For this example, we'll be triggering the workflow via chat, so we don't need to configure anything on the Start block.
+    
+    Now drag an **Agent Block** onto the canvas from the blocks panel on the left.
+    
+    Configure the Agent Block:
+    - **Model**: Select "OpenAI GPT-4o"
+    - **System Prompt**: "You are a people research agent. When given a person's name, use your available search tools to find comprehensive information about them including their location, profession, educational background, and other relevant details."
+    - **User Prompt**: Drag the connection from the Start block's output into this field (this connects `<start.input>` to the user prompt)
+    
+    <div className="mx-auto w-full overflow-hidden rounded-lg">
+      <Video src="examples/started-2.mp4" />
+    </div>
+  </Step>
+  
+  <Step title="Add tools to the agent">
+    Let's enhance our agent with tools for better capabilities. Click on the Agent block to select it.
+    
+    In the **Tools** section:
+    - Click **Add Tool**
+    - Select **Exa** from the available tools
+    - Select **Linkup** from the available tools
+    - Add your API keys for both tools (this allows the agent to search the web and access additional information)
+    
+    <div className="mx-auto w-3/5 overflow-hidden rounded-lg">
+      <Video src="examples/started-3.mp4" />
+    </div>
+  </Step>
+  
+  <Step title="Test the basic workflow">
+    Now let's test our workflow. Go to the **Chat panel** on the right side of the screen.
+    
+    In the chat panel:
+    - Click the dropdown and select `agent1.content` (this will show us the output of our agent)
+    - Enter a test message like: "John is a software engineer from San Francisco who studied Computer Science at Stanford University."
+    - Click "Send" to run the workflow
+    
+    You should see the agent's response analyzing the person described in your text.
+    
+    <div className="mx-auto w-full overflow-hidden rounded-lg">
+      <Video src="examples/started-4.mp4" />
+    </div>
+  </Step>
+  
+  <Step title="Add structured output">
+    Now let's make our agent return structured data. Click on the Agent block to select it.
+    
+    In the **Response Format** section:
+    - Click the **magic wand icon** (✨) next to the schema field
+    - In the prompt that appears, type: "create a schema named person, that contains location, profession, and education"
+    - The AI will generate a JSON schema for you automatically
+    
+    <div className="mx-auto w-full overflow-hidden rounded-lg">
+      <Video src="examples/started-5.mp4" />
+    </div>
+  </Step>
+  
+  <Step title="Test the structured output">
+    Go back to the **Chat panel**.
+    
+    Since we added a response format, new output options are now available:
+    - Click the dropdown and select the new structured output option (the schema we just created)
+    - Enter a new test message like: "Sarah is a marketing manager from New York who has an MBA from Harvard Business School."
+    - Click "Send" to run the workflow again
+    
+    You should now see structured JSON output with the person's information organized into location, profession, and education fields.
+    
+    <div className="mx-auto w-full overflow-hidden rounded-lg">
+      <Video src="examples/started-6.mp4" />
+    </div>
+  </Step>
+</Steps>
+
+## What You Just Built
+
+Congratulations! You've created your first AI workflow that:
+- ✅ Receives text input via chat interface
+- ✅ Uses AI to extract information from unstructured text
+- ✅ Integrates external tools (Exa and Linkup) for enhanced capabilities
+- ✅ Returns structured JSON data using AI-generated schemas
+- ✅ Demonstrates workflow testing and iteration
+- ✅ Shows the power of visual workflow building
+
+## Key Concepts You Learned
+
+### Block Types Used
 
 <Files>
+  <File
+    name="Start Block"
+    icon={<ConnectIcon className="h-4 w-4" />}
+    annotation="Entry point for user input (auto-included)"
+  />
   <File
     name="Agent Block"
     icon={<AgentIcon className="h-4 w-4" />}
-    annotation="Create AI agents using any LLM provider"
-  />
-  <File
-    name="API Block"
-    icon={<ApiIcon className="h-4 w-4" />}
-    annotation="Connect to external services and APIs"
-  />
-  <File
-    name="Condition Block"
-    icon={<ConditionalIcon className="h-4 w-4" />}
-    annotation="Add conditional branching to your workflows"
-  />
-  <File
-    name="Function Block"
-    icon={<CodeIcon className="h-4 w-4" />}
-    annotation="Execute custom JavaScript/TypeScript code"
-  />
-  <File
-    name="Evaluator Block"
-    icon={<ChartBarIcon className="h-4 w-4" />}
-    annotation="Assess responses against defined criteria"
-  />
-  <File
-    name="Router Block"
-    icon={<ConnectIcon className="h-4 w-4" />}
-    annotation="Direct workflow execution based on input analysis"
+    annotation="AI model for text processing and analysis"
   />
 </Files>
 
-### Tools
+### Core Workflow Concepts
 
-Tools extend the capabilities of agents. They provide additional functionality for agents by enabling you to interface with your favorite data sources and take action (e.g posting on X, sending an email)
+**Data Flow**: Variables flow between blocks by dragging connections
 
-<Files>
-  <File name="Gmail Tool" icon={<GmailIcon className="h-4 w-4" />} />
-  <File name="Firecrawl Tool" icon={<FirecrawlIcon className="h-4 w-4" />} />
-  <File name="Perplexity Tool" icon={<PerplexityIcon className="h-4 w-4" />} />
-  <File name="Notion Tool" icon={<NotionIcon className="h-4 w-4" />} />
-  <File name="Exa AI Tool" icon={<ExaAIIcon className="h-4 w-4" />} />
-  <File name="Slack Tool" icon={<SlackIcon className="h-4 w-4" />} />
-</Files>
+**Chat Interface**: Test workflows in real-time using the chat panel with different output options
 
-## Getting Started
+**Tool Integration**: Enhance agent capabilities by adding external tools like Exa and Linkup
 
-<Steps>
-  <Step title="Create a new workflow">
-    Start by creating a new workflow in the Sim Studio dashboard.
-  </Step>
-  <Step title="Add your first block">Drag and drop a block from the sidebar onto the canvas.</Step>
-  <Step title="Configure the block">
-    Set up the block's parameters and inputs according to your needs.
-  </Step>
-  <Step title="Connect blocks">
-    Create connections between blocks to define the flow of data and execution.
-  </Step>
-  <Step title="Test your workflow">Run your workflow with test inputs to verify its behavior.</Step>
-</Steps>
+**Variable References**: Access block outputs using `<blockName.output>` syntax
+
+**Structured Output**: Use JSON schemas to get consistent, structured data from AI
+
+**AI-Generated Schemas**: Use the magic wand (✨) to generate schemas with natural language
+
+**Iterative Development**: Test, modify, and re-test workflows easily
+
+## Next Steps
+
+<Cards>
+  <Card title="Add More Blocks" href="/blocks">
+    Learn about API, Function, and Condition blocks
+  </Card>
+  <Card title="Use Tools" href="/tools">
+    Integrate with external services like Gmail, Slack, and Notion
+  </Card>
+  <Card title="Add Custom Logic" href="/blocks/function">
+    Use Function blocks for custom data processing
+  </Card>
+  <Card title="Deploy Your Workflow" href="/execution">
+    Make your workflow accessible via REST API
+  </Card>
+</Cards>
+
+## Need Help?
+
+**Stuck on a step?** Check our [Blocks documentation](/blocks) for detailed explanations of each component.
+
+**Want to see more examples?** Browse our [Tools documentation](/tools) to see what integrations are available.
+
+**Ready to deploy?** Learn about [Execution and Deployment](/execution) to make your workflows live.

apps/docs/content/docs/introduction/index.mdx

@@ -1,84 +1,94 @@
 ---
 title: Introduction
-description: The UI for agents
+description: Build AI workflows visually without code
 ---
 
 import { Card, Cards } from 'fumadocs-ui/components/card'
 import { File, Files, Folder } from 'fumadocs-ui/components/files'
 import { Features } from '@/components/ui/features'
 
-Sim Studio is a powerful platform for building, testing, and optimizing agentic workflows. It provides developers with intuitive tools to design sophisticated agent-based applications through a visual interface. Whether you're prototyping a simple AI assistant or building complex multi-agent systems, Sim Studio offers the flexibility and performance needed for modern AI applications.
+Sim is a visual workflow editor that enables you to build AI-powered applications by connecting blocks on a canvas. Drag and drop components to create chatbots, automation workflows, and data processing pipelines without writing code.
 
-## Why Sim Studio?
+## What Makes Sim Powerful
 
-Building agentic applications requires extensive coding and integration work. Developers spend more time on infrastructure and plumbing than focusing on core AI logic. Sim Studio changes this with a <span className="text-highlight">comprehensive visual workflow editor</span> that handles complexity while keeping you in control of what matters.
+**Multi-Model AI Support** - Connect to OpenAI, Anthropic, Google, Groq, Cerebras, and local models through Ollama. Switch providers without rebuilding workflows.
 
-## How Sim Studio Differs
+**60+ Pre-Built Tools** - Gmail, Slack, Notion, Google Sheets, Airtable, Supabase, Pinecone, and more. Extensible architecture allows custom tool integration.
 
-Sim Studio takes a fundamentally different approach from existing agent development solutions:
+**Flexible Execution** - Run workflows via chat interface, REST API, webhooks, scheduled jobs, or trigger from external systems.
 
-### Focus on What Matters
+**Production Deployment** - Deploy as APIs, integrate with existing systems using our SDK, or embed as plugins. Built-in monitoring, logging, and error handling.
 
-Developers waste countless hours customizing multi-agent frameworks, writing boilerplate code, creating integrations, and building tooling from scratch. By the time they've configured their environment, precious resources are consumed before any real agent work begins.
+**Real-time Collaboration** - Work simultaneously with team members on the same workflow, like Google Docs for AI development.
 
-Sim Studio eliminates this overhead. We've distilled agent development to its essence, removing boilerplate and infrastructure complexity. With Sim Studio, you can <span className="text-highlight">immediately start designing intelligence</span> rather than wrestling with configuration. Your time is best spent refining agent behaviors, not writing glue code that doesn't improve the end-user experience.
+Connect multiple AI models, integrate with 60+ services, and deploy production-ready applications through an intuitive visual interface designed specifically for AI development.
 
-### Provider-Aligned Interfaces
+## Core Building Blocks
 
-Existing frameworks abstract away provider-specific features, forcing developers to navigate layers of abstraction to access specific capabilities. The result: lost functionality, reduced flexibility, and additional code to bridge these gaps.
+**Processing Blocks**
 
-Sim Studio stays <span className="text-highlight">close to provider definitions</span>, directly exposing the parameters that matter:
+- **Agent** - Execute AI model inference with any LLM provider
+- **API** - Connect to REST endpoints and external services  
+- **Function** - Run custom JavaScript for data processing
 
-<ul className="highlight-markers list-disc space-y-2 pl-6">
-  <li>System prompts and instructions with native formatting</li>
-  <li>Tool definitions and access patterns that match provider implementations</li>
-  <li>Temperature and sampling parameters with their full range of options</li>
-  <li>Structured output formatting that aligns with provider capabilities</li>
-  <li>Model selection and configuration with provider-specific optimizations</li>
-</ul>
+**Logic Blocks**
 
-This approach gives you full control over agent behavior without unnecessary complexity. You leverage each provider's full capabilities without sacrificing the convenience of a unified platform.
+- **Condition** - Create branching logic based on data evaluation
+- **Router** - Route execution paths using AI-powered decision making
+- **Loop** - Iterate over collections sequentially
+- **Parallel** - Execute multiple operations concurrently
 
-### Unified Model Interface
+**Output Blocks**
 
-Most environments lock you into a specific LLM provider early in development. Changing providers later requires significant refactoring, often affecting your entire application architecture and limiting your ability to leverage advances in model capabilities.
+- **Response** - Format and return final workflow results
+- **Evaluator** - Validate outputs against defined criteria
 
-Our platform provides a <span className="text-highlight">consistent interface across different AI models</span>, letting you switch between OpenAI, Anthropic, Claude, Llama, Gemini and others without rewriting your agent logic. This model-agnostic approach future-proofs your applications and gives you freedom to select the best model for each specific use case—optimize for cost with one agent and performance with another, all within the same workflow.
+## Built-in Integrations
 
-### AI-Native Design
+**AI Models**: OpenAI, Anthropic, Google, Groq, Cerebras, Ollama
 
-Traditional development environments were designed for conventional software and later adapted for AI. These adaptations often feel like afterthoughts, with AI capabilities awkwardly grafted onto existing paradigms.
+**Communication**: Gmail, Slack, Telegram, WhatsApp, Microsoft Teams
 
-Sim Studio is <span className="text-highlight">built from the ground up as an AI-native application</span>. Every aspect—from the visual workflow editor to testing environments—is designed specifically for agent development. Common AI development patterns are first-class concepts in our platform, not workarounds. Testing prompts, adjusting parameters, or implementing complex tool calling patterns feel natural because they're core to our design philosophy.
+**Data Sources**: Notion, Google Sheets, Airtable, Supabase, Pinecone
 
-### Local Development Support
+**Web Services**: Firecrawl, Google Search, Exa AI, Perplexity
 
-Many AI platforms force you to develop against cloud APIs, creating dependencies on internet connectivity, increasing costs, and introducing privacy concerns with sensitive data.
+**Development**: GitHub, Jira, Linear, browser automation
 
-Sim Studio supports <span className="text-highlight">full local development</span> using Ollama integration. Develop with privacy-preserving local models, then seamlessly deploy with cloud providers in production. This hybrid approach gives you the best of both worlds: privacy, cost-efficiency, and reliability during development, with scalability and performance in production.
+## Use Cases
 
-### Comprehensive Observability
+**AI Assistants** - Build chatbots with web search, calendar access, and email capabilities
 
-Existing solutions provide limited visibility into agent performance, making it difficult to identify bottlenecks, understand costs, or diagnose failures. Developers build custom instrumentation or operate in the dark.
+**Content Generation** - Create blog posts, social media content, and marketing materials
 
-Sim Studio provides <span className="text-highlight">full visibility into agent performance</span> with integrated observability:
+**Data Processing** - Extract insights from documents, analyze datasets, and generate reports
 
-<ul className="highlight-markers list-disc space-y-2 pl-6">
-  <li>Detailed execution logs capturing every interaction between agents and models</li>
-  <li>Latency tracing with span visualization to identify performance bottlenecks</li>
-  <li>Cost tracking and optimization to prevent budget overruns</li>
-  <li>Error analysis and debugging tools for complex workflows</li>
-  <li>Performance comparisons across different model configurations</li>
-</ul>
+**Process Automation** - Automate business workflows with event-driven triggers
 
-This comprehensive observability means less time investigating issues and more time resolving them—faster development cycles and more reliable agent workflows.
+**API Orchestration** - Combine multiple services into unified endpoints
 
-## Features
+## Key Features
 
-Sim Studio provides a wide range of features designed to accelerate your development process:
+**Multi-Provider AI Support** - Switch between OpenAI, Anthropic, Google, and local models without rebuilding workflows
 
-<Features />
+**Real-time Collaboration** - Work simultaneously with team members on the same workflow
 
-##
+**Production-Ready** - Built-in error handling, logging, and monitoring for production deployments
 
-Ready to get started? Check out our [Getting Started](/getting-started) guide or explore our [Blocks](/blocks) and [Tools](/tools) in more detail.
+**Local Development** - Test with Ollama locally, then deploy with cloud providers
+
+## Getting Started
+
+Ready to build your first workflow? Our [Getting Started guide](/getting-started) will walk you through creating a customer support assistant in under 10 minutes.
+
+<Cards>
+  <Card title="Getting Started" href="/getting-started">
+    Build your first workflow
+  </Card>
+  <Card title="Blocks" href="/blocks">
+    Learn about workflow components
+  </Card>
+  <Card title="Tools" href="/tools">
+    Explore integrations
+  </Card>
+</Cards>

apps/docs/content/docs/meta.json

@@ -1,18 +1,22 @@
 {
-  "title": "Sim Studio Documentation",
+  "title": "Sim Documentation",
   "pages": [
     "---Introduction---",
     "./introduction/index",
     "./getting-started/index",
     "---Create---",
+    "triggers",
     "blocks",
     "tools",
     "---Connections---",
     "connections",
     "---Execution---",
     "execution",
+    "---Copilot---",
+    "copilot",
     "---Advanced---",
     "./variables/index",
+    "yaml",
     "---SDKs---",
     "./sdks/python",
     "./sdks/typescript"

apps/docs/content/docs/sdks/python.mdx

@@ -1,6 +1,6 @@
 ---
 title: Python SDK
-description: The official Python SDK for Sim Studio
+description: The official Python SDK for Sim
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,7 +8,7 @@ import { Card, Cards } from 'fumadocs-ui/components/card'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 
-The official Python SDK for Sim Studio allows you to execute workflows programmatically from your Python applications.
+The official Python SDK for Sim allows you to execute workflows programmatically from your Python applications.
 
 <Callout type="info">
   The Python SDK supports Python 3.8+ and provides synchronous workflow execution. All workflow executions are currently synchronous.
@@ -32,7 +32,7 @@ from simstudio import SimStudioClient
 # Initialize the client
 client = SimStudioClient(
     api_key="your-api-key-here",
-    base_url="https://simstudio.ai"  # optional, defaults to https://simstudio.ai
+    base_url="https://sim.ai"  # optional, defaults to https://sim.ai
 )
 
 # Execute a workflow
@@ -50,12 +50,12 @@ except Exception as error:
 #### Constructor
 
 ```python
-SimStudioClient(api_key: str, base_url: str = "https://simstudio.ai")
+SimStudioClient(api_key: str, base_url: str = "https://sim.ai")
 ```
 
 **Parameters:**
-- `api_key` (str): Your Sim Studio API key
-- `base_url` (str, optional): Base URL for the Sim Studio API
+- `api_key` (str): Your Sim API key
+- `base_url` (str, optional): Base URL for the Sim API
 
 #### Methods
 
@@ -353,7 +353,7 @@ Configure the client using environment variables:
     # Development configuration
     client = SimStudioClient(
         api_key=os.getenv("SIMSTUDIO_API_KEY"),
-        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://simstudio.ai")
+        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://sim.ai")
     )
     ```
   </Tab>
@@ -369,7 +369,7 @@ Configure the client using environment variables:
 
     client = SimStudioClient(
         api_key=api_key,
-        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://simstudio.ai")
+        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://sim.ai")
     )
     ```
   </Tab>
@@ -378,8 +378,8 @@ Configure the client using environment variables:
 ## Getting Your API Key
 
 <Steps>
-  <Step title="Log in to Sim Studio">
-    Navigate to [Sim Studio](https://simstudio.ai) and log in to your account.
+  <Step title="Log in to Sim">
+    Navigate to [Sim](https://sim.ai) and log in to your account.
   </Step>
   <Step title="Open your workflow">
     Navigate to the workflow you want to execute programmatically.

apps/docs/content/docs/sdks/typescript.mdx

@@ -1,6 +1,6 @@
 ---
 title: TypeScript/JavaScript SDK
-description: The official TypeScript/JavaScript SDK for Sim Studio
+description: The official TypeScript/JavaScript SDK for Sim
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,7 +8,7 @@ import { Card, Cards } from 'fumadocs-ui/components/card'
 import { Step, Steps } from 'fumadocs-ui/components/steps'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 
-The official TypeScript/JavaScript SDK for Sim Studio allows you to execute workflows programmatically from your Node.js applications, web applications, and other JavaScript environments.
+The official TypeScript/JavaScript SDK for Sim allows you to execute workflows programmatically from your Node.js applications, web applications, and other JavaScript environments.
 
 <Callout type="info">
   The TypeScript SDK provides full type safety and supports both Node.js and browser environments. All workflow executions are currently synchronous.
@@ -46,7 +46,7 @@ import { SimStudioClient } from 'simstudio-ts-sdk';
 // Initialize the client
 const client = new SimStudioClient({
   apiKey: 'your-api-key-here',
-  baseUrl: 'https://simstudio.ai' // optional, defaults to https://simstudio.ai
+  baseUrl: 'https://sim.ai' // optional, defaults to https://sim.ai
 });
 
 // Execute a workflow
@@ -69,8 +69,8 @@ new SimStudioClient(config: SimStudioConfig)
 ```
 
 **Configuration:**
-- `config.apiKey` (string): Your Sim Studio API key
-- `config.baseUrl` (string, optional): Base URL for the Sim Studio API (defaults to `https://simstudio.ai`)
+- `config.apiKey` (string): Your Sim API key
+- `config.baseUrl` (string, optional): Base URL for the Sim API (defaults to `https://sim.ai`)
 
 #### Methods
 
@@ -332,7 +332,7 @@ Configure the client using environment variables:
 
     const client = new SimStudioClient({
       apiKey,
-      baseUrl: process.env.SIMSTUDIO_BASE_URL || 'https://simstudio.ai'
+      baseUrl: process.env.SIMSTUDIO_BASE_URL || 'https://sim.ai'
     });
     ```
   </Tab>
@@ -429,7 +429,7 @@ import { SimStudioClient } from 'simstudio-ts-sdk';
 // Note: In production, use a proxy server to avoid exposing API keys
 const client = new SimStudioClient({
   apiKey: 'your-public-api-key', // Use with caution in browser
-  baseUrl: 'https://simstudio.ai'
+  baseUrl: 'https://sim.ai'
 });
 
 async function executeClientSideWorkflow() {
@@ -539,8 +539,8 @@ function WorkflowComponent() {
 ## Getting Your API Key
 
 <Steps>
-  <Step title="Log in to Sim Studio">
-    Navigate to [Sim Studio](https://simstudio.ai) and log in to your account.
+  <Step title="Log in to Sim">
+    Navigate to [Sim](https://sim.ai) and log in to your account.
   </Step>
   <Step title="Open your workflow">
     Navigate to the workflow you want to execute programmatically.

apps/docs/content/docs/tools/airtable.mdx

@@ -51,7 +51,7 @@ With Airtable, you can:
 - **Automate workflows**: Set up triggers and actions to automate repetitive tasks
 - **Integrate with other tools**: Connect with hundreds of other applications through native integrations and APIs
 
-In Sim Studio, the Airtable integration enables your agents to interact with your Airtable bases programmatically. This allows for seamless data operations like retrieving information, creating new records, and updating existing data - all within your agent workflows. Use Airtable as a dynamic data source or destination for your agents, enabling them to access and manipulate structured information as part of their decision-making and task execution processes.
+In Sim, the Airtable integration enables your agents to interact with your Airtable bases programmatically. This allows for seamless data operations like retrieving information, creating new records, and updating existing data - all within your agent workflows. Use Airtable as a dynamic data source or destination for your agents, enabling them to access and manipulate structured information as part of their decision-making and task execution processes.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -71,19 +71,16 @@ Read records from an Airtable table
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID of the table |
 | `maxRecords` | number | No | Maximum number of records to return |
-| `filterFormula` | string | No | Formula to filter records \(e.g.,  |
+| `filterFormula` | string | No | Formula to filter records \(e.g., "\(\{Field Name\} = \'Value\'\)"\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `records` | string |
-| `metadata` | string |
-| `totalRecords` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `records` | json | Array of retrieved Airtable records |
 
 ### `airtable_get_record`
 
@@ -93,17 +90,16 @@ Retrieve a single record from an Airtable table by its ID
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
 | `recordId` | string | Yes | ID of the record to retrieve |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `record` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `record` | json | Retrieved Airtable record with id, createdTime, and fields |
+| `metadata` | json | Operation metadata including record count |
 
 ### `airtable_create_records`
 
@@ -113,16 +109,16 @@ Write new records to an Airtable table
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
+| `records` | json | Yes | Array of records to create, each with a `fields` object |
+| `fields` | string | No | No description |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `records` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `records` | json | Array of created Airtable records |
 
 ### `airtable_update_record`
 
@@ -132,7 +128,6 @@ Update an existing record in an Airtable table by ID
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
 | `recordId` | string | Yes | ID of the record to update |
@@ -140,11 +135,10 @@ Update an existing record in an Airtable table by ID
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `record` | string |
-| `metadata` | string |
-| `updatedFields` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `record` | json | Updated Airtable record with id, createdTime, and fields |
+| `metadata` | json | Operation metadata including record count and updated field names |
 
 ### `airtable_update_multiple_records`
 
@@ -154,40 +148,18 @@ Update multiple existing records in an Airtable table
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
+| `records` | json | Yes | Array of records to update, each with an `id` and a `fields` object |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `records` | string |
-| `metadata` | string |
-| `updatedRecordIds` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `records` | json | Array of updated Airtable records |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `records` | json | records of the response |
-| ↳ `record` | json | record of the response |
-| ↳ `metadata` | json | metadata of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/arxiv.mdx

@@ -0,0 +1,114 @@
+---
+title: ArXiv
+description: Search and retrieve academic papers from ArXiv
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="arxiv"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"  id='logomark' xmlns='http://www.w3.org/2000/svg' viewBox='0 0 17.732 24.269'>
+      <g id='tiny'>
+        <path
+          d='M573.549,280.916l2.266,2.738,6.674-7.84c.353-.47.52-.717.353-1.117a1.218,1.218,0,0,0-1.061-.748h0a.953.953,0,0,0-.712.262Z'
+          transform='translate(-566.984 -271.548)'
+          fill='#bdb9b4'
+        />
+        <path
+          d='M579.525,282.225l-10.606-10.174a1.413,1.413,0,0,0-.834-.5,1.09,1.09,0,0,0-1.027.66c-.167.4-.047.681.319,1.206l8.44,10.242h0l-6.282,7.716a1.336,1.336,0,0,0-.323,1.3,1.114,1.114,0,0,0,1.04.69A.992.992,0,0,0,571,293l8.519-7.92A1.924,1.924,0,0,0,579.525,282.225Z'
+          transform='translate(-566.984 -271.548)'
+          fill='#b31b1b'
+        />
+        <path
+          d='M584.32,293.912l-8.525-10.275,0,0L573.53,280.9l-1.389,1.254a2.063,2.063,0,0,0,0,2.965l10.812,10.419a.925.925,0,0,0,.742.282,1.039,1.039,0,0,0,.953-.667A1.261,1.261,0,0,0,584.32,293.912Z'
+          transform='translate(-566.984 -271.548)'
+          fill='#bdb9b4'
+        />
+      </g>
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[ArXiv](https://arxiv.org/) is a free, open-access repository of scientific research papers in fields such as physics, mathematics, computer science, quantitative biology, quantitative finance, statistics, electrical engineering, systems science, and economics. ArXiv provides a vast collection of preprints and published articles, making it a primary resource for researchers and practitioners worldwide.
+
+With ArXiv, you can:
+
+- **Search for academic papers**: Find research by keywords, author names, titles, categories, and more
+- **Retrieve paper metadata**: Access abstracts, author lists, publication dates, and other bibliographic information
+- **Download full-text PDFs**: Obtain the complete text of most papers for in-depth study
+- **Explore author contributions**: View all papers by a specific author
+- **Stay up-to-date**: Discover the latest submissions and trending topics in your field
+
+In Sim, the ArXiv integration enables your agents to programmatically search, retrieve, and analyze scientific papers from ArXiv. This allows you to automate literature reviews, build research assistants, or incorporate up-to-date scientific knowledge into your agentic workflows. Use ArXiv as a dynamic data source for research, discovery, and knowledge extraction within your Sim projects.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Search for academic papers, retrieve metadata, download papers, and access the vast collection of scientific research on ArXiv.
+
+
+
+## Tools
+
+### `arxiv_search`
+
+Search for academic papers on ArXiv by keywords, authors, titles, or other fields.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `searchQuery` | string | Yes | The search query to execute |
+| `searchField` | string | No | Field to search in: all, ti \(title\), au \(author\), abs \(abstract\), co \(comment\), jr \(journal\), cat \(category\), rn \(report number\) |
+| `maxResults` | number | No | Maximum number of results to return \(default: 10, max: 2000\) |
+| `sortBy` | string | No | Sort by: relevance, lastUpdatedDate, submittedDate \(default: relevance\) |
+| `sortOrder` | string | No | Sort order: ascending, descending \(default: descending\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `papers` | json | Array of papers matching the search query |
+
+### `arxiv_get_paper`
+
+Get detailed information about a specific ArXiv paper by its ID.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `paperId` | string | Yes | ArXiv paper ID \(e.g., "1706.03762"\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `paper` | json | Detailed information about the requested ArXiv paper |
+
+### `arxiv_get_author_papers`
+
+Search for papers by a specific author on ArXiv.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `authorName` | string | Yes | Author name to search for |
+| `maxResults` | number | No | Maximum number of results to return \(default: 10, max: 2000\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `authorPapers` | json | Array of papers authored by the specified author |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `arxiv`

apps/docs/content/docs/tools/autoblocks.mdx

@@ -1,187 +0,0 @@
----
-title: Autoblocks
-description: Manage and use versioned prompts with Autoblocks
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="autoblocks"
-  color="#0D2929"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      version='1.1'
-      id='Layer_1'
-      xmlns='http://www.w3.org/2000/svg'
-      xmlnsXlink='http://www.w3.org/1999/xlink'
-      x='0px'
-      y='0px'
-      
-      viewBox='0 0 1250 1250'
-      enableBackground='new 0 0 1250 1250'
-      xmlSpace='preserve'
-    >
-      <path
-        fill='#FFFFFF'
-        opacity='1.000000'
-        stroke='none'
-        d='
-M671.222290,1079.959839 
-	C671.176025,1077.962891 671.089233,1075.965820 671.089111,1073.968872 
-	C671.082825,918.318481 671.062683,762.668091 671.192322,607.017761 
-	C671.195862,602.748474 669.789551,600.693787 666.180847,598.638306 
-	C636.091125,581.500183 606.140991,564.117126 576.145508,546.813599 
-	C556.393311,535.419128 536.677856,523.960449 516.869568,512.664307 
-	C495.246002,500.332977 473.461487,488.282806 451.883911,475.872253 
-	C434.220825,465.713257 416.802856,455.129089 399.195587,444.871857 
-	C379.466736,433.378601 359.648438,422.038818 339.866608,410.636597 
-	C320.229004,399.317505 300.588470,388.003510 280.948822,376.688019 
-	C271.840149,371.440033 262.730530,366.193695 253.057938,360.622070 
-	C267.185272,352.478241 280.655273,344.713531 294.125092,336.948517 
-	C329.023163,316.830566 363.943237,296.750366 398.783295,276.532349 
-	C402.073059,274.623260 404.534790,274.139191 408.118988,276.252319 
-	C435.683502,292.503723 463.371948,308.546082 491.084290,324.545258 
-	C509.340118,335.084839 527.725525,345.399719 546.006958,355.895203 
-	C585.713440,378.690979 625.427124,401.474670 665.069397,424.381744 
-	C705.530884,447.762177 745.895203,471.310669 786.336243,494.726715 
-	C796.959717,500.877930 807.667236,506.888184 818.432190,512.787903 
-	C820.966064,514.176636 821.763611,515.816772 821.762329,518.659241 
-	C821.692932,676.145020 821.688171,833.630737 821.793762,991.116455 
-	C821.795837,994.184937 820.514771,995.521545 818.222412,996.837891 
-	C782.578491,1017.306641 746.954346,1037.809570 711.333679,1058.318848 
-	C698.839661,1065.512573 686.367554,1072.744629 673.219116,1079.994141 
-	C672.109314,1080.006104 671.665771,1079.982910 671.222290,1079.959839 
-z'
-      />
-      <path
-        fill='#FFFFFF'
-        opacity='1.000000'
-        stroke='none'
-        d='
-M684.421631,400.605865 
-	C600.749390,352.376038 517.388306,304.342010 433.717010,256.129181 
-	C455.858643,243.338989 477.724731,230.689346 499.608948,218.071136 
-	C526.744324,202.425217 553.916504,186.842911 581.002014,171.111252 
-	C583.487793,169.667450 585.282104,169.727783 587.700562,171.126724 
-	C627.018250,193.870560 666.389465,216.521790 705.739136,239.210449 
-	C744.537903,261.581543 783.343262,283.941437 822.113525,306.361786 
-	C854.544006,325.115936 886.886658,344.022156 919.345703,362.726379 
-	C945.337769,377.704102 971.415039,392.534851 997.539551,407.280151 
-	C1001.126465,409.304749 1002.459045,411.581146 1002.455444,415.839966 
-	C1002.322388,571.647339 1002.315430,727.454834 1002.468750,883.262207 
-	C1002.473694,888.329590 1001.184082,891.101135 996.646118,893.690186 
-	C949.437134,920.624695 902.383667,947.831665 855.284607,974.958862 
-	C854.453491,975.437500 853.591980,975.863708 851.884216,976.772095 
-	C851.884216,974.236023 851.884216,972.347290 851.884216,970.458557 
-	C851.884216,814.817688 851.876099,659.176880 851.927551,503.536011 
-	C851.928955,499.372650 851.416870,497.004883 846.802246,494.523651 
-	C829.014954,484.959839 811.879517,474.190002 794.417969,464.012421 
-	C774.549316,452.431854 754.597900,440.993225 734.670959,429.512817 
-	C718.033508,419.927551 701.379517,410.370911 684.421631,400.605865 
-z'
-      />
-      <path
-        fill='#FFFFFF'
-        opacity='1.000000'
-        stroke='none'
-        d='
-M398.927063,451.754761 
-	C400.510162,450.940521 401.764893,450.328430 403.700867,449.383972 
-	C403.700867,452.154175 403.700897,454.096252 403.700897,456.038330 
-	C403.700897,554.021851 403.720520,652.005371 403.628479,749.988831 
-	C403.624847,753.876892 404.584320,756.067810 408.236908,758.155518 
-	C451.188324,782.705505 493.996735,807.505737 536.834656,832.254150 
-	C575.355164,854.508362 613.866882,876.777893 652.379028,899.046387 
-	C658.236328,902.433167 664.075500,905.851257 670.506531,909.594543 
-	C660.506226,915.396240 650.958069,920.955383 641.391357,926.482483 
-	C602.367798,949.028442 563.293213,971.486938 524.376099,994.215210 
-	C520.155334,996.680237 517.203247,996.930176 512.863708,994.408752 
-	C454.421143,960.451721 395.851410,926.713562 337.314575,892.918823 
-	C319.777893,882.794556 302.245758,872.662292 284.710938,862.534790 
-	C274.721008,856.764954 264.759888,850.944214 254.717163,845.267761 
-	C252.338959,843.923462 251.216995,842.476929 251.219849,839.499817 
-	C251.315567,739.849976 251.312408,640.200073 251.234558,540.550232 
-	C251.232254,537.601685 252.346344,536.241150 254.806610,534.827820 
-	C302.775909,507.271362 350.680695,479.602600 398.927063,451.754761 
-z'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Autoblocks](https://www.autoblocks.ai/) is a comprehensive platform for managing, monitoring, and optimizing AI applications. It provides robust tools for prompt management that enable teams to collaborate effectively on AI prompts while maintaining version control and type safety.
-
-With Autoblocks, you can:
-
-- **Version and manage prompts**: Track changes, roll back to previous versions, and maintain a history of prompt iterations
-- **Collaborate across teams**: Enable product, engineering, and AI teams to work together on prompt development
-- **Ensure type safety**: Get autocomplete and validation for prompt variables
-- **Monitor prompt performance**: Track metrics and analyze how changes affect outcomes
-- **Test prompts**: Compare different versions and evaluate results before deployment
-
-Autoblocks integrates seamlessly with your existing AI workflows in Sim Studio, providing a structured approach to prompt engineering that improves consistency and reduces errors.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Collaborate on prompts with type safety, autocomplete, and backwards-incompatibility protection. Autoblocks prompt management allows product teams to collaborate while maintaining excellent developer experience.
-
-
-
-## Tools
-
-### `autoblocks_prompt_manager`
-
-Manage and render prompts using Autoblocks prompt management system
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `promptId` | string | Yes | The ID of the prompt to retrieve |
-| `version` | string | Yes | Version strategy \(latest or specific\) |
-| `specificVersion` | string | No | Specific version to use \(e.g.,  |
-| `templateParams` | object | No | Parameters to render the template with |
-| `apiKey` | string | Yes | Autoblocks API key |
-| `enableABTesting` | boolean | No | Whether to enable A/B testing between versions |
-| `abTestConfig` | object | No | Configuration for A/B testing between versions |
-| `environment` | string | Yes | Environment to use \(production, staging, development\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `promptId` | string |
-| `version` | string |
-| `renderedPrompt` | string |
-| `templates` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `promptId` | string | Yes | Prompt ID - Enter the Autoblocks prompt ID |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `promptId` | string | promptId of the response |
-| ↳ `version` | string | version of the response |
-| ↳ `renderedPrompt` | string | renderedPrompt of the response |
-| ↳ `templates` | json | templates of the response |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `autoblocks`

apps/docs/content/docs/tools/browser_use.mdx

@@ -51,7 +51,7 @@ With BrowserUse, you can:
 - **Monitor task execution**: Watch browser tasks run in real-time with visual feedback
 - **Process results programmatically**: Receive structured output from web automation tasks
 
-In Sim Studio, the BrowserUse integration allows your agents to interact with the web as if they were human users. This enables scenarios like research, data collection, form submission, and web testing - all through simple natural language instructions. Your agents can gather information from websites, interact with web applications, and perform actions that would typically require manual browsing, expanding their capabilities to include the entire web as a resource.
+In Sim, the BrowserUse integration allows your agents to interact with the web as if they were human users. This enables scenarios like research, data collection, form submission, and web testing - all through simple natural language instructions. Your agents can gather information from websites, interact with web applications, and perform actions that would typically require manual browsing, expanding their capabilities to include the entire web as a resource.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -73,42 +73,22 @@ Runs a browser automation task using BrowserUse
 | --------- | ---- | -------- | ----------- |
 | `task` | string | Yes | What should the browser agent do |
 | `variables` | json | No | Optional variables to use as secrets \(format: \{key: value\}\) |
+| `format` | string | No | No description |
 | `save_browser_data` | boolean | No | Whether to save browser data |
 | `model` | string | No | LLM model to use \(default: gpt-4o\) |
 | `apiKey` | string | Yes | API key for BrowserUse API |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `id` | string |
-| `success` | string |
-| `output` | string |
-| `steps` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `id` | string | Task execution identifier |
+| `success` | boolean | Task completion status |
+| `output` | json | Task output data |
+| `steps` | json | Execution steps taken |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `task` | string | Yes | Task - Describe what the browser agent should do... |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `id` | string | id of the response |
-| ↳ `success` | boolean | success of the response |
-| ↳ `output` | any | output of the response |
-| ↳ `steps` | json | steps of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/clay.mdx

@@ -174,13 +174,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Clay](https://www.clay.com/) is a data enrichment and workflow automation platform that helps teams streamline lead generation, research, and data operations through powerful integrations and flexible inputs.
 
-Learn how to use the Clay Tool in Sim Studio to seamlessly insert data into a Clay workbook through webhook triggers. This tutorial walks you through setting up a webhook, configuring data mapping, and automating real-time updates to your Clay workbooks. Perfect for streamlining lead generation and data enrichment directly from your workflow!
+Learn how to use the Clay Tool in Sim to seamlessly insert data into a Clay workbook through webhook triggers. This tutorial walks you through setting up a webhook, configuring data mapping, and automating real-time updates to your Clay workbooks. Perfect for streamlining lead generation and data enrichment directly from your workflow!
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/cx_75X5sI_s"
-  title="Clay Integration with Sim Studio"
+  title="Clay Integration with Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -188,11 +188,11 @@ Learn how to use the Clay Tool in Sim Studio to seamlessly insert data into a Cl
 
 With Clay, you can:
 
-- **Enrich agent outputs**: Automatically feed your Sim Studio agent data into Clay tables for structured tracking and analysis
-- **Trigger workflows via webhooks**: Use Clay’s webhook support to initiate Sim Studio agent tasks from within Clay
+- **Enrich agent outputs**: Automatically feed your Sim agent data into Clay tables for structured tracking and analysis
+- **Trigger workflows via webhooks**: Use Clay’s webhook support to initiate Sim agent tasks from within Clay
 - **Leverage data loops**: Seamlessly iterate over enriched data rows with agents that operate across dynamic datasets
 
-In Sim Studio, the Clay integration allows your agents to push structured data into Clay tables via webhooks. This makes it easy to collect, enrich, and manage dynamic outputs such as leads, research summaries, or action items—all in a collaborative, spreadsheet-like interface. Your agents can populate rows in real time, enabling asynchronous workflows where AI-generated insights are captured, reviewed, and used by your team. Whether you're automating research, enriching CRM data, or tracking operational outcomes, Clay becomes a living data layer that interacts intelligently with your agents. By connecting Sim Studio with Clay, you gain a powerful way to operationalize agent results, loop over datasets with precision, and maintain a clean, auditable record of AI-driven work.
+In Sim, the Clay integration allows your agents to push structured data into Clay tables via webhooks. This makes it easy to collect, enrich, and manage dynamic outputs such as leads, research summaries, or action items—all in a collaborative, spreadsheet-like interface. Your agents can populate rows in real time, enabling asynchronous workflows where AI-generated insights are captured, reviewed, and used by your team. Whether you're automating research, enriching CRM data, or tracking operational outcomes, Clay becomes a living data layer that interacts intelligently with your agents. By connecting Sim with Clay, you gain a powerful way to operationalize agent results, loop over datasets with precision, and maintain a clean, auditable record of AI-driven work.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -214,34 +214,17 @@ Populate Clay with data from a JSON file. Enables direct communication and notif
 | --------- | ---- | -------- | ----------- |
 | `webhookURL` | string | Yes | The webhook URL to populate |
 | `data` | json | Yes | The data to populate |
-| `authToken` | string | No | Optional auth token for WebhookURL |
+| `authToken` | string | Yes | Auth token for Clay webhook authentication |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | json | Clay populate operation results including response data from Clay webhook |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `authToken` | string | Yes | Auth Token - Enter your Clay Auth token |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `data` | any | data of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/confluence.mdx

@@ -37,7 +37,7 @@ With Confluence, you can:
 - **Integrate with other tools**: Connect with Jira, Trello, and other Atlassian products for seamless workflow integration
 - **Control access permissions**: Manage who can view, edit, or comment on specific content
 
-In Sim Studio, the Confluence integration enables your agents to access and leverage your organization's knowledge base. Agents can retrieve information from Confluence pages, search for specific content, and even update documentation when needed. This allows your workflows to incorporate the collective knowledge stored in your Confluence instance, making it possible to build agents that can reference internal documentation, follow established procedures, and maintain up-to-date information resources as part of their operations.
+In Sim, the Confluence integration enables your agents to access and leverage your organization's knowledge base. Agents can retrieve information from Confluence pages, search for specific content, and even update documentation when needed. This allows your workflows to incorporate the collective knowledge stored in your Confluence instance, making it possible to build agents that can reference internal documentation, follow established procedures, and maintain up-to-date information resources as part of their operations.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -57,19 +57,18 @@ Retrieve content from Confluence pages using the Confluence API.
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Confluence |
 | `domain` | string | Yes | Your Confluence domain \(e.g., yourcompany.atlassian.net\) |
 | `pageId` | string | Yes | Confluence page ID to retrieve |
 | `cloudId` | string | No | Confluence Cloud ID for the instance. If not provided, it will be fetched using the domain. |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `pageId` | string |
-| `content` | string |
-| `title` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `ts` | string | Timestamp of retrieval |
+| `pageId` | string | Confluence page ID |
+| `content` | string | Page content with HTML tags stripped |
+| `title` | string | Page title |
 
 ### `confluence_update`
 
@@ -79,7 +78,6 @@ Update a Confluence page using the Confluence API.
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Confluence |
 | `domain` | string | Yes | Your Confluence domain \(e.g., yourcompany.atlassian.net\) |
 | `pageId` | string | Yes | Confluence page ID to update |
 | `title` | string | No | New title for the page |
@@ -89,38 +87,15 @@ Update a Confluence page using the Confluence API.
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `pageId` | string |
-| `title` | string |
-| `body` | string |
-| `success` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `ts` | string | Timestamp of update |
+| `pageId` | string | Confluence page ID |
+| `title` | string | Updated page title |
+| `success` | boolean | Update operation success status |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `ts` | string | ts of the response |
-| ↳ `pageId` | string | pageId of the response |
-| ↳ `content` | string | content of the response |
-| ↳ `title` | string | title of the response |
-| ↳ `success` | boolean | success of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/discord.mdx

@@ -39,11 +39,11 @@ With a Discord account or bot, you can:
 - **Get server**: Get information about a specific server
 - **Get user**: Get information about a specific user
 
-In Sim Studio, the Discord integration enables your agents to access and leverage your organization's Discord servers. Agents can retrieve information from Discord channels, search for specific users, get server information, and send messages. This allows your workflows to integrate with your Discord communities, automate notifications, and create interactive experiences.
+In Sim, the Discord integration enables your agents to access and leverage your organization's Discord servers. Agents can retrieve information from Discord channels, search for specific users, get server information, and send messages. This allows your workflows to integrate with your Discord communities, automate notifications, and create interactive experiences.
 
 > **Important:** To read message content, your Discord bot needs the "Message Content Intent" enabled in the Discord Developer Portal. Without this permission, you'll still receive message metadata but the content field will appear empty.
 
-Discord components in Sim Studio use efficient lazy loading, only fetching data when needed to minimize API calls and prevent rate limiting. Token refreshing happens automatically in the background to maintain your connection.
+Discord components in Sim use efficient lazy loading, only fetching data when needed to minimize API calls and prevent rate limiting. Token refreshing happens automatically in the background to maintain your connection.
 
 ### Setting Up Your Discord Bot
 
@@ -78,9 +78,10 @@ Send a message to a Discord channel
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `data` | object | Discord message data |
 
 ### `discord_get_messages`
 
@@ -96,9 +97,10 @@ Retrieve messages from a Discord channel
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `messages` | array | Array of Discord messages with full metadata |
 
 ### `discord_get_server`
 
@@ -113,9 +115,10 @@ Retrieve information about a Discord server (guild)
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `data` | object | Discord server \(guild\) information |
 
 ### `discord_get_user`
 
@@ -130,31 +133,13 @@ Retrieve information about a Discord user
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `data` | object | Discord user information |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `message` | string | message of the response |
-| ↳ `data` | any | data of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/elevenlabs.mdx

@@ -33,7 +33,7 @@ With ElevenLabs, you can:
 - **Control speech parameters**: Adjust stability, clarity, and emotional tone to fine-tune output
 - **Add realistic emotions**: Incorporate natural-sounding emotions like happiness, sadness, or excitement
 
-In Sim Studio, the ElevenLabs integration enables your agents to convert text to lifelike speech, enhancing the interactivity and engagement of your applications. This is particularly valuable for creating voice assistants, generating audio content, developing accessible applications, or building conversational interfaces that feel more human. The integration allows you to seamlessly incorporate ElevenLabs' advanced speech synthesis capabilities into your agent workflows, bridging the gap between text-based AI and natural human communication.
+In Sim, the ElevenLabs integration enables your agents to convert text to lifelike speech, enhancing the interactivity and engagement of your applications. This is particularly valuable for creating voice assistants, generating audio content, developing accessible applications, or building conversational interfaces that feel more human. The integration allows you to seamlessly incorporate ElevenLabs' advanced speech synthesis capabilities into your agent workflows, bridging the gap between text-based AI and natural human communication.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -53,37 +53,19 @@ Convert TTS using ElevenLabs voices
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Your ElevenLabs API key |
 | `text` | string | Yes | The text to convert to speech |
 | `voiceId` | string | Yes | The ID of the voice to use |
 | `modelId` | string | No | The ID of the model to use \(defaults to eleven_monolingual_v1\) |
+| `apiKey` | string | Yes | Your ElevenLabs API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `audioUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `audioUrl` | string | The URL of the generated audio |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `text` | string | Yes | Text - Enter the text to convert to speech |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `audioUrl` | string | audioUrl of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/exa.mdx

@@ -26,7 +26,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Exa](https://exa.ai/) is an AI-powered search engine designed specifically for developers and researchers that provides highly relevant and up-to-date information from across the web. It combines advanced semantic search capabilities with AI understanding to deliver more accurate and contextually relevant results than traditional search engines.
+[Exa](https://exa.ai/) is an AI-powered search engine designed specifically for developers and researchers, providing highly relevant and up-to-date information from across the web. It combines advanced semantic search capabilities with AI understanding to deliver more accurate and contextually relevant results than traditional search engines.
 
 With Exa, you can:
 
@@ -35,14 +35,16 @@ With Exa, you can:
 - **Access up-to-date information**: Retrieve current information from across the web
 - **Find similar content**: Discover related resources based on content similarity
 - **Extract webpage contents**: Retrieve and process the full text of web pages
+- **Answer questions with citations**: Ask questions and receive direct answers with supporting sources
+- **Perform research tasks**: Automate multi-step research workflows to gather, synthesize, and summarize information
 
-In Sim Studio, the Exa integration allows your agents to search the web for information, retrieve content from specific URLs, and find similar resources - all programmatically through API calls. This enables your agents to access real-time information from the internet, enhancing their ability to provide accurate, current, and relevant responses. The integration is particularly valuable for research tasks, information gathering, content discovery, and answering questions that require up-to-date information from across the web.
+In Sim, the Exa integration allows your agents to search the web for information, retrieve content from specific URLs, find similar resources, answer questions with citations, and conduct research tasks—all programmatically through API calls. This enables your agents to access real-time information from the internet, enhancing their ability to provide accurate, current, and relevant responses. The integration is particularly valuable for research tasks, information gathering, content discovery, and answering questions that require up-to-date information from across the web.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Search the web, retrieve content, find similar links, and answer questions using Exa
+Search the web, retrieve content, find similar links, and answer questions using Exa's powerful AI search capabilities.
 
 
 
@@ -59,22 +61,14 @@ Search the web using Exa AI. Returns relevant search results with titles, URLs,
 | `query` | string | Yes | The search query to execute |
 | `numResults` | number | No | Number of results to return \(default: 10, max: 25\) |
 | `useAutoprompt` | boolean | No | Whether to use autoprompt to improve the query \(default: false\) |
-| `type` | string | No | Search type: neural, keyword, auto or magic \(default: auto\) |
+| `type` | string | No | Search type: neural, keyword, auto or fast \(default: auto\) |
 | `apiKey` | string | Yes | Exa AI API Key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `results` | string |
-| `url` | string |
-| `publishedDate` | string |
-| `author` | string |
-| `summary` | string |
-| `favicon` | string |
-| `image` | string |
-| `text` | string |
-| `score` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Search results with titles, URLs, and text snippets |
 
 ### `exa_get_contents`
 
@@ -91,12 +85,9 @@ Retrieve the contents of webpages using Exa AI. Returns the title, text content,
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `results` | string |
-| `title` | string |
-| `text` | string |
-| `summary` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Retrieved content from URLs with title, text, and summaries |
 
 ### `exa_find_similar_links`
 
@@ -113,12 +104,9 @@ Find webpages similar to a given URL using Exa AI. Returns a list of similar lin
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `similarLinks` | string |
-| `url` | string |
-| `text` | string |
-| `score` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `similarLinks` | array | Similar links found with titles, URLs, and text snippets |
 
 ### `exa_answer`
 
@@ -134,36 +122,30 @@ Get an AI-generated answer to a question with citations from the web using Exa A
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `query` | string |
-| `answer` | string |
-| `citations` | string |
-| `url` | string |
-| `text` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `answer` | string | AI-generated answer to the question |
+| `citations` | array | Sources and citations for the answer |
 
+### `exa_research`
 
+Perform comprehensive research using AI to generate detailed reports with citations
 
-## Block Configuration
+#### Input
 
-### Input
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `query` | string | Yes | Research query or topic |
+| `includeText` | boolean | No | Include full text content in results |
+| `apiKey` | string | Yes | Exa AI API Key |
 
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
+#### Output
 
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `research` | array | Comprehensive research findings with citations and summaries |
 
 
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `results` | json | results of the response |
-| ↳ `similarLinks` | json | similarLinks of the response |
-| ↳ `answer` | string | answer of the response |
-| ↳ `citations` | json | citations of the response |
-
 
 ## Notes
 

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

@@ -50,7 +50,7 @@ The File Parser tool is particularly useful for scenarios where your agents need
 
 ## Usage Instructions
 
-Upload and extract contents from structured file formats including PDFs, CSV spreadsheets, and Word documents (DOCX). Upload files directly. Specialized parsers extract text and metadata from each format. You can upload multiple files at once and access them individually or as a combined document.
+Upload and extract contents from structured file formats including PDFs, CSV spreadsheets, and Word documents (DOCX). You can either provide a URL to a file or upload files directly. Specialized parsers extract text and metadata from each format. You can upload multiple files at once and access them individually or as a combined document.
 
 
 
@@ -69,29 +69,13 @@ Parse one or more uploaded files or files from URLs (text, PDF, CSV, images, etc
 
 #### Output
 
-This tool does not produce any outputs.
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `files` | array | Array of parsed files |
+| `combinedContent` | string | Combined content of all parsed files |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `inputMethod` | string | No |  |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `files` | json | files of the response |
-| ↳ `combinedContent` | string | combinedContent of the response |
-
-
 ## Notes
 
 - Category: `tools`

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

@@ -34,9 +34,9 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Firecrawl](https://firecrawl.dev/) is a powerful web scraping and content extraction API that integrates seamlessly into Sim Studio, enabling developers to extract clean, structured content from any website. This integration provides a simple way to transform web pages into usable data formats like Markdown and HTML while preserving the essential content.
+[Firecrawl](https://firecrawl.dev/) is a powerful web scraping and content extraction API that integrates seamlessly into Sim, enabling developers to extract clean, structured content from any website. This integration provides a simple way to transform web pages into usable data formats like Markdown and HTML while preserving the essential content.
 
-With Firecrawl in Sim Studio, you can:
+With Firecrawl in Sim, you can:
 
 - **Extract clean content**: Remove ads, navigation elements, and other distractions to get just the main content
 - **Convert to structured formats**: Transform web pages into Markdown, HTML, or JSON
@@ -44,8 +44,16 @@ With Firecrawl in Sim Studio, you can:
 - **Handle JavaScript-heavy sites**: Process content from modern web applications that rely on JavaScript
 - **Filter content**: Focus on specific parts of a page using CSS selectors
 - **Process at scale**: Handle high-volume scraping needs with a reliable API
+- **Search the web**: Perform intelligent web searches and retrieve structured results
+- **Crawl entire sites**: Crawl multiple pages from a website and aggregate their content
 
-The Firecrawl integration allows your agents to access and process web content programmatically without leaving the Sim Studio environment. This enables scenarios like research, content aggregation, data extraction, and information analysis from across the web. Your agents can gather information from websites, extract structured data, and use that information to make decisions or generate insights - all without having to navigate the complexities of raw HTML parsing or browser automation. Simply configure the Firecrawl block with your API key, provide the target URL, and your agents can immediately begin working with web content in a clean, structured format.
+In Sim, the Firecrawl integration enables your agents to access and process web content programmatically as part of their workflows. Supported operations include:
+
+- **Scrape**: Extract structured content (Markdown, HTML, metadata) from a single web page.
+- **Search**: Search the web for information using Firecrawl's intelligent search capabilities.
+- **Crawl**: Crawl multiple pages from a website, returning structured content and metadata for each page.
+
+This allows your agents to gather information from websites, extract structured data, and use that information to make decisions or generate insights—all without having to navigate the complexities of raw HTML parsing or browser automation. Simply configure the Firecrawl block with your API key, select the operation (Scrape, Search, or Crawl), and provide the relevant parameters. Your agents can immediately begin working with web content in a clean, structured format.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -65,17 +73,17 @@ Extract structured content from web pages with comprehensive metadata support. C
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Firecrawl API key |
 | `url` | string | Yes | The URL to scrape content from |
 | `scrapeOptions` | json | No | Options for content scraping |
+| `apiKey` | string | Yes | Firecrawl API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `markdown` | string |
-| `html` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `markdown` | string | Page content in markdown format |
+| `html` | string | Raw HTML content of the page |
+| `metadata` | object | Page metadata including SEO and Open Graph information |
 
 ### `firecrawl_search`
 
@@ -85,39 +93,35 @@ Search for information on the web using Firecrawl
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Firecrawl API key |
 | `query` | string | Yes | The search query to use |
+| `apiKey` | string | Yes | Firecrawl API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `warning` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | array | Search results data |
 
+### `firecrawl_crawl`
 
+Crawl entire websites and extract structured content from all accessible pages
 
-## Block Configuration
+#### Input
 
-### Input
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `url` | string | Yes | The website URL to crawl |
+| `limit` | number | No | Maximum number of pages to crawl \(default: 100\) |
+| `onlyMainContent` | boolean | No | Extract only main content from pages |
+| `apiKey` | string | Yes | Firecrawl API Key |
 
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `apiKey` | string | Yes |  |
+#### Output
 
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `pages` | array | Array of crawled pages with their content and metadata |
 
 
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `markdown` | string | markdown of the response |
-| ↳ `html` | any | html of the response |
-| ↳ `metadata` | json | metadata of the response |
-| ↳ `data` | json | data of the response |
-| ↳ `warning` | any | warning of the response |
-
 
 ## Notes
 

apps/docs/content/docs/tools/generic_webhook.mdx

@@ -0,0 +1,32 @@
+---
+title: Webhook
+description: Receive webhooks from any service
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="generic_webhook"
+  color="#10B981"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      fill='currentColor'
+      
+      
+      viewBox='0 0 24 24'
+      xmlns='http://www.w3.org/2000/svg'
+    >
+      <path d='M17.974 7A4.967 4.967 0 0 0 18 6.5a5.5 5.5 0 1 0-8.672 4.491L7.18 15.114A2.428 2.428 0 0 0 6.496 15 2.5 2.5 0 1 0 9 17.496a2.36 2.36 0 0 0-.93-1.925l2.576-4.943-.41-.241A4.5 4.5 0 1 1 17 6.5a4.8 4.8 0 0 1-.022.452zM6.503 18.999a1.5 1.5 0 1 1 1.496-1.503A1.518 1.518 0 0 1 6.503 19zM18.5 12a5.735 5.735 0 0 0-1.453.157l-2.744-3.941A2.414 2.414 0 0 0 15 6.5a2.544 2.544 0 1 0-1.518 2.284l3.17 4.557.36-.13A4.267 4.267 0 0 1 18.5 13a4.5 4.5 0 1 1-.008 9h-.006a4.684 4.684 0 0 1-3.12-1.355l-.703.71A5.653 5.653 0 0 0 18.49 23h.011a5.5 5.5 0 0 0 0-11zM11 6.5A1.5 1.5 0 1 1 12.5 8 1.509 1.509 0 0 1 11 6.5zM18.5 20a2.5 2.5 0 1 0-2.447-3h-5.05l-.003.497A4.546 4.546 0 0 1 6.5 22 4.526 4.526 0 0 1 2 17.5a4.596 4.596 0 0 1 3.148-4.37l-.296-.954A5.606 5.606 0 0 0 1 17.5 5.532 5.532 0 0 0 6.5 23a5.573 5.573 0 0 0 5.478-5h4.08a2.487 2.487 0 0 0 2.442 2zm0-4a1.5 1.5 0 1 1-1.5 1.5 1.509 1.509 0 0 1 1.5-1.5z' />
+      <path fill='none' d='M0 0h24v24H0z' />
+    </svg>`}
+/>
+
+
+
+
+
+## Notes
+
+- Category: `triggers`
+- Type: `generic_webhook`

apps/docs/content/docs/tools/github.mdx

@@ -1,6 +1,6 @@
 ---
 title: GitHub
-description: Interact with GitHub
+description: Interact with GitHub or trigger workflows from GitHub events
 ---
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
@@ -29,13 +29,13 @@ With GitHub, you can:
 - **Manage projects**: Organize work with project boards, milestones, and task tracking
 - **Document code**: Create and maintain documentation with GitHub Pages and wikis
 
-In Sim Studio, the GitHub integration enables your agents to interact directly with GitHub repositories and workflows. This allows for powerful automation scenarios such as code review assistance, pull request management, issue tracking, and repository exploration. Your agents can fetch repository data, analyze code changes, post comments on pull requests, and perform other GitHub operations programmatically. This integration bridges the gap between your AI workflows and your development processes, enabling seamless collaboration between your agents and your development team.
+In Sim, the GitHub integration enables your agents to interact directly with GitHub repositories and workflows. This allows for powerful automation scenarios such as code review assistance, pull request management, issue tracking, and repository exploration. Your agents can fetch repository data, analyze code changes, post comments on pull requests, and perform other GitHub operations programmatically. This integration bridges the gap between your AI workflows and your development processes, enabling seamless collaboration between your agents and your development team.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Access GitHub repositories, pull requests, and comments through the GitHub API. Automate code reviews, PR management, and repository interactions within your workflow.
+Access GitHub repositories, pull requests, and comments through the GitHub API. Automate code reviews, PR management, and repository interactions within your workflow. Trigger workflows from GitHub events like push, pull requests, and issues.
 
 
 
@@ -56,24 +56,10 @@ Fetch PR details including diff and files changed
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `title` | string |
-| `state` | string |
-| `html_url` | string |
-| `diff_url` | string |
-| `created_at` | string |
-| `updated_at` | string |
-| `files` | string |
-| `additions` | string |
-| `deletions` | string |
-| `changes` | string |
-| `patch` | string |
-| `blob_url` | string |
-| `raw_url` | string |
-| `status` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable PR summary |
+| `metadata` | object | Detailed PR metadata including file changes |
 
 ### `github_comment`
 
@@ -85,29 +71,22 @@ Create comments on GitHub PRs
 | --------- | ---- | -------- | ----------- |
 | `owner` | string | Yes | Repository owner |
 | `repo` | string | Yes | Repository name |
-| `pullNumber` | number | Yes | Pull request number |
 | `body` | string | Yes | Comment content |
+| `pullNumber` | number | Yes | Pull request number |
 | `path` | string | No | File path for review comment |
 | `position` | number | No | Line number for review comment |
-| `apiKey` | string | Yes | GitHub API token |
 | `commentType` | string | No | Type of comment \(pr_comment or file_comment\) |
 | `line` | number | No | Line number for review comment |
 | `side` | string | No | Side of the diff \(LEFT or RIGHT\) |
 | `commitId` | string | No | The SHA of the commit to comment on |
+| `apiKey` | string | Yes | GitHub API token |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `html_url` | string |
-| `created_at` | string |
-| `updated_at` | string |
-| `path` | string |
-| `line` | string |
-| `side` | string |
-| `commit_id` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable comment confirmation |
+| `metadata` | object | Comment metadata |
 
 ### `github_repo_info`
 
@@ -123,15 +102,10 @@ Retrieve comprehensive GitHub repository metadata including stars, forks, issues
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `description` | string |
-| `stars` | string |
-| `forks` | string |
-| `openIssues` | string |
-| `language` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable repository summary |
+| `metadata` | object | Repository metadata |
 
 ### `github_latest_commit`
 
@@ -143,42 +117,18 @@ Retrieve the latest commit from a GitHub repository
 | --------- | ---- | -------- | ----------- |
 | `owner` | string | Yes | Repository owner \(user or organization\) |
 | `repo` | string | Yes | Repository name |
-| `branch` | string | No | Branch name \(defaults to the repository |
+| `branch` | string | No | Branch name \(defaults to the repository's default branch\) |
 | `apiKey` | string | Yes | GitHub API token |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `html_url` | string |
-| `commit_message` | string |
-| `author` | string |
-| `login` | string |
-| `avatar_url` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable commit summary |
+| `metadata` | object | Commit metadata |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `metadata` | json | metadata of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/gmail.mdx

@@ -1,6 +1,6 @@
 ---
 title: Gmail
-description: Send Gmail
+description: Send Gmail or trigger workflows from Gmail events
 ---
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
@@ -45,13 +45,13 @@ With Gmail, you can:
 - **Access from anywhere**: Use Gmail across devices with synchronized content and settings
 - **Integrate with other services**: Connect with Google Calendar, Drive, and other productivity tools
 
-In Sim Studio, the Gmail integration enables your agents to send, read, and search emails programmatically. This allows for powerful automation scenarios such as sending notifications, processing incoming messages, extracting information from emails, and managing communication workflows. Your agents can compose and send personalized emails, search for specific messages using Gmail's query syntax, and extract content from emails to use in other parts of your workflow. Coming soon, agents will also be able to listen for new emails in real-time, enabling responsive workflows that can trigger actions based on incoming messages. This integration bridges the gap between your AI workflows and email communications, enabling seamless interaction with one of the world's most widely used communication platforms.
+In Sim, the Gmail integration enables your agents to send, read, and search emails programmatically. This allows for powerful automation scenarios such as sending notifications, processing incoming messages, extracting information from emails, and managing communication workflows. Your agents can compose and send personalized emails, search for specific messages using Gmail's query syntax, and extract content from emails to use in other parts of your workflow. Coming soon, agents will also be able to listen for new emails in real-time, enabling responsive workflows that can trigger actions based on incoming messages. This integration bridges the gap between your AI workflows and email communications, enabling seamless interaction with one of the world's most widely used communication platforms.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Integrate Gmail functionality to send email messages within your workflow. Automate email communications and process email content using OAuth authentication.
+Comprehensive Gmail integration with OAuth authentication. Send email messages, read email content, and trigger workflows from Gmail events like new emails and label changes.
 
 
 
@@ -65,19 +65,39 @@ Send emails using Gmail
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Gmail API |
 | `to` | string | Yes | Recipient email address |
 | `subject` | string | Yes | Email subject |
 | `body` | string | Yes | Email body content |
+| `cc` | string | No | CC recipients \(comma-separated\) |
+| `bcc` | string | No | BCC recipients \(comma-separated\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `threadId` | string |
-| `labelIds` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Success message |
+| `metadata` | object | Email metadata |
+
+### `gmail_draft`
+
+Draft emails using Gmail
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `to` | string | Yes | Recipient email address |
+| `subject` | string | Yes | Email subject |
+| `body` | string | Yes | Email body content |
+| `cc` | string | No | CC recipients \(comma-separated\) |
+| `bcc` | string | No | BCC recipients \(comma-separated\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Success message |
+| `metadata` | object | Draft metadata |
 
 ### `gmail_read`
 
@@ -87,18 +107,19 @@ Read emails from Gmail
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Gmail API |
 | `messageId` | string | No | ID of the message to read |
 | `folder` | string | No | Folder/label to read emails from |
 | `unreadOnly` | boolean | No | Only retrieve unread messages |
 | `maxResults` | number | No | Maximum number of messages to retrieve \(default: 1, max: 10\) |
+| `includeAttachments` | boolean | No | Download and include email attachments |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Text content of the email |
+| `metadata` | json | Metadata of the email |
+| `attachments` | file[] | Attachments of the email |
 
 ### `gmail_search`
 
@@ -108,33 +129,18 @@ Search emails in Gmail
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Gmail API |
 | `query` | string | Yes | Search query for emails |
 | `maxResults` | number | No | Maximum number of results to return |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Search results summary |
+| `metadata` | object | Search metadata |
 
 
 
-## Block Configuration
-
-No configuration parameters required.
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `metadata` | json | metadata of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/google_calendar.mdx

@@ -84,13 +84,13 @@ With Google Calendar, you can:
 - **View and search events**: Easily find and access your scheduled events across multiple calendars
 - **Manage multiple calendars**: Organize different types of events across various calendars
 
-In Sim Studio, the Google Calendar integration enables your agents to programmatically create, read, and manage calendar events. This allows for powerful automation scenarios such as scheduling meetings, sending calendar invites, checking availability, and managing event details. Your agents can create events with natural language input, send automated calendar invitations to attendees, retrieve event information, and list upcoming events. This integration bridges the gap between your AI workflows and calendar management, enabling seamless scheduling automation and coordination with one of the world's most widely used calendar platforms.
+In Sim, the Google Calendar integration enables your agents to programmatically create, read, and manage calendar events. This allows for powerful automation scenarios such as scheduling meetings, sending calendar invites, checking availability, and managing event details. Your agents can create events with natural language input, send automated calendar invitations to attendees, retrieve event information, and list upcoming events. This integration bridges the gap between your AI workflows and calendar management, enabling seamless scheduling automation and coordination with one of the world's most widely used calendar platforms.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Integrate Google Calendar functionality to create, read, update, and list calendar events within your workflow. Automate scheduling, check availability, and manage events using OAuth authentication. Email invitations are sent asynchronously and delivery depends on recipients
+Integrate Google Calendar functionality to create, read, update, and list calendar events within your workflow. Automate scheduling, check availability, and manage events using OAuth authentication. Email invitations are sent asynchronously and delivery depends on recipients' Google Calendar settings.
 
 
 
@@ -104,7 +104,6 @@ Create a new event in Google Calendar
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
 | `calendarId` | string | No | Calendar ID \(defaults to primary\) |
 | `summary` | string | Yes | Event title/summary |
 | `description` | string | No | Event description |
@@ -117,9 +116,10 @@ Create a new event in Google Calendar
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Event creation confirmation message |
+| `metadata` | json | Created event metadata including ID, status, and details |
 
 ### `google_calendar_list`
 
@@ -129,7 +129,6 @@ List events from Google Calendar
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
 | `calendarId` | string | No | Calendar ID \(defaults to primary\) |
 | `timeMin` | string | No | Lower bound for events \(RFC3339 timestamp, e.g., 2025-06-03T00:00:00Z\) |
 | `timeMax` | string | No | Upper bound for events \(RFC3339 timestamp, e.g., 2025-06-04T00:00:00Z\) |
@@ -138,9 +137,10 @@ List events from Google Calendar
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Summary of found events count |
+| `metadata` | json | List of events with pagination tokens and event details |
 
 ### `google_calendar_get`
 
@@ -150,15 +150,15 @@ Get a specific event from Google Calendar
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
 | `calendarId` | string | No | Calendar ID \(defaults to primary\) |
 | `eventId` | string | Yes | Event ID to retrieve |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Event retrieval confirmation message |
+| `metadata` | json | Event details including ID, status, times, and attendees |
 
 ### `google_calendar_quick_add`
 
@@ -168,17 +168,17 @@ Create events from natural language text
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
 | `calendarId` | string | No | Calendar ID \(defaults to primary\) |
-| `text` | string | Yes | Natural language text describing the event \(e.g.,  |
+| `text` | string | Yes | Natural language text describing the event \(e.g., "Meeting with John tomorrow at 3pm"\) |
 | `attendees` | array | No | Array of attendee email addresses \(comma-separated string also accepted\) |
 | `sendUpdates` | string | No | How to send updates to attendees: all, externalOnly, or none |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Event creation confirmation message from natural language |
+| `metadata` | json | Created event metadata including parsed details |
 
 ### `google_calendar_invite`
 
@@ -188,7 +188,6 @@ Invite attendees to an existing Google Calendar event
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
 | `calendarId` | string | No | Calendar ID \(defaults to primary\) |
 | `eventId` | string | Yes | Event ID to invite attendees to |
 | `attendees` | array | Yes | Array of attendee email addresses to invite |
@@ -197,42 +196,13 @@ Invite attendees to an existing Google Calendar event
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `htmlLink` | string |
-| `status` | string |
-| `summary` | string |
-| `description` | string |
-| `location` | string |
-| `start` | string |
-| `end` | string |
-| `attendees` | string |
-| `creator` | string |
-| `organizer` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Attendee invitation confirmation message with email delivery status |
+| `metadata` | json | Updated event metadata including attendee list and details |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `metadata` | json | metadata of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/google_docs.mdx

@@ -29,37 +29,37 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Docs](https://docs.google.com) is a powerful cloud-based document creation and editing service that allows users to create, edit, and collaborate on documents in real-time. As part of Google's productivity suite, Google Docs offers a versatile platform for text documents with robust formatting, commenting, and sharing capabilities.
 
-Learn how to integrate the Google Docs "Read" tool in Sim Studio to effortlessly fetch data from your docs and to integrate into your workflows. This tutorial walks you through connecting Google Docs, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
+Learn how to integrate the Google Docs "Read" tool in Sim to effortlessly fetch data from your docs and to integrate into your workflows. This tutorial walks you through connecting Google Docs, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/f41gy9rBHhE"
-  title="Use the Google Docs Read tool in Sim Studio"
+  title="Use the Google Docs Read tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Learn how to integrate the Google Docs "Update" tool in Sim Studio to effortlessly add content in your docs through your workflows. This tutorial walks you through connecting Google Docs, configuring data writes, and using that information to automate document updates seamlessly. Perfect for maintaining dynamic, real-time documentation with minimal effort.
+Learn how to integrate the Google Docs "Update" tool in Sim to effortlessly add content in your docs through your workflows. This tutorial walks you through connecting Google Docs, configuring data writes, and using that information to automate document updates seamlessly. Perfect for maintaining dynamic, real-time documentation with minimal effort.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/L64ROHS2ivA"
-  title="Use the Google Docs Update tool in Sim Studio"
+  title="Use the Google Docs Update tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Learn how to integrate the Google Docs "Create" tool in Sim Studio to effortlessly generate new documents through your workflows. This tutorial walks you through connecting Google Docs, setting up document creation, and using workflow data to populate content automatically. Perfect for streamlining document generation and enhancing productivity.
+Learn how to integrate the Google Docs "Create" tool in Sim to effortlessly generate new documents through your workflows. This tutorial walks you through connecting Google Docs, setting up document creation, and using workflow data to populate content automatically. Perfect for streamlining document generation and enhancing productivity.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/lWpHH4qddWk"
-  title="Use the Google Docs Create tool in Sim Studio"
+  title="Use the Google Docs Create tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -75,7 +75,7 @@ With Google Docs, you can:
 - **Work offline**: Continue working without internet connection with changes syncing when back online
 - **Integrate with other services**: Connect with Google Drive, Sheets, Slides, and third-party applications
 
-In Sim Studio, the Google Docs integration enables your agents to interact directly with document content programmatically. This allows for powerful automation scenarios such as document creation, content extraction, collaborative editing, and document management. Your agents can read existing documents to extract information, write to documents to update content, and create new documents from scratch. This integration bridges the gap between your AI workflows and document management, enabling seamless interaction with one of the world's most widely used document platforms. By connecting Sim Studio with Google Docs, you can automate document workflows, generate reports, extract insights from documents, and maintain documentation - all through your intelligent agents.
+In Sim, the Google Docs integration enables your agents to interact directly with document content programmatically. This allows for powerful automation scenarios such as document creation, content extraction, collaborative editing, and document management. Your agents can read existing documents to extract information, write to documents to update content, and create new documents from scratch. This integration bridges the gap between your AI workflows and document management, enabling seamless interaction with one of the world's most widely used document platforms. By connecting Sim with Google Docs, you can automate document workflows, generate reports, extract insights from documents, and maintain documentation - all through your intelligent agents.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -95,15 +95,14 @@ Read content from a Google Docs document
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Docs API |
 | `documentId` | string | Yes | The ID of the document to read |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Extracted document text content |
+| `metadata` | json | Document metadata including ID, title, and URL |
 
 ### `google_docs_write`
 
@@ -113,16 +112,15 @@ Write or update content in a Google Docs document
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Docs API |
 | `documentId` | string | Yes | The ID of the document to write to |
 | `content` | string | Yes | The content to write to the document |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedContent` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedContent` | boolean | Indicates if document content was updated successfully |
+| `metadata` | json | Updated document metadata including ID, title, and URL |
 
 ### `google_docs_create`
 
@@ -132,39 +130,19 @@ Create a new Google Docs document
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Docs API |
 | `title` | string | Yes | The title of the document to create |
 | `content` | string | No | The content of the document to create |
-| `folderId` | string | No | The ID of the folder to create the document in |
+| `folderSelector` | string | No | Select the folder to create the document in |
+| `folderId` | string | No | The ID of the folder to create the document in \(internal use\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `metadata` | json | Created document metadata including ID, title, and URL |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `metadata` | json | metadata of the response |
-| ↳ `updatedContent` | boolean | updatedContent of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/google_drive.mdx

@@ -46,13 +46,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Drive](https://drive.google.com) is Google's cloud storage and file synchronization service that allows users to store files, synchronize files across devices, and share files with others. As a core component of Google's productivity ecosystem, Google Drive offers robust storage, organization, and collaboration capabilities.
 
-Learn how to integrate the Google Drive tool in Sim Studio to effortlessly pull information from your Drive through your workflows. This tutorial walks you through connecting Google Drive, setting up data retrieval, and using stored documents and files to enhance automation. Perfect for syncing important data with your agents in real-time.
+Learn how to integrate the Google Drive tool in Sim to effortlessly pull information from your Drive through your workflows. This tutorial walks you through connecting Google Drive, setting up data retrieval, and using stored documents and files to enhance automation. Perfect for syncing important data with your agents in real-time.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/cRoRr4b-EAs"
-  title="Use the Google Drive tool in Sim Studio"
+  title="Use the Google Drive tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -67,7 +67,7 @@ With Google Drive, you can:
 - **Access across devices**: Use Google Drive on desktop, mobile, and web platforms
 - **Integrate with other services**: Connect with Google Docs, Sheets, Slides, and third-party applications
 
-In Sim Studio, the Google Drive integration enables your agents to interact directly with your cloud storage programmatically. This allows for powerful automation scenarios such as file management, content organization, and document workflows. Your agents can upload new files to specific folders, download existing files to process their contents, and list folder contents to navigate your storage structure. This integration bridges the gap between your AI workflows and your document management system, enabling seamless file operations without manual intervention. By connecting Sim Studio with Google Drive, you can automate file-based workflows, manage documents intelligently, and incorporate cloud storage operations into your agent's capabilities.
+In Sim, the Google Drive integration enables your agents to interact directly with your cloud storage programmatically. This allows for powerful automation scenarios such as file management, content organization, and document workflows. Your agents can upload new files to specific folders, download existing files to process their contents, and list folder contents to navigate your storage structure. This integration bridges the gap between your AI workflows and your document management system, enabling seamless file operations without manual intervention. By connecting Sim with Google Drive, you can automate file-based workflows, manage documents intelligently, and incorporate cloud storage operations into your agent's capabilities.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -87,25 +87,17 @@ Upload a file to Google Drive
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Drive API |
 | `fileName` | string | Yes | The name of the file to upload |
 | `content` | string | Yes | The content of the file to upload |
 | `mimeType` | string | No | The MIME type of the file to upload |
-| `folderId` | string | No | The ID of the folder to upload the file to |
+| `folderSelector` | string | No | Select the folder to upload the file to |
+| `folderId` | string | No | The ID of the folder to upload the file to \(internal use\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `file` | string |
-| `name` | string |
-| `mimeType` | string |
-| `webViewLink` | string |
-| `webContentLink` | string |
-| `size` | string |
-| `createdTime` | string |
-| `modifiedTime` | string |
-| `parents` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `file` | json | Uploaded file metadata including ID, name, and links |
 
 ### `google_drive_create_folder`
 
@@ -115,23 +107,15 @@ Create a new folder in Google Drive
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Drive API |
 | `fileName` | string | Yes | Name of the folder to create |
-| `folderId` | string | No | ID of the parent folder \(leave empty for root folder\) |
+| `folderSelector` | string | No | Select the parent folder to create the folder in |
+| `folderId` | string | No | ID of the parent folder \(internal use\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `file` | string |
-| `name` | string |
-| `mimeType` | string |
-| `webViewLink` | string |
-| `webContentLink` | string |
-| `size` | string |
-| `createdTime` | string |
-| `modifiedTime` | string |
-| `parents` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `file` | json | Created folder metadata including ID, name, and parent information |
 
 ### `google_drive_list`
 
@@ -141,47 +125,20 @@ List files and folders in Google Drive
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Drive API |
-| `folderId` | string | No | The ID of the folder to list files from |
+| `folderSelector` | string | No | Select the folder to list files from |
+| `folderId` | string | No | The ID of the folder to list files from \(internal use\) |
 | `query` | string | No | A query to filter the files |
 | `pageSize` | number | No | The number of files to return |
 | `pageToken` | string | No | The page token to use for pagination |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `files` | string |
-| `name` | string |
-| `mimeType` | string |
-| `webViewLink` | string |
-| `webContentLink` | string |
-| `size` | string |
-| `createdTime` | string |
-| `modifiedTime` | string |
-| `parents` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `files` | json | Array of file metadata objects from the specified folder |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `file` | json | file of the response |
-| ↳ `files` | json | files of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/google_search.mdx

@@ -32,13 +32,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Search](https://www.google.com) is the world's most widely used search engine, providing access to billions of web pages and information sources. Google Search uses sophisticated algorithms to deliver relevant search results based on user queries, making it an essential tool for finding information on the internet.
 
-Learn how to integrate the Google Search tool in Sim Studio to effortlessly fetch real-time search results through your workflows. This tutorial walks you through connecting Google Search, configuring search queries, and using live data to enhance automation. Perfect for powering your agents with up-to-date information and smarter decision-making.
+Learn how to integrate the Google Search tool in Sim to effortlessly fetch real-time search results through your workflows. This tutorial walks you through connecting Google Search, configuring search queries, and using live data to enhance automation. Perfect for powering your agents with up-to-date information and smarter decision-making.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/1B7hV9b5UMQ"
-  title="Use the Google Search tool in Sim Studio"
+  title="Use the Google Search tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -52,7 +52,7 @@ With Google Search, you can:
 - **Access knowledge graphs**: Get structured information about people, places, and things
 - **Utilize search features**: Take advantage of specialized search tools like calculators, unit converters, and more
 
-In Sim Studio, the Google Search integration enables your agents to search the web programmatically and incorporate search results into their workflows. This allows for powerful automation scenarios such as research, fact-checking, data gathering, and information synthesis. Your agents can formulate search queries, retrieve relevant results, and extract information from those results to make decisions or generate insights. This integration bridges the gap between your AI workflows and the vast information available on the web, enabling your agents to access up-to-date information from across the internet. By connecting Sim Studio with Google Search, you can create agents that stay informed with the latest information, verify facts, conduct research, and provide users with relevant web content - all without leaving your workflow.
+In Sim, the Google Search integration enables your agents to search the web programmatically and incorporate search results into their workflows. This allows for powerful automation scenarios such as research, fact-checking, data gathering, and information synthesis. Your agents can formulate search queries, retrieve relevant results, and extract information from those results to make decisions or generate insights. This integration bridges the gap between your AI workflows and the vast information available on the web, enabling your agents to access up-to-date information from across the internet. By connecting Sim with Google Search, you can create agents that stay informed with the latest information, verify facts, conduct research, and provide users with relevant web content - all without leaving your workflow.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -73,36 +73,18 @@ Search the web with the Custom Search API
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `query` | string | Yes | The search query to execute |
-| `apiKey` | string | Yes | Google API key |
 | `searchEngineId` | string | Yes | Custom Search Engine ID |
 | `num` | string | No | Number of results to return \(default: 10, max: 10\) |
+| `apiKey` | string | Yes | Google API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `items` | string |
-| `searchInformation` | string |
-| `searchTime` | string |
-| `formattedSearchTime` | string |
-| `formattedTotalResults` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `items` | array | Array of search results from Google |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `query` | string | Yes | Search Query - Enter your search query |
-
-
-
-### Outputs
-
-This block does not produce any outputs.
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/google_sheets.mdx

@@ -32,49 +32,49 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Sheets](https://sheets.google.com) is a powerful cloud-based spreadsheet application that allows users to create, edit, and collaborate on spreadsheets in real-time. As part of Google's productivity suite, Google Sheets offers a versatile platform for data organization, analysis, and visualization with robust formatting, formula, and sharing capabilities.
 
-Learn how to integrate the Google Sheets "Read" tool in Sim Studio to effortlessly fetch data from your spreadsheets to integrate into your workflows. This tutorial walks you through connecting Google Sheets, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
+Learn how to integrate the Google Sheets "Read" tool in Sim to effortlessly fetch data from your spreadsheets to integrate into your workflows. This tutorial walks you through connecting Google Sheets, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/xxP7MZRuq_0"
-  title="Use the Google Sheets Read tool in Sim Studio"
+  title="Use the Google Sheets Read tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Discover how to use the Google Sheets "Write" tool in Sim Studio to automatically send data from your workflows to your Google Sheets. This tutorial covers setting up the integration, configuring write operations, and updating your sheets seamlessly as workflows execute. Perfect for maintaining real-time records without manual input.
+Discover how to use the Google Sheets "Write" tool in Sim to automatically send data from your workflows to your Google Sheets. This tutorial covers setting up the integration, configuring write operations, and updating your sheets seamlessly as workflows execute. Perfect for maintaining real-time records without manual input.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/cO86qTj7qeY"
-  title="Use the Google Sheets Write tool in Sim Studio"
+  title="Use the Google Sheets Write tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Explore how to leverage the Google Sheets "Update" tool in Sim Studio to modify existing entries in your spreadsheets based on workflow execution. This tutorial demonstrates setting up the update logic, mapping data fields, and synchronizing changes instantly. Perfect for keeping your data current and consistent.
+Explore how to leverage the Google Sheets "Update" tool in Sim to modify existing entries in your spreadsheets based on workflow execution. This tutorial demonstrates setting up the update logic, mapping data fields, and synchronizing changes instantly. Perfect for keeping your data current and consistent.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/95by2fL9yn4"
-  title="Use the Google Sheets Update tool in Sim Studio"
+  title="Use the Google Sheets Update tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Learn how to use the Google Sheets "Append" tool in Sim Studio to effortlessly add new rows of data to your spreadsheets during workflow execution. This tutorial walks you through setting up the integration, configuring append actions, and ensuring smooth data growth. Perfect for expanding records without manual effort!
+Learn how to use the Google Sheets "Append" tool in Sim to effortlessly add new rows of data to your spreadsheets during workflow execution. This tutorial walks you through setting up the integration, configuring append actions, and ensuring smooth data growth. Perfect for expanding records without manual effort!
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/8DgNvLBCsAo"
-  title="Use the Google Sheets Append tool in Sim Studio"
+  title="Use the Google Sheets Append tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -90,7 +90,7 @@ With Google Sheets, you can:
 - **Work offline**: Continue working without internet connection with changes syncing when back online
 - **Integrate with other services**: Connect with Google Drive, Forms, and third-party applications
 
-In Sim Studio, the Google Sheets integration enables your agents to interact directly with spreadsheet data programmatically. This allows for powerful automation scenarios such as data extraction, analysis, reporting, and management. Your agents can read existing spreadsheets to extract information, write to spreadsheets to update data, and create new spreadsheets from scratch. This integration bridges the gap between your AI workflows and data management, enabling seamless interaction with structured data. By connecting Sim Studio with Google Sheets, you can automate data workflows, generate reports, extract insights from data, and maintain up-to-date information - all through your intelligent agents. The integration supports various data formats and range specifications, making it flexible enough to handle diverse data management needs while maintaining the collaborative and accessible nature of Google Sheets.
+In Sim, the Google Sheets integration enables your agents to interact directly with spreadsheet data programmatically. This allows for powerful automation scenarios such as data extraction, analysis, reporting, and management. Your agents can read existing spreadsheets to extract information, write to spreadsheets to update data, and create new spreadsheets from scratch. This integration bridges the gap between your AI workflows and data management, enabling seamless interaction with structured data. By connecting Sim with Google Sheets, you can automate data workflows, generate reports, extract insights from data, and maintain up-to-date information - all through your intelligent agents. The integration supports various data formats and range specifications, making it flexible enough to handle diverse data management needs while maintaining the collaborative and accessible nature of Google Sheets.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -110,15 +110,15 @@ Read data from a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to read from |
 | `range` | string | No | The range of cells to read from |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | json | Sheet data including range and cell values |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 ### `google_sheets_write`
 
@@ -128,7 +128,6 @@ Write data to a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to write to |
 | `range` | string | No | The range of cells to write to |
 | `values` | array | Yes | The data to write to the spreadsheet |
@@ -137,15 +136,13 @@ Write data to a Google Sheets spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedRange` | string |
-| `updatedRows` | string |
-| `updatedColumns` | string |
-| `updatedCells` | string |
-| `metadata` | string |
-| `spreadsheetId` | string |
-| `spreadsheetUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedRange` | string | Range of cells that were updated |
+| `updatedRows` | number | Number of rows updated |
+| `updatedColumns` | number | Number of columns updated |
+| `updatedCells` | number | Number of cells updated |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 ### `google_sheets_update`
 
@@ -155,7 +152,6 @@ Update data in a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to update |
 | `range` | string | No | The range of cells to update |
 | `values` | array | Yes | The data to update in the spreadsheet |
@@ -164,15 +160,13 @@ Update data in a Google Sheets spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedRange` | string |
-| `updatedRows` | string |
-| `updatedColumns` | string |
-| `updatedCells` | string |
-| `metadata` | string |
-| `spreadsheetId` | string |
-| `spreadsheetUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedRange` | string | Range of cells that were updated |
+| `updatedRows` | number | Number of rows updated |
+| `updatedColumns` | number | Number of columns updated |
+| `updatedCells` | number | Number of cells updated |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 ### `google_sheets_append`
 
@@ -182,7 +176,6 @@ Append data to the end of a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to append to |
 | `range` | string | No | The range of cells to append after |
 | `values` | array | Yes | The data to append to the spreadsheet |
@@ -192,36 +185,17 @@ Append data to the end of a Google Sheets spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `tableRange` | string | Range of the table where data was appended |
+| `updatedRange` | string | Range of cells that were updated |
+| `updatedRows` | number | Number of rows updated |
+| `updatedColumns` | number | Number of columns updated |
+| `updatedCells` | number | Number of cells updated |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `data` | json | data of the response |
-| ↳ `metadata` | json | metadata of the response |
-| ↳ `updatedRange` | string | updatedRange of the response |
-| ↳ `updatedRows` | number | updatedRows of the response |
-| ↳ `updatedColumns` | number | updatedColumns of the response |
-| ↳ `updatedCells` | number | updatedCells of the response |
-| ↳ `tableRange` | string | tableRange of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/guesty.mdx

@@ -1,124 +0,0 @@
----
-title: Guesty
-description: Interact with Guesty property management system
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="guesty"
-  color="#0051F8"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      
-      
-      viewBox='0 0 101 100'
-      fill='none'
-      xmlns='http://www.w3.org/2000/svg'
-    >
-      <path
-        d='M56.6019 2.6685C53.2445 0.339792 48.8025 0.308905 45.413 2.5907L44.1323 3.45286C44.1309 3.45379 44.1296 3.45471 44.1282 3.45564L5.37916 29.5416C5.37801 29.5424 5.37687 29.5431 5.37572 29.5439L4.37839 30.2153C1.64126 32.058 0 35.1414 0 38.441V90.0841C0 95.5599 4.4395 100 9.91593 100H67.4737C72.9501 100 77.389 95.5605 77.389 90.0841V49.6765C77.389 46.3038 75.675 43.1622 72.8385 41.3373L56.3027 30.6989C53.0908 28.6325 48.9777 28.5944 45.728 30.6009L28.3986 41.301C25.4732 43.1073 23.6922 46.3001 23.6922 49.7382V75.553H33.3248V51.0025C33.3248 50.1189 33.7823 49.2983 34.5337 48.8337L34.535 48.8329L49.5731 39.5476C50.408 39.0322 51.4645 39.0414 52.29 39.5714L66.5886 48.7705C67.3167 49.24 67.7564 50.0471 67.7564 50.9134V87.8176C67.7564 89.2256 66.6152 90.3674 65.2072 90.3674H12.1824C10.7742 90.3674 9.63262 89.2256 9.63262 87.8176V39.6474C9.63262 38.7995 10.0541 38.0071 10.7571 37.5331L49.5075 11.4463C50.3783 10.8601 51.5192 10.8675 52.3822 11.4646L89.8995 37.4867C89.9007 37.4877 89.9024 37.4886 89.9035 37.4896C90.588 37.9663 90.9959 38.7476 90.9959 39.5819V100H100.629V38.3956C100.629 35.1448 99.0352 32.1005 96.3641 30.2478L95.3969 29.5767C95.3941 29.575 95.3918 29.5733 95.3895 29.5717L56.6019 2.6685Z'
-        fill='currentColor'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Guesty](https://www.guesty.com) is a comprehensive property management platform designed for short-term and vacation rental property managers. It provides a centralized system to manage listings, reservations, guest communications, and operations across multiple booking channels like Airbnb, Booking.com, and VRBO.
-
-With Guesty, property managers can:
-
-- **Centralize operations**: Manage multiple properties and listings from a single dashboard
-- **Automate workflows**: Set up automated messaging, task assignments, and cleaning schedules
-- **Synchronize calendars**: Keep availability updated across all booking channels
-- **Process payments**: Handle secure payment processing and financial reporting
-- **Manage guest communications**: Streamline guest interactions through unified inbox
-- **Generate reports**: Access analytics and insights to optimize property performance
-
-In Sim Studio, the Guesty integration enables your agents to interact directly with your property management system programmatically. This allows for powerful automation scenarios such as reservation management, guest communication, and operational workflows. Your agents can retrieve detailed reservation information by ID, including guest details, booking dates, and property information. They can also search for guests by phone number to access their profiles and booking history. This integration bridges the gap between your AI workflows and your property management operations, enabling seamless handling of hospitality tasks without manual intervention. By connecting Sim Studio with Guesty, you can automate guest communications, streamline check-in processes, manage reservation details, and enhance the overall guest experience through intelligent automation.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Access Guesty property management data including reservations and guest information. Retrieve reservation details by ID or search for guests by phone number.
-
-
-
-## Tools
-
-### `guesty_reservation`
-
-Fetch reservation details from Guesty by reservation ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Your Guesty API token |
-| `reservationId` | string | Yes | The ID of the reservation to fetch |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `id` | string |
-| `guest` | string |
-| `email` | string |
-| `phone` | string |
-
-### `guesty_guest`
-
-Search for guests in Guesty by phone number
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Your Guesty API token |
-| `phoneNumber` | string | Yes | The phone number to search for |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `guests` | string |
-| `fullName` | string |
-| `email` | string |
-| `phone` | string |
-| `address` | string |
-| `city` | string |
-| `country` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `action` | string | Yes | Action |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `id` | string | id of the response |
-| ↳ `guest` | json | guest of the response |
-| ↳ `checkIn` | string | checkIn of the response |
-| ↳ `checkOut` | string | checkOut of the response |
-| ↳ `status` | string | status of the response |
-| ↳ `listing` | json | listing of the response |
-| ↳ `money` | json | money of the response |
-| ↳ `guests` | json | guests of the response |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `guesty`

apps/docs/content/docs/tools/huggingface.mdx

@@ -60,7 +60,7 @@ Natural language processing: Process and analyze text with specialized NLP model
 Deploy at scale: Host and serve models for production applications
 Customize models: Fine-tune existing models for specific use cases
 
-In Sim Studio, the HuggingFace integration enables your agents to programmatically generate completions using the HuggingFace Inference API. This allows for powerful automation scenarios such as content generation, text analysis, code completion, and creative writing. Your agents can generate completions with natural language prompts, access specialized models for different tasks, and integrate AI-generated content into workflows. This integration bridges the gap between your AI workflows and machine learning capabilities, enabling seamless AI-powered automation with one of the world's most comprehensive ML platforms.
+In Sim, the HuggingFace integration enables your agents to programmatically generate completions using the HuggingFace Inference API. This allows for powerful automation scenarios such as content generation, text analysis, code completion, and creative writing. Your agents can generate completions with natural language prompts, access specialized models for different tasks, and integrate AI-generated content into workflows. This integration bridges the gap between your AI workflows and machine learning capabilities, enabling seamless AI-powered automation with one of the world's most comprehensive ML platforms.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -80,47 +80,23 @@ Generate completions using Hugging Face Inference API
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Hugging Face API token |
+| `systemPrompt` | string | No | System prompt to guide the model behavior |
+| `content` | string | Yes | The user message content to send to the model |
 | `provider` | string | Yes | The provider to use for the API request \(e.g., novita, cerebras, etc.\) |
 | `model` | string | Yes | Model to use for chat completions \(e.g., deepseek/deepseek-v3-0324\) |
-| `content` | string | Yes | The user message content to send to the model |
-| `systemPrompt` | string | No | System prompt to guide the model behavior |
 | `maxTokens` | number | No | Maximum number of tokens to generate |
 | `temperature` | number | No | Sampling temperature \(0-2\). Higher values make output more random |
-| `stream` | boolean | No | Whether to stream the response |
+| `apiKey` | string | Yes | Hugging Face API token |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `model` | string |
-| `usage` | string |
-| `completion_tokens` | string |
-| `total_tokens` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Chat completion results |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `systemPrompt` | string | No | System Prompt - Enter system prompt to guide the model behavior... |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `model` | string | model of the response |
-| ↳ `usage` | json | usage of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/hunter.mdx

@@ -0,0 +1,211 @@
+---
+title: Hunter io
+description: Find and verify professional email addresses
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="hunter"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      
+      
+      viewBox='0 0 20 19'
+      fill='none'
+      xmlns='http://www.w3.org/2000/svg'
+    >
+      <path
+        d='M12.0671 8.43455C11.6625 8.55094 11.2164 8.55288 10.7992 8.53525C10.3141 8.51472 9.80024 8.45339 9.35223 8.25426C8.98359 8.09047 8.68787 7.79493 8.84262 7.36805C8.95175 7.06699 9.19361 6.79803 9.47319 6.64644C9.78751 6.4759 10.1329 6.50361 10.4474 6.65774C10.8005 6.83082 11.0942 7.11235 11.3604 7.3964C11.5 7.54536 11.6332 7.70002 11.7646 7.85617C11.8252 7.92801 12.2364 8.33865 12.0671 8.43455ZM18.7923 8.58131C18.17 8.43655 17.4348 8.4884 16.811 8.38867C15.8284 8.23146 14.3648 7.08576 13.5714 5.92122C13.0201 5.11202 12.757 4.28785 12.3356 3.28356C12.0415 2.58257 11.4001 0.365389 10.5032 1.40318C10.1339 1.83057 9.7204 3.23752 9.41837 3.2177C9.19467 3.26971 9.15818 2.83371 9.08739 2.64738C8.95886 2.30903 8.89071 1.9176 8.7185 1.59854C8.58086 1.34353 8.40014 1.03806 8.12337 0.91412C7.63027 0.660572 7.03575 1.42476 6.74072 2.33095C6.61457 2.81687 5.76653 3.75879 5.39721 3.9866C3.71684 5.02352 0.344233 6.11595 0.000262184 9.75358C-0.00114142 9.76867 0.000262182 9.81455 0.0573714 9.77323C0.459591 9.48197 5.02183 6.19605 2.09392 12.5476C0.300195 16.439 8.96062 18.917 9.40582 18.9271C9.46582 18.9284 9.46144 18.9011 9.46347 18.8832C10.1546 12.6724 16.9819 13.3262 18.5718 11.8387C20.1474 10.3649 20.1796 8.93816 18.7923 8.58131Z'
+        fill='#FA5320'
+      />
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[Hunter.io](https://hunter.io/) is a leading platform for finding and verifying professional email addresses, discovering companies, and enriching contact data. Hunter.io provides robust APIs for domain search, email finding, verification, and company discovery, making it an essential tool for sales, recruiting, and business development.
+
+With Hunter.io, you can:
+
+- **Find email addresses by domain:** Search for all publicly available email addresses associated with a specific company domain.
+- **Discover companies:** Use advanced filters and AI-powered search to find companies matching your criteria.
+- **Find a specific email address:** Locate the most likely email address for a person at a company using their name and domain.
+- **Verify email addresses:** Check the deliverability and validity of any email address.
+- **Enrich company data:** Retrieve detailed information about companies, including size, technologies used, and more.
+
+In Sim, the Hunter.io integration enables your agents to programmatically search for and verify email addresses, discover companies, and enrich contact data using Hunter.io’s API. This allows you to automate lead generation, contact enrichment, and email verification directly within your workflows. Your agents can leverage Hunter.io’s tools to streamline outreach, keep your CRM up-to-date, and power intelligent automation scenarios for sales, recruiting, and more.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Search for email addresses, verify their deliverability, discover companies, and enrich contact data using Hunter.io's powerful email finding capabilities.
+
+
+
+## Tools
+
+### `hunter_discover`
+
+Returns companies matching a set of criteria using Hunter.io AI-powered search.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `query` | string | No | Natural language search query for companies |
+| `domain` | string | No | Company domain names to filter by |
+| `headcount` | string | No | Company size filter \(e.g., "1-10", "11-50"\) |
+| `company_type` | string | No | Type of organization |
+| `technology` | string | No | Technology used by companies |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Array of companies matching the search criteria, each containing domain, name, headcount, technologies, and email_count |
+
+### `hunter_domain_search`
+
+Returns all the email addresses found using one given domain name, with sources.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | Yes | Domain name to search for email addresses |
+| `limit` | number | No | Maximum email addresses to return \(default: 10\) |
+| `offset` | number | No | Number of email addresses to skip |
+| `type` | string | No | Filter for personal or generic emails |
+| `seniority` | string | No | Filter by seniority level: junior, senior, or executive |
+| `department` | string | No | Filter by specific departments \(e.g., sales, marketing\) |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `domain` | string | The searched domain name |
+| `disposable` | boolean | Whether the domain accepts disposable email addresses |
+| `webmail` | boolean | Whether the domain is a webmail provider |
+| `accept_all` | boolean | Whether the domain accepts all email addresses |
+| `pattern` | string | The email pattern used by the organization |
+| `organization` | string | The organization name |
+| `description` | string | Description of the organization |
+| `industry` | string | Industry of the organization |
+| `twitter` | string | Twitter profile of the organization |
+| `facebook` | string | Facebook profile of the organization |
+| `linkedin` | string | LinkedIn profile of the organization |
+| `instagram` | string | Instagram profile of the organization |
+| `youtube` | string | YouTube channel of the organization |
+| `technologies` | array | Array of technologies used by the organization |
+| `country` | string | Country where the organization is located |
+| `state` | string | State where the organization is located |
+| `city` | string | City where the organization is located |
+| `postal_code` | string | Postal code of the organization |
+| `street` | string | Street address of the organization |
+| `emails` | array | Array of email addresses found for the domain, each containing value, type, confidence, sources, and person details |
+
+### `hunter_email_finder`
+
+Finds the most likely email address for a person given their name and company domain.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | Yes | Company domain name |
+| `first_name` | string | Yes | Person's first name |
+| `last_name` | string | Yes | Person's last name |
+| `company` | string | No | Company name |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `email` | string | The found email address |
+| `score` | number | Confidence score for the found email address |
+| `sources` | array | Array of sources where the email was found, each containing domain, uri, extracted_on, last_seen_on, and still_on_page |
+| `verification` | object | Verification information containing date and status |
+
+### `hunter_email_verifier`
+
+Verifies the deliverability of an email address and provides detailed verification status.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `email` | string | Yes | The email address to verify |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `result` | string | Deliverability result: deliverable, undeliverable, or risky |
+| `score` | number | Confidence score for the verification result |
+| `email` | string | The verified email address |
+| `regexp` | boolean | Whether the email follows a valid regex pattern |
+| `gibberish` | boolean | Whether the email appears to be gibberish |
+| `disposable` | boolean | Whether the email is from a disposable email provider |
+| `webmail` | boolean | Whether the email is from a webmail provider |
+| `mx_records` | boolean | Whether MX records exist for the domain |
+| `smtp_server` | boolean | Whether the SMTP server is reachable |
+| `smtp_check` | boolean | Whether the SMTP check was successful |
+| `accept_all` | boolean | Whether the domain accepts all email addresses |
+| `block` | boolean | Whether the email is blocked |
+| `status` | string | Verification status: valid, invalid, accept_all, webmail, disposable, or unknown |
+| `sources` | array | Array of sources where the email was found |
+
+### `hunter_companies_find`
+
+Enriches company data using domain name.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | Yes | Domain to find company data for |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `person` | object | Person information \(undefined for companies_find tool\) |
+| `company` | object | Company information including name, domain, industry, size, country, linkedin, and twitter |
+
+### `hunter_email_count`
+
+Returns the total number of email addresses found for a domain or company.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | No | Domain to count emails for \(required if company not provided\) |
+| `company` | string | No | Company name to count emails for \(required if domain not provided\) |
+| `type` | string | No | Filter for personal or generic emails only |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `total` | number | Total number of email addresses found |
+| `personal_emails` | number | Number of personal email addresses found |
+| `generic_emails` | number | Number of generic email addresses found |
+| `department` | object | Breakdown of email addresses by department \(executive, it, finance, management, sales, legal, support, hr, marketing, communication\) |
+| `seniority` | object | Breakdown of email addresses by seniority level \(junior, senior, executive\) |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `hunter`

apps/docs/content/docs/tools/image_generator.mdx

@@ -40,13 +40,13 @@ With DALL-E, you can:
 - **Visualize products**: Generate product mockups and design concepts
 - **Illustrate ideas**: Turn written concepts into visual illustrations
 
-In Sim Studio, the DALL-E integration enables your agents to generate images programmatically as part of their workflows. This allows for powerful automation scenarios such as content creation, visual design, and creative ideation. Your agents can formulate detailed prompts, generate corresponding images, and incorporate these visuals into their outputs or downstream processes. This integration bridges the gap between natural language processing and visual content creation, enabling your agents to communicate not just through text but also through compelling imagery. By connecting Sim Studio with DALL-E, you can create agents that produce visual content on demand, illustrate concepts, generate design assets, and enhance user experiences with rich visual elements - all without requiring human intervention in the creative process.
+In Sim, the DALL-E integration enables your agents to generate images programmatically as part of their workflows. This allows for powerful automation scenarios such as content creation, visual design, and creative ideation. Your agents can formulate detailed prompts, generate corresponding images, and incorporate these visuals into their outputs or downstream processes. This integration bridges the gap between natural language processing and visual content creation, enabling your agents to communicate not just through text but also through compelling imagery. By connecting Sim with DALL-E, you can create agents that produce visual content on demand, illustrate concepts, generate design assets, and enhance user experiences with rich visual elements - all without requiring human intervention in the creative process.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Create high-quality images using OpenAI
+Create high-quality images using OpenAI's image generation models. Configure resolution, quality, style, and other parameters to get exactly the image you need.
 
 
 
@@ -60,8 +60,8 @@ Generate images using OpenAI
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `prompt` | string | Yes | A text description of the desired image |
 | `model` | string | Yes | The model to use \(gpt-image-1 or dall-e-3\) |
+| `prompt` | string | Yes | A text description of the desired image |
 | `size` | string | Yes | The size of the generated images \(1024x1024, 1024x1792, or 1792x1024\) |
 | `quality` | string | No | The quality of the image \(standard or hd\) |
 | `style` | string | No | The style of the image \(vivid or natural\) |
@@ -71,34 +71,13 @@ Generate images using OpenAI
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `image` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Generated image data |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `prompt` | string | Yes |  |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `image` | string | image of the response |
-| ↳ `metadata` | json | metadata of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/index.mdx

@@ -7,7 +7,7 @@ import { Card, Cards } from "fumadocs-ui/components/card";
 import { Step, Steps } from "fumadocs-ui/components/steps";
 import { Tab, Tabs } from "fumadocs-ui/components/tabs";
 
-Tools are powerful components in Sim Studio that allow your workflows to interact with external services, process data, and perform specialized tasks. They extend the capabilities of your agents and workflows by providing access to various APIs and services.
+Tools are powerful components in Sim that allow your workflows to interact with external services, process data, and perform specialized tasks. They extend the capabilities of your agents and workflows by providing access to various APIs and services.
 
 ## What is a Tool?
 
@@ -15,7 +15,7 @@ A tool is a specialized component that provides a specific functionality or inte
 
 ## Using Tools in Workflows
 
-There are two primary ways to use tools in your Sim Studio workflows:
+There are two primary ways to use tools in your Sim workflows:
 
 <Steps>
   <Step>
@@ -43,7 +43,7 @@ Each tool requires specific configuration to function properly. Common configura
 
 ## Available Tools
 
-Sim Studio provides a diverse collection of tools for various purposes, including:
+Sim provides a diverse collection of tools for various purposes, including:
 
 - **AI and Language Processing**: OpenAI, ElevenLabs, Translation services
 - **Search and Research**: Google Search, Tavily, Exa, Perplexity
@@ -64,3 +64,14 @@ Tools typically return structured data that can be processed by subsequent block
 - Status information
 
 Refer to each tool's specific documentation to understand its exact output format.
+
+## YAML Configuration
+
+For detailed YAML workflow configuration and syntax, see the [YAML Workflow Reference](/yaml) documentation. This includes comprehensive guides for:
+
+- **Block Reference Syntax**: How to connect and reference data between blocks
+- **Tool Configuration**: Using tools in both standalone blocks and agent configurations  
+- **Environment Variables**: Secure handling of API keys and credentials
+- **Complete Examples**: Real-world workflow patterns and configurations
+
+For specific tool parameters and configuration options, refer to each tool's individual documentation page.

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

@@ -45,11 +45,11 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Jina AI](https://jina.ai/) is a powerful content extraction tool that seamlessly integrates with Sim Studio to transform web content into clean, readable text. This integration allows developers to easily incorporate web content processing capabilities into their agentic workflows.
+[Jina AI](https://jina.ai/) is a powerful content extraction tool that seamlessly integrates with Sim to transform web content into clean, readable text. This integration allows developers to easily incorporate web content processing capabilities into their agentic workflows.
 
 Jina AI Reader specializes in extracting the most relevant content from web pages, removing clutter, advertisements, and formatting issues to produce clean, structured text that's optimized for language models and other text processing tasks.
 
-With the Jina AI integration in Sim Studio, you can:
+With the Jina AI integration in Sim, you can:
 
 - **Extract clean content** from any web page by simply providing a URL
 - **Process complex web layouts** into structured, readable text
@@ -63,7 +63,7 @@ This integration is particularly valuable for building agents that need to gathe
 
 ## Usage Instructions
 
-Transform web content into clean, readable text using Jina AI
+Transform web content into clean, readable text using Jina AI's advanced extraction capabilities. Extract meaningful content from websites while preserving important information and optionally gathering links.
 
 
 
@@ -78,33 +78,19 @@ Extract and process web content into clean, LLM-friendly text using Jina AI Read
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `url` | string | Yes | The URL to read and convert to markdown |
+| `useReaderLMv2` | boolean | No | Whether to use ReaderLM-v2 for better quality |
+| `gatherLinks` | boolean | No | Whether to gather all links at the end |
+| `jsonResponse` | boolean | No | Whether to return response in JSON format |
+| `apiKey` | string | Yes | Your Jina AI API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | The extracted content from the URL, processed into clean, LLM-friendly text |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `url` | string | Yes | URL - Enter URL to extract content from |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/jira.mdx

@@ -37,7 +37,7 @@ Key features of Jira include:
 - Workflow Automation: Powerful automation rules to streamline repetitive tasks and processes
 - Advanced Search: JQL (Jira Query Language) for complex issue filtering and reporting
 
-In Sim Studio, the Jira integration allows your agents to seamlessly interact with your project management workflow. This creates opportunities for automated issue creation, updates, and tracking as part of your AI workflows. The integration enables agents to create, retrieve, and update Jira issues programmatically, facilitating automated project management tasks and ensuring that important information is properly tracked and documented. By connecting Sim Studio with Jira, you can build intelligent agents that maintain project visibility while automating routine project management tasks, enhancing team productivity and ensuring consistent project tracking.
+In Sim, the Jira integration allows your agents to seamlessly interact with your project management workflow. This creates opportunities for automated issue creation, updates, and tracking as part of your AI workflows. The integration enables agents to create, retrieve, and update Jira issues programmatically, facilitating automated project management tasks and ensuring that important information is properly tracked and documented. By connecting Sim with Jira, you can build intelligent agents that maintain project visibility while automating routine project management tasks, enhancing team productivity and ensuring consistent project tracking.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -57,7 +57,6 @@ Retrieve detailed information about a specific Jira issue
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
 | `projectId` | string | No | Jira project ID to retrieve issues from. If not provided, all issues will be retrieved. |
 | `issueKey` | string | Yes | Jira issue key to retrieve \(e.g., PROJ-123\) |
@@ -65,14 +64,10 @@ Retrieve detailed information about a specific Jira issue
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `issueKey` | string |
-| `summary` | string |
-| `description` | string |
-| `created` | string |
-| `updated` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Jira issue details with issue key, summary, description, created and updated timestamps |
 
 ### `jira_update`
 
@@ -82,7 +77,6 @@ Update a Jira issue
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
 | `projectId` | string | No | Jira project ID to update issues in. If not provided, all issues will be retrieved. |
 | `issueKey` | string | Yes | Jira issue key to update |
@@ -95,12 +89,10 @@ Update a Jira issue
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `issueKey` | string |
-| `summary` | string |
-| `success` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Updated Jira issue details with timestamp, issue key, summary, and success status |
 
 ### `jira_write`
 
@@ -110,7 +102,6 @@ Write a Jira issue
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
 | `projectId` | string | Yes | Project ID for the issue |
 | `summary` | string | Yes | Summary for the issue |
@@ -118,17 +109,14 @@ Write a Jira issue
 | `priority` | string | No | Priority for the issue |
 | `assignee` | string | No | Assignee for the issue |
 | `cloudId` | string | No | Jira Cloud ID for the instance. If not provided, it will be fetched using the domain. |
-| `issueType` | string | Yes | Type of issue to create \(e.g., Task, Story, Bug, Sub-task\) |
+| `issueType` | string | Yes | Type of issue to create \(e.g., Task, Story\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `issueKey` | string |
-| `summary` | string |
-| `success` | string |
-| `url` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Created Jira issue details with timestamp, issue key, summary, success status, and URL |
 
 ### `jira_bulk_read`
 
@@ -138,44 +126,19 @@ Retrieve multiple Jira issues in bulk
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
 | `projectId` | string | Yes | Jira project ID |
 | `cloudId` | string | No | Jira cloud ID |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `issues` | array |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | array | Array of Jira issues with summary, description, created and updated timestamps |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `ts` | string | ts of the response |
-| ↳ `issueKey` | string | issueKey of the response |
-| ↳ `summary` | string | summary of the response |
-| ↳ `description` | string | description of the response |
-| ↳ `created` | string | created of the response |
-| ↳ `updated` | string | updated of the response |
-| ↳ `success` | boolean | success of the response |
-| ↳ `url` | string | url of the response |
-
-
 ## Notes
 
 - Category: `tools`

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

@@ -31,7 +31,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-Sim Studio's Knowledge Base is a powerful native feature that enables you to create, manage, and query custom knowledge bases directly within the platform. Using advanced AI embeddings and vector search technology, the Knowledge Base block allows you to build intelligent search capabilities into your workflows, making it easy to find and utilize relevant information across your organization.
+Sim's Knowledge Base is a powerful native feature that enables you to create, manage, and query custom knowledge bases directly within the platform. Using advanced AI embeddings and vector search technology, the Knowledge Base block allows you to build intelligent search capabilities into your workflows, making it easy to find and utilize relevant information across your organization.
 
 The Knowledge Base system provides a comprehensive solution for managing organizational knowledge through its flexible and scalable architecture. With its built-in vector search capabilities, teams can perform semantic searches that understand meaning and context, going beyond traditional keyword matching.
 
@@ -43,7 +43,7 @@ Key features of the Knowledge Base include:
 - Flexible Content Types: Support for various document formats and content types
 - Real-time Updates: Immediate indexing of new content for instant searchability
 
-In Sim Studio, the Knowledge Base block enables your agents to perform intelligent semantic searches across your custom knowledge bases. This creates opportunities for automated information retrieval, content recommendations, and knowledge discovery as part of your AI workflows. The integration allows agents to search and retrieve relevant information programmatically, facilitating automated knowledge management tasks and ensuring that important information is easily accessible. By leveraging the Knowledge Base block, you can build intelligent agents that enhance information discovery while automating routine knowledge management tasks, improving team efficiency and ensuring consistent access to organizational knowledge.
+In Sim, the Knowledge Base block enables your agents to perform intelligent semantic searches across your custom knowledge bases. This creates opportunities for automated information retrieval, content recommendations, and knowledge discovery as part of your AI workflows. The integration allows agents to search and retrieve relevant information programmatically, facilitating automated knowledge management tasks and ensuring that important information is easily accessible. By leveraging the Knowledge Base block, you can build intelligent agents that enhance information discovery while automating routine knowledge management tasks, improving team efficiency and ensuring consistent access to organizational knowledge.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -57,23 +57,22 @@ Perform semantic vector search across knowledge bases, upload individual chunks
 
 ### `knowledge_search`
 
-Search for similar content in one or more knowledge bases using vector similarity
+Search for similar content in a knowledge base using vector similarity
 
 #### Input
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `knowledgeBaseIds` | string | Yes | ID of the knowledge base to search in, or comma-separated IDs for multiple knowledge bases |
-| `query` | string | Yes | Search query text |
+| `knowledgeBaseId` | string | Yes | ID of the knowledge base to search in |
+| `query` | string | No | Search query text \(optional when using tag filters\) |
 | `topK` | number | No | Number of most similar results to return \(1-100\) |
+| `tagFilters` | any | No | Array of tag filters with tagName and tagValue properties |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `results` | string |
-| `query` | string |
-| `totalResults` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Array of search results from the knowledge base |
 
 ### `knowledge_upload_chunk`
 
@@ -89,16 +88,9 @@ Upload a new chunk to a document in a knowledge base
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `chunkIndex` | string |
-| `content` | string |
-| `contentLength` | string |
-| `tokenCount` | string |
-| `enabled` | string |
-| `createdAt` | string |
-| `updatedAt` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | object | Information about the uploaded chunk |
 
 ### `knowledge_create_document`
 
@@ -111,36 +103,23 @@ Create a new document in a knowledge base
 | `knowledgeBaseId` | string | Yes | ID of the knowledge base containing the document |
 | `name` | string | Yes | Name of the document |
 | `content` | string | Yes | Content of the document |
+| `tag1` | string | No | Tag 1 value for the document |
+| `tag2` | string | No | Tag 2 value for the document |
+| `tag3` | string | No | Tag 3 value for the document |
+| `tag4` | string | No | Tag 4 value for the document |
+| `tag5` | string | No | Tag 5 value for the document |
+| `tag6` | string | No | Tag 6 value for the document |
+| `tag7` | string | No | Tag 7 value for the document |
+| `documentTagsData` | array | No | Structured tag data with names, types, and values |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `name` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | object | Information about the created document |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `results` | json | results of the response |
-| ↳ `query` | string | query of the response |
-| ↳ `totalResults` | number | totalResults of the response |
-
-
 ## Notes
 
 - Category: `blocks`

apps/docs/content/docs/tools/linear.mdx

@@ -36,7 +36,7 @@ Key features of Linear include:
 - Workflow Automation: Powerful automation rules to streamline repetitive tasks and processes
 - Advanced Search: Complex filtering and reporting capabilities for efficient issue management
 
-In Sim Studio, the Linear integration allows your agents to seamlessly interact with your project management workflow. This creates opportunities for automated issue creation, updates, and tracking as part of your AI workflows. The integration enables agents to read existing issues and create new ones programmatically, facilitating automated project management tasks and ensuring that important information is properly tracked and documented. By connecting Sim Studio with Linear, you can build intelligent agents that maintain project visibility while automating routine project management tasks, enhancing team productivity and ensuring consistent project tracking.
+In Sim, the Linear integration allows your agents to seamlessly interact with your project management workflow. This creates opportunities for automated issue creation, updates, and tracking as part of your AI workflows. The integration enables agents to read existing issues and create new ones programmatically, facilitating automated project management tasks and ensuring that important information is properly tracked and documented. By connecting Sim with Linear, you can build intelligent agents that maintain project visibility while automating routine project management tasks, enhancing team productivity and ensuring consistent project tracking.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -61,9 +61,9 @@ Fetch and filter issues from Linear
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `issues` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `issues` | array | Array of issues from the specified Linear team and project, each containing id, title, description, state, teamId, and projectId |
 
 ### `linear_create_issue`
 
@@ -80,36 +80,12 @@ Create a new issue in Linear
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `issue` | string |
-| `title` | string |
-| `description` | string |
-| `state` | string |
-| `teamId` | string |
-| `projectId` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `issue` | object | The created issue containing id, title, description, state, teamId, and projectId |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `issues` | json | issues of the response |
-| ↳ `issue` | json | issue of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/mem0.mdx

@@ -38,7 +38,7 @@ With Mem0, you can:
 - **Implement long-term memory**: Create agents that learn and adapt over time
 - **Scale memory management**: Handle memory needs for multiple users and complex workflows
 
-In Sim Studio, the Mem0 integration enables your agents to maintain persistent memory across workflow executions. This allows for more natural, context-aware interactions where agents can recall past conversations, remember user preferences, and build upon previous interactions. By connecting Sim Studio with Mem0, you can create agents that feel more human-like in their ability to remember and learn from past experiences. The integration supports adding new memories, searching existing memories semantically, and retrieving specific memory records. This memory management capability is essential for building sophisticated agents that can maintain context over time, personalize interactions based on user history, and continuously improve their performance through accumulated knowledge.
+In Sim, the Mem0 integration enables your agents to maintain persistent memory across workflow executions. This allows for more natural, context-aware interactions where agents can recall past conversations, remember user preferences, and build upon previous interactions. By connecting Sim with Mem0, you can create agents that feel more human-like in their ability to remember and learn from past experiences. The integration supports adding new memories, searching existing memories semantically, and retrieving specific memory records. This memory management capability is essential for building sophisticated agents that can maintain context over time, personalize interactions based on user history, and continuously improve their performance through accumulated knowledge.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -58,15 +58,16 @@ Add memories to Mem0 for persistent storage and retrieval
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Your Mem0 API key |
 | `userId` | string | Yes | User ID associated with the memory |
 | `messages` | json | Yes | Array of message objects with role and content |
+| `apiKey` | string | Yes | Your Mem0 API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `ids` | array | Array of memory IDs that were created |
+| `memories` | array | Array of memory objects that were created |
 
 ### `mem0_search_memories`
 
@@ -76,17 +77,17 @@ Search for memories in Mem0 using semantic search
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Your Mem0 API key |
 | `userId` | string | Yes | User ID to search memories for |
 | `query` | string | Yes | Search query to find relevant memories |
 | `limit` | number | No | Maximum number of results to return |
+| `apiKey` | string | Yes | Your Mem0 API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `searchResults` | string |
-| `ids` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `searchResults` | array | Array of search results with memory data, each containing id, data, and score |
+| `ids` | array | Array of memory IDs found in the search results |
 
 ### `mem0_get_memories`
 
@@ -96,42 +97,22 @@ Retrieve memories from Mem0 by ID or filter criteria
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Your Mem0 API key |
 | `userId` | string | Yes | User ID to retrieve memories for |
 | `memoryId` | string | No | Specific memory ID to retrieve |
 | `startDate` | string | No | Start date for filtering by created_at \(format: YYYY-MM-DD\) |
 | `endDate` | string | No | End date for filtering by created_at \(format: YYYY-MM-DD\) |
 | `limit` | number | No | Maximum number of results to return |
+| `apiKey` | string | Yes | Your Mem0 API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
-| `ids` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `memories` | array | Array of retrieved memory objects |
+| `ids` | array | Array of memory IDs that were retrieved |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `ids` | any | ids of the response |
-| ↳ `memories` | any | memories of the response |
-| ↳ `searchResults` | any | searchResults of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/memory.mdx

@@ -55,9 +55,11 @@ Add a new memory to the database or append to existing memory with the same ID.
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the memory was added successfully |
+| `memories` | array | Array of memory objects including the new or updated memory |
+| `error` | string | Error message if operation failed |
 
 ### `memory_get`
 
@@ -71,10 +73,12 @@ Retrieve a specific memory by its ID
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the memory was retrieved successfully |
+| `memories` | array | Array of memory data for the requested ID |
+| `message` | string | Success or error message |
+| `error` | string | Error message if operation failed |
 
 ### `memory_get_all`
 
@@ -87,10 +91,12 @@ Retrieve all memories from the database
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `memories` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether all memories were retrieved successfully |
+| `memories` | array | Array of all memory objects with keys, types, and data |
+| `message` | string | Success or error message |
+| `error` | string | Error message if operation failed |
 
 ### `memory_delete`
 
@@ -104,31 +110,14 @@ Delete a specific memory by its ID
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the memory was deleted successfully |
+| `message` | string | Success or error message |
+| `error` | string | Error message if operation failed |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `memories` | any | memories of the response |
-| ↳ `id` | string | id of the response |
-
-
 ## Notes
 
 - Category: `blocks`

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

@@ -2,7 +2,7 @@
   "items": [
     "index",
     "airtable",
-    "autoblocks",
+    "arxiv",
     "browser_use",
     "clay",
     "confluence",
@@ -11,6 +11,7 @@
     "exa",
     "file",
     "firecrawl",
+    "generic_webhook",
     "github",
     "gmail",
     "google_calendar",
@@ -18,8 +19,8 @@
     "google_drive",
     "google_search",
     "google_sheets",
-    "guesty",
     "huggingface",
+    "hunter",
     "image_generator",
     "jina",
     "jira",
@@ -29,16 +30,24 @@
     "mem0",
     "memory",
     "microsoft_excel",
+    "microsoft_planner",
     "microsoft_teams",
     "mistral_parse",
+    "mysql",
     "notion",
+    "onedrive",
     "openai",
     "outlook",
+    "parallel_ai",
     "perplexity",
     "pinecone",
+    "postgresql",
+    "qdrant",
     "reddit",
     "s3",
+    "schedule",
     "serper",
+    "sharepoint",
     "slack",
     "stagehand",
     "stagehand_agent",
@@ -50,7 +59,10 @@
     "twilio_sms",
     "typeform",
     "vision",
+    "wealthbox",
+    "webhook",
     "whatsapp",
+    "wikipedia",
     "x",
     "youtube"
   ]

apps/docs/content/docs/tools/microsoft_excel.mdx

@@ -78,7 +78,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Microsoft Teams](https://www.microsoft.com/en-us/microsoft-365/excel) is a powerful spreadsheet application that enables data management, analysis, and visualization. Through the Microsoft Excel integration in Sim Studio, you can programmatically read, write, and manipulate spreadsheet data to support your workflow automation needs.
+[Microsoft Teams](https://www.microsoft.com/en-us/microsoft-365/excel) is a powerful spreadsheet application that enables data management, analysis, and visualization. Through the Microsoft Excel integration in Sim, you can programmatically read, write, and manipulate spreadsheet data to support your workflow automation needs.
 
 With Microsoft Excel integration, you can:
 
@@ -88,7 +88,7 @@ With Microsoft Excel integration, you can:
 - **Handle Multiple Sheets**: Work with multiple worksheets in a workbook
 - **Process Data**: Import, export, and transform spreadsheet data
 
-In Sim Studio, the Microsoft Excel integration provides seamless access to spreadsheet functionality through OAuth authentication. You can read data from specific ranges, write new information, update existing cells, and handle various data formats. The integration supports both reading and writing operations with flexible input and output options. This enables you to build workflows that can effectively manage spreadsheet data, whether you're extracting information for analysis, updating records automatically, or maintaining data consistency across your applications.
+In Sim, the Microsoft Excel integration provides seamless access to spreadsheet functionality through OAuth authentication. You can read data from specific ranges, write new information, update existing cells, and handle various data formats. The integration supports both reading and writing operations with flexible input and output options. This enables you to build workflows that can effectively manage spreadsheet data, whether you're extracting information for analysis, updating records automatically, or maintaining data consistency across your applications.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -108,15 +108,14 @@ Read data from a Microsoft Excel spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Excel API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to read from |
-| `range` | string | No | The range of cells to read from |
+| `range` | string | No | The range of cells to read from. Accepts "SheetName!A1:B2" for explicit ranges or just "SheetName" to read the used range of that sheet. If omitted, reads the used range of the first sheet. |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | object | Range data from the spreadsheet |
 
 ### `microsoft_excel_write`
 
@@ -126,7 +125,6 @@ Write data to a Microsoft Excel spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Excel API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to write to |
 | `range` | string | No | The range of cells to write to |
 | `values` | array | Yes | The data to write to the spreadsheet |
@@ -135,15 +133,13 @@ Write data to a Microsoft Excel spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedRange` | string |
-| `updatedRows` | string |
-| `updatedColumns` | string |
-| `updatedCells` | string |
-| `metadata` | string |
-| `spreadsheetId` | string |
-| `spreadsheetUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedRange` | string | The range that was updated |
+| `updatedRows` | number | Number of rows that were updated |
+| `updatedColumns` | number | Number of columns that were updated |
+| `updatedCells` | number | Number of cells that were updated |
+| `metadata` | object | Spreadsheet metadata |
 
 ### `microsoft_excel_table_add`
 
@@ -153,44 +149,20 @@ Add new rows to a Microsoft Excel table
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Excel API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet containing the table |
 | `tableName` | string | Yes | The name of the table to add rows to |
 | `values` | array | Yes | The data to add to the table \(array of arrays or array of objects\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `index` | number | Index of the first row that was added |
+| `values` | array | Array of rows that were added to the table |
+| `metadata` | object | Spreadsheet metadata |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `data` | json | data of the response |
-| ↳ `metadata` | json | metadata of the response |
-| ↳ `updatedRange` | string | updatedRange of the response |
-| ↳ `updatedRows` | number | updatedRows of the response |
-| ↳ `updatedColumns` | number | updatedColumns of the response |
-| ↳ `updatedCells` | number | updatedCells of the response |
-| ↳ `index` | number | index of the response |
-| ↳ `values` | json | values of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/microsoft_planner.mdx

@@ -0,0 +1,178 @@
+---
+title: Microsoft Planner
+description: Read and create tasks in Microsoft Planner
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="microsoft_planner"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"  fill='currentColor' viewBox='-1 -1 27 27' xmlns='http://www.w3.org/2000/svg'>
+      <defs>
+        <linearGradient
+          id='paint0_linear_3984_11038'
+          x1='6.38724'
+          y1='3.74167'
+          x2='2.15779'
+          y2='12.777'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop stopColor='#8752E0' />
+          <stop offset='1' stopColor='#541278' />
+        </linearGradient>
+        <linearGradient
+          id='paint1_linear_3984_11038'
+          x1='8.38032'
+          y1='11.0696'
+          x2='4.94062'
+          y2='7.69244'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop offset='0.12172' stopColor='#3D0D59' />
+          <stop offset='1' stopColor='#7034B0' stopOpacity='0' />
+        </linearGradient>
+        <linearGradient
+          id='paint2_linear_3984_11038'
+          x1='18.3701'
+          y1='-3.33385e-05'
+          x2='9.85717'
+          y2='20.4192'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop stopColor='#DB45E0' />
+          <stop offset='1' stopColor='#6C0F71' />
+        </linearGradient>
+        <linearGradient
+          id='paint3_linear_3984_11038'
+          x1='18.3701'
+          y1='-3.33385e-05'
+          x2='9.85717'
+          y2='20.4192'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop stopColor='#DB45E0' />
+          <stop offset='0.677403' stopColor='#A829AE' />
+          <stop offset='1' stopColor='#8F28B3' />
+        </linearGradient>
+        <linearGradient
+          id='paint4_linear_3984_11038'
+          x1='18.0002'
+          y1='7.49958'
+          x2='14.0004'
+          y2='23.9988'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop stopColor='#3DCBFF' />
+          <stop offset='1' stopColor='#00479E' />
+        </linearGradient>
+        <linearGradient
+          id='paint5_linear_3984_11038'
+          x1='18.2164'
+          y1='7.92626'
+          x2='10.5237'
+          y2='22.9363'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop stopColor='#3DCBFF' />
+          <stop offset='1' stopColor='#4A40D4' />
+        </linearGradient>
+      </defs>
+      <path
+        d='M8.25809 15.7412C7.22488 16.7744 5.54971 16.7744 4.5165 15.7412L0.774909 11.9996C-0.258303 10.9664 -0.258303 9.29129 0.774908 8.25809L4.5165 4.51655C5.54971 3.48335 7.22488 3.48335 8.25809 4.51655L11.9997 8.2581C13.0329 9.29129 13.0329 10.9664 11.9997 11.9996L8.25809 15.7412Z'
+        fill='url(#paint0_linear_3984_11038)'
+      />
+      <path
+        d='M8.25809 15.7412C7.22488 16.7744 5.54971 16.7744 4.5165 15.7412L0.774909 11.9996C-0.258303 10.9664 -0.258303 9.29129 0.774908 8.25809L4.5165 4.51655C5.54971 3.48335 7.22488 3.48335 8.25809 4.51655L11.9997 8.2581C13.0329 9.29129 13.0329 10.9664 11.9997 11.9996L8.25809 15.7412Z'
+        fill='url(#paint1_linear_3984_11038)'
+      />
+      <path
+        d='M0.774857 11.9999C1.80809 13.0331 3.48331 13.0331 4.51655 11.9999L15.7417 0.774926C16.7749 -0.258304 18.4501 -0.258309 19.4834 0.774914L23.225 4.51655C24.2583 5.54977 24.2583 7.22496 23.225 8.25819L11.9999 19.4832C10.9667 20.5164 9.29146 20.5164 8.25822 19.4832L0.774857 11.9999Z'
+        fill='url(#paint2_linear_3984_11038)'
+      />
+      <path
+        d='M0.774857 11.9999C1.80809 13.0331 3.48331 13.0331 4.51655 11.9999L15.7417 0.774926C16.7749 -0.258304 18.4501 -0.258309 19.4834 0.774914L23.225 4.51655C24.2583 5.54977 24.2583 7.22496 23.225 8.25819L11.9999 19.4832C10.9667 20.5164 9.29146 20.5164 8.25822 19.4832L0.774857 11.9999Z'
+        fill='url(#paint3_linear_3984_11038)'
+      />
+      <path
+        d='M4.51642 15.7413C5.54966 16.7746 7.22487 16.7746 8.25812 15.7413L15.7415 8.25803C16.7748 7.2248 18.45 7.2248 19.4832 8.25803L23.2249 11.9997C24.2582 13.0329 24.2582 14.7081 23.2249 15.7413L15.7415 23.2246C14.7083 24.2579 13.033 24.2579 11.9998 23.2246L4.51642 15.7413Z'
+        fill='url(#paint4_linear_3984_11038)'
+      />
+      <path
+        d='M4.51642 15.7413C5.54966 16.7746 7.22487 16.7746 8.25812 15.7413L15.7415 8.25803C16.7748 7.2248 18.45 7.2248 19.4832 8.25803L23.2249 11.9997C24.2582 13.0329 24.2582 14.7081 23.2249 15.7413L15.7415 23.2246C14.7083 24.2579 13.033 24.2579 11.9998 23.2246L4.51642 15.7413Z'
+        fill='url(#paint5_linear_3984_11038)'
+      />
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[Microsoft Planner](https://www.microsoft.com/en-us/microsoft-365/planner) is a task management tool that helps teams organize work visually using boards, tasks, and buckets. Integrated with Microsoft 365, it offers a simple, intuitive way to manage team projects, assign responsibilities, and track progress.
+
+With Microsoft Planner, you can:
+
+- **Create and manage tasks**: Add new tasks with due dates, priorities, and assigned users
+- **Organize with buckets**: Group tasks by phase, status, or category to reflect your team’s workflow
+- **Visualize project status**: Use boards, charts, and filters to monitor workload and track progress
+- **Stay integrated with Microsoft 365**: Seamlessly connect tasks with Teams, Outlook, and other Microsoft tools
+
+In Sim, the Microsoft Planner integration allows your agents to programmatically create, read, and manage tasks as part of their workflows. Agents can generate new tasks based on incoming requests, retrieve task details to drive decisions, and track status across projects — all without human intervention. Whether you're building workflows for client onboarding, internal project tracking, or follow-up task generation, integrating Microsoft Planner with Sim gives your agents a structured way to coordinate work, automate task creation, and keep teams aligned.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Integrate Microsoft Planner functionality to manage tasks. Read all user tasks, tasks from specific plans, individual tasks, or create new tasks with various properties like title, description, due date, and assignees using OAuth authentication.
+
+
+
+## Tools
+
+### `microsoft_planner_read_task`
+
+Read tasks from Microsoft Planner - get all user tasks or all tasks from a specific plan
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `planId` | string | No | The ID of the plan to get tasks from \(if not provided, gets all user tasks\) |
+| `taskId` | string | No | The ID of the task to get |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether tasks were retrieved successfully |
+| `tasks` | array | Array of task objects with filtered properties |
+| `metadata` | object | Metadata including planId, userId, and planUrl |
+
+### `microsoft_planner_create_task`
+
+Create a new task in Microsoft Planner
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `planId` | string | Yes | The ID of the plan where the task will be created |
+| `title` | string | Yes | The title of the task |
+| `description` | string | No | The description of the task |
+| `dueDateTime` | string | No | The due date and time for the task \(ISO 8601 format\) |
+| `assigneeUserId` | string | No | The user ID to assign the task to |
+| `bucketId` | string | No | The bucket ID to place the task in |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the task was created successfully |
+| `task` | object | The created task object with all properties |
+| `metadata` | object | Metadata including planId, taskId, and taskUrl |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `microsoft_planner`

apps/docs/content/docs/tools/microsoft_teams.mdx

@@ -92,7 +92,7 @@ With Microsoft Teams, you can:
 - **Access across devices**: Use Teams on desktop, web, and mobile with cloud-synced conversations  
 - **Secure communication**: Leverage enterprise-grade security and compliance features
 
-In Sim Studio, the Microsoft Teams integration enables your agents to interact directly with chat messages programmatically. This allows for powerful automation scenarios such as sending updates, posting alerts, coordinating tasks, and responding to conversations in real time. Your agents can write new messages to chats or channels, update content based on workflow data, and engage with users where collaboration happens. By integrating Sim Studio with Microsoft Teams, you bridge the gap between intelligent workflows and team communication — empowering your agents to streamline collaboration, automate communication tasks, and keep your teams aligned.
+In Sim, the Microsoft Teams integration enables your agents to interact directly with chat messages programmatically. This allows for powerful automation scenarios such as sending updates, posting alerts, coordinating tasks, and responding to conversations in real time. Your agents can write new messages to chats or channels, update content based on workflow data, and engage with users where collaboration happens. By integrating Sim with Microsoft Teams, you bridge the gap between intelligent workflows and team communication — empowering your agents to streamline collaboration, automate communication tasks, and keep your teams aligned.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -112,19 +112,19 @@ Read content from a Microsoft Teams chat
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
 | `chatId` | string | Yes | The ID of the chat to read from |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `messageCount` | string |
-| `messages` | string |
-| `totalAttachments` | string |
-| `attachmentTypes` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Teams chat read operation success status |
+| `messageCount` | number | Number of messages retrieved from chat |
+| `chatId` | string | ID of the chat that was read from |
+| `messages` | array | Array of chat message objects |
+| `attachmentCount` | number | Total number of attachments found |
+| `attachmentTypes` | array | Types of attachments found |
+| `content` | string | Formatted content of chat messages |
 
 ### `microsoft_teams_write_chat`
 
@@ -134,16 +134,19 @@ Write or update content in a Microsoft Teams chat
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
 | `chatId` | string | Yes | The ID of the chat to write to |
 | `content` | string | Yes | The content to write to the message |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedContent` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Teams chat message send success status |
+| `messageId` | string | Unique identifier for the sent message |
+| `chatId` | string | ID of the chat where message was sent |
+| `createdTime` | string | Timestamp when message was created |
+| `url` | string | Web URL to the message |
+| `updatedContent` | boolean | Whether content was successfully updated |
 
 ### `microsoft_teams_read_channel`
 
@@ -153,21 +156,21 @@ Read content from a Microsoft Teams channel
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
 | `teamId` | string | Yes | The ID of the team to read from |
 | `channelId` | string | Yes | The ID of the channel to read from |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `channelId` | string |
-| `messageCount` | string |
-| `messages` | string |
-| `totalAttachments` | string |
-| `attachmentTypes` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Teams channel read operation success status |
+| `messageCount` | number | Number of messages retrieved from channel |
+| `teamId` | string | ID of the team that was read from |
+| `channelId` | string | ID of the channel that was read from |
+| `messages` | array | Array of channel message objects |
+| `attachmentCount` | number | Total number of attachments found |
+| `attachmentTypes` | array | Types of attachments found |
+| `content` | string | Formatted content of channel messages |
 
 ### `microsoft_teams_write_channel`
 
@@ -177,40 +180,24 @@ Write or send a message to a Microsoft Teams channel
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
 | `teamId` | string | Yes | The ID of the team to write to |
 | `channelId` | string | Yes | The ID of the channel to write to |
 | `content` | string | Yes | The content to write to the channel |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedContent` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Teams channel message send success status |
+| `messageId` | string | Unique identifier for the sent message |
+| `teamId` | string | ID of the team where message was sent |
+| `channelId` | string | ID of the channel where message was sent |
+| `createdTime` | string | Timestamp when message was created |
+| `url` | string | Web URL to the message |
+| `updatedContent` | boolean | Whether content was successfully updated |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `metadata` | json | metadata of the response |
-| ↳ `updatedContent` | boolean | updatedContent of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/mistral_parse.mdx

@@ -79,7 +79,7 @@ The Mistral Parse tool is particularly useful for scenarios where your agents ne
 
 ## Usage Instructions
 
-Extract text and structure from PDF documents using Mistral's OCR API. Configure processing options and get the content in your preferred format. For URLs, they must be publicly accessible and point to a valid PDF file. Note: Google Drive, Dropbox, and other cloud storage links are not supported; use a direct download URL from a web server instead.
+Extract text and structure from PDF documents using Mistral's OCR API. Either enter a URL to a PDF document or upload a PDF file directly. Configure processing options and get the content in your preferred format. For URLs, they must be publicly accessible and point to a valid PDF file. Note: Google Drive, Dropbox, and other cloud storage links are not supported; use a direct download URL from a web server instead.
 
 
 
@@ -96,37 +96,22 @@ Parse PDF documents using Mistral OCR API
 | `filePath` | string | Yes | URL to a PDF document to be processed |
 | `fileUpload` | object | No | File upload data from file-upload component |
 | `resultType` | string | No | Type of parsed result \(markdown, text, or json\). Defaults to markdown. |
-| `apiKey` | string | Yes | Mistral API key \(MISTRAL_API_KEY\) |
 | `includeImageBase64` | boolean | No | Include base64-encoded images in the response |
 | `pages` | array | No | Specific pages to process \(array of page numbers, starting from 0\) |
 | `imageLimit` | number | No | Maximum number of images to extract from the PDF |
 | `imageMinSize` | number | No | Minimum height and width of images to extract from the PDF |
+| `apiKey` | string | Yes | Mistral API key \(MISTRAL_API_KEY\) |
 
 #### Output
 
-This tool does not produce any outputs.
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the PDF was parsed successfully |
+| `content` | string | Extracted content in the requested format \(markdown, text, or JSON\) |
+| `metadata` | object | Processing metadata including jobId, fileType, pageCount, and usage info |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `inputMethod` | string | No |  |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `metadata` | json | metadata of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/mysql.mdx

@@ -0,0 +1,180 @@
+---
+title: MySQL
+description: Connect to MySQL database
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="mysql"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      xmlns='http://www.w3.org/2000/svg'
+      
+      
+      viewBox='0 0 25.6 25.6'
+    >
+      <path
+        d='M179.076 94.886c-3.568-.1-6.336.268-8.656 1.25-.668.27-1.74.27-1.828 1.116.357.355.4.936.713 1.428.535.893 1.473 2.096 2.32 2.72l2.855 2.053c1.74 1.07 3.703 1.695 5.398 2.766.982.625 1.963 1.428 2.945 2.098.5.357.803.938 1.428 1.16v-.135c-.312-.4-.402-.98-.713-1.428l-1.34-1.293c-1.293-1.74-2.9-3.258-4.64-4.506-1.428-.982-4.55-2.32-5.13-3.97l-.088-.1c.98-.1 2.14-.447 3.078-.715 1.518-.4 2.9-.312 4.46-.713l2.143-.625v-.4c-.803-.803-1.383-1.874-2.23-2.632-2.275-1.963-4.775-3.882-7.363-5.488-1.383-.892-3.168-1.473-4.64-2.23-.537-.268-1.428-.402-1.74-.848-.805-.98-1.25-2.275-1.83-3.436l-3.658-7.763c-.803-1.74-1.295-3.48-2.275-5.086-4.596-7.585-9.594-12.18-17.268-16.687-1.65-.937-3.613-1.34-5.7-1.83l-3.346-.18c-.715-.312-1.428-1.16-2.053-1.562-2.543-1.606-9.102-5.086-10.977-.5-1.205 2.9 1.785 5.755 2.8 7.228.76 1.026 1.74 2.186 2.277 3.346.3.758.4 1.562.713 2.365.713 1.963 1.383 4.15 2.32 5.98.5.937 1.025 1.92 1.65 2.767.357.5.982.714 1.115 1.517-.625.893-.668 2.23-1.025 3.347-1.607 5.042-.982 11.288 1.293 15 .715 1.115 2.4 3.57 4.686 2.632 2.008-.803 1.56-3.346 2.14-5.577.135-.535.045-.892.312-1.25v.1l1.83 3.703c1.383 2.186 3.793 4.462 5.8 5.98 1.07.803 1.918 2.187 3.256 2.677v-.135h-.088c-.268-.4-.67-.58-1.027-.892-.803-.803-1.695-1.785-2.32-2.677-1.873-2.498-3.523-5.265-4.996-8.12-.715-1.383-1.34-2.9-1.918-4.283-.27-.536-.27-1.34-.715-1.606-.67.98-1.65 1.83-2.143 3.034-.848 1.918-.936 4.283-1.248 6.737-.18.045-.1 0-.18.1-1.426-.356-1.918-1.83-2.453-3.078-1.338-3.168-1.562-8.254-.402-11.913.312-.937 1.652-3.882 1.117-4.774-.27-.848-1.16-1.338-1.652-2.008-.58-.848-1.203-1.918-1.605-2.855-1.07-2.5-1.605-5.265-2.766-7.764-.537-1.16-1.473-2.365-2.232-3.435-.848-1.205-1.783-2.053-2.453-3.48-.223-.5-.535-1.294-.178-1.83.088-.357.268-.5.623-.58.58-.5 2.232.134 2.812.4 1.65.67 3.033 1.294 4.416 2.23.625.446 1.295 1.294 2.098 1.518h.938c1.428.312 3.033.1 4.37.5 2.365.76 4.506 1.874 6.426 3.08 5.844 3.703 10.664 8.968 13.92 15.26.535 1.026.758 1.963 1.25 3.034.938 2.187 2.098 4.417 3.033 6.56.938 2.097 1.83 4.24 3.168 5.98.67.937 3.346 1.427 4.55 1.918.893.4 2.275.76 3.08 1.25 1.516.937 3.033 2.008 4.46 3.034.713.534 2.945 1.65 3.078 2.54zm-45.5-38.772a7.09 7.09 0 0 0-1.828.223v.1h.088c.357.714.982 1.205 1.428 1.83l1.027 2.142.088-.1c.625-.446.938-1.16.938-2.23-.268-.312-.312-.625-.535-.937-.268-.446-.848-.67-1.206-1.026z'
+        transform='matrix(.390229 0 0 .38781 -46.300037 -16.856717)'
+        fillRule='evenodd'
+        fill='#00678c'
+      />
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+The [MySQL](https://www.mysql.com/) tool enables you to connect to any MySQL database and perform a wide range of database operations directly within your agentic workflows. With secure connection handling and flexible configuration, you can easily manage and interact with your data.
+
+With the MySQL tool, you can:
+
+- **Query data**: Execute SELECT queries to retrieve data from your MySQL tables using the `mysql_query` operation.
+- **Insert records**: Add new rows to your tables with the `mysql_insert` operation by specifying the table and data to insert.
+- **Update records**: Modify existing data in your tables using the `mysql_update` operation, providing the table, new data, and WHERE conditions.
+- **Delete records**: Remove rows from your tables with the `mysql_delete` operation, specifying the table and WHERE conditions.
+- **Execute raw SQL**: Run any custom SQL command using the `mysql_execute` operation for advanced use cases.
+
+The MySQL tool is ideal for scenarios where your agents need to interact with structured data—such as automating reporting, syncing data between systems, or powering data-driven workflows. It streamlines database access, making it easy to read, write, and manage your MySQL data programmatically.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Connect to any MySQL database to execute queries, manage data, and perform database operations. Supports SELECT, INSERT, UPDATE, DELETE operations with secure connection handling.
+
+
+
+## Tools
+
+### `mysql_query`
+
+Execute SELECT query on MySQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | MySQL server hostname or IP address |
+| `port` | number | Yes | MySQL server port \(default: 3306\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `query` | string | Yes | SQL SELECT query to execute |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Array of rows returned from the query |
+| `rowCount` | number | Number of rows returned |
+
+### `mysql_insert`
+
+Insert new record into MySQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | MySQL server hostname or IP address |
+| `port` | number | Yes | MySQL server port \(default: 3306\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `table` | string | Yes | Table name to insert into |
+| `data` | object | Yes | Data to insert as key-value pairs |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Array of inserted rows |
+| `rowCount` | number | Number of rows inserted |
+
+### `mysql_update`
+
+Update existing records in MySQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | MySQL server hostname or IP address |
+| `port` | number | Yes | MySQL server port \(default: 3306\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `table` | string | Yes | Table name to update |
+| `data` | object | Yes | Data to update as key-value pairs |
+| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Array of updated rows |
+| `rowCount` | number | Number of rows updated |
+
+### `mysql_delete`
+
+Delete records from MySQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | MySQL server hostname or IP address |
+| `port` | number | Yes | MySQL server port \(default: 3306\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `table` | string | Yes | Table name to delete from |
+| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Array of deleted rows |
+| `rowCount` | number | Number of rows deleted |
+
+### `mysql_execute`
+
+Execute raw SQL query on MySQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | MySQL server hostname or IP address |
+| `port` | number | Yes | MySQL server port \(default: 3306\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `query` | string | Yes | Raw SQL query to execute |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Array of rows returned from the query |
+| `rowCount` | number | Number of rows affected |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `mysql`

apps/docs/content/docs/tools/notion.mdx

@@ -29,7 +29,17 @@ With Notion, you can:
 - **Connect information**: Link between pages and databases to create a knowledge network
 - **Access anywhere**: Use Notion across web, desktop, and mobile platforms with automatic syncing
 
-In Sim Studio, the Notion integration enables your agents to interact directly with your Notion workspace programmatically. This allows for powerful automation scenarios such as knowledge management, content creation, and information retrieval. Your agents can read existing Notion pages to extract information, write to pages to update content, and create new pages from scratch. This integration bridges the gap between your AI workflows and your knowledge base, enabling seamless documentation and information management. By connecting Sim Studio with Notion, you can automate documentation processes, maintain up-to-date information repositories, generate reports, and organize information intelligently - all through your intelligent agents.
+In Sim, the Notion integration enables your agents to interact directly with your Notion workspace programmatically. This allows for powerful automation scenarios such as knowledge management, content creation, and information retrieval. Your agents can:
+
+- **Read Notion pages**: Extract content and metadata from any Notion page.
+- **Read Notion databases**: Retrieve database structure and information.
+- **Write to pages**: Append new content to existing Notion pages.
+- **Create new pages**: Generate new Notion pages under a parent page, with custom titles and content.
+- **Query databases**: Search and filter database entries using advanced filter and sort criteria.
+- **Search workspace**: Search across your entire Notion workspace for pages or databases matching specific queries.
+- **Create new databases**: Programmatically create new databases with custom properties and structure.
+
+This integration bridges the gap between your AI workflows and your knowledge base, enabling seamless documentation and information management. By connecting Sim with Notion, you can automate documentation processes, maintain up-to-date information repositories, generate reports, and organize information intelligently—all through your intelligent agents.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -50,17 +60,30 @@ Read content from a Notion page
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `pageId` | string | Yes | The ID of the Notion page to read |
-| `accessToken` | string | Yes | Notion OAuth access token |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `lastEditedTime` | string |
-| `createdTime` | string |
-| `url` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Page content in markdown format with headers, paragraphs, lists, and todos |
+| `metadata` | object | Page metadata including title, URL, and timestamps |
+
+### `notion_read_database`
+
+Read database information and structure from Notion
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `databaseId` | string | Yes | The ID of the Notion database to read |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Database information including title, properties schema, and metadata |
+| `metadata` | object | Database metadata including title, ID, URL, timestamps, and properties schema |
 
 ### `notion_write`
 
@@ -72,13 +95,12 @@ Append content to a Notion page
 | --------- | ---- | -------- | ----------- |
 | `pageId` | string | Yes | The ID of the Notion page to append content to |
 | `content` | string | Yes | The content to append to the page |
-| `accessToken` | string | Yes | Notion OAuth access token |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Success message confirming content was appended to page |
 
 ### `notion_create_page`
 
@@ -88,38 +110,75 @@ Create a new page in Notion
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `parentType` | string | Yes | Type of parent:  |
-| `parentId` | string | Yes | ID of the parent page or database |
-| `title` | string | No | Title of the page \(required for parent pages, not for databases\) |
-| `properties` | json | No | JSON object of properties for database pages |
+| `parentId` | string | Yes | ID of the parent page |
+| `title` | string | No | Title of the new page |
 | `content` | string | No | Optional content to add to the page upon creation |
-| `accessToken` | string | Yes | Notion OAuth access token |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Success message confirming page creation |
+| `metadata` | object | Page metadata including title, page ID, URL, and timestamps |
 
+### `notion_query_database`
 
+Query and filter Notion database entries with advanced filtering
 
-## Block Configuration
+#### Input
 
-### Input
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `databaseId` | string | Yes | The ID of the database to query |
+| `filter` | string | No | Filter conditions as JSON \(optional\) |
+| `sorts` | string | No | Sort criteria as JSON array \(optional\) |
+| `pageSize` | number | No | Number of results to return \(default: 100, max: 100\) |
 
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
+#### Output
 
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Formatted list of database entries with their properties |
+| `metadata` | object | Query metadata including total results count, pagination info, and raw results array |
 
+### `notion_search`
 
-### Outputs
+Search across all pages and databases in Notion workspace
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `query` | string | No | Search terms \(leave empty to get all pages\) |
+| `filterType` | string | No | Filter by object type: page, database, or leave empty for all |
+| `pageSize` | number | No | Number of results to return \(default: 100, max: 100\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Formatted list of search results including pages and databases |
+| `metadata` | object | Search metadata including total results count, pagination info, and raw results array |
+
+### `notion_create_database`
+
+Create a new database in Notion with custom properties
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `parentId` | string | Yes | ID of the parent page where the database will be created |
+| `title` | string | Yes | Title for the new database |
+| `properties` | string | No | Database properties as JSON object \(optional, will create a default "Name" property if empty\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Success message with database details and properties list |
+| `metadata` | object | Database metadata including ID, title, URL, creation time, and properties schema |
 
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `metadata` | any | metadata of the response |
 
 
 ## Notes

apps/docs/content/docs/tools/onedrive.mdx

@@ -0,0 +1,125 @@
+---
+title: OneDrive
+description: Create, upload, and list files
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="onedrive"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"  fill='currentColor' viewBox='0 0 32 32' xmlns='http://www.w3.org/2000/svg'>
+      <g>
+        <path
+          d='M12.20245,11.19292l.00031-.0011,6.71765,4.02379,4.00293-1.68451.00018.00068A6.4768,6.4768,0,0,1,25.5,13c.14764,0,.29358.0067.43878.01639a10.00075,10.00075,0,0,0-18.041-3.01381C7.932,10.00215,7.9657,10,8,10A7.96073,7.96073,0,0,1,12.20245,11.19292Z'
+          fill='#0364b8'
+        />
+        <path
+          d='M12.20276,11.19182l-.00031.0011A7.96073,7.96073,0,0,0,8,10c-.0343,0-.06805.00215-.10223.00258A7.99676,7.99676,0,0,0,1.43732,22.57277l5.924-2.49292,2.63342-1.10819,5.86353-2.46746,3.06213-1.28859Z'
+          fill='#0078d4'
+        />
+        <path
+          d='M25.93878,13.01639C25.79358,13.0067,25.64764,13,25.5,13a6.4768,6.4768,0,0,0-2.57648.53178l-.00018-.00068-4.00293,1.68451,1.16077.69528L23.88611,18.19l1.66009.99438,5.67633,3.40007a6.5002,6.5002,0,0,0-5.28375-9.56805Z'
+          fill='#1490df'
+        />
+        <path
+          d='M25.5462,19.18437,23.88611,18.19l-3.80493-2.2791-1.16077-.69528L15.85828,16.5042,9.99475,18.97166,7.36133,20.07985l-5.924,2.49292A7.98889,7.98889,0,0,0,8,26H25.5a6.49837,6.49837,0,0,0,5.72253-3.41556Z'
+          fill='#28a8ea'
+        />
+      </g>
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[OneDrive](https://onedrive.live.com) is Microsoft’s cloud storage and file synchronization service that allows users to securely store, access, and share files across devices. Integrated deeply into the Microsoft 365 ecosystem, OneDrive supports seamless collaboration, version control, and real-time access to content across teams and organizations.
+
+Learn how to integrate the OneDrive tool in Sim to automatically pull, manage, and organize your cloud files within your workflows. This tutorial walks you through connecting OneDrive, setting up file access, and using stored content to power automation. Ideal for syncing essential documents and media with your agents in real time.
+
+With OneDrive, you can:
+
+- **Store files securely in the cloud**: Upload and access documents, images, and other files from any device
+- **Organize your content**: Create structured folders and manage file versions with ease
+- **Collaborate in real time**: Share files, edit them simultaneously with others, and track changes
+- **Access across devices**: Use OneDrive from desktop, mobile, and web platforms
+- **Integrate with Microsoft 365**: Work seamlessly with Word, Excel, PowerPoint, and Teams
+- **Control permissions**: Share files and folders with custom access settings and expiration controls
+
+In Sim, the OneDrive integration enables your agents to directly interact with your cloud storage. Agents can upload new files to specific folders, retrieve and read existing files, and list folder contents to dynamically organize and access information. This integration allows your agents to incorporate file operations into intelligent workflows — automating document intake, content analysis, and structured storage management. By connecting Sim with OneDrive, you empower your agents to manage and use cloud documents programmatically, eliminating manual steps and enhancing automation with secure, real-time file access.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Integrate OneDrive functionality to manage files and folders. Upload new files, create new folders, and list contents of folders using OAuth authentication. Supports file operations with custom MIME types and folder organization.
+
+
+
+## Tools
+
+### `onedrive_upload`
+
+Upload a file to OneDrive
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `fileName` | string | Yes | The name of the file to upload |
+| `content` | string | Yes | The content of the file to upload |
+| `folderSelector` | string | No | Select the folder to upload the file to |
+| `manualFolderId` | string | No | Manually entered folder ID \(advanced mode\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the file was uploaded successfully |
+| `file` | object | The uploaded file object with metadata including id, name, webViewLink, webContentLink, and timestamps |
+
+### `onedrive_create_folder`
+
+Create a new folder in OneDrive
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `folderName` | string | Yes | Name of the folder to create |
+| `folderSelector` | string | No | Select the parent folder to create the folder in |
+| `manualFolderId` | string | No | Manually entered parent folder ID \(advanced mode\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the folder was created successfully |
+| `file` | object | The created folder object with metadata including id, name, webViewLink, and timestamps |
+
+### `onedrive_list`
+
+List files and folders in OneDrive
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `folderSelector` | string | No | Select the folder to list files from |
+| `manualFolderId` | string | No | The manually entered folder ID \(advanced mode\) |
+| `query` | string | No | A query to filter the files |
+| `pageSize` | number | No | The number of files to return |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether files were listed successfully |
+| `files` | array | Array of file and folder objects with metadata |
+| `nextPageToken` | string | Token for retrieving the next page of results \(optional\) |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `onedrive`

apps/docs/content/docs/tools/openai.mdx

@@ -37,13 +37,13 @@ With OpenAI, you can:
 - **Translate languages**: Convert content between different languages with high accuracy
 - **Summarize content**: Condense long-form text while preserving key information
 
-In Sim Studio, the OpenAI integration enables your agents to leverage these powerful AI capabilities programmatically as part of their workflows. This allows for sophisticated automation scenarios that combine natural language understanding, content generation, and semantic analysis. Your agents can generate vector embeddings from text, which are numerical representations that capture semantic meaning, enabling advanced search, classification, and recommendation systems. Additionally, through the DALL-E integration, agents can create images from text descriptions, opening up possibilities for visual content generation. This integration bridges the gap between your workflow automation and state-of-the-art AI capabilities, enabling your agents to understand context, generate relevant content, and make intelligent decisions based on semantic understanding. By connecting Sim Studio with OpenAI, you can create agents that process information more intelligently, generate creative content, and deliver more personalized experiences to users.
+In Sim, the OpenAI integration enables your agents to leverage these powerful AI capabilities programmatically as part of their workflows. This allows for sophisticated automation scenarios that combine natural language understanding, content generation, and semantic analysis. Your agents can generate vector embeddings from text, which are numerical representations that capture semantic meaning, enabling advanced search, classification, and recommendation systems. Additionally, through the DALL-E integration, agents can create images from text descriptions, opening up possibilities for visual content generation. This integration bridges the gap between your workflow automation and state-of-the-art AI capabilities, enabling your agents to understand context, generate relevant content, and make intelligent decisions based on semantic understanding. By connecting Sim with OpenAI, you can create agents that process information more intelligently, generate creative content, and deliver more personalized experiences to users.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Convert text into numerical vector representations using OpenAI
+Convert text into numerical vector representations using OpenAI's embedding models. Transform text data into embeddings for semantic search, clustering, and other vector-based operations.
 
 
 
@@ -57,43 +57,20 @@ Generate embeddings from text using OpenAI
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | OpenAI API key |
 | `input` | string | Yes | Text to generate embeddings for |
 | `model` | string | No | Model to use for embeddings |
-| `encoding_format` | string | No | The format to return the embeddings in |
-| `user` | string | No | A unique identifier for the end-user |
+| `encodingFormat` | string | No | The format to return the embeddings in |
+| `apiKey` | string | Yes | OpenAI API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `embeddings` | string |
-| `model` | string |
-| `usage` | string |
-| `total_tokens` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Embeddings generation results |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `input` | string | Yes | Input Text - Enter text to generate embeddings for |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `embeddings` | json | embeddings of the response |
-| ↳ `model` | string | model of the response |
-| ↳ `usage` | json | usage of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/outlook.mdx

@@ -134,7 +134,7 @@ With Microsoft Outlook, you can:
 - **Access across devices**: Use Outlook on desktop, web, and mobile with real-time sync  
 - **Maintain privacy and security**: Leverage enterprise-grade encryption and compliance controls
 
-In Sim Studio, the Microsoft Outlook integration enables your agents to interact directly with email and calendar data programmatically. This allows for powerful automation scenarios such as sending custom email updates, parsing incoming messages for workflow triggers, creating calendar events, and managing task reminders. By connecting Sim Studio with Microsoft Outlook, you enable intelligent agents to automate communications, streamline scheduling, and maintain visibility into organizational correspondence — all within your workflow ecosystem.
+In Sim, the Microsoft Outlook integration enables your agents to interact directly with email and calendar data programmatically. This allows for powerful automation scenarios such as sending custom email updates, parsing incoming messages for workflow triggers, creating calendar events, and managing task reminders. By connecting Sim with Microsoft Outlook, you enable intelligent agents to automate communications, streamline scheduling, and maintain visibility into organizational correspondence — all within your workflow ecosystem.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -154,18 +154,22 @@ Send emails using Outlook
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Outlook API |
 | `to` | string | Yes | Recipient email address |
 | `subject` | string | Yes | Email subject |
 | `body` | string | Yes | Email body content |
+| `replyToMessageId` | string | No | Message ID to reply to \(for threading\) |
+| `conversationId` | string | No | Conversation ID for threading |
+| `cc` | string | No | CC recipients \(comma-separated\) |
+| `bcc` | string | No | BCC recipients \(comma-separated\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `results` | string |
-| `timestamp` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Email send success status |
+| `status` | string | Delivery status of the email |
+| `timestamp` | string | Timestamp when email was sent |
+| `message` | string | Success or error message |
 
 ### `outlook_draft`
 
@@ -175,20 +179,22 @@ Draft emails using Outlook
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Outlook API |
 | `to` | string | Yes | Recipient email address |
 | `subject` | string | Yes | Email subject |
 | `body` | string | Yes | Email body content |
+| `cc` | string | No | CC recipients \(comma-separated\) |
+| `bcc` | string | No | BCC recipients \(comma-separated\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `results` | string |
-| `subject` | string |
-| `status` | string |
-| `timestamp` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Email draft creation success status |
+| `messageId` | string | Unique identifier for the drafted email |
+| `status` | string | Draft status of the email |
+| `subject` | string | Subject of the drafted email |
+| `timestamp` | string | Timestamp when draft was created |
+| `message` | string | Success or error message |
 
 ### `outlook_read`
 
@@ -198,37 +204,36 @@ Read emails from Outlook
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Outlook |
 | `folder` | string | No | Folder ID to read emails from \(default: Inbox\) |
 | `maxResults` | number | No | Maximum number of emails to retrieve \(default: 1, max: 10\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `results` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or status message |
+| `results` | array | Array of email message objects |
 
+### `outlook_forward`
 
+Forward an existing Outlook message to specified recipients
 
-## Block Configuration
+#### Input
 
-### Input
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `messageId` | string | Yes | The ID of the message to forward |
+| `to` | string | Yes | Recipient email address\(es\), comma-separated |
+| `comment` | string | No | Optional comment to include with the forwarded message |
 
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
+#### Output
 
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `results` | object | Delivery result details |
 
 
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `message` | string | message of the response |
-| ↳ `results` | json | results of the response |
-
 
 ## Notes
 

apps/docs/content/docs/tools/parallel_ai.mdx

@@ -0,0 +1,106 @@
+---
+title: Parallel AI
+description: Search with Parallel AI
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="parallel_ai"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      fill='currentColor'
+      
+      
+      viewBox='0 0 271 270'
+      xmlns='http://www.w3.org/2000/svg'
+    >
+      <path
+        d='M267.804 105.65H193.828C194.026 106.814 194.187 107.996 194.349 109.178H76.6703C76.4546 110.736 76.2388 112.312 76.0591 113.87H1.63342C1.27387 116.198 0.950289 118.543 0.698608 120.925H75.3759C75.2501 122.483 75.1602 124.059 75.0703 125.617H195.949C196.003 126.781 196.057 127.962 196.093 129.144H270.68V125.384C270.195 118.651 269.242 112.061 267.804 105.65Z'
+        fill='#1D1C1A'
+      />
+      <path
+        d='M195.949 144.401H75.0703C75.1422 145.977 75.2501 147.535 75.3759 149.093H0.698608C0.950289 151.457 1.2559 153.802 1.63342 156.148H76.0591C76.2388 157.724 76.4366 159.282 76.6703 160.84H194.349C194.187 162.022 194.008 163.186 193.828 164.367H267.804C269.242 157.957 270.195 151.367 270.68 144.634V140.874H196.093C196.057 142.055 196.003 143.219 195.949 144.401Z'
+        fill='#1D1C1A'
+      />
+      <path
+        d='M190.628 179.642H80.3559C80.7514 181.218 81.1828 182.776 81.6143 184.334H9.30994C10.2448 186.715 11.2515 189.061 12.3121 191.389H83.7536C84.2749 192.965 84.7962 194.523 85.3535 196.08H185.594C185.163 197.262 184.732 198.426 184.282 199.608H254.519C258.6 192.177 261.98 184.316 264.604 176.114H191.455C191.185 177.296 190.898 178.46 190.61 179.642H190.628Z'
+        fill='#1D1C1A'
+      />
+      <path
+        d='M177.666 214.883H93.3352C94.1082 216.458 94.9172 218.034 95.7441 219.574H29.8756C31.8351 221.992 33.8666 224.337 35.9699 226.63H99.6632C100.598 228.205 101.551 229.781 102.522 231.321H168.498C167.761 232.503 167.006 233.685 166.233 234.849H226.762C234.474 227.847 241.36 219.95 247.292 211.355H179.356C178.799 212.537 178.26 213.719 177.684 214.883H177.666Z'
+        fill='#1D1C1A'
+      />
+      <path
+        d='M154.943 250.106H116.058C117.371 251.699 118.701 253.257 120.067 254.797H73.021C91.6094 264.431 112.715 269.946 135.096 270C135.24 270 135.366 270 135.492 270C135.618 270 135.761 270 135.887 270C164.04 269.911 190.178 261.28 211.805 246.56H157.748C156.813 247.742 155.878 248.924 154.925 250.088L154.943 250.106Z'
+        fill='#1D1C1A'
+      />
+      <path
+        d='M116.059 19.9124H154.943C155.896 21.0764 156.831 22.2582 157.766 23.4401H211.823C190.179 8.72065 164.058 0.0895344 135.906 0C135.762 0 135.636 0 135.51 0C135.384 0 135.24 0 135.115 0C112.715 0.0716275 91.6277 5.56904 73.0393 15.2029H120.086C118.719 16.7429 117.389 18.3187 116.077 19.8945L116.059 19.9124Z'
+        fill='#1D1C1A'
+      />
+      <path
+        d='M93.3356 55.1532H177.667C178.242 56.3171 178.799 57.499 179.339 58.6808H247.274C241.342 50.0855 234.457 42.1886 226.744 35.187H166.215C166.988 36.351 167.743 37.5328 168.48 38.7147H102.504C101.533 40.2726 100.58 41.8305 99.6456 43.4063H35.9523C33.831 45.6804 31.7996 48.0262 29.858 50.4616H95.7265C94.8996 52.0195 94.1086 53.5774 93.3176 55.1532H93.3356Z'
+        fill='#1D1C1A'
+      />
+      <path
+        d='M80.3736 90.3758H190.646C190.933 91.5398 191.221 92.7216 191.491 93.9035H264.64C262.015 85.7021 258.636 77.841 254.555 70.4097H184.318C184.767 71.5736 185.199 72.7555 185.63 73.9373H85.3893C84.832 75.4952 84.2927 77.0531 83.7893 78.6289H12.3479C11.2872 80.9389 10.2805 83.2847 9.3457 85.6842H81.65C81.2186 87.2421 80.7871 88.8 80.3916 90.3758H80.3736Z'
+        fill='#1D1C1A'
+      />
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[Parallel AI](https://parallel.ai/) is an advanced web search and content extraction platform designed to deliver comprehensive, high-quality results for any query. By leveraging intelligent processing and large-scale data extraction, Parallel AI enables users and agents to access, analyze, and synthesize information from across the web with speed and accuracy.
+
+With Parallel AI, you can:
+
+- **Search the web intelligently**: Retrieve relevant, up-to-date information from a wide range of sources  
+- **Extract and summarize content**: Get concise, meaningful excerpts from web pages and documents  
+- **Customize search objectives**: Tailor queries to specific needs or questions for targeted results  
+- **Process results at scale**: Handle large volumes of search results with advanced processing options  
+- **Integrate with workflows**: Use Parallel AI within Sim to automate research, content gathering, and knowledge extraction  
+- **Control output granularity**: Specify the number of results and the amount of content per result  
+- **Secure API access**: Protect your searches and data with API key authentication
+
+In Sim, the Parallel AI integration empowers your agents to perform web searches and extract content programmatically. This enables powerful automation scenarios such as real-time research, competitive analysis, content monitoring, and knowledge base creation. By connecting Sim with Parallel AI, you unlock the ability for agents to gather, process, and utilize web data as part of your automated workflows.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Search the web using Parallel AI's advanced search capabilities. Get comprehensive results with intelligent processing and content extraction.
+
+
+
+## Tools
+
+### `parallel_search`
+
+Search the web using Parallel AI. Provides comprehensive search results with intelligent processing and content extraction.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `objective` | string | Yes | The search objective or question to answer |
+| `search_queries` | string | No | Optional comma-separated list of search queries to execute |
+| `processor` | string | No | Processing method: base or pro \(default: base\) |
+| `max_results` | number | No | Maximum number of results to return \(default: 5\) |
+| `max_chars_per_result` | number | No | Maximum characters per result \(default: 1500\) |
+| `apiKey` | string | Yes | Parallel AI API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Search results with excerpts from relevant pages |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `parallel_ai`

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

@@ -31,7 +31,7 @@ With Perplexity AI, you can:
 - **Research efficiently**: Streamline research processes with comprehensive answers to complex queries
 - **Interact conversationally**: Engage in natural dialogue to refine questions and explore topics
 
-In Sim Studio, the Perplexity integration enables your agents to leverage these powerful AI capabilities programmatically as part of their workflows. This allows for sophisticated automation scenarios that combine natural language understanding, real-time information retrieval, and content generation. Your agents can formulate queries, receive comprehensive answers with citations, and incorporate this information into their decision-making processes or outputs. This integration bridges the gap between your workflow automation and access to current, reliable information, enabling your agents to make more informed decisions and provide more accurate responses. By connecting Sim Studio with Perplexity, you can create agents that stay current with the latest information, provide well-researched answers, and deliver more valuable insights to users - all without requiring manual research or information gathering.
+In Sim, the Perplexity integration enables your agents to leverage these powerful AI capabilities programmatically as part of their workflows. This allows for sophisticated automation scenarios that combine natural language understanding, real-time information retrieval, and content generation. Your agents can formulate queries, receive comprehensive answers with citations, and incorporate this information into their decision-making processes or outputs. This integration bridges the gap between your workflow automation and access to current, reliable information, enabling your agents to make more informed decisions and provide more accurate responses. By connecting Sim with Perplexity, you can create agents that stay current with the latest information, provide well-researched answers, and deliver more valuable insights to users - all without requiring manual research or information gathering.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -51,44 +51,22 @@ Generate completions using Perplexity AI chat models
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Perplexity API key |
+| `systemPrompt` | string | No | System prompt to guide the model behavior |
+| `content` | string | Yes | The user message content to send to the model |
 | `model` | string | Yes | Model to use for chat completions \(e.g., sonar, mistral\) |
-| `messages` | array | Yes | Array of message objects with role and content |
 | `max_tokens` | number | No | Maximum number of tokens to generate |
 | `temperature` | number | No | Sampling temperature between 0 and 1 |
+| `apiKey` | string | Yes | Perplexity API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `model` | string |
-| `usage` | string |
-| `completion_tokens` | string |
-| `total_tokens` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Chat completion results |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `prompt` | string | Yes | User Prompt - Enter your prompt here... |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `content` | string | content of the response |
-| ↳ `model` | string | model of the response |
-| ↳ `usage` | json | usage of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/pinecone.mdx

@@ -39,13 +39,13 @@ With Pinecone, you can:
 - **Scale seamlessly**: Handle billions of vectors with consistent performance
 - **Maintain real-time indexes**: Update your vector database in real-time as new data arrives
 
-In Sim Studio, the Pinecone integration enables your agents to leverage vector search capabilities programmatically as part of their workflows. This allows for sophisticated automation scenarios that combine natural language processing with semantic search and retrieval. Your agents can generate embeddings from text, store these vectors in Pinecone indexes, and perform similarity searches to find the most relevant information. This integration bridges the gap between your AI workflows and vector search infrastructure, enabling more intelligent information retrieval based on semantic meaning rather than exact keyword matching. By connecting Sim Studio with Pinecone, you can create agents that understand context, retrieve relevant information from large datasets, and deliver more accurate and personalized responses to users - all without requiring complex infrastructure management or specialized knowledge of vector databases.
+In Sim, the Pinecone integration enables your agents to leverage vector search capabilities programmatically as part of their workflows. This allows for sophisticated automation scenarios that combine natural language processing with semantic search and retrieval. Your agents can generate embeddings from text, store these vectors in Pinecone indexes, and perform similarity searches to find the most relevant information. This integration bridges the gap between your AI workflows and vector search infrastructure, enabling more intelligent information retrieval based on semantic meaning rather than exact keyword matching. By connecting Sim with Pinecone, you can create agents that understand context, retrieve relevant information from large datasets, and deliver more accurate and personalized responses to users - all without requiring complex infrastructure management or specialized knowledge of vector databases.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Store, search, and retrieve vector embeddings using Pinecone
+Store, search, and retrieve vector embeddings using Pinecone's specialized vector database. Generate embeddings from text and perform semantic similarity searches with customizable filtering options.
 
 
 
@@ -59,18 +59,18 @@ Generate embeddings from text using Pinecone
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Pinecone API key |
 | `model` | string | Yes | Model to use for generating embeddings |
 | `inputs` | array | Yes | Array of text inputs to generate embeddings for |
+| `apiKey` | string | Yes | Pinecone API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `model` | string |
-| `vector_type` | string |
-| `usage` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | array | Generated embeddings data with values and vector type |
+| `model` | string | Model used for generating embeddings |
+| `vector_type` | string | Type of vector generated \(dense/sparse\) |
+| `usage` | object | Usage statistics for embeddings generation |
 
 ### `pinecone_upsert_text`
 
@@ -80,16 +80,17 @@ Insert or update text records in a Pinecone index
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Pinecone API key |
 | `indexHost` | string | Yes | Full Pinecone index host URL |
 | `namespace` | string | Yes | Namespace to upsert records into |
 | `records` | array | Yes | Record or array of records to upsert, each containing _id, text, and optional metadata |
+| `apiKey` | string | Yes | Pinecone API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `statusText` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `statusText` | string | Status of the upsert operation |
+| `upsertedCount` | number | Number of records successfully upserted |
 
 ### `pinecone_search_text`
 
@@ -99,7 +100,6 @@ Search for similar text in a Pinecone index
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Pinecone API key |
 | `indexHost` | string | Yes | Full Pinecone index host URL |
 | `namespace` | string | No | Namespace to search in |
 | `searchQuery` | string | Yes | Text to search for |
@@ -107,14 +107,13 @@ Search for similar text in a Pinecone index
 | `fields` | array | No | Fields to return in the results |
 | `filter` | object | No | Filter to apply to the search |
 | `rerank` | object | No | Reranking parameters |
+| `apiKey` | string | Yes | Pinecone API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `matches` | string |
-| `score` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `matches` | array | Search results with ID, score, and metadata |
 
 ### `pinecone_search_vector`
 
@@ -124,7 +123,6 @@ Search for similar vectors in a Pinecone index
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Pinecone API key |
 | `indexHost` | string | Yes | Full Pinecone index host URL |
 | `namespace` | string | No | Namespace to search in |
 | `vector` | array | Yes | Vector to search for |
@@ -132,15 +130,14 @@ Search for similar vectors in a Pinecone index
 | `filter` | object | No | Filter to apply to the search |
 | `includeValues` | boolean | No | Include vector values in response |
 | `includeMetadata` | boolean | No | Include metadata in response |
+| `apiKey` | string | Yes | Pinecone API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `matches` | string |
-| `score` | string |
-| `values` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `matches` | array | Vector search results with ID, score, values, and metadata |
+| `namespace` | string | Namespace where the search was performed |
 
 ### `pinecone_fetch`
 
@@ -150,46 +147,19 @@ Fetch vectors by ID from a Pinecone index
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `apiKey` | string | Yes | Pinecone API key |
 | `indexHost` | string | Yes | Full Pinecone index host URL |
 | `ids` | array | Yes | Array of vector IDs to fetch |
 | `namespace` | string | No | Namespace to fetch vectors from |
+| `apiKey` | string | Yes | Pinecone API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `matches` | string |
-| `values` | string |
-| `metadata` | string |
-| `score` | string |
-| `id` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `matches` | array | Fetched vectors with ID, values, metadata, and score |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `matches` | any | matches of the response |
-| ↳ `upsertedCount` | any | upsertedCount of the response |
-| ↳ `data` | any | data of the response |
-| ↳ `model` | any | model of the response |
-| ↳ `vector_type` | any | vector_type of the response |
-| ↳ `usage` | any | usage of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/postgresql.mdx

@@ -0,0 +1,188 @@
+---
+title: PostgreSQL
+description: Connect to PostgreSQL database
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="postgresql"
+  color="#336791"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      
+      
+      viewBox='-4 0 264 264'
+      xmlns='http://www.w3.org/2000/svg'
+      preserveAspectRatio='xMinYMin meet'
+    >
+      <path d='M255.008 158.086c-1.535-4.649-5.556-7.887-10.756-8.664-2.452-.366-5.26-.21-8.583.475-5.792 1.195-10.089 1.65-13.225 1.738 11.837-19.985 21.462-42.775 27.003-64.228 8.96-34.689 4.172-50.492-1.423-57.64C233.217 10.847 211.614.683 185.552.372c-13.903-.17-26.108 2.575-32.475 4.549-5.928-1.046-12.302-1.63-18.99-1.738-12.537-.2-23.614 2.533-33.079 8.15-5.24-1.772-13.65-4.27-23.362-5.864-22.842-3.75-41.252-.828-54.718 8.685C6.622 25.672-.937 45.684.461 73.634c.444 8.874 5.408 35.874 13.224 61.48 4.492 14.718 9.282 26.94 14.237 36.33 7.027 13.315 14.546 21.156 22.987 23.972 4.731 1.576 13.327 2.68 22.368-4.85 1.146 1.388 2.675 2.767 4.704 4.048 2.577 1.625 5.728 2.953 8.875 3.74 11.341 2.835 21.964 2.126 31.027-1.848.056 1.612.099 3.152.135 4.482.06 2.157.12 4.272.199 6.25.537 13.374 1.447 23.773 4.143 31.049.148.4.347 1.01.557 1.657 1.345 4.118 3.594 11.012 9.316 16.411 5.925 5.593 13.092 7.308 19.656 7.308 3.292 0 6.433-.432 9.188-1.022 9.82-2.105 20.973-5.311 29.041-16.799 7.628-10.86 11.336-27.217 12.007-52.99.087-.729.167-1.425.244-2.088l.16-1.362 1.797.158.463.031c10.002.456 22.232-1.665 29.743-5.154 5.935-2.754 24.954-12.795 20.476-26.351' />
+      <path
+        d='M237.906 160.722c-29.74 6.135-31.785-3.934-31.785-3.934 31.4-46.593 44.527-105.736 33.2-120.211-30.904-39.485-84.399-20.811-85.292-20.327l-.287.052c-5.876-1.22-12.451-1.946-19.842-2.067-13.456-.22-23.664 3.528-31.41 9.402 0 0-95.43-39.314-90.991 49.444.944 18.882 27.064 142.873 58.218 105.422 11.387-13.695 22.39-25.274 22.39-25.274 5.464 3.63 12.006 5.482 18.864 4.817l.533-.452c-.166 1.7-.09 3.363.213 5.332-8.026 8.967-5.667 10.541-21.711 13.844-16.235 3.346-6.698 9.302-.471 10.86 7.549 1.887 25.013 4.561 36.813-11.958l-.47 1.885c3.144 2.519 5.352 16.383 4.982 28.952-.37 12.568-.617 21.197 1.86 27.937 2.479 6.74 4.948 21.905 26.04 17.386 17.623-3.777 26.756-13.564 28.027-29.89.901-11.606 2.942-9.89 3.07-20.267l1.637-4.912c1.887-15.733.3-20.809 11.157-18.448l2.64.232c7.99.363 18.45-1.286 24.589-4.139 13.218-6.134 21.058-16.377 8.024-13.686h.002'
+        fill='#336791'
+      />
+      <path
+        d='M108.076 81.525c-2.68-.373-5.107-.028-6.335.902-.69.523-.904 1.129-.962 1.546-.154 1.105.62 2.327 1.096 2.957 1.346 1.784 3.312 3.01 5.258 3.28.282.04.563.058.842.058 3.245 0 6.196-2.527 6.456-4.392.325-2.336-3.066-3.893-6.355-4.35M196.86 81.599c-.256-1.831-3.514-2.353-6.606-1.923-3.088.43-6.082 1.824-5.832 3.659.2 1.427 2.777 3.863 5.827 3.863.258 0 .518-.017.78-.054 2.036-.282 3.53-1.575 4.24-2.32 1.08-1.136 1.706-2.402 1.591-3.225'
+        fill='#FFF'
+      />
+      <path
+        d='M247.802 160.025c-1.134-3.429-4.784-4.532-10.848-3.28-18.005 3.716-24.453 1.142-26.57-.417 13.995-21.32 25.508-47.092 31.719-71.137 2.942-11.39 4.567-21.968 4.7-30.59.147-9.463-1.465-16.417-4.789-20.665-13.402-17.125-33.072-26.311-56.882-26.563-16.369-.184-30.199 4.005-32.88 5.183-5.646-1.404-11.801-2.266-18.502-2.376-12.288-.199-22.91 2.743-31.704 8.74-3.82-1.422-13.692-4.811-25.765-6.756-20.872-3.36-37.458-.814-49.294 7.571-14.123 10.006-20.643 27.892-19.38 53.16.425 8.501 5.269 34.653 12.913 59.698 10.062 32.964 21 51.625 32.508 55.464 1.347.449 2.9.763 4.613.763 4.198 0 9.345-1.892 14.7-8.33a529.832 529.832 0 0 1 20.261-22.926c4.524 2.428 9.494 3.784 14.577 3.92.01.133.023.266.035.398a117.66 117.66 0 0 0-2.57 3.175c-3.522 4.471-4.255 5.402-15.592 7.736-3.225.666-11.79 2.431-11.916 8.435-.136 6.56 10.125 9.315 11.294 9.607 4.074 1.02 7.999 1.523 11.742 1.523 9.103 0 17.114-2.992 23.516-8.781-.197 23.386.778 46.43 3.586 53.451 2.3 5.748 7.918 19.795 25.664 19.794 2.604 0 5.47-.303 8.623-.979 18.521-3.97 26.564-12.156 29.675-30.203 1.665-9.645 4.522-32.676 5.866-45.03 2.836.885 6.487 1.29 10.434 1.289 8.232 0 17.731-1.749 23.688-4.514 6.692-3.108 18.768-10.734 16.578-17.36zm-44.106-83.48c-.061 3.647-.563 6.958-1.095 10.414-.573 3.717-1.165 7.56-1.314 12.225-.147 4.54.42 9.26.968 13.825 1.108 9.22 2.245 18.712-2.156 28.078a36.508 36.508 0 0 1-1.95-4.009c-.547-1.326-1.735-3.456-3.38-6.404-6.399-11.476-21.384-38.35-13.713-49.316 2.285-3.264 8.084-6.62 22.64-4.813zm-17.644-61.787c21.334.471 38.21 8.452 50.158 23.72 9.164 11.711-.927 64.998-30.14 110.969a171.33 171.33 0 0 0-.886-1.117l-.37-.462c7.549-12.467 6.073-24.802 4.759-35.738-.54-4.488-1.05-8.727-.92-12.709.134-4.22.692-7.84 1.232-11.34.663-4.313 1.338-8.776 1.152-14.037.139-.552.195-1.204.122-1.978-.475-5.045-6.235-20.144-17.975-33.81-6.422-7.475-15.787-15.84-28.574-21.482 5.5-1.14 13.021-2.203 21.442-2.016zM66.674 175.778c-5.9 7.094-9.974 5.734-11.314 5.288-8.73-2.912-18.86-21.364-27.791-50.624-7.728-25.318-12.244-50.777-12.602-57.916-1.128-22.578 4.345-38.313 16.268-46.769 19.404-13.76 51.306-5.524 64.125-1.347-.184.182-.376.352-.558.537-21.036 21.244-20.537 57.54-20.485 59.759-.002.856.07 2.068.168 3.735.362 6.105 1.036 17.467-.764 30.334-1.672 11.957 2.014 23.66 10.111 32.109a36.275 36.275 0 0 0 2.617 2.468c-3.604 3.86-11.437 12.396-19.775 22.426zm22.479-29.993c-6.526-6.81-9.49-16.282-8.133-25.99 1.9-13.592 1.199-25.43.822-31.79-.053-.89-.1-1.67-.127-2.285 3.073-2.725 17.314-10.355 27.47-8.028 4.634 1.061 7.458 4.217 8.632 9.645 6.076 28.103.804 39.816-3.432 49.229-.873 1.939-1.698 3.772-2.402 5.668l-.546 1.466c-1.382 3.706-2.668 7.152-3.465 10.424-6.938-.02-13.687-2.984-18.819-8.34zm1.065 37.9c-2.026-.506-3.848-1.385-4.917-2.114.893-.42 2.482-.992 5.238-1.56 13.337-2.745 15.397-4.683 19.895-10.394 1.031-1.31 2.2-2.794 3.819-4.602l.002-.002c2.411-2.7 3.514-2.242 5.514-1.412 1.621.67 3.2 2.702 3.84 4.938.303 1.056.643 3.06-.47 4.62-9.396 13.156-23.088 12.987-32.921 10.526zm69.799 64.952c-16.316 3.496-22.093-4.829-25.9-14.346-2.457-6.144-3.665-33.85-2.808-64.447.011-.407-.047-.8-.159-1.17a15.444 15.444 0 0 0-.456-2.162c-1.274-4.452-4.379-8.176-8.104-9.72-1.48-.613-4.196-1.738-7.46-.903.696-2.868 1.903-6.107 3.212-9.614l.549-1.475c.618-1.663 1.394-3.386 2.214-5.21 4.433-9.848 10.504-23.337 3.915-53.81-2.468-11.414-10.71-16.988-23.204-15.693-7.49.775-14.343 3.797-17.761 5.53-.735.372-1.407.732-2.035 1.082.954-11.5 4.558-32.992 18.04-46.59 8.489-8.56 19.794-12.788 33.568-12.56 27.14.444 44.544 14.372 54.366 25.979 8.464 10.001 13.047 20.076 14.876 25.51-13.755-1.399-23.11 1.316-27.852 8.096-10.317 14.748 5.644 43.372 13.315 57.129 1.407 2.521 2.621 4.7 3.003 5.626 2.498 6.054 5.732 10.096 8.093 13.046.724.904 1.426 1.781 1.96 2.547-4.166 1.201-11.649 3.976-10.967 17.847-.55 6.96-4.461 39.546-6.448 51.059-2.623 15.21-8.22 20.875-23.957 24.25zm68.104-77.936c-4.26 1.977-11.389 3.46-18.161 3.779-7.48.35-11.288-.838-12.184-1.569-.42-8.644 2.797-9.547 6.202-10.503.535-.15 1.057-.297 1.561-.473.313.255.656.508 1.032.756 6.012 3.968 16.735 4.396 31.874 1.271l.166-.033c-2.042 1.909-5.536 4.471-10.49 6.772z'
+        fill='#FFF'
+      />
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+The [PostgreSQL](https://www.postgresql.org/) tool enables you to connect to any PostgreSQL database and perform a wide range of database operations directly within your agentic workflows. With secure connection handling and flexible configuration, you can easily manage and interact with your data.
+
+With the PostgreSQL tool, you can:
+
+- **Query data**: Execute SELECT queries to retrieve data from your PostgreSQL tables using the `postgresql_query` operation.
+- **Insert records**: Add new rows to your tables with the `postgresql_insert` operation by specifying the table and data to insert.
+- **Update records**: Modify existing data in your tables using the `postgresql_update` operation, providing the table, new data, and WHERE conditions.
+- **Delete records**: Remove rows from your tables with the `postgresql_delete` operation, specifying the table and WHERE conditions.
+- **Execute raw SQL**: Run any custom SQL command using the `postgresql_execute` operation for advanced use cases.
+
+The PostgreSQL tool is ideal for scenarios where your agents need to interact with structured data—such as automating reporting, syncing data between systems, or powering data-driven workflows. It streamlines database access, making it easy to read, write, and manage your PostgreSQL data programmatically.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Connect to any PostgreSQL database to execute queries, manage data, and perform database operations. Supports SELECT, INSERT, UPDATE, DELETE operations with secure connection handling.
+
+
+
+## Tools
+
+### `postgresql_query`
+
+Execute a SELECT query on PostgreSQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | PostgreSQL server hostname or IP address |
+| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `query` | string | Yes | SQL SELECT query to execute |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Array of rows returned from the query |
+| `rowCount` | number | Number of rows returned |
+
+### `postgresql_insert`
+
+Insert data into PostgreSQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | PostgreSQL server hostname or IP address |
+| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `table` | string | Yes | Table name to insert data into |
+| `data` | object | Yes | Data object to insert \(key-value pairs\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Inserted data \(if RETURNING clause used\) |
+| `rowCount` | number | Number of rows inserted |
+
+### `postgresql_update`
+
+Update data in PostgreSQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | PostgreSQL server hostname or IP address |
+| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `table` | string | Yes | Table name to update data in |
+| `data` | object | Yes | Data object with fields to update \(key-value pairs\) |
+| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Updated data \(if RETURNING clause used\) |
+| `rowCount` | number | Number of rows updated |
+
+### `postgresql_delete`
+
+Delete data from PostgreSQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | PostgreSQL server hostname or IP address |
+| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `table` | string | Yes | Table name to delete data from |
+| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Deleted data \(if RETURNING clause used\) |
+| `rowCount` | number | Number of rows deleted |
+
+### `postgresql_execute`
+
+Execute raw SQL query on PostgreSQL database
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `host` | string | Yes | PostgreSQL server hostname or IP address |
+| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
+| `database` | string | Yes | Database name to connect to |
+| `username` | string | Yes | Database username |
+| `password` | string | Yes | Database password |
+| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
+| `query` | string | Yes | Raw SQL query to execute |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Operation status message |
+| `rows` | array | Array of rows returned from the query |
+| `rowCount` | number | Number of rows affected |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `postgresql`

apps/docs/content/docs/tools/qdrant.mdx

@@ -0,0 +1,183 @@
+---
+title: Qdrant
+description: Use Qdrant vector database
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="qdrant"
+  color="#1A223F"
+  icon={true}
+  iconSvg={`<svg className="block-icon"  fill='none' viewBox='0 0 49 56' xmlns='http://www.w3.org/2000/svg'>
+      <g clipPath='url(#b)'>
+        <path
+          d='m38.489 51.477-1.1167-30.787-2.0223-8.1167 13.498 1.429v37.242l-8.2456 4.7589-2.1138-4.5259z'
+          clipRule='evenodd'
+          fill='#24386C'
+          fillRule='evenodd'
+        />
+        <path
+          d='m48.847 14-8.2457 4.7622-17.016-3.7326-19.917 8.1094-3.3183-9.139 12.122-7 12.126-7 12.123 7 12.126 7z'
+          clipRule='evenodd'
+          fill='#7589BE'
+          fillRule='evenodd'
+        />
+        <path
+          d='m0.34961 13.999 8.2457 4.7622 4.7798 14.215 16.139 12.913-4.9158 10.109-12.126-7.0004-12.123-7v-28z'
+          clipRule='evenodd'
+          fill='#B2BFE8'
+          fillRule='evenodd'
+        />
+        <path
+          d='m30.066 38.421-5.4666 8.059v9.5207l7.757-4.4756 3.9968-5.9681'
+          clipRule='evenodd'
+          fill='#24386C'
+          fillRule='evenodd'
+        />
+        <path
+          d='m24.602 36.962-7.7603-13.436 1.6715-4.4531 6.3544-3.0809 7.488 7.5343-7.7536 13.436z'
+          clipRule='evenodd'
+          fill='#7589BE'
+          fillRule='evenodd'
+        />
+        <path
+          d='m16.843 23.525 7.7569 4.4756v8.9585l-7.1741 0.3087-4.3397-5.5412 3.7569-8.2016z'
+          clipRule='evenodd'
+          fill='#B2BFE8'
+          fillRule='evenodd'
+        />
+        <path
+          d='m24.6 28 7.757-4.4752 5.2792 8.7903-6.3886 5.2784-6.6476-0.6346v-8.9589z'
+          clipRule='evenodd'
+          fill='#24386C'
+          fillRule='evenodd'
+        />
+        <path
+          d='m32.355 51.524 8.2457 4.476v-37.238l-8.0032-4.6189-7.9995-4.6189-8.0031 4.6189-7.9995 4.6189v18.479l7.9995 4.6189 8.0031 4.6193 7.757-4.4797v9.5244zm0-19.045-7.757 4.4793-7.7569-4.4793v-8.9549l7.7569-4.4792 7.757 4.4792v8.9549z'
+          clipRule='evenodd'
+          fill='#DC244C'
+          fillRule='evenodd'
+        />
+        <path d='m24.603 46.483v-9.5222l-7.7166-4.4411v9.5064l7.7166 4.4569z' fill='url(#a)' />
+      </g>
+      <defs>
+        <linearGradient
+          id='a'
+          x1='23.18'
+          x2='15.491'
+          y1='38.781'
+          y2='38.781'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop stopColor='#FF3364' offset='0' />
+          <stop stopColor='#C91540' stopOpacity='0' offset='1' />
+        </linearGradient>
+        <clipPath id='b'>
+          <rect transform='translate(.34961)'   fill='#fff' />
+        </clipPath>
+      </defs>
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[Qdrant](https://qdrant.tech) is an open-source vector database designed for efficient storage, management, and retrieval of high-dimensional vector embeddings. Qdrant enables fast and scalable semantic search, making it ideal for AI applications that require similarity search, recommendation systems, and contextual information retrieval.
+
+With Qdrant, you can:
+
+- **Store vector embeddings**: Efficiently manage and persist high-dimensional vectors at scale
+- **Perform semantic similarity search**: Find the most similar vectors to a query vector in real time
+- **Filter and organize data**: Use advanced filtering to narrow down search results based on metadata or payload
+- **Fetch specific points**: Retrieve vectors and their associated payloads by ID
+- **Scale seamlessly**: Handle large collections and high-throughput workloads
+
+In Sim, the Qdrant integration enables your agents to interact with Qdrant programmatically as part of their workflows. Supported operations include:
+
+- **Upsert**: Insert or update points (vectors and payloads) in a Qdrant collection
+- **Search**: Perform similarity search to find vectors most similar to a given query vector, with optional filtering and result customization
+- **Fetch**: Retrieve specific points from a collection by their IDs, with options to include payloads and vectors
+
+This integration allows your agents to leverage powerful vector search and management capabilities, enabling advanced automation scenarios such as semantic search, recommendation, and contextual retrieval. By connecting Sim with Qdrant, you can build agents that understand context, retrieve relevant information from large datasets, and deliver more intelligent and personalized responses—all without managing complex infrastructure.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Store, search, and retrieve vector embeddings using Qdrant. Perform semantic similarity searches and manage your vector collections.
+
+
+
+## Tools
+
+### `qdrant_upsert_points`
+
+Insert or update points in a Qdrant collection
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `url` | string | Yes | Qdrant base URL |
+| `apiKey` | string | No | Qdrant API key \(optional\) |
+| `collection` | string | Yes | Collection name |
+| `points` | array | Yes | Array of points to upsert |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `status` | string | Status of the upsert operation |
+| `data` | object | Result data from the upsert operation |
+
+### `qdrant_search_vector`
+
+Search for similar vectors in a Qdrant collection
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `url` | string | Yes | Qdrant base URL |
+| `apiKey` | string | No | Qdrant API key \(optional\) |
+| `collection` | string | Yes | Collection name |
+| `vector` | array | Yes | Vector to search for |
+| `limit` | number | No | Number of results to return |
+| `filter` | object | No | Filter to apply to the search |
+| `with_payload` | boolean | No | Include payload in response |
+| `with_vector` | boolean | No | Include vector in response |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | array | Vector search results with ID, score, payload, and optional vector data |
+| `status` | string | Status of the search operation |
+
+### `qdrant_fetch_points`
+
+Fetch points by ID from a Qdrant collection
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `url` | string | Yes | Qdrant base URL |
+| `apiKey` | string | No | Qdrant API key \(optional\) |
+| `collection` | string | Yes | Collection name |
+| `ids` | array | Yes | Array of point IDs to fetch |
+| `with_payload` | boolean | No | Include payload in response |
+| `with_vector` | boolean | No | Include vector in response |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | array | Fetched points with ID, payload, and optional vector data |
+| `status` | string | Status of the fetch operation |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `qdrant`

apps/docs/content/docs/tools/reddit.mdx

@@ -26,19 +26,14 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Reddit](https://www.reddit.com/) is a vast social news aggregation, content rating, and discussion platform where registered users submit content such as text posts, images, and links, which are then voted up or down by other members. Known as "the front page of the internet," Reddit is organized into thousands of communities called subreddits, each focused on a specific topic.
+[Reddit](https://www.reddit.com/) is a social platform where users share and discuss content in topic-based communities called subreddits.
 
-With Reddit, you can:
+In Sim, you can use the Reddit integration to:
 
-- **Access diverse content**: Browse thousands of specialized communities covering virtually every topic
-- **Stay informed**: Get real-time updates on trending news, discussions, and viral content
-- **Engage with communities**: Participate in discussions with like-minded individuals
-- **Discover trending topics**: See what's popular across different interest groups
-- **Gather insights**: Collect opinions, feedback, and perspectives from diverse user groups
-- **Monitor public sentiment**: Track reactions and discussions around specific topics or brands
-- **Research niche topics**: Access specialized knowledge in dedicated communities
+- **Get Posts**: Retrieve posts from any subreddit, with options to sort (Hot, New, Top, Rising) and filter Top posts by time (Day, Week, Month, Year, All Time).
+- **Get Comments**: Fetch comments from a specific post, with options to sort and set the number of comments.
 
-In Sim Studio, the Reddit integration enables your agents to programmatically access and analyze content from Reddit's vast ecosystem. This allows for powerful automation scenarios such as trend monitoring, content aggregation, and sentiment analysis. Your agents can retrieve popular posts from specific subreddits, extract valuable information, and incorporate these insights into their workflows. This integration bridges the gap between social media monitoring and your AI workflows, enabling more informed decision-making based on public discussions and trending topics. By connecting Sim Studio with Reddit, you can create agents that stay on top of relevant conversations, identify emerging trends, gather diverse perspectives, and deliver timely insights - all without requiring manual browsing of countless Reddit threads.
+These operations let your agents access and analyze Reddit content as part of your automated workflows.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -50,24 +45,6 @@ Access Reddit data to retrieve posts and comments from any subreddit. Get post t
 
 ## Tools
 
-### `reddit_hot_posts`
-
-Fetch the most popular (hot) posts from a specified subreddit.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `subreddit` | string | Yes | The name of the subreddit to fetch posts from \(without the r/ prefix\) |
-| `limit` | number | No | Maximum number of posts to return \(default: 10, max: 100\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `subreddit` | string |
-| `posts` | string |
-
 ### `reddit_get_posts`
 
 Fetch posts from a subreddit with different sorting options
@@ -77,16 +54,16 @@ Fetch posts from a subreddit with different sorting options
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `subreddit` | string | Yes | The name of the subreddit to fetch posts from \(without the r/ prefix\) |
-| `sort` | string | No | Sort method for posts:  |
+| `sort` | string | No | Sort method for posts: "hot", "new", "top", or "rising" \(default: "hot"\) |
 | `limit` | number | No | Maximum number of posts to return \(default: 10, max: 100\) |
-| `time` | string | No | Time filter for  |
+| `time` | string | No | Time filter for "top" sorted posts: "day", "week", "month", "year", or "all" \(default: "day"\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `subreddit` | string |
-| `posts` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `subreddit` | string | Name of the subreddit where posts were fetched from |
+| `posts` | array | Array of posts with title, author, URL, score, comments count, and metadata |
 
 ### `reddit_get_comments`
 
@@ -98,44 +75,17 @@ Fetch comments from a specific Reddit post
 | --------- | ---- | -------- | ----------- |
 | `postId` | string | Yes | The ID of the Reddit post to fetch comments from |
 | `subreddit` | string | Yes | The subreddit where the post is located \(without the r/ prefix\) |
-| `sort` | string | No | Sort method for comments:  |
+| `sort` | string | No | Sort method for comments: "confidence", "top", "new", "controversial", "old", "random", "qa" \(default: "confidence"\) |
 | `limit` | number | No | Maximum number of comments to return \(default: 50, max: 100\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `post` | string |
-| `title` | string |
-| `author` | string |
-| `selftext` | string |
-| `created_utc` | string |
-| `score` | string |
-| `permalink` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `post` | object | Post information including ID, title, author, content, and metadata |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `action` | string | Yes | Action |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `subreddit` | string | subreddit of the response |
-| ↳ `posts` | json | posts of the response |
-| ↳ `post` | json | post of the response |
-| ↳ `comments` | json | comments of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/s3.mdx

@@ -43,6 +43,23 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
   </svg>`}
 />
 
+{/* MANUAL-CONTENT-START:intro */}
+[Amazon S3](https://aws.amazon.com/s3/) is a highly scalable, secure, and durable cloud storage service provided by Amazon Web Services. It's designed to store and retrieve any amount of data from anywhere on the web, making it one of the most widely used cloud storage solutions for businesses of all sizes.
+
+With Amazon S3, you can:
+
+- **Store unlimited data**: Upload files of any size and type with virtually unlimited storage capacity
+- **Access from anywhere**: Retrieve your files from anywhere in the world with low-latency access
+- **Ensure data durability**: Benefit from 99.999999999% (11 9's) durability with automatic data replication
+- **Control access**: Manage permissions and access controls with fine-grained security policies
+- **Scale automatically**: Handle varying workloads without manual intervention or capacity planning
+- **Integrate seamlessly**: Connect with other AWS services and third-party applications easily
+- **Optimize costs**: Choose from multiple storage classes to optimize costs based on access patterns
+
+In Sim, the S3 integration enables your agents to retrieve and access files stored in your Amazon S3 buckets using secure presigned URLs. This allows for powerful automation scenarios such as processing documents, analyzing stored data, retrieving configuration files, and accessing media content as part of your workflows. Your agents can securely fetch files from S3 without exposing your AWS credentials, making it easy to incorporate cloud-stored assets into your automation processes. This integration bridges the gap between your cloud storage and AI workflows, enabling seamless access to your stored data while maintaining security best practices through AWS's robust authentication mechanisms.
+{/* MANUAL-CONTENT-END */}
+
+
 ## Usage Instructions
 
 Retrieve and view files from Amazon S3 buckets using presigned URLs.
@@ -61,39 +78,17 @@ Retrieve an object from an AWS S3 bucket
 | --------- | ---- | -------- | ----------- |
 | `accessKeyId` | string | Yes | Your AWS Access Key ID |
 | `secretAccessKey` | string | Yes | Your AWS Secret Access Key |
-| `s3Uri` | string | Yes | S3 Object URL \(e.g., https://bucket-name.s3.region.amazonaws.com/path/to/file\) |
+| `s3Uri` | string | Yes | S3 Object URL |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `size` | string |
-| `name` | string |
-| `lastModified` | string |
-| `url` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `url` | string | Pre-signed URL for downloading the S3 object |
+| `metadata` | object | File metadata including type, size, name, and last modified date |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `accessKeyId` | string | Yes | Access Key ID - Enter your AWS Access Key ID |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `response` | object | Output from response |
-| ↳ `url` | string | url of the response |
-| ↳ `metadata` | json | metadata of the response |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/schedule.mdx

@@ -0,0 +1,42 @@
+---
+title: Schedule
+description: Trigger workflow execution on a schedule
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="schedule"
+  color="#7B68EE"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      xmlns='http://www.w3.org/2000/svg'
+      
+      
+      viewBox='0 0 24 24'
+      fill='none'
+      stroke='currentColor'
+      strokeWidth='2'
+      strokeLinecap='round'
+      strokeLinejoin='round'
+    >
+      <path d='M8 2v4' />
+      <path d='M16 2v4' />
+      <rect   x='3' y='4' rx='2' />
+      <path d='M3 10h18' />
+    </svg>`}
+/>
+
+## Usage Instructions
+
+Configure automated workflow execution with flexible timing options. Set up recurring workflows that run at specific intervals or times.
+
+
+
+
+
+## Notes
+
+- Category: `triggers`
+- Type: `schedule`