v0.3.56: i18n, sharepoint operations & logs search improvements

* added add list items

(cherry picked from commit df6ea35d5bb975c03c7ec0c787bd915f34890ac0)

* bun run lint

* minor changes

---------

Co-authored-by: Adam Gough <adamgough@Mac.attlocal.net>
Co-authored-by: Adam Gough <adamgough@Adams-MacBook-Pro.local>

.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

@@ -2,22 +2,47 @@ name: Build and Publish Docker Image
 
 on:
   push:
-    branches: [main]
-    tags: ['v*']
+    branches: [main, staging]
 
 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,14 +51,11 @@ 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
 
       - name: Log in to the Container registry
-        if: github.event_name != 'pull_request'
+        if: github.event_name != 'pull_request' && github.ref == 'refs/heads/main'
         uses: docker/login-action@v3
         with:
           registry: ghcr.io
@@ -46,21 +68,84 @@ jobs:
         with:
           images: ${{ matrix.image }}
           tags: |
-            type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}
-            type=ref,event=pr
-            type=semver,pattern={{version}}
-            type=semver,pattern={{major}}.{{minor}}
-            type=semver,pattern={{major}}.{{minor}}.{{patch}}
-            type=sha,format=long
+            type=raw,value=latest-${{ matrix.arch }},enable=${{ github.ref == 'refs/heads/main' }}
+            type=raw,value=staging-${{ github.sha }}-${{ matrix.arch }},enable=${{ github.ref == 'refs/heads/staging' }}
+            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: linux/amd64,linux/arm64
-          push: ${{ github.event_name != 'pull_request' }}
+          platforms: ${{ matrix.platform }}
+          push: ${{ github.event_name != 'pull_request' && github.ref == 'refs/heads/main' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
+          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' && github.ref == 'refs/heads/main'
+    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:
+          images: ${{ matrix.image }}
+          tags: |
+            type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}
+            type=sha,format=long
+
+      - 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,21 @@ 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'
+          DATABASE_URL: 'postgresql://postgres:postgres@localhost:5432/simstudio'
           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'
+          DATABASE_URL: 'postgresql://postgres:postgres@localhost:5432/simstudio'
           STRIPE_SECRET_KEY: 'dummy_key_for_ci_only'
           STRIPE_WEBHOOK_SECRET: 'dummy_secret_for_ci_only'
           RESEND_API_KEY: 'dummy_key_for_ci_only'
@@ -71,7 +73,7 @@ jobs:
         run: bun install
 
       - name: Apply migrations
-        working-directory: ./apps/sim
+        working-directory: ./packages/db
         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 --config=./drizzle.config.ts

.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/i18n.yml

@@ -0,0 +1,151 @@
+name: 'Auto-translate Documentation'
+
+on:
+  push:
+    branches: [ staging ]
+    paths: 
+      - 'apps/docs/content/docs/en/**'
+      - 'apps/docs/i18n.json'
+  workflow_dispatch: # Allow manual triggers
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  translate:
+    runs-on: ubuntu-latest
+    if: github.actor != 'github-actions[bot]' # Prevent infinite loops
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GH_PAT }}
+          fetch-depth: 0
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Run Lingo.dev translations
+        env:
+          LINGODOTDEV_API_KEY: ${{ secrets.LINGODOTDEV_API_KEY }}
+        run: |
+          cd apps/docs
+          bunx lingo.dev@latest i18n
+      
+      - name: Check for translation changes
+        id: changes
+        run: |
+          cd apps/docs
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action"
+          
+          if [ -n "$(git status --porcelain content/docs)" ]; then
+            echo "changes=true" >> $GITHUB_OUTPUT
+          else
+            echo "changes=false" >> $GITHUB_OUTPUT
+          fi
+      
+      - name: Create Pull Request with translations
+        if: steps.changes.outputs.changes == 'true'
+        uses: peter-evans/create-pull-request@v5
+        with:
+          token: ${{ secrets.GH_PAT }}
+          commit-message: "feat(i18n): update translations"
+          title: "🌐 Auto-update translations"
+          body: |
+            ## Summary
+            Automated translation updates triggered by changes to documentation.
+            
+            This PR was automatically created after content changes were made, updating translations for all supported languages using Lingo.dev AI translation engine.
+            
+            **Original trigger**: ${{ github.event.head_commit.message }}
+            **Commit**: ${{ github.sha }}
+            **Workflow**: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+            
+            ## Type of Change
+            - [ ] Bug fix
+            - [ ] New feature  
+            - [ ] Breaking change
+            - [x] Documentation
+            - [ ] Other: ___________
+            
+            ## Testing
+            This PR includes automated translations for modified English documentation content:
+            - 🇪🇸 Spanish (es) translations
+            - 🇫🇷 French (fr) translations  
+            - 🇨🇳 Chinese (zh) translations
+            
+            **What reviewers should focus on:**
+            - Verify translated content accuracy and context
+            - Check that all links and references work correctly in translated versions
+            - Ensure formatting, code blocks, and structure are preserved
+            - Validate that technical terms are appropriately translated
+            
+            ## Checklist
+            - [x] Code follows project style guidelines (automated translation)
+            - [x] Self-reviewed my changes (automated process)
+            - [ ] Tests added/updated and passing
+            - [x] No new warnings introduced
+            - [x] I confirm that I have read and agree to the terms outlined in the [Contributor License Agreement (CLA)](./CONTRIBUTING.md#contributor-license-agreement-cla)
+            
+            ## Screenshots/Videos
+            <!-- Translation changes are text-based - no visual changes expected -->
+            <!-- Reviewers should check the documentation site renders correctly for all languages -->
+          branch: auto-translate/staging-merge-${{ github.run_id }}
+          base: staging
+          labels: |
+            i18n
+
+  verify-translations:
+    needs: translate
+    runs-on: ubuntu-latest
+    if: always() # Run even if translation fails
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          ref: staging
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: |
+          cd apps/docs
+          bun install
+
+      - name: Build documentation to verify translations
+        run: |
+          cd apps/docs
+          bun run build
+
+      - name: Report translation status
+        run: |
+          cd apps/docs
+          echo "## Translation Status Report" >> $GITHUB_STEP_SUMMARY
+          echo "**Triggered by merge to staging branch**" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          
+          en_count=$(find content/docs/en -name "*.mdx" | wc -l)
+          es_count=$(find content/docs/es -name "*.mdx" 2>/dev/null | wc -l || echo 0)
+          fr_count=$(find content/docs/fr -name "*.mdx" 2>/dev/null | wc -l || echo 0)
+          zh_count=$(find content/docs/zh -name "*.mdx" 2>/dev/null | wc -l || echo 0)
+          
+          es_percentage=$((es_count * 100 / en_count))
+          fr_percentage=$((fr_count * 100 / en_count))
+          zh_percentage=$((zh_count * 100 / en_count))
+          
+          echo "### Coverage Statistics" >> $GITHUB_STEP_SUMMARY
+          echo "- **🇬🇧 English**: $en_count files (source)" >> $GITHUB_STEP_SUMMARY
+          echo "- **🇪🇸 Spanish**: $es_count/$en_count files ($es_percentage%)" >> $GITHUB_STEP_SUMMARY
+          echo "- **🇫🇷 French**: $fr_count/$en_count files ($fr_percentage%)" >> $GITHUB_STEP_SUMMARY
+          echo "- **🇨🇳 Chinese**: $zh_count/$en_count files ($zh_percentage%)" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "🔄 **Auto-translation PR**: Check for new pull request with updated translations" >> $GITHUB_STEP_SUMMARY

.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,8 @@ start-collector.sh
 .turbo
 
 # VSCode
-.vscode
+.vscode
+
+## Helm Chart Tests
+helm/sim/test
+i18n.cache

.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,73 @@ 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 (from packages/db):
 
 ```bash
-bun run dev
+cd packages/db
+bunx drizzle-kit migrate --config=./drizzle.config.ts
 ```
 
-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` environment variable in your self-hosted apps/sim/.env file to that value
+
 ## Tech Stack
 
 - **Framework**: [Next.js](https://nextjs.org/) (App Router)
@@ -143,6 +174,8 @@ 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/)
+- **Remote Code Execution**: [E2B](https://www.e2b.dev/)
 
 ## Contributing
 
@@ -152,4 +185,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)/[[...slug]]/layout.tsx

@@ -1,5 +0,0 @@
-import type { ReactNode } from 'react'
-
-export default function SlugLayout({ children }: { children: ReactNode }) {
-  return children
-}

apps/docs/app/(docs)/[[...slug]]/page.tsx

@@ -1,58 +0,0 @@
-import { DocsBody, DocsDescription, DocsPage, DocsTitle } from 'fumadocs-ui/page'
-import { notFound } from 'next/navigation'
-import mdxComponents from '@/components/mdx-components'
-import { source } from '@/lib/source'
-
-export const dynamic = 'force-dynamic'
-
-export default async function Page(props: { params: Promise<{ slug?: string[] }> }) {
-  const params = await props.params
-  const page = source.getPage(params.slug)
-  if (!page) notFound()
-
-  const MDX = page.data.body
-
-  return (
-    <DocsPage
-      toc={page.data.toc}
-      full={page.data.full}
-      tableOfContent={{
-        style: 'clerk',
-        enabled: true,
-        header: <div className='mb-2 font-medium text-sm'>On this page</div>,
-        single: false,
-      }}
-      article={{
-        className: 'scroll-smooth max-sm:pb-16',
-      }}
-      tableOfContentPopover={{
-        style: 'clerk',
-        enabled: true,
-      }}
-      footer={{
-        enabled: false,
-      }}
-    >
-      <DocsTitle>{page.data.title}</DocsTitle>
-      <DocsDescription>{page.data.description}</DocsDescription>
-      <DocsBody>
-        <MDX components={mdxComponents} />
-      </DocsBody>
-    </DocsPage>
-  )
-}
-
-export async function generateStaticParams() {
-  return source.generateParams()
-}
-
-export async function generateMetadata(props: { params: Promise<{ slug?: string[] }> }) {
-  const params = await props.params
-  const page = source.getPage(params.slug)
-  if (!page) notFound()
-
-  return {
-    title: page.data.title,
-    description: page.data.description,
-  }
-}

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

@@ -1,46 +0,0 @@
-import type { ReactNode } from 'react'
-import { DocsLayout } from 'fumadocs-ui/layouts/docs'
-import { ExternalLink, GithubIcon } from 'lucide-react'
-import Link from 'next/link'
-import { source } from '@/lib/source'
-
-const GitHubLink = () => (
-  <div className='fixed right-4 bottom-4 z-50'>
-    <Link
-      href='https://github.com/simstudioai/sim'
-      target='_blank'
-      rel='noopener noreferrer'
-      className='flex h-8 w-8 items-center justify-center rounded-full border border-border bg-background transition-colors hover:bg-muted'
-    >
-      <GithubIcon className='h-4 w-4' />
-    </Link>
-  </div>
-)
-
-export default function Layout({ children }: { children: ReactNode }) {
-  return (
-    <>
-      <DocsLayout
-        tree={source.pageTree}
-        nav={{
-          title: <div className='flex items-center font-medium'>Sim Studio</div>,
-        }}
-        links={[
-          {
-            text: 'Visit Sim Studio',
-            url: 'https://simstudio.ai',
-            icon: <ExternalLink className='h-4 w-4' />,
-          },
-        ]}
-        sidebar={{
-          defaultOpenLevel: 1,
-          collapsible: true,
-          footer: null,
-        }}
-      >
-        {children}
-      </DocsLayout>
-      <GitHubLink />
-    </>
-  )
-}

apps/docs/app/[lang]/[[...slug]]/page.tsx

@@ -0,0 +1,161 @@
+import { findNeighbour } from 'fumadocs-core/server'
+import defaultMdxComponents from 'fumadocs-ui/mdx'
+import { DocsBody, DocsDescription, DocsPage, DocsTitle } from 'fumadocs-ui/page'
+import { ChevronLeft, ChevronRight } from 'lucide-react'
+import Link from 'next/link'
+import { notFound } from 'next/navigation'
+import { StructuredData } from '@/components/structured-data'
+import { source } from '@/lib/source'
+
+export const dynamic = 'force-dynamic'
+
+export default async function Page(props: { params: Promise<{ slug?: string[]; lang: string }> }) {
+  const params = await props.params
+  const page = source.getPage(params.slug, params.lang)
+  if (!page) notFound()
+
+  const MDX = page.data.body
+  const baseUrl = 'https://docs.sim.ai'
+
+  const pageTreeRecord = source.pageTree as Record<string, any>
+  const pageTree =
+    pageTreeRecord[params.lang] ?? pageTreeRecord.en ?? Object.values(pageTreeRecord)[0]
+  const neighbours = pageTree ? findNeighbour(pageTree, page.url) : null
+
+  const CustomFooter = () => (
+    <div className='mt-12 flex items-center justify-between border-border border-t py-8'>
+      {neighbours?.previous ? (
+        <Link
+          href={neighbours.previous.url}
+          className='group flex items-center gap-2 text-muted-foreground transition-colors hover:text-foreground'
+        >
+          <ChevronLeft className='group-hover:-translate-x-1 h-4 w-4 transition-transform' />
+          <span className='font-medium'>{neighbours.previous.name}</span>
+        </Link>
+      ) : (
+        <div />
+      )}
+
+      {neighbours?.next ? (
+        <Link
+          href={neighbours.next.url}
+          className='group flex items-center gap-2 text-muted-foreground transition-colors hover:text-foreground'
+        >
+          <span className='font-medium'>{neighbours.next.name}</span>
+          <ChevronRight className='h-4 w-4 transition-transform group-hover:translate-x-1' />
+        </Link>
+      ) : (
+        <div />
+      )}
+    </div>
+  )
+
+  return (
+    <>
+      <StructuredData
+        title={page.data.title}
+        description={page.data.description || ''}
+        url={`${baseUrl}${page.url}`}
+        lang={params.lang}
+      />
+      <DocsPage
+        toc={page.data.toc}
+        full={page.data.full}
+        tableOfContent={{
+          style: 'clerk',
+          enabled: true,
+          header: <div className='mb-2 font-medium text-sm'>On this page</div>,
+          single: false,
+        }}
+        article={{
+          className: 'scroll-smooth max-sm:pb-16',
+        }}
+        tableOfContentPopover={{
+          style: 'clerk',
+          enabled: true,
+        }}
+        footer={{
+          enabled: true,
+          component: <CustomFooter />,
+        }}
+      >
+        <DocsTitle>{page.data.title}</DocsTitle>
+        <DocsDescription>{page.data.description}</DocsDescription>
+        <DocsBody>
+          <MDX components={defaultMdxComponents} />
+        </DocsBody>
+      </DocsPage>
+    </>
+  )
+}
+
+export async function generateStaticParams() {
+  return source.generateParams()
+}
+
+export async function generateMetadata(props: {
+  params: Promise<{ slug?: string[]; lang: string }>
+}) {
+  const params = await props.params
+  const page = source.getPage(params.slug, params.lang)
+  if (!page) notFound()
+
+  const baseUrl = 'https://docs.sim.ai'
+  const fullUrl = `${baseUrl}${page.url}`
+
+  return {
+    title: page.data.title,
+    description:
+      page.data.description || 'Sim visual workflow builder for AI applications documentation',
+    keywords: [
+      'AI workflow builder',
+      'visual workflow editor',
+      'AI automation',
+      'workflow automation',
+      'AI agents',
+      'no-code AI',
+      'drag and drop workflows',
+      page.data.title?.toLowerCase().split(' '),
+    ]
+      .flat()
+      .filter(Boolean),
+    authors: [{ name: 'Sim Team' }],
+    category: 'Developer Tools',
+    openGraph: {
+      title: page.data.title,
+      description:
+        page.data.description || 'Sim visual workflow builder for AI applications documentation',
+      url: fullUrl,
+      siteName: 'Sim Documentation',
+      type: 'article',
+      locale: params.lang,
+      alternateLocale: ['en', 'fr', 'zh'].filter((lang) => lang !== params.lang),
+    },
+    twitter: {
+      card: 'summary',
+      title: page.data.title,
+      description:
+        page.data.description || 'Sim visual workflow builder for AI applications documentation',
+    },
+    robots: {
+      index: true,
+      follow: true,
+      googleBot: {
+        index: true,
+        follow: true,
+        'max-video-preview': -1,
+        'max-image-preview': 'large',
+        'max-snippet': -1,
+      },
+    },
+    canonical: fullUrl,
+    alternates: {
+      canonical: fullUrl,
+      languages: {
+        en: `${baseUrl}/en${page.url.replace(`/${params.lang}`, '')}`,
+        fr: `${baseUrl}/fr${page.url.replace(`/${params.lang}`, '')}`,
+        zh: `${baseUrl}/zh${page.url.replace(`/${params.lang}`, '')}`,
+      },
+    },
+  }
+}

apps/docs/app/[lang]/layout.tsx

@@ -0,0 +1,99 @@
+import type { ReactNode } from 'react'
+import { defineI18nUI } from 'fumadocs-ui/i18n'
+import { DocsLayout } from 'fumadocs-ui/layouts/docs'
+import { RootProvider } from 'fumadocs-ui/provider'
+import { ExternalLink, GithubIcon } from 'lucide-react'
+import { Inter } from 'next/font/google'
+import Image from 'next/image'
+import Link from 'next/link'
+import { LanguageDropdown } from '@/components/ui/language-dropdown'
+import { i18n } from '@/lib/i18n'
+import { source } from '@/lib/source'
+import '../global.css'
+import { Analytics } from '@vercel/analytics/next'
+
+const inter = Inter({
+  subsets: ['latin'],
+})
+
+const { provider } = defineI18nUI(i18n, {
+  translations: {
+    en: {
+      displayName: 'English',
+    },
+    es: {
+      displayName: 'Español',
+    },
+    fr: {
+      displayName: 'Français',
+    },
+    zh: {
+      displayName: '简体中文',
+    },
+  },
+})
+
+const GitHubLink = () => (
+  <div className='fixed right-4 bottom-4 z-50'>
+    <Link
+      href='https://github.com/simstudioai/sim'
+      target='_blank'
+      rel='noopener noreferrer'
+      className='flex h-8 w-8 items-center justify-center rounded-full border border-border bg-background transition-colors hover:bg-muted'
+    >
+      <GithubIcon className='h-4 w-4' />
+    </Link>
+  </div>
+)
+
+type LayoutProps = {
+  children: ReactNode
+  params: Promise<{ lang: string }>
+}
+
+export default async function Layout({ children, params }: LayoutProps) {
+  const { lang } = await params
+
+  return (
+    <html lang={lang} className={inter.className} suppressHydrationWarning>
+      <body className='flex min-h-screen flex-col'>
+        <RootProvider i18n={provider(lang)}>
+          <DocsLayout
+            tree={source.pageTree[lang]}
+            nav={{
+              title: (
+                <div className='flex items-center gap-3'>
+                  <Image
+                    src='/static/logo.png'
+                    alt='Sim'
+                    width={60}
+                    height={24}
+                    className='h-6 w-auto'
+                  />
+                  <LanguageDropdown />
+                </div>
+              ),
+            }}
+            links={[
+              {
+                text: 'Visit Sim',
+                url: 'https://sim.ai',
+                icon: <ExternalLink className='h-4 w-4' />,
+              },
+            ]}
+            sidebar={{
+              defaultOpenLevel: 0,
+              collapsible: true,
+              footer: null,
+              banner: null,
+            }}
+          >
+            {children}
+          </DocsLayout>
+          <GitHubLink />
+          <Analytics />
+        </RootProvider>
+      </body>
+    </html>
+  )
+}

apps/docs/app/global.css

@@ -1,10 +1,155 @@
 @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 */
 }
 
+/* Target any potential border classes */
+* {
+  --fd-border-sidebar: transparent !important;
+}
+
+/* Override any CSS custom properties for borders */
+:root {
+  --fd-border: transparent !important;
+  --fd-border-sidebar: transparent !important;
+}
+
+/* Sidebar improvements for cleaner design */
+[data-sidebar] {
+  --fd-sidebar-width: 280px;
+  background-color: rgb(255 255 255);
+  padding-top: 16px;
+}
+
+/* Clean sidebar container */
+[data-sidebar] > div {
+  padding: 0 16px;
+}
+
+/* Section headers/separators styling */
+[data-sidebar] .text-sm.font-medium.text-muted-foreground,
+[data-sidebar] [data-separator] {
+  font-size: 11px;
+  font-weight: 600;
+  text-transform: uppercase;
+  letter-spacing: 0.05em;
+  margin-top: 20px;
+  margin-bottom: 6px;
+  padding-left: 12px;
+  padding-right: 12px;
+  color: rgb(115 115 115);
+  border: none;
+  background: none;
+}
+
+/* First separator should have less top margin */
+[data-sidebar] [data-separator]:first-of-type {
+  margin-top: 12px;
+}
+
+/* Clean sidebar item styling */
+[data-sidebar] a {
+  padding: 8px 12px;
+  margin: 1px 0;
+  border-radius: 6px;
+  font-size: 14px;
+  font-weight: 400;
+  line-height: 1.4;
+  transition: all 0.15s ease;
+  display: block;
+  color: rgb(71 85 105);
+  text-decoration: none;
+}
+
+[data-sidebar] a[data-active="true"] {
+  background-color: rgba(128, 47, 255, 0.08);
+  color: var(--color-fd-primary);
+  font-weight: 500;
+}
+
+[data-sidebar] a:hover:not([data-active="true"]) {
+  background-color: rgb(248 250 252);
+  color: rgb(51 65 85);
+}
+
+/* Improve spacing between sidebar items */
+[data-sidebar] nav > * + * {
+  margin-top: 2px;
+}
+
+/* Section group styling */
+[data-sidebar] [data-folder] {
+  margin-bottom: 4px;
+}
+
+[data-sidebar] [data-folder] > div:first-child {
+  font-weight: 500;
+  font-size: 13px;
+  color: rgb(15 23 42);
+  padding: 6px 12px;
+  margin-bottom: 4px;
+}
+
+/* Clean up folder toggle buttons */
+[data-sidebar] button[data-folder-toggle] {
+  padding: 4px 8px 4px 12px;
+  border-radius: 6px;
+  font-size: 13px;
+  font-weight: 500;
+  color: rgb(51 65 85);
+}
+
+[data-sidebar] button[data-folder-toggle]:hover {
+  background-color: rgb(248 250 252);
+}
+
+/* Nested item indentation */
+[data-sidebar] [data-folder] a {
+  padding-left: 24px;
+  font-size: 14px;
+}
+
+/* Dark mode adjustments */
+@media (prefers-color-scheme: dark) {
+  [data-sidebar] {
+    background-color: rgb(2 8 23);
+  }
+
+  [data-sidebar] a {
+    color: rgb(148 163 184);
+  }
+
+  [data-sidebar] a:hover:not([data-active="true"]) {
+    background-color: rgb(30 41 59);
+    color: rgb(226 232 240);
+  }
+
+  [data-sidebar] a[data-active="true"] {
+    background-color: rgba(128, 47, 255, 0.15);
+    color: var(--color-fd-primary);
+  }
+
+  [data-sidebar] .text-sm.font-medium.text-muted-foreground,
+  [data-sidebar] [data-separator] {
+    color: rgb(148 163 184);
+  }
+
+  [data-sidebar] [data-folder] > div:first-child {
+    color: rgb(226 232 240);
+  }
+
+  [data-sidebar] button[data-folder-toggle] {
+    color: rgb(148 163 184);
+  }
+
+  [data-sidebar] button[data-folder-toggle]:hover {
+    background-color: rgb(30 41 59);
+  }
+}
+
 /* Custom text highlighting styles */
 .text-highlight {
   color: var(--color-fd-primary);
@@ -15,4 +160,26 @@
   color: var(--color-fd-primary);
 }
 
+/* Add bottom spacing to prevent abrupt page endings */
+[data-content] {
+  padding-bottom: 4rem;
+}
+
+/* Alternative fallback for different Fumadocs versions */
+main article,
+.docs-page main {
+  padding-bottom: 4rem;
+}
+
+/* Remove any unwanted borders/outlines from video elements */
+video {
+  outline: none !important;
+  border-style: solid !important;
+}
+
+/* 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

@@ -1,30 +1,32 @@
 import type { ReactNode } from 'react'
-import { RootProvider } from 'fumadocs-ui/provider'
-import { Inter } from 'next/font/google'
-import './global.css'
-import { Analytics } from '@vercel/analytics/next'
 
-const inter = Inter({
-  subsets: ['latin'],
-})
-
-export default function Layout({ children }: { children: ReactNode }) {
-  return (
-    <html lang='en' className={inter.className} suppressHydrationWarning>
-      <body className='flex min-h-screen flex-col'>
-        <RootProvider>
-          {children}
-          <Analytics />
-        </RootProvider>
-      </body>
-    </html>
-  )
+export default function RootLayout({ children }: { children: ReactNode }) {
+  return children
 }
 
 export const metadata = {
-  title: 'Sim Studio',
+  metadataBase: new URL('https://docs.sim.ai'),
+  title: {
+    default: 'Sim Documentation - Visual Workflow Builder for AI Applications',
+    template: '%s',
+  },
   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.',
+    'Comprehensive documentation for Sim - the visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas—no coding required.',
+  keywords: [
+    'AI workflow builder',
+    'visual workflow editor',
+    'AI automation',
+    'workflow automation',
+    'AI agents',
+    'no-code AI',
+    'drag and drop workflows',
+    'AI integrations',
+    'workflow canvas',
+    'AI development platform',
+  ],
+  authors: [{ name: 'Sim Team', url: 'https://sim.ai' }],
+  category: 'Developer Tools',
+  classification: 'Developer Documentation',
   manifest: '/favicon/site.webmanifest',
   icons: {
     icon: [
@@ -37,6 +39,42 @@ export const metadata = {
   appleWebApp: {
     capable: true,
     statusBarStyle: 'default',
-    title: 'Sim Studio Docs',
+    title: 'Sim Docs',
+  },
+  openGraph: {
+    type: 'website',
+    locale: 'en_US',
+    alternateLocale: ['fr_FR', 'zh_CN'],
+    url: 'https://docs.sim.ai',
+    siteName: 'Sim Documentation',
+    title: 'Sim Documentation - Visual Workflow Builder for AI Applications',
+    description:
+      'Comprehensive documentation for Sim - the visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines.',
+  },
+  twitter: {
+    card: 'summary',
+    title: 'Sim Documentation - Visual Workflow Builder for AI Applications',
+    description:
+      'Comprehensive documentation for Sim - the visual workflow builder for AI applications.',
+    creator: '@sim_ai',
+  },
+  robots: {
+    index: true,
+    follow: true,
+    googleBot: {
+      index: true,
+      follow: true,
+      'max-video-preview': -1,
+      'max-image-preview': 'large',
+      'max-snippet': -1,
+    },
+  },
+  alternates: {
+    canonical: 'https://docs.sim.ai',
+    languages: {
+      en: '/en',
+      fr: '/fr',
+      zh: '/zh',
+    },
   },
 }

apps/docs/app/llms.txt/route.ts

@@ -1,7 +1,6 @@
 import { getLLMText } from '@/lib/llms'
 import { source } from '@/lib/source'
 
-// cached forever
 export const revalidate = false
 
 export async function GET() {

apps/docs/app/robots.txt/route.ts

@@ -0,0 +1,58 @@
+export const revalidate = false
+
+export async function GET() {
+  const baseUrl = 'https://docs.sim.ai'
+
+  const robotsTxt = `# Robots.txt for Sim Documentation
+# Generated on ${new Date().toISOString()}
+
+User-agent: *
+Allow: /
+
+# Allow all well-behaved crawlers
+User-agent: Googlebot
+Allow: /
+
+User-agent: Bingbot
+Allow: /
+
+# AI and LLM crawlers
+User-agent: GPTBot
+Allow: /
+
+User-agent: ChatGPT-User
+Allow: /
+
+User-agent: CCBot
+Allow: /
+
+User-agent: anthropic-ai
+Allow: /
+
+User-agent: Claude-Web
+Allow: /
+
+# Disallow admin and internal paths (if any exist)
+Disallow: /.next/
+Disallow: /api/internal/
+Disallow: /_next/static/
+Disallow: /admin/
+
+# Allow but don't prioritize these
+Allow: /api/search
+Allow: /llms.txt
+Allow: /llms.mdx/
+
+# Sitemaps
+Sitemap: ${baseUrl}/sitemap.xml
+
+# Additional resources for AI indexing
+# See https://github.com/AnswerDotAI/llms-txt for more info
+# LLM-friendly content available at: ${baseUrl}/llms.txt`
+
+  return new Response(robotsTxt, {
+    headers: {
+      'Content-Type': 'text/plain',
+    },
+  })
+}

apps/docs/app/sitemap.xml/route.ts

@@ -0,0 +1,54 @@
+import { i18n } from '@/lib/i18n'
+import { source } from '@/lib/source'
+
+export const revalidate = false
+
+export async function GET() {
+  const baseUrl = 'https://docs.sim.ai'
+
+  const allPages = source.getPages()
+
+  const urls = allPages
+    .flatMap((page) => {
+      const urlWithoutLang = page.url.replace(/^\/[a-z]{2}\//, '/')
+
+      return i18n.languages.map((lang) => {
+        const url =
+          lang === i18n.defaultLanguage
+            ? `${baseUrl}${urlWithoutLang}`
+            : `${baseUrl}/${lang}${urlWithoutLang}`
+
+        return `  <url>
+    <loc>${url}</loc>
+    <lastmod>${new Date().toISOString().split('T')[0]}</lastmod>
+    <changefreq>weekly</changefreq>
+    <priority>${urlWithoutLang === '/introduction' ? '1.0' : '0.8'}</priority>
+    ${i18n.languages.length > 1 ? generateAlternateLinks(baseUrl, urlWithoutLang) : ''}
+  </url>`
+      })
+    })
+    .join('\n')
+
+  const sitemap = `<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml">
+${urls}
+</urlset>`
+
+  return new Response(sitemap, {
+    headers: {
+      'Content-Type': 'application/xml',
+    },
+  })
+}
+
+function generateAlternateLinks(baseUrl: string, urlWithoutLang: string): string {
+  return i18n.languages
+    .map((lang) => {
+      const url =
+        lang === i18n.defaultLanguage
+          ? `${baseUrl}${urlWithoutLang}`
+          : `${baseUrl}/${lang}${urlWithoutLang}`
+      return `    <xhtml:link rel="alternate" hreflang="${lang}" href="${url}" />`
+    })
+    .join('\n')
+}

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/mdx-components.tsx

@@ -1,10 +0,0 @@
-import defaultMdxComponents from 'fumadocs-ui/mdx'
-import { ThemeImage } from './ui/theme-image'
-
-// Extend the default MDX components with our custom components
-const mdxComponents = {
-  ...defaultMdxComponents,
-  ThemeImage,
-}
-
-export default mdxComponents

apps/docs/components/structured-data.tsx

@@ -0,0 +1,174 @@
+import Script from 'next/script'
+
+interface StructuredDataProps {
+  title: string
+  description: string
+  url: string
+  lang: string
+  dateModified?: string
+  breadcrumb?: Array<{ name: string; url: string }>
+}
+
+export function StructuredData({
+  title,
+  description,
+  url,
+  lang,
+  dateModified,
+  breadcrumb,
+}: StructuredDataProps) {
+  const baseUrl = 'https://docs.sim.ai'
+
+  const articleStructuredData = {
+    '@context': 'https://schema.org',
+    '@type': 'TechArticle',
+    headline: title,
+    description: description,
+    url: url,
+    datePublished: dateModified || new Date().toISOString(),
+    dateModified: dateModified || new Date().toISOString(),
+    author: {
+      '@type': 'Organization',
+      name: 'Sim Team',
+      url: baseUrl,
+    },
+    publisher: {
+      '@type': 'Organization',
+      name: 'Sim',
+      url: baseUrl,
+      logo: {
+        '@type': 'ImageObject',
+        url: `${baseUrl}/static/logo.png`,
+      },
+    },
+    mainEntityOfPage: {
+      '@type': 'WebPage',
+      '@id': url,
+    },
+    inLanguage: lang,
+    isPartOf: {
+      '@type': 'WebSite',
+      name: 'Sim Documentation',
+      url: baseUrl,
+    },
+    potentialAction: {
+      '@type': 'ReadAction',
+      target: url,
+    },
+  }
+
+  const breadcrumbStructuredData = breadcrumb && {
+    '@context': 'https://schema.org',
+    '@type': 'BreadcrumbList',
+    itemListElement: breadcrumb.map((item, index) => ({
+      '@type': 'ListItem',
+      position: index + 1,
+      name: item.name,
+      item: item.url,
+    })),
+  }
+
+  const websiteStructuredData = url === baseUrl && {
+    '@context': 'https://schema.org',
+    '@type': 'WebSite',
+    name: 'Sim Documentation',
+    url: baseUrl,
+    description:
+      'Comprehensive documentation for Sim visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines.',
+    publisher: {
+      '@type': 'Organization',
+      name: 'Sim',
+      url: baseUrl,
+    },
+    potentialAction: {
+      '@type': 'SearchAction',
+      target: {
+        '@type': 'EntryPoint',
+        urlTemplate: `${baseUrl}/search?q={search_term_string}`,
+      },
+      'query-input': 'required name=search_term_string',
+    },
+    inLanguage: ['en', 'fr', 'zh'],
+  }
+
+  const faqStructuredData = title.toLowerCase().includes('faq') && {
+    '@context': 'https://schema.org',
+    '@type': 'FAQPage',
+    mainEntity: [],
+  }
+
+  const softwareStructuredData = {
+    '@context': 'https://schema.org',
+    '@type': 'SoftwareApplication',
+    name: 'Sim',
+    applicationCategory: 'DeveloperApplication',
+    operatingSystem: 'Any',
+    description:
+      'Visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas—no coding required.',
+    url: baseUrl,
+    author: {
+      '@type': 'Organization',
+      name: 'Sim Team',
+    },
+    offers: {
+      '@type': 'Offer',
+      category: 'Developer Tools',
+    },
+    featureList: [
+      'Visual workflow builder with drag-and-drop interface',
+      'AI agent creation and automation',
+      '80+ built-in integrations',
+      'Real-time team collaboration',
+      'Multiple deployment options',
+      'Custom integrations via MCP protocol',
+    ],
+  }
+
+  return (
+    <>
+      <Script
+        id='article-structured-data'
+        type='application/ld+json'
+        dangerouslySetInnerHTML={{
+          __html: JSON.stringify(articleStructuredData),
+        }}
+      />
+      {breadcrumbStructuredData && (
+        <Script
+          id='breadcrumb-structured-data'
+          type='application/ld+json'
+          dangerouslySetInnerHTML={{
+            __html: JSON.stringify(breadcrumbStructuredData),
+          }}
+        />
+      )}
+      {websiteStructuredData && (
+        <Script
+          id='website-structured-data'
+          type='application/ld+json'
+          dangerouslySetInnerHTML={{
+            __html: JSON.stringify(websiteStructuredData),
+          }}
+        />
+      )}
+      {faqStructuredData && (
+        <Script
+          id='faq-structured-data'
+          type='application/ld+json'
+          dangerouslySetInnerHTML={{
+            __html: JSON.stringify(faqStructuredData),
+          }}
+        />
+      )}
+      {url === baseUrl && (
+        <Script
+          id='software-structured-data'
+          type='application/ld+json'
+          dangerouslySetInnerHTML={{
+            __html: JSON.stringify(softwareStructuredData),
+          }}
+        />
+      )}
+    </>
+  )
+}

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

@@ -1,163 +0,0 @@
-import { cn } from '@/lib/utils'
-import {
-  AgentIcon,
-  ApiIcon,
-  ChartBarIcon,
-  CodeIcon,
-  ConditionalIcon,
-  ConnectIcon,
-  ResponseIcon,
-} from '../icons'
-
-// Custom Feature component specifically for BlockTypes to handle the 6-item layout
-const BlockFeature = ({
-  title,
-  description,
-  icon,
-  href,
-  index,
-  totalItems,
-  itemsPerRow,
-}: {
-  title: string
-  description: string
-  icon: React.ReactNode
-  href?: string
-  index: number
-  totalItems: number
-  itemsPerRow: number
-}) => {
-  const blockColor = {
-    '--block-color':
-      title === 'Agent'
-        ? '#8b5cf6'
-        : title === 'API'
-          ? '#3b82f6'
-          : title === 'Condition'
-            ? '#f59e0b'
-            : title === 'Function'
-              ? '#10b981'
-              : title === 'Router'
-                ? '#6366f1'
-                : title === 'Evaluator'
-                  ? '#ef4444'
-                  : '#8b5cf6',
-  } as React.CSSProperties
-
-  const content = (
-    <>
-      {index < itemsPerRow && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-t from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      {index >= itemsPerRow && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-b from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      <div
-        className='relative z-10 mb-4 px-10 text-neutral-500 transition-colors duration-200 group-hover/feature:text-[color:var(--block-color,#8b5cf6)] dark:text-neutral-400 dark:group-hover/feature:text-[color:var(--block-color,#a78bfa)]'
-        style={blockColor}
-      >
-        {icon}
-      </div>
-      <div className='relative z-10 mb-2 px-10 font-bold text-lg'>
-        <div
-          className='absolute inset-y-0 left-0 h-6 w-1 origin-center rounded-tr-full rounded-br-full bg-neutral-300 transition-all duration-200 group-hover/feature:h-8 group-hover/feature:bg-[color:var(--block-color,#8b5cf6)] dark:bg-neutral-700'
-          style={blockColor}
-        />
-        <span className='inline-block text-neutral-800 transition duration-200 group-hover/feature:translate-x-2 dark:text-neutral-100'>
-          {title}
-        </span>
-      </div>
-      <p className='relative z-10 max-w-xs px-10 text-neutral-600 text-sm dark:text-neutral-300'>
-        {description}
-      </p>
-    </>
-  )
-
-  const containerClasses = cn(
-    'flex flex-col lg:border-r py-5 relative group/feature dark:border-neutral-800',
-    (index === 0 || index === itemsPerRow) && 'lg:border-l dark:border-neutral-800',
-    index < itemsPerRow && 'lg:border-b dark:border-neutral-800',
-    href && 'cursor-pointer hover:bg-neutral-50 dark:hover:bg-neutral-900/50 transition-colors'
-  )
-
-  if (href) {
-    return (
-      <a href={href} className={containerClasses} style={{ textDecoration: 'none' }}>
-        {content}
-      </a>
-    )
-  }
-
-  return <div className={containerClasses}>{content}</div>
-}
-
-export function BlockTypes() {
-  const features = [
-    {
-      title: 'Agent',
-      description:
-        'Create powerful AI agents using any LLM provider with customizable system prompts and tool integrations.',
-      icon: <AgentIcon className='h-6 w-6' />,
-      href: '/blocks/agent',
-    },
-    {
-      title: 'API',
-      description:
-        'Connect to any external API with support for all standard HTTP methods and customizable request parameters.',
-      icon: <ApiIcon className='h-6 w-6' />,
-      href: '/blocks/api',
-    },
-    {
-      title: 'Condition',
-      description:
-        'Add a condition to the workflow to branch the execution path based on a boolean expression.',
-      icon: <ConditionalIcon className='h-6 w-6' />,
-      href: '/blocks/condition',
-    },
-    {
-      title: 'Function',
-      description:
-        'Execute custom JavaScript or TypeScript code within your workflow to transform data or implement complex logic.',
-      icon: <CodeIcon className='h-6 w-6' />,
-      href: '/blocks/function',
-    },
-    {
-      title: 'Router',
-      description:
-        'Intelligently direct workflow execution to different paths based on input analysis.',
-      icon: <ConnectIcon className='h-6 w-6' />,
-      href: '/blocks/router',
-    },
-    {
-      title: 'Evaluator',
-      description:
-        'Assess content using customizable evaluation metrics and scoring criteria across multiple dimensions.',
-      icon: <ChartBarIcon className='h-6 w-6' />,
-      href: '/blocks/evaluator',
-    },
-    {
-      title: 'Response',
-      description:
-        'Send a response back to the caller with customizable data, status, and headers.',
-      icon: <ResponseIcon className='h-6 w-6' />,
-      href: '/blocks/response',
-    },
-  ]
-
-  const totalItems = features.length
-  const itemsPerRow = 3 // For large screens
-
-  return (
-    <div className='relative z-10 mx-auto grid max-w-7xl grid-cols-1 py-10 md:grid-cols-2 lg:grid-cols-3'>
-      {features.map((feature, index) => (
-        <BlockFeature
-          key={feature.title}
-          {...feature}
-          index={index}
-          totalItems={totalItems}
-          itemsPerRow={itemsPerRow}
-        />
-      ))}
-    </div>
-  )
-}

apps/docs/components/ui/features.tsx

@@ -1,102 +0,0 @@
-import {
-  IconAdjustmentsBolt,
-  IconCloud,
-  IconEaseInOut,
-  IconHeart,
-  IconHelp,
-  IconHistory,
-  IconRouteAltLeft,
-  IconTerminal2,
-} from '@tabler/icons-react'
-import { cn } from '@/lib/utils'
-
-export function Features() {
-  const features = [
-    {
-      title: 'Multi-LLM Support',
-      description: 'Connect to any LLM provider including OpenAI, Anthropic, and more',
-      icon: <IconCloud />,
-    },
-    {
-      title: 'API Deployment',
-      description: 'Deploy your workflows as secure, scalable APIs',
-      icon: <IconTerminal2 />,
-    },
-    {
-      title: 'Webhook Integration',
-      description: 'Trigger workflows via webhooks from external services',
-      icon: <IconRouteAltLeft />,
-    },
-    {
-      title: 'Scheduled Execution',
-      description: 'Schedule workflows to run at specific times or intervals',
-      icon: <IconEaseInOut />,
-    },
-    {
-      title: '40+ Integrations',
-      description: 'Connect to hundreds of external services and data sources',
-      icon: <IconAdjustmentsBolt />,
-    },
-    {
-      title: 'Visual Debugging',
-      description: 'Debug workflows visually with detailed execution logs',
-      icon: <IconHelp />,
-    },
-    {
-      title: 'Version Control',
-      description: 'Track changes and roll back to previous versions',
-      icon: <IconHistory />,
-    },
-    {
-      title: 'Team Collaboration',
-      description: 'Collaborate with team members on workflow development',
-      icon: <IconHeart />,
-    },
-  ]
-  return (
-    <div className='relative z-20 mx-auto grid max-w-7xl grid-cols-1 py-10 md:grid-cols-2 lg:grid-cols-4'>
-      {features.map((feature, index) => (
-        <Feature key={feature.title} {...feature} index={index} />
-      ))}
-    </div>
-  )
-}
-
-export const Feature = ({
-  title,
-  description,
-  icon,
-  index,
-}: {
-  title: string
-  description: string
-  icon: React.ReactNode
-  index: number
-}) => {
-  return (
-    <div
-      className={cn(
-        'group/feature relative flex flex-col py-5 lg:border-r dark:border-neutral-800',
-        (index === 0 || index === 4) && 'lg:border-l dark:border-neutral-800',
-        index < 4 && 'lg:border-b dark:border-neutral-800'
-      )}
-    >
-      {index < 4 && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-t from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      {index >= 4 && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-b from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      <div className='relative z-10 mb-4 px-10 text-neutral-600 dark:text-neutral-400'>{icon}</div>
-      <div className='relative z-10 mb-2 px-10 font-bold text-lg'>
-        <div className='absolute inset-y-0 left-0 h-6 w-1 origin-center rounded-tr-full rounded-br-full bg-neutral-300 transition-all duration-200 group-hover/feature:h-8 group-hover/feature:bg-purple-500 dark:bg-neutral-700' />
-        <span className='inline-block text-neutral-800 transition duration-200 group-hover/feature:translate-x-2 dark:text-neutral-100'>
-          {title}
-        </span>
-      </div>
-      <p className='relative z-10 max-w-xs px-10 text-neutral-600 text-sm dark:text-neutral-300'>
-        {description}
-      </p>
-    </div>
-  )
-}

apps/docs/components/ui/image.tsx

@@ -0,0 +1,53 @@
+'use client'
+
+import { useState } from 'react'
+import NextImage, { type ImageProps as NextImageProps } from 'next/image'
+import { cn } from '@/lib/utils'
+import { Lightbox } from './lightbox'
+
+interface ImageProps extends Omit<NextImageProps, 'className'> {
+  className?: string
+  enableLightbox?: boolean
+}
+
+export function Image({
+  className = 'w-full',
+  enableLightbox = true,
+  alt = '',
+  src,
+  ...props
+}: ImageProps) {
+  const [isLightboxOpen, setIsLightboxOpen] = useState(false)
+
+  const handleImageClick = () => {
+    if (enableLightbox) {
+      setIsLightboxOpen(true)
+    }
+  }
+
+  return (
+    <>
+      <NextImage
+        className={cn(
+          'overflow-hidden rounded-xl border border-border object-cover shadow-sm',
+          enableLightbox && 'cursor-pointer transition-opacity hover:opacity-90',
+          className
+        )}
+        alt={alt}
+        src={src}
+        onClick={handleImageClick}
+        {...props}
+      />
+
+      {enableLightbox && (
+        <Lightbox
+          isOpen={isLightboxOpen}
+          onClose={() => setIsLightboxOpen(false)}
+          src={typeof src === 'string' ? src : String(src)}
+          alt={alt}
+          type='image'
+        />
+      )}
+    </>
+  )
+}

apps/docs/components/ui/language-dropdown.tsx

@@ -0,0 +1,107 @@
+'use client'
+
+import { useEffect, useState } from 'react'
+import { Check, ChevronDown } from 'lucide-react'
+import { useParams, usePathname } from 'next/navigation'
+
+const languages = {
+  en: { name: 'English', flag: '🇺🇸' },
+  es: { name: 'Español', flag: '🇪🇸' },
+  fr: { name: 'Français', flag: '🇫🇷' },
+  zh: { name: '简体中文', flag: '🇨🇳' },
+}
+
+export function LanguageDropdown() {
+  const [isOpen, setIsOpen] = useState(false)
+  const pathname = usePathname()
+  const params = useParams()
+
+  const [currentLang, setCurrentLang] = useState(() => {
+    const langFromParams = params?.lang as string
+    return langFromParams && Object.keys(languages).includes(langFromParams) ? langFromParams : 'en'
+  })
+
+  useEffect(() => {
+    const langFromParams = params?.lang as string
+
+    if (langFromParams && Object.keys(languages).includes(langFromParams)) {
+      if (langFromParams !== currentLang) {
+        setCurrentLang(langFromParams)
+      }
+    } else {
+      if (currentLang !== 'en') {
+        setCurrentLang('en')
+      }
+    }
+  }, [params, currentLang])
+
+  const handleLanguageChange = (locale: string) => {
+    if (locale === currentLang) {
+      setIsOpen(false)
+      return
+    }
+
+    setIsOpen(false)
+
+    const segments = pathname.split('/').filter(Boolean)
+
+    if (segments[0] && Object.keys(languages).includes(segments[0])) {
+      segments.shift()
+    }
+
+    let newPath = ''
+    if (locale === 'en') {
+      newPath = segments.length > 0 ? `/${segments.join('/')}` : '/introduction'
+    } else {
+      newPath = `/${locale}${segments.length > 0 ? `/${segments.join('/')}` : '/introduction'}`
+    }
+
+    window.location.href = newPath
+  }
+
+  return (
+    <div className='relative'>
+      <button
+        onClick={(e) => {
+          e.preventDefault()
+          e.stopPropagation()
+          setIsOpen(!isOpen)
+        }}
+        className='flex items-center gap-2 rounded-xl border border-border/20 bg-muted/50 px-3 py-2 text-sm backdrop-blur-sm transition-colors hover:bg-muted'
+      >
+        <span className='text-base'>{languages[currentLang as keyof typeof languages]?.flag}</span>
+        <span className='font-medium text-foreground'>
+          {languages[currentLang as keyof typeof languages]?.name}
+        </span>
+        <ChevronDown
+          className={`h-3 w-3 text-muted-foreground transition-transform ${isOpen ? 'rotate-180' : ''}`}
+        />
+      </button>
+
+      {isOpen && (
+        <>
+          <div className='fixed inset-0 z-10' onClick={() => setIsOpen(false)} />
+          <div className='absolute top-full left-0 z-20 mt-1 w-48 rounded-lg border border-border/50 bg-background/95 shadow-xl backdrop-blur-md'>
+            {Object.entries(languages).map(([code, lang]) => (
+              <button
+                key={code}
+                onClick={(e) => {
+                  e.preventDefault()
+                  e.stopPropagation()
+                  handleLanguageChange(code)
+                }}
+                className={`flex w-full items-center gap-3 px-3 py-2.5 text-sm transition-colors first:rounded-t-lg last:rounded-b-lg hover:bg-muted/80 ${
+                  currentLang === code ? 'bg-muted/60 font-medium text-primary' : 'text-foreground'
+                }`}
+              >
+                <span className='text-base'>{lang.flag}</span>
+                <span>{lang.name}</span>
+                {currentLang === code && <Check className='ml-auto h-4 w-4 text-primary' />}
+              </button>
+            ))}
+          </div>
+        </>
+      )}
+    </div>
+  )
+}

apps/docs/components/ui/lightbox.tsx

@@ -0,0 +1,74 @@
+'use client'
+
+import { useEffect, useRef } from 'react'
+import { getVideoUrl } from '@/lib/utils'
+
+interface LightboxProps {
+  isOpen: boolean
+  onClose: () => void
+  src: string
+  alt: string
+  type: 'image' | 'video'
+}
+
+export function Lightbox({ isOpen, onClose, src, alt, type }: LightboxProps) {
+  const overlayRef = useRef<HTMLDivElement>(null)
+
+  useEffect(() => {
+    const handleKeyDown = (event: KeyboardEvent) => {
+      if (event.key === 'Escape') {
+        onClose()
+      }
+    }
+
+    const handleClickOutside = (event: MouseEvent) => {
+      if (overlayRef.current && event.target === overlayRef.current) {
+        onClose()
+      }
+    }
+
+    if (isOpen) {
+      document.addEventListener('keydown', handleKeyDown)
+      document.addEventListener('click', handleClickOutside)
+      document.body.style.overflow = 'hidden'
+    }
+
+    return () => {
+      document.removeEventListener('keydown', handleKeyDown)
+      document.removeEventListener('click', handleClickOutside)
+      document.body.style.overflow = 'unset'
+    }
+  }, [isOpen, onClose])
+
+  if (!isOpen) return null
+
+  return (
+    <div
+      ref={overlayRef}
+      className='fixed inset-0 z-50 flex items-center justify-center bg-black/80 p-12 backdrop-blur-sm'
+      role='dialog'
+      aria-modal='true'
+      aria-label='Media viewer'
+    >
+      <div className='relative max-h-full max-w-full overflow-hidden rounded-xl shadow-2xl'>
+        {type === 'image' ? (
+          <img
+            src={src}
+            alt={alt}
+            className='max-h-[calc(100vh-6rem)] max-w-[calc(100vw-6rem)] rounded-xl object-contain'
+            loading='lazy'
+          />
+        ) : (
+          <video
+            src={getVideoUrl(src)}
+            autoPlay
+            loop
+            muted
+            playsInline
+            className='max-h-[calc(100vh-6rem)] max-w-[calc(100vw-6rem)] rounded-xl outline-none focus:outline-none'
+          />
+        )}
+      </div>
+    </div>
+  )
+}

apps/docs/components/ui/theme-image.tsx

@@ -1,48 +0,0 @@
-'use client'
-
-import { useEffect, useState } from 'react'
-import Image from 'next/image'
-import { useTheme } from 'next-themes'
-
-interface ThemeImageProps {
-  lightSrc: string
-  darkSrc: string
-  alt: string
-  width?: number
-  height?: number
-  className?: string
-}
-
-export function ThemeImage({
-  lightSrc,
-  darkSrc,
-  alt,
-  width = 600,
-  height = 400,
-  className = 'rounded-lg border border-border my-6',
-}: ThemeImageProps) {
-  const { resolvedTheme } = useTheme()
-  const [imageSrc, setImageSrc] = useState(lightSrc)
-  const [mounted, setMounted] = useState(false)
-
-  // Wait until component is mounted to avoid hydration mismatch
-  useEffect(() => {
-    setMounted(true)
-  }, [])
-
-  useEffect(() => {
-    if (mounted) {
-      setImageSrc(resolvedTheme === 'dark' ? darkSrc : lightSrc)
-    }
-  }, [resolvedTheme, lightSrc, darkSrc, mounted])
-
-  if (!mounted) {
-    return null
-  }
-
-  return (
-    <div className='flex justify-center'>
-      <Image src={imageSrc} alt={alt} width={width} height={height} className={className} />
-    </div>
-  )
-}

apps/docs/components/ui/video.tsx

@@ -0,0 +1,57 @@
+'use client'
+
+import { useState } from 'react'
+import { getVideoUrl } from '@/lib/utils'
+import { Lightbox } from './lightbox'
+
+interface VideoProps {
+  src: string
+  className?: string
+  autoPlay?: boolean
+  loop?: boolean
+  muted?: boolean
+  playsInline?: boolean
+  enableLightbox?: boolean
+}
+
+export function Video({
+  src,
+  className = 'w-full rounded-xl border border-border shadow-sm overflow-hidden outline-none focus:outline-none',
+  autoPlay = true,
+  loop = true,
+  muted = true,
+  playsInline = true,
+  enableLightbox = true,
+}: VideoProps) {
+  const [isLightboxOpen, setIsLightboxOpen] = useState(false)
+
+  const handleVideoClick = () => {
+    if (enableLightbox) {
+      setIsLightboxOpen(true)
+    }
+  }
+
+  return (
+    <>
+      <video
+        autoPlay={autoPlay}
+        loop={loop}
+        muted={muted}
+        playsInline={playsInline}
+        className={`${className} ${enableLightbox ? 'cursor-pointer transition-opacity hover:opacity-90' : ''}`}
+        src={getVideoUrl(src)}
+        onClick={handleVideoClick}
+      />
+
+      {enableLightbox && (
+        <Lightbox
+          isOpen={isLightboxOpen}
+          onClose={() => setIsLightboxOpen(false)}
+          src={src}
+          alt={`Video: ${src}`}
+          type='video'
+        />
+      )}
+    </>
+  )
+}

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

@@ -1,212 +0,0 @@
----
-title: Agent
-description: Create powerful AI agents using any LLM provider
----
-
-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 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.
-
-<ThemeImage
-  lightSrc="/static/light/agent-light.png"
-  darkSrc="/static/dark/agent-dark.png"
-  alt="Agent Block"
-  width={300}
-  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:
-
-<Steps>
-  <Step>
-    <strong>Respond to user inputs</strong>: Generate natural language responses based on provided
-    inputs
-  </Step>
-  <Step>
-    <strong>Follow instructions</strong>: Adhere to specific instructions defined in the system
-    prompt
-  </Step>
-  <Step>
-    <strong>Use specialized tools</strong>: Interact with integrated tools to extend capabilities
-  </Step>
-  <Step>
-    <strong>Structure output</strong>: Generate responses in structured formats when needed
-  </Step>
-</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.
-
-```markdown
-You are a helpful assistant that specializes in financial analysis.
-Always provide clear explanations and cite sources when possible.
-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:
-
-- Directly provided in the block configuration
-- Connected from another block's output
-- Dynamically generated during workflow execution
-
-### Model Selection
-
-Choose from a variety of LLM providers:
-
-- 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
-
-### Temperature
-
-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>
-  </Tab>
-  <Tab>
-    <p>
-      Balanced creativity and focus. Suitable for general purpose applications that require both
-      accuracy and some creativity.
-    </p>
-  </Tab>
-  <Tab>
-    <p>
-      More creative, varied responses. Ideal for creative writing, brainstorming, and generating
-      diverse ideas.
-    </p>
-  </Tab>
-</Tabs>
-
-<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
-  The temperature range (0-1 or 0-2) varies depending on the selected model.
-</p>
-
-### API Key
-
-Your API key for the selected LLM provider. This is securely stored and used for authentication.
-
-### Tools
-
-Integrate specialized tools to enhance the agent's capabilities. You can add tools to your agent by:
-
-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
-
-<ThemeImage
-  lightSrc="/static/light/tooldropdown-light.png"
-  darkSrc="/static/dark/tooldropdown-dark.png"
-  alt="Tools Dropdown"
-  width={150}
-  height={125}
-/>
-
-Available tools include:
-
-- **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
-
-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>
-
-### Response Format
-
-Define a structured format for the agent's response when needed, using JSON or other formats.
-
-## Inputs and Outputs
-
-<Tabs items={['Inputs', 'Outputs']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>User Prompt</strong>: The user's query or context for the agent
-      </li>
-      <li>
-        <strong>System Prompt</strong>: Instructions for the agent (optional)
-      </li>
-      <li>
-        <strong>Tools</strong>: Optional tool connections that the agent can use
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Content</strong>: The agent's response text
-      </li>
-      <li>
-        <strong>Model</strong>: The model used for generation
-      </li>
-      <li>
-        <strong>Tokens</strong>: Usage statistics (prompt, completion, total)
-      </li>
-      <li>
-        <strong>Tool Calls</strong>: Details of any tools used during processing
-      </li>
-      <li>
-        <strong>Cost</strong>: Cost of the response
-      </li>
-      <li>
-        <strong>Usage</strong>: Usage statistics (prompt, completion, total)
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Usage
-
-Here's an example of how an Agent block might be configured for a customer support workflow:
-
-```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.
-
-model: OpenAI/gpt-4
-temperature: 0.2
-tools:
-  - ProductDatabase
-  - OrderHistory
-  - SupportTicketCreator
-```
-
-## 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.

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

@@ -1,128 +0,0 @@
----
-title: API
-description: Connect to external services through API endpoints
----
-
-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 API block enables you to connect your workflow to external services through HTTP requests. It supports various methods like GET, POST, PUT, DELETE, and PATCH, allowing you to interact with virtually any API endpoint.
-
-<ThemeImage
-  lightSrc="/static/light/api-light.png"
-  darkSrc="/static/dark/api-dark.png"
-  alt="API Block"
-  width={300}
-  height={175}
-/>
-
-## Overview
-
-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
-
-## Configuration Options
-
-### URL
-
-The endpoint URL for the API request. This can be:
-
-- A static URL entered directly in the block
-- A dynamic URL connected from another block's output
-- A URL with path parameters
-
-### Method
-
-Select the HTTP method for your request:
-
-- **GET**: Retrieve data from the server
-- **POST**: Send data to the server to create a resource
-- **PUT**: Update an existing resource on the server
-- **DELETE**: Remove a resource from the server
-- **PATCH**: Partially update an existing resource
-
-### Query Parameters
-
-Define key-value pairs that will be appended to the URL as query parameters. For example:
-
-```
-Key: apiKey
-Value: your_api_key_here
-
-Key: limit
-Value: 10
-```
-
-These would be added to the URL as `?apiKey=your_api_key_here&limit=10`.
-
-### Headers
-
-Configure HTTP headers for your request. Common headers include:
-
-```
-Key: Content-Type
-Value: application/json
-
-Key: Authorization
-Value: Bearer your_token_here
-```
-
-### Request Body
-
-For methods that support a request body (POST, PUT, PATCH), you can define the data to send. The body can be:
-
-- JSON data entered directly in the block
-- Data connected from another block's output
-- Dynamically generated during workflow execution
-
-## Inputs and Outputs
-
-### Inputs
-
-- **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)
-
-### Outputs
-
-- **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
-
-## Example Usage
-
-Here's an example of how an API block might be configured to fetch weather data:
-
-```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
-```
-
-## Best Practices
-
-- **Use environment variables for sensitive data**: Don't hardcode API keys or credentials
-- **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

@@ -1,191 +0,0 @@
----
-title: Condition
-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 { 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.
-
-<ThemeImage
-  lightSrc="/static/light/condition-light.png"
-  darkSrc="/static/dark/condition-dark.png"
-  alt="Condition Block"
-  width={300}
-  height={175}
-/>
-
-<Callout>
-  Condition blocks enable deterministic decision-making without requiring an LLM, making them ideal
-  for straightforward branching logic.
-</Callout>
-
-## 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:
-
-<Steps>
-  <Step>
-    <strong>Evaluate Expression</strong>: Evaluates a boolean expression or condition
-  </Step>
-  <Step>
-    <strong>Determine Result</strong>: Determines whether the condition evaluates to true or false
-  </Step>
-  <Step>
-    <strong>Route Workflow</strong>: Routes the workflow to the appropriate path based on the result
-  </Step>
-  <Step>
-    <strong>Provide Context</strong>: Provides context about the decision made
-  </Step>
-</Steps>
-
-## Configuration Options
-
-### Conditions
-
-Define one or more conditions that will be evaluated. Each condition includes:
-
-- **Expression**: A JavaScript/TypeScript expression that evaluates to true or false
-- **Path**: The destination block to route to if the condition is true
-- **Description**: Optional explanation of what the condition checks
-
-You can create multiple conditions that are evaluated in order, with the first matching condition determining the execution path.
-
-### Condition Expression Format
-
-Conditions use JavaScript syntax and can reference input values from previous blocks.
-
-<Tabs items={['Score Threshold', 'Text Analysis', 'Multiple Conditions']}>
-  <Tab>
-    ```javascript
-    // Check if a score is above a threshold
-    input.score > 75
-    ```
-  </Tab>
-  <Tab>
-    ```javascript
-    // Check if a text contains specific keywords
-    input.text.includes('urgent') || input.text.includes('emergency')
-    ```
-  </Tab>
-  <Tab>
-    ```javascript
-    // Check multiple conditions
-    input.age >= 18 && input.country === 'US'
-    ```
-  </Tab>
-</Tabs>
-
-## Inputs and Outputs
-
-<Tabs items={['Inputs', 'Outputs']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Variables</strong>: Values from previous blocks that can be referenced in conditions
-      </li>
-      <li>
-        <strong>Conditions</strong>: Boolean expressions to evaluate
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Content</strong>: A description of the evaluation result
-      </li>
-      <li>
-        <strong>Condition Result</strong>: The boolean result of the condition evaluation
-      </li>
-      <li>
-        <strong>Selected Path</strong>: Details of the chosen routing destination
-      </li>
-      <li>
-        <strong>Selected Condition ID</strong>: Identifier of the condition that was matched
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Usage
-
-Here's an example of how a Condition block might be used in a customer satisfaction workflow:
-
-```yaml
-# Example Condition Configuration
-conditions:
-  - id: 'high_satisfaction'
-    expression: 'input.satisfactionScore >= 8'
-    description: 'Customer is highly satisfied'
-    path: 'positive_feedback_block'
-
-  - id: 'medium_satisfaction'
-    expression: 'input.satisfactionScore >= 5'
-    description: 'Customer is moderately satisfied'
-    path: 'neutral_feedback_block'
-
-  - id: 'default'
-    expression: 'true'
-    description: 'Customer is not satisfied'
-    path: 'improvement_feedback_block'
-```
-
-## 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.

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

@@ -1,128 +0,0 @@
----
-title: Evaluator
-description: Assess content quality using customizable evaluation metrics
----
-
-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 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.
-
-<ThemeImage
-  lightSrc="/static/light/evaluator-light.png"
-  darkSrc="/static/dark/evaluator-dark.png"
-  alt="Evaluator Block"
-  width={300}
-  height={175}
-/>
-
-## Overview
-
-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
-
-## Configuration Options
-
-### Evaluation Metrics
-
-Define custom metrics to evaluate content against. Each metric includes:
-
-- **Name**: A short identifier for the metric
-- **Description**: A detailed explanation of what the metric measures
-- **Range**: The numeric range for scoring (e.g., 1-5, 0-10)
-
-Example metrics:
-
-```
-Accuracy (1-5): How factually accurate is the content?
-Clarity (1-5): How clear and understandable is the content?
-Relevance (1-5): How relevant is the content to the original query?
-```
-
-### Content
-
-The content to be evaluated. This can be:
-
-- Directly provided in the block configuration
-- Connected from another block's output (typically an Agent block)
-- Dynamically generated during workflow execution
-
-### Model Selection
-
-Choose an LLM provider 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
-
-The chosen model should have strong reasoning capabilities to provide accurate evaluations.
-
-### API Key
-
-Your API key for the selected LLM provider. This is securely stored and used for authentication.
-
-## How It Works
-
-1. The Evaluator block takes the provided content and your custom metrics
-2. It generates a specialized prompt that instructs the LLM to evaluate the content
-3. The prompt includes clear guidelines on how to score each metric
-4. The LLM evaluates the content and returns numeric scores for each metric
-5. The Evaluator block formats these scores as structured output for use in your workflow
-
-## Inputs and Outputs
-
-### Inputs
-
-- **Content**: The text or structured data to evaluate
-- **Metrics**: Custom evaluation criteria with scoring ranges
-- **Model Settings**: LLM provider and parameters
-
-### Outputs
-
-- **Content**: A summary of the evaluation
-- **Model**: The model used for evaluation
-- **Tokens**: Usage statistics
-- **Metric Scores**: Numeric scores for each defined metric
-
-## Example Usage
-
-Here's an example of how an Evaluator block might be configured for assessing customer service responses:
-
-```yaml
-# Example Evaluator Configuration
-metrics:
-  - name: Empathy
-    description: How well does the response acknowledge and address the customer's emotional state?
-    range:
-      min: 1
-      max: 5
-  - name: Solution
-    description: How effectively does the response solve the customer's problem?
-    range:
-      min: 1
-      max: 5
-  - name: Clarity
-    description: How clear and easy to understand is the response?
-    range:
-      min: 1
-      max: 5
-
-model: Anthropic/claude-3-opus
-```
-
-## Best Practices
-
-- **Use specific metric descriptions**: Clearly define what each metric measures to get more accurate evaluations
-- **Choose appropriate ranges**: Select scoring ranges that provide enough granularity without being overly complex
-- **Connect with Agent blocks**: Use Evaluator blocks to assess Agent block outputs and create feedback loops
-- **Use consistent metrics**: For comparative analysis, maintain consistent metrics across similar evaluations
-- **Combine multiple metrics**: Use several metrics to get a comprehensive evaluation

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

@@ -1,137 +0,0 @@
----
-title: Function
-description: Execute custom JavaScript or TypeScript code in your workflows
----
-
-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 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.
-
-<ThemeImage
-  lightSrc="/static/light/function-light.png"
-  darkSrc="/static/dark/function-dark.png"
-  alt="Function Block"
-  width={300}
-  height={175}
-/>
-
-## Overview
-
-The Function block brings the full power of JavaScript/TypeScript to your workflows, allowing for:
-
-- Custom data transformation and manipulation
-- Complex conditional logic
-- Mathematical calculations and algorithms
-- Integration with external libraries
-- Creation of reusable utility functions
-
-## How It Works
-
-The Function block:
-
-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
-
-## Configuration Options
-
-### Code Editor
-
-A full-featured code editor where you can write your JavaScript/TypeScript code. The editor supports:
-
-- Syntax highlighting
-- Code completion
-- Error checking
-- Multiple lines of code
-
-### Inputs
-
-Your function can access inputs from previous blocks through an `input` object. For example:
-
-```javascript
-// Access data from a previous block
-const customerName = input.customerData.name;
-const orderTotal = input.orderData.total;
-
-// 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
-};
-```
-
-## Safety and Limitations
-
-For security and performance reasons, function execution has certain limitations:
-
-- **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
-
-## Inputs and Outputs
-
-### Inputs
-
-- **Code**: Your JavaScript/TypeScript code to execute
-- **Input Data**: Values from previous blocks that can be accessed in your code
-
-### Outputs
-
-- **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)
-
-## Example Usage
-
-Here's an example of a Function block that processes customer data and calculates a loyalty score:
-
-```javascript
-// Example Function Block Code
-// Process customer data and calculate loyalty score
-
-// Access input from previous blocks
-const { purchaseHistory, accountAge, supportTickets } = input;
-
-// Calculate metrics
-const totalSpent = purchaseHistory.reduce((sum, purchase) => sum + purchase.amount, 0);
-const purchaseFrequency = purchaseHistory.length / (accountAge / 365);
-const ticketRatio = supportTickets.resolved / supportTickets.total;
-
-// Calculate loyalty score (0-100)
-const spendScore = Math.min(totalSpent / 1000 * 30, 30);
-const frequencyScore = Math.min(purchaseFrequency * 20, 40);
-const supportScore = ticketRatio * 30;
-
-const loyaltyScore = Math.round(spendScore + frequencyScore + supportScore);
-
-// Return results
-return {
-  customer: input.name,
-  loyaltyScore,
-  loyaltyTier: loyaltyScore >= 80 ? "Platinum" : loyaltyScore >= 60 ? "Gold" : loyaltyScore >= 40 ? "Silver" : "Bronze",
-  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

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

@@ -1,54 +0,0 @@
----
-title: Blocks
-description: Building blocks for your agentic 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'
-
-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.
-
-## What is a Block?
-
-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.
-
-## Primary Block Types
-
-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.
-
-<BlockTypes />
-
-## Block Connections
-
-Blocks can be connected to form a directed graph representing your workflow. Each connection represents the flow of data from one block to another:
-
-<Steps>
-  <Step>
-    <strong>Outputs to Inputs</strong>: A block's outputs can be connected to another block's
-    inputs.
-  </Step>
-  <Step>
-    <strong>Multiple Connections</strong>: A block can have multiple incoming and outgoing
-    connections.
-  </Step>
-  <Step>
-    <strong>Conditional Flows</strong>: Some blocks (like Router and Condition) can have multiple
-    output paths based on conditions.
-  </Step>
-</Steps>
-
-## Block Configuration
-
-Each block type has its own configuration options allowing you to customize its behavior.
-
-### Common Configuration Options
-
-- **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
-
-See the specific documentation for each block type to learn about its configuration options.

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

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

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

@@ -1,188 +0,0 @@
----
-title: Response
-description: Send a structured response back to API calls
----
-
-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 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.
-
-<ThemeImage
-  lightSrc="/static/light/response-light.png"
-  darkSrc="/static/dark/response-dark.png"
-  alt="Response Block"
-  width={430}
-  height={784}
-/>
-
-<Callout type="info">
-  Response blocks are terminal blocks - they mark the end of a workflow execution and cannot have further connections.
-</Callout>
-
-## Overview
-
-The Response block serves as the final output mechanism for API workflows, enabling you to:
-
-<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>
-
-## Configuration Options
-
-### Response Data
-
-The response data is the main content that will be sent back to the API caller. This should be formatted as JSON and can include:
-
-- Static values
-- Dynamic references to workflow variables using the `<variable.name>` syntax
-- Nested objects and arrays
-- Any valid JSON structure
-
-### Status Code
-
-Set the HTTP status code for the response. Common status codes include:
-
-<Tabs items={['Success (2xx)', 'Client Error (4xx)', 'Server Error (5xx)']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>200</strong>: OK - Standard success response</li>
-      <li><strong>201</strong>: Created - Resource successfully created</li>
-      <li><strong>204</strong>: No Content - Success with no response body</li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>400</strong>: Bad Request - Invalid request parameters</li>
-      <li><strong>401</strong>: Unauthorized - Authentication required</li>
-      <li><strong>404</strong>: Not Found - Resource doesn't exist</li>
-      <li><strong>422</strong>: Unprocessable Entity - Validation errors</li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>500</strong>: Internal Server Error - Server-side error</li>
-      <li><strong>502</strong>: Bad Gateway - External service error</li>
-      <li><strong>503</strong>: Service Unavailable - Service temporarily down</li>
-    </ul>
-  </Tab>
-</Tabs>
-
-<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
-  Default status code is 200 if not specified.
-</p>
-
-### Response Headers
-
-Configure additional HTTP headers to include in the response.
-
-Headers are configured as key-value pairs:
-
-| Key | Value |
-|-----|-------|
-| Content-Type | application/json |
-| Cache-Control | no-cache |
-| X-API-Version | 1.0 |
-
-## Inputs and Outputs
-
-<Tabs items={['Inputs', 'Outputs']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>data</strong> (JSON, optional): The JSON data to send in the response body
-      </li>
-      <li>
-        <strong>status</strong> (number, optional): HTTP status code (default: 200)
-      </li>
-      <li>
-        <strong>headers</strong> (JSON, optional): Additional response headers
-      </li>
-    </ul>
-  </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>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Variable References
-
-Use the `<variable.name>` syntax to dynamically insert workflow variables into your response:
-
-```json
-{
-  "user": {
-    "id": "<variable.userId>",
-    "name": "<variable.userName>",
-    "email": "<variable.userEmail>"
-  },
-  "query": "<variable.searchQuery>",
-  "results": "<variable.searchResults>",
-  "totalFound": "<variable.resultCount>",
-  "processingTime": "<variable.executionTime>ms"
-}
-```
-
-<Callout type="warning">
-  Variable names are case-sensitive and must match exactly with the variables available in your workflow.
-</Callout>
-
-## Example Usage
-
-Here's an example of how a Response block might be configured for a user search API:
-
-```yaml
-data: |
-  {
-    "success": true,
-    "data": {
-      "users": "<variable.searchResults>",
-      "pagination": {
-        "page": "<variable.currentPage>",
-        "limit": "<variable.pageSize>",
-        "total": "<variable.totalUsers>"
-      }
-    },
-    "query": {
-      "searchTerm": "<variable.searchTerm>",
-      "filters": "<variable.appliedFilters>"
-    },
-    "timestamp": "<variable.timestamp>"
-  }
-status: 200
-headers:
-  - key: X-Total-Count
-    value: <variable.totalUsers>
-  - key: Cache-Control
-    value: public, max-age=300
-```
-
-## Best Practices
-
-- **Use meaningful status codes**: Choose appropriate HTTP status codes that accurately reflect the outcome of the workflow
-- **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

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

@@ -1,120 +0,0 @@
----
-title: Router
-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 { ThemeImage } from '@/components/ui/theme-image'
-
-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.
-
-<ThemeImage
-  lightSrc="/static/light/router-light.png"
-  darkSrc="/static/dark/router-dark.png"
-  alt="Router Block"
-  width={300}
-  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:
-
-- Creating dynamic, adaptable workflows
-- Implementing complex decision trees
-- Routing user requests to specialized components
-- Building conversational systems that can handle diverse inputs
-
-## 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
-
-## Configuration Options
-
-### Content/Prompt
-
-The content or prompt that the Router will analyze to make routing decisions. This can be:
-
-- A direct user query or input
-- Output from a previous block
-- A system-generated message
-
-### Target Blocks
-
-The possible destination blocks that the Router can select from. The Router will automatically detect connected blocks, but you can also:
-
-- Customize the descriptions of target blocks to improve routing accuracy
-- Specify routing criteria for each target block
-- Exclude certain blocks from being considered as routing targets
-
-### Model Selection
-
-Choose an LLM provider 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
-
-Select a model with strong reasoning capabilities 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
-
-### Inputs
-
-- **Content/Prompt**: The text to analyze for routing decisions
-- **Target Blocks**: Connected blocks that are potential routing destinations
-- **Model Settings**: LLM provider and parameters
-
-### Outputs
-
-- **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
-
-## Example Usage
-
-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
-```
-
-In this example, the Router might be connected to:
-
-- A product support block
-- A billing inquiries block
-- A technical support block
-- A general inquiries block
-
-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

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

@@ -1,231 +0,0 @@
----
-title: Workflow
-description: Execute other workflows as reusable components within your current workflow
----
-
-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 Workflow block allows you to execute other workflows as reusable components within your current workflow. This powerful feature enables modular design, code reuse, and the creation of complex nested workflows that can be composed from smaller, focused workflows.
-
-<ThemeImage
-  lightSrc="/static/light/workflow-light.png"
-  darkSrc="/static/dark/workflow-dark.png"
-  alt="Workflow Block"
-  width={300}
-  height={175}
-/>
-
-<Callout type="info">
-  Workflow blocks enable modular design by allowing you to compose complex workflows from smaller, reusable components.
-</Callout>
-
-## Overview
-
-The Workflow block serves as a bridge between workflows, enabling you to:
-
-<Steps>
-  <Step>
-    <strong>Reuse existing workflows</strong>: Execute previously created workflows as components within new workflows
-  </Step>
-  <Step>
-    <strong>Create modular designs</strong>: Break down complex processes into smaller, manageable workflows
-  </Step>
-  <Step>
-    <strong>Maintain separation of concerns</strong>: Keep different business logic isolated in separate workflows
-  </Step>
-  <Step>
-    <strong>Enable team collaboration</strong>: Share and reuse workflows across different projects and team members
-  </Step>
-</Steps>
-
-## How It Works
-
-The Workflow block:
-
-1. Takes a reference to another workflow in your workspace
-2. Passes input data from the current workflow to the child workflow
-3. Executes the child workflow in an isolated context
-4. Returns the results back to the parent workflow for further processing
-
-## Configuration Options
-
-### Workflow Selection
-
-Choose which workflow to execute from a dropdown list of available workflows in your workspace. The list includes:
-
-- All workflows you have access to in the current workspace
-- Workflows shared with you by other team members
-- Both enabled and disabled workflows (though only enabled workflows can be executed)
-
-### Input Data
-
-Define the data to pass to the child workflow:
-
-- **Single Variable Input**: Select a variable or block output to pass to the child workflow
-- **Variable References**: Use `<variable.name>` to reference workflow variables
-- **Block References**: Use `<blockName.response.field>` to reference outputs from previous blocks
-- **Automatic Mapping**: The selected data is automatically available as `start.response.input` in 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
-
-- `<variable.customerData>` - Pass a workflow variable
-- `<dataProcessor.response.result>` - Pass the result from a previous block
-- `<start.response.input>` - Pass the original workflow input
-- `<apiCall.response.data.user>` - Pass a specific field from an API response
-
-### Execution Context
-
-The child workflow executes with:
-
-- Its own isolated execution context
-- Access to the same workspace resources (API keys, environment variables)
-- Proper workspace membership and permission checks
-- Independent logging and monitoring
-
-## Safety and Limitations
-
-To prevent infinite recursion and ensure system stability, the Workflow block includes several safety mechanisms:
-
-<Callout type="warning">
-  **Cycle Detection**: The system automatically detects and prevents circular dependencies between workflows to avoid infinite loops.
-</Callout>
-
-- **Maximum Depth Limit**: Nested workflows are limited to a maximum depth of 10 levels
-- **Cycle Detection**: Automatic detection and prevention of circular workflow dependencies
-- **Timeout Protection**: Child workflows inherit timeout settings to prevent indefinite execution
-- **Resource Limits**: Memory and execution time limits apply to prevent resource exhaustion
-
-## Inputs and Outputs
-
-<Tabs items={['Inputs', 'Outputs']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Workflow ID</strong>: The identifier of the 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.response.field>`)
-      </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
-      </li>
-      <li>
-        <strong>Child Workflow Name</strong>: The name of the executed child workflow
-      </li>
-      <li>
-        <strong>Success Status</strong>: Boolean indicating whether the child workflow completed successfully
-      </li>
-      <li>
-        <strong>Error Information</strong>: Details about any errors that occurred during execution
-      </li>
-      <li>
-        <strong>Execution Metadata</strong>: Information about execution time, resource usage, and performance
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Usage
-
-Here's an example of how a Workflow block might be used to create a modular customer onboarding process:
-
-### 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.response.result>"
-  
-  - type: workflow
-    name: "Send Welcome Email"
-    workflowId: "welcome-email-workflow"
-    input: "<Setup Customer Account.response.result.accountDetails>"
-```
-
-### Child Workflow: Customer Validation
-```yaml
-# Reusable customer validation workflow
-# Access the input data using: start.response.input
-blocks:
-  - type: function
-    name: "Validate Email"
-    code: |
-      const customerData = start.response.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.response.input>"
-```
-
-### Variable Reference Examples
-
-```yaml
-# Using workflow variables
-input: "<variable.customerInfo>"
-
-# Using block outputs
-input: "<dataProcessor.response.cleanedData>"
-
-# Using nested object properties
-input: "<apiCall.response.data.user.profile>"
-
-# Using array elements (if supported by the resolver)
-input: "<listProcessor.response.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> 

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

@@ -1,190 +0,0 @@
----
-title: Accessing Connected Data
-description: Techniques for accessing and manipulating data from connected blocks
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { File, Files, Folder } from 'fumadocs-ui/components/files'
-
-Once blocks are connected, you can access data from source blocks in destination blocks using connection tags and various data access techniques.
-
-## Basic Data Access
-
-The simplest way to access data is through direct references using connection tags:
-
-<Files>
-  <File name="Simple Property" annotation="<block.content>" />
-  <File name="Nested Property" annotation="<block.tokens.total>" />
-  <File name="Array Element" annotation="<block.items[0].name>" />
-  <File name="Complex Path" annotation="<block.data.users[2].profile.email>" />
-</Files>
-
-## Advanced Data Access Techniques
-
-### Array Access
-
-You can access array elements using square bracket notation:
-
-```javascript
-// Access the first item in an array
-<block.items[0]>
-
-// Access a specific property of an array item
-<block.items[2].name>
-
-// Access the last item in an array (in Function blocks)
-const items = input.block.items;
-const lastItem = items[items.length - 1];
-```
-
-### Object Property Access
-
-Access object properties using dot notation:
-
-```javascript
-// Access a simple property
-<block.content>
-
-// Access a nested property
-<block.data.user.profile.name>
-
-// Access a property with special characters (in Function blocks)
-const data = input.block.data;
-const specialProp = data['property-with-dashes'];
-```
-
-### Dynamic References
-
-Connection references are evaluated at runtime, allowing for dynamic data flow through your workflow:
-
-```javascript
-// In a Function block, you can access connected data
-const userName = input.userBlock.name;
-const orderTotal = input.apiBlock.body.order.total;
-
-// Process the data
-const discount = orderTotal > 100 ? 0.1 : 0;
-const finalPrice = orderTotal * (1 - discount);
-
-// Return the result
-return {
-  userName,
-  originalTotal: orderTotal,
-  discount: discount * 100 + '%',
-  finalPrice
-};
-```
-
-## Data Transformation
-
-### Using Function Blocks
-
-Function blocks are the most powerful way to transform data between connections:
-
-```javascript
-// Example: Transform API response data
-const apiResponse = input.apiBlock.data;
-const transformedData = {
-  users: apiResponse.results.map(user => ({
-    id: user.id,
-    fullName: `${user.firstName} ${user.lastName}`,
-    email: user.email.toLowerCase(),
-    isActive: user.status === 'active'
-  })),
-  totalCount: apiResponse.count,
-  timestamp: new Date().toISOString()
-};
-
-return transformedData;
-```
-
-### String Interpolation
-
-You can combine connection tags with static text:
-
-```
-Hello, <userBlock.name>! Your order #<orderBlock.id> has been processed.
-```
-
-### Conditional Content
-
-In Function blocks, you can create conditional content based on connected data:
-
-```javascript
-const user = input.userBlock;
-const orderTotal = input.orderBlock.total;
-
-let message = `Thank you for your order, ${user.name}!`;
-
-if (orderTotal > 100) {
-  message += " You've qualified for free shipping!";
-} else {
-  message += ` Add $${(100 - orderTotal).toFixed(2)} more to qualify for free shipping.`;
-}
-
-return { message };
-```
-
-## Handling Missing Data
-
-It's important to handle cases where connected data might be missing or null:
-
-<Callout type="warning">
-  Always validate connected data before using it, especially when accessing nested properties or
-  array elements.
-</Callout>
-
-### Default Values
-
-In Function blocks, you can provide default values for missing data:
-
-```javascript
-const userName = input.userBlock?.name || 'Guest'
-const items = input.orderBlock?.items || []
-const total = input.orderBlock?.total ?? 0
-```
-
-### Conditional Checks
-
-Check if data exists before accessing nested properties:
-
-```javascript
-let userEmail = 'No email provided'
-if (input.userBlock && input.userBlock.contact && input.userBlock.contact.email) {
-  userEmail = input.userBlock.contact.email
-}
-```
-
-### Optional Chaining
-
-In Function blocks, use optional chaining to safely access nested properties:
-
-```javascript
-const userCity = input.userBlock?.address?.city
-const firstItemName = input.orderBlock?.items?.[0]?.name
-```
-
-## Debugging Connection Data
-
-When troubleshooting connection issues, these techniques can help:
-
-1. **Log Data**: In Function blocks, use `console.log()` to inspect connected data
-2. **Return Full Objects**: Return the full input object to see all available data
-3. **Check Types**: Verify the data types of connected values
-4. **Validate Paths**: Ensure you're using the correct path to access nested data
-
-```javascript
-// Example debugging function
-function debugConnections() {
-  console.log('All inputs:', input)
-  console.log('User data type:', typeof input.userBlock)
-  console.log('Order items:', input.orderBlock?.items)
-
-  return {
-    debug: true,
-    allInputs: input,
-    userExists: !!input.userBlock,
-    orderItemCount: input.orderBlock?.items?.length || 0,
-  }
-}
-```

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

@@ -1,76 +0,0 @@
----
-title: Connection Basics
-description: Learn how connections work in Sim Studio
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-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.
-
-<Callout type="info">
-  Each connection represents a directed relationship where data flows from a source block's output
-  to a destination block's input.
-</Callout>
-
-### Creating Connections
-
-<Steps>
-  <Step>
-    <strong>Select Source Block</strong>: Click on the output port of the block you want to connect
-    from
-  </Step>
-  <Step>
-    <strong>Draw Connection</strong>: Drag to the input port of the destination block
-  </Step>
-  <Step>
-    <strong>Confirm Connection</strong>: Release to create the connection
-  </Step>
-  <Step>
-    <strong>Configure (Optional)</strong>: Some connections may require additional configuration
-  </Step>
-</Steps>
-
-### Connection Flow
-
-The flow of data through connections follows these principles:
-
-1. **Directional Flow**: Data always flows from outputs to inputs
-2. **Execution Order**: Blocks execute in order based on their connections
-3. **Data Transformation**: Data may be transformed as it passes between blocks
-4. **Conditional Paths**: Some blocks (like Router and Condition) can direct flow to different paths
-
-### Connection Visualization
-
-Connections are visually represented in the workflow editor:
-
-- **Solid Lines**: Active connections that will pass data
-- **Animated Flow**: During execution, data flow is visualized along connections
-- **Color Coding**: Different connection types may have different colors
-- **Connection Tags**: Visual indicators showing what data is available
-
-### Managing Connections
-
-You can manage your connections in several ways:
-
-- **Delete**: Click on a connection and press Delete or use the context menu
-- **Reroute**: Drag a connection to change its path
-- **Inspect**: Click on a connection to see details about the data being passed
-- **Disable**: Temporarily disable a connection without deleting it
-
-<Callout type="warning">
-  Deleting a connection will immediately stop data flow between the blocks. Make sure this is
-  intended before removing connections.
-</Callout>
-
-## Connection Compatibility
-
-Not all blocks can be connected to each other. Compatibility depends on:
-
-1. **Data Type Compatibility**: The output type must be compatible with the input type
-2. **Block Restrictions**: Some blocks may have restrictions on what they can connect to
-3. **Workflow Logic**: Connections must make logical sense in the context of your workflow
-
-The editor will indicate when connections are invalid or incompatible.

apps/docs/content/docs/connections/best-practices.mdx

@@ -1,208 +0,0 @@
----
-title: Connection Best Practices
-description: Recommended patterns for effective connection management
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-
-## Workflow Organization
-
-### Organize Your Connections
-
-Keep your workflow clean and understandable by organizing connections logically:
-
-- **Minimize crossing connections** when possible to reduce visual complexity
-- **Group related blocks together** to make data flow more intuitive
-- **Use consistent flow direction** (typically left-to-right or top-to-bottom)
-- **Label complex connections** with descriptive names
-
-<Callout type="info">
-  A well-organized workflow is easier to understand, debug, and maintain. Take time to arrange your
-  blocks and connections in a logical manner.
-</Callout>
-
-### Connection Naming Conventions
-
-When working with multiple connections, consistent naming helps maintain clarity:
-
-<Steps>
-  <Step>
-    <strong>Use descriptive block names</strong>: Name blocks based on their function (e.g.,
-    "UserDataFetcher", "ResponseGenerator")
-  </Step>
-  <Step>
-    <strong>Be specific with connection references</strong>: Use clear variable names when
-    referencing connections in code
-  </Step>
-  <Step>
-    <strong>Document complex connections</strong>: Add comments explaining non-obvious data
-    transformations
-  </Step>
-</Steps>
-
-## Data Validation
-
-### Validate Data Flow
-
-Ensure that the data being passed between blocks is compatible:
-
-- **Check that required fields are available** in the source block
-- **Verify data types match expectations** before using them
-- **Use Function blocks to transform data** when necessary
-- **Handle missing or null values** with default values or conditional logic
-
-```javascript
-// Example: Validating and transforming data in a Function block
-function processUserData() {
-  // Validate required fields
-  if (!input.userBlock || !input.userBlock.id) {
-    return { error: 'Missing user data', valid: false }
-  }
-
-  // Transform and validate data types
-  const userId = String(input.userBlock.id)
-  const userName = input.userBlock.name || 'Unknown User'
-  const userScore = Number(input.userBlock.score) || 0
-
-  return {
-    valid: true,
-    user: {
-      id: userId,
-      name: userName,
-      score: userScore,
-      isHighScore: userScore > 100,
-    },
-  }
-}
-```
-
-## Documentation
-
-### Document Connection Purpose
-
-Add comments or descriptions to clarify the purpose of connections, especially in complex workflows:
-
-- **What data is being passed**: Document the key fields and their purpose
-- **Why this connection exists**: Explain the relationship between blocks
-- **Any transformations or conditions applied**: Note any data processing that occurs
-
-```javascript
-// Example: Documenting connection purpose in a Function block
-/*
- * This function processes user data from the UserFetcher block
- * and order history from the OrderHistory block to generate
- * personalized product recommendations.
- *
- * Input:
- * - userBlock: User profile data (id, preferences, history)
- * - orderBlock: Recent order history (items, dates, amounts)
- *
- * Output:
- * - recommendations: Array of recommended product IDs
- * - userSegment: Calculated user segment for marketing
- * - conversionProbability: Estimated likelihood of purchase
- */
-function generateRecommendations() {
-  // Implementation...
-}
-```
-
-## Testing and Debugging
-
-### Test Connection References
-
-Verify that connection references work as expected:
-
-- **Test with different input values** to ensure robustness
-- **Check edge cases** (empty values, large datasets, special characters)
-- **Ensure error handling for missing or invalid data**
-- **Use console logging in Function blocks** to debug connection issues
-
-```javascript
-// Example: Testing connection references with edge cases
-function testConnections() {
-  console.log('Testing connections...')
-
-  // Log all inputs for debugging
-  console.log('All inputs:', JSON.stringify(input, null, 2))
-
-  // Test for missing data
-  const hasUserData = !!input.userBlock
-  console.log('Has user data:', hasUserData)
-
-  // Test edge cases
-  const items = input.orderBlock?.items || []
-  console.log('Item count:', items.length)
-  console.log('Empty items test:', items.length === 0 ? 'Passed' : 'Failed')
-
-  // Return test results
-  return {
-    tests: {
-      hasUserData,
-      hasItems: items.length > 0,
-      hasLargeOrder: items.length > 10,
-    },
-  }
-}
-```
-
-## Performance Considerations
-
-### Optimize Data Flow
-
-Keep your workflows efficient by optimizing how data flows through connections:
-
-- **Pass only necessary data** between blocks to reduce memory usage
-- **Use Function blocks to filter large datasets** before passing them on
-- **Consider caching results** for expensive operations
-- **Break complex workflows into smaller, reusable components**
-
-```javascript
-// Example: Optimizing data flow by filtering
-function optimizeUserData() {
-  const userData = input.userBlock
-
-  // Only pass necessary fields to downstream blocks
-  return {
-    id: userData.id,
-    name: userData.name,
-    email: userData.email,
-    // Filter out unnecessary profile data, history, etc.
-  }
-}
-```
-
-## Security Best Practices
-
-### Secure Sensitive Data
-
-Protect sensitive information when using connections:
-
-- **Never expose API keys or credentials** in connection data
-- **Sanitize user input** before processing it
-- **Redact sensitive information** when logging connection data
-- **Use secure connections** for external API calls
-
-<Callout type="warning">
-  Be careful when logging connection data that might contain sensitive information. Always redact or
-  mask sensitive fields like passwords, API keys, or personal information.
-</Callout>
-
-## Advanced Patterns
-
-### Conditional Connections
-
-Use Condition blocks to create dynamic workflows:
-
-- **Route data based on content** to different processing paths
-- **Implement fallback paths** for error handling
-- **Create decision trees** for complex business logic
-
-### Feedback Loops
-
-Create more sophisticated workflows with feedback connections:
-
-- **Implement iterative processing** by connecting later blocks back to earlier ones
-- **Use Memory blocks** to store state between iterations
-- **Set termination conditions** to prevent infinite loops

apps/docs/content/docs/connections/meta.json

@@ -1,4 +0,0 @@
-{
-  "title": "Connections",
-  "pages": ["basics", "tags", "data-structure", "accessing-data", "best-practices"]
-}

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

@@ -0,0 +1,306 @@
+---
+title: Agent
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
+
+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.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/agent.png"
+    alt="Agent Block Configuration"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+## Overview
+
+The Agent block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Process natural language</strong>: Analyze user input and generate contextual responses
+  </Step>
+  <Step>
+    <strong>Execute AI-powered tasks</strong>: Perform content analysis, generation, and decision-making
+  </Step>
+  <Step>
+    <strong>Call external tools</strong>: Access APIs, databases, and services during processing
+  </Step>
+  <Step>
+    <strong>Generate structured output</strong>: Return JSON data that matches your schema requirements
+  </Step>
+</Steps> 
+
+## Configuration Options
+
+### System Prompt
+
+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.
+Always provide clear explanations and cite sources when possible.
+When responding to questions about investments, include risk disclaimers.
+```
+
+### User Prompt
+
+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:
+
+- **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
+
+The Agent block supports multiple LLM providers through a unified inference interface. Available models include:
+
+**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 src="models.mp4" width={500} height={350} />
+</div>
+
+### Temperature
+
+Control the creativity and randomness of responses:
+
+<Tabs items={['Low (0-0.3)', 'Medium (0.3-0.7)', 'High (0.7-2.0)']}>
+  <Tab>
+    More deterministic, focused responses. Best for factual tasks, customer support, and
+    situations where accuracy is critical.
+  </Tab>
+  <Tab>
+    Balanced creativity and focus. Suitable for general purpose applications that require both
+    accuracy and some creativity.
+  </Tab>
+  <Tab>
+    More creative, varied responses. Ideal for creative writing, brainstorming, and generating
+    diverse ideas.
+  </Tab>
+</Tabs>
+
+<div className="mt-4 text-sm text-gray-600 dark:text-gray-400">
+  The temperature range (0-1 or 0-2) varies depending on the selected model.
+</div>
+
+### API Key
+
+Your API key for the selected LLM provider. This is securely stored and used for authentication.
+
+### Tools
+
+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.
+
+**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
+
+<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
+  <Video src="tools.mp4" width={500} height={350} />
+</div>
+
+**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
+
+**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
+
+<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
+  <Video src="granular-tool-control.mp4" width={500} height={350} />
+</div>
+
+### Response Format
+
+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 + Agent: Conversation History
+
+Use a `Memory` block with a consistent `id` (for example, `chat`) to persist messages between runs, and include that history in the Agent's prompt.
+
+- Add the user's message before the Agent
+- Read the conversation history for context
+- Append the Agent's reply after it runs
+
+```yaml
+# 1) Add latest user message
+- Memory (operation: add)
+  id: chat
+  role: user
+  content: {{input}}
+
+# 2) Load conversation history
+- Memory (operation: get)
+  id: chat
+
+# 3) Run the agent with prior messages available
+- Agent
+  System Prompt: ...
+  User Prompt: |
+    Use the conversation so far:
+    {{memory_get.memories}}
+    Current user message: {{input}}
+
+# 4) Store the agent reply
+- Memory (operation: add)
+  id: chat
+  role: assistant
+  content: {{agent.content}}
+```
+
+See the `Memory` block reference for details: [/tools/memory](/tools/memory).
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>System Prompt</strong>: Instructions defining agent behavior and role
+      </li>
+      <li>
+        <strong>User Prompt</strong>: Input text or data to process
+      </li>
+      <li>
+        <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>agent.content</strong>: Agent's response text or structured data
+      </li>
+      <li>
+        <strong>agent.tokens</strong>: Token usage statistics object
+      </li>
+      <li>
+        <strong>agent.tool_calls</strong>: Array of tool execution details
+      </li>
+      <li>
+        <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>Metadata</strong>: Usage statistics and execution details
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the agent
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Example Use Cases
+
+### Customer Support Automation
+
+<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 a support ticket via the API block</li>
+    <li>Agent checks orders/subscriptions in Postgres and searches the knowledge base for guidance</li>
+    <li>If escalation is needed, the Agent creates a Linear issue with relevant context</li>
+    <li>Agent drafts a clear email reply</li>
+    <li>Gmail sends the reply to the customer</li>
+    <li>Conversation is saved to Memory to maintain history for future messages</li>
+  </ol>
+</div>
+
+### 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
+- **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/en/blocks/api.mdx

@@ -0,0 +1,232 @@
+---
+title: API
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+The API block enables you to connect your workflow to external services through API endpoints using HTTP requests. It supports various methods like GET, POST, PUT, DELETE, and PATCH, allowing you to interact with virtually any API endpoint.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/api.png"
+    alt="API Block"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+## Overview
+
+The API block enables you to:
+
+<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>
+
+## How It Works
+
+The API block processes HTTP requests through a structured approach:
+
+1. **Configure Request** - Set URL, method, headers, and body parameters
+2. **Execute Request** - Send HTTP request to the specified endpoint
+3. **Process Response** - Handle response data, status codes, and headers
+4. **Error Handling** - Manage timeouts, retries, and error conditions
+
+## Configuration Options
+
+### URL
+
+The endpoint URL for the API request. This can be:
+
+- A static URL entered directly in the block
+- A dynamic URL connected from another block's output
+- A URL with path parameters
+
+### Method
+
+Select the HTTP method for your request:
+
+- **GET**: Retrieve data from the server
+- **POST**: Send data to the server to create a resource
+- **PUT**: Update an existing resource on the server
+- **DELETE**: Remove a resource from the server
+- **PATCH**: Partially update an existing resource
+
+### Query Parameters
+
+Define key-value pairs that will be appended to the URL as query parameters. For example:
+
+```
+Key: apiKey
+Value: your_api_key_here
+
+Key: limit
+Value: 10
+```
+
+These would be added to the URL as `?apiKey=your_api_key_here&limit=10`.
+
+### Headers
+
+Configure HTTP headers for your request. Common headers include:
+
+```
+Key: Content-Type
+Value: application/json
+
+Key: Authorization
+Value: Bearer your_token_here
+```
+
+### Request Body
+
+For methods that support a request body (POST, PUT, PATCH), you can define the data to send. The body can be:
+
+- JSON data entered directly in the block
+- 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
+
+<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>
+
+## Example Use Cases
+
+### Fetch User Profile Data
+
+<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>
+
+### 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>Supabase block updates order status in database</li>
+  </ol>
+</div>
+
+## Best Practices
+
+- **Use environment variables for sensitive data**: Don't hardcode API keys or credentials
+- **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

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

@@ -0,0 +1,237 @@
+---
+title: Condition
+---
+
+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 { Image } from '@/components/ui/image'
+
+The Condition block allows you to branch your workflow execution path based on boolean expressions, enabling you to create dynamic, responsive workflows with different execution paths. It evaluates conditions and routes the workflow accordingly, letting you control execution flow based on data or logic without requiring an LLM.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/condition.png"
+    alt="Condition Block"
+    width={500}
+    height={350}
+    className="my-6"
+  />
+</div>
+
+<Callout>
+  Condition blocks enable deterministic decision-making without requiring an LLM, making them ideal
+  for straightforward branching logic.
+</Callout>
+
+## Overview
+
+The Condition block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Create branching logic</strong>: Route workflows based on boolean expressions
+  </Step>
+  <Step>
+    <strong>Make data-driven decisions</strong>: Evaluate conditions using previous block outputs
+  </Step>
+  <Step>
+    <strong>Handle multiple scenarios</strong>: Define multiple conditions with different paths
+  </Step>
+  <Step>
+    <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
+
+Define one or more conditions that will be evaluated. Each condition includes:
+
+- **Expression**: A JavaScript/TypeScript expression that evaluates to true or false
+- **Path**: The destination block to route to if the condition is true
+- **Description**: Optional explanation of what the condition checks
+
+You can create multiple conditions that are evaluated in order, with the first matching condition determining the execution path.
+
+### Condition Expression Format
+
+Conditions use JavaScript syntax and can reference input values from previous blocks.
+
+<Tabs items={['Score Threshold', 'Text Analysis', 'Multiple Conditions']}>
+  <Tab>
+    ```javascript
+    // Check if a score is above a threshold
+    <agent.score> > 75
+    ```
+  </Tab>
+  <Tab>
+    ```javascript
+    // Check if a text contains specific keywords
+    <agent.text>.includes('urgent') || <agent.text>.includes('emergency')
+    ```
+  </Tab>
+  <Tab>
+    ```javascript
+    // Check multiple conditions
+    <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={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Conditions</strong>: Array of boolean expressions to evaluate
+      </li>
+      <li>
+        <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>condition.result</strong>: Boolean result of condition evaluation
+      </li>
+      <li>
+        <strong>condition.matched_condition</strong>: ID of the matched condition
+      </li>
+      <li>
+        <strong>condition.content</strong>: Description of evaluation result
+      </li>
+      <li>
+        <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 Use Cases
+
+### Customer Support Routing
+
+<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>
+
+### Content Moderation
+
+<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**: 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/en/blocks/evaluator.mdx

@@ -0,0 +1,199 @@
+---
+title: Evaluator
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
+
+The Evaluator block uses AI to score and assess content quality using customizable evaluation metrics that you define. Perfect for quality control, A/B testing, and ensuring your AI outputs meet specific standards.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/evaluator.png"
+    alt="Evaluator Block Configuration"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+## Overview
+
+The Evaluator block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Score Content Quality</strong>: Use AI to evaluate content against custom metrics with numeric scores
+  </Step>
+  <Step>
+    <strong>Define Custom Metrics</strong>: Create specific evaluation criteria tailored to your use case  
+  </Step>
+  <Step>
+    <strong>Automate Quality Control</strong>: Build workflows that automatically assess and filter content
+  </Step>
+  <Step>
+    <strong>Track Performance</strong>: Monitor improvements and consistency over time with objective scoring
+  </Step>
+</Steps>
+
+## How It Works
+
+The Evaluator block processes content through AI-powered assessment:
+
+1. **Receive Content** - Takes input content from previous blocks in your workflow
+2. **Apply Metrics** - Evaluates content against your defined custom metrics  
+3. **Generate Scores** - AI model assigns numeric scores for each metric
+4. **Provide Summary** - Returns detailed evaluation with scores and explanations
+
+## Configuration Options
+
+### Evaluation Metrics
+
+Define custom metrics to evaluate content against. Each metric includes:
+
+- **Name**: A short identifier for the metric
+- **Description**: A detailed explanation of what the metric measures
+- **Range**: The numeric range for scoring (e.g., 1-5, 0-10)
+
+Example metrics:
+
+```
+Accuracy (1-5): How factually accurate is the content?
+Clarity (1-5): How clear and understandable is the content?
+Relevance (1-5): How relevant is the content to the original query?
+```
+
+### Content
+
+The content to be evaluated. This can be:
+
+- Directly provided in the block configuration
+- Connected from another block's output (typically an Agent block)
+- Dynamically generated during workflow execution
+
+### Model Selection
+
+Choose an AI model to perform the evaluation:
+
+**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
+
+<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
+  <Video src="models.mp4" width={500} height={350} />
+</div>
+
+**Recommendation**: Use models with strong reasoning capabilities like GPT-4o or Claude 3.7 Sonnet for more accurate evaluations.
+
+### API Key
+
+Your API key for the selected LLM provider. This is securely stored and used for authentication.
+
+## How It Works
+
+1. The Evaluator block takes the provided content and your custom metrics
+2. It generates a specialized prompt that instructs the LLM to evaluate the content
+3. The prompt includes clear guidelines on how to score each metric
+4. The LLM evaluates the content and returns numeric scores for each metric
+5. The Evaluator block formats these scores as structured output for use in your workflow
+
+## Example Use Cases
+
+### Content Quality Assessment
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Evaluate blog post quality before publication</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Agent block generates blog post content</li>
+    <li>Evaluator assesses accuracy, readability, and engagement</li>
+    <li>Condition block checks if scores meet minimum thresholds</li>
+    <li>High scores → Publish, Low scores → Revise and retry</li>
+  </ol>
+</div>
+
+### A/B Testing Content
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Compare multiple AI-generated responses</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Parallel block generates multiple response variations</li>
+    <li>Evaluator scores each variation on clarity and relevance</li>
+    <li>Function block selects highest-scoring response</li>
+    <li>Response block returns the best result</li>
+  </ol>
+</div>
+
+### Customer Support Quality Control
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Ensure support responses meet quality standards</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Support agent generates response to customer inquiry</li>
+    <li>Evaluator scores helpfulness, empathy, and accuracy</li>
+    <li>Scores logged for training and performance monitoring</li>
+    <li>Low scores trigger human review process</li>
+  </ol>
+</div>
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Content</strong>: The text or structured data to evaluate
+      </li>
+      <li>
+        <strong>Evaluation Metrics</strong>: Custom criteria with scoring ranges
+      </li>
+      <li>
+        <strong>Model</strong>: AI model for evaluation 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>evaluator.content</strong>: Summary of the evaluation
+      </li>
+      <li>
+        <strong>evaluator.model</strong>: Model used for evaluation
+      </li>
+      <li>
+        <strong>evaluator.tokens</strong>: Token usage statistics
+      </li>
+      <li>
+        <strong>evaluator.cost</strong>: Cost summary for the evaluation call
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Metric Scores</strong>: Numeric scores for each defined metric
+      </li>
+      <li>
+        <strong>Evaluation Summary</strong>: Detailed assessment with explanations
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the evaluator
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Best Practices
+
+- **Use specific metric descriptions**: Clearly define what each metric measures to get more accurate evaluations
+- **Choose appropriate ranges**: Select scoring ranges that provide enough granularity without being overly complex
+- **Connect with Agent blocks**: Use Evaluator blocks to assess Agent block outputs and create feedback loops
+- **Use consistent metrics**: For comparative analysis, maintain consistent metrics across similar evaluations
+- **Combine multiple metrics**: Use several metrics to get a comprehensive evaluation

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

@@ -0,0 +1,156 @@
+---
+title: Function
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+The Function block lets you execute custom JavaScript or TypeScript code in your workflows. Use it to transform data, perform calculations, or implement custom logic that isn't available in other blocks.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/function.png"
+    alt="Function Block with Code Editor"
+    width={500}
+    height={350}
+    className="my-6"
+  />
+</div>
+
+## Overview
+
+The Function block enables you to:
+
+<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 runs your code in a secure, isolated environment:
+
+1. **Receive Input**: Access data from previous blocks via the `input` object
+2. **Execute Code**: Run your JavaScript/Python code 
+3. **Return Results**: Use `return` to pass data to the next block
+4. **Handle Errors**: Built-in error handling and logging
+
+## Remote Execution (E2B)
+
+  - **Languages**: Run JavaScript and Python in an isolated E2B sandbox.
+  - **How to enable**: Toggle “Remote Code Execution” in the Function block.
+  - **When to use**: Heavier logic, external libraries, or Python-specific code.
+  - **Performance**: Slower than local JS due to sandbox startup and network overhead.
+  - **Notes**: Requires `E2B_API_KEY` if running locally. For lowest latency, use natively local JS (Fast Mode).
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Code</strong>: Your JavaScript/Python 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>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Example Use Cases
+
+### Data Processing Pipeline
+
+<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>
+
+### Business Logic Implementation
+
+<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>
+
+### 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
+const { purchaseHistory, accountAge, supportTickets } = <agent>;
+
+// Calculate metrics
+const totalSpent = purchaseHistory.reduce((sum, purchase) => sum + purchase.amount, 0);
+const purchaseFrequency = purchaseHistory.length / (accountAge / 365);
+const ticketRatio = supportTickets.resolved / supportTickets.total;
+
+// Calculate loyalty score (0-100)
+const spendScore = Math.min(totalSpent / 1000 * 30, 30);
+const frequencyScore = Math.min(purchaseFrequency * 20, 40);
+const supportScore = ticketRatio * 30;
+
+const loyaltyScore = Math.round(spendScore + frequencyScore + supportScore);
+
+return {
+  customer: <agent.name>,
+  loyaltyScore,
+  loyaltyTier: loyaltyScore >= 80 ? "Platinum" : loyaltyScore >= 60 ? "Gold" : "Silver",
+  metrics: { spendScore, frequencyScore, supportScore }
+};
+```
+
+## Best Practices
+
+- **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/en/blocks/index.mdx

@@ -0,0 +1,126 @@
+---
+title: Blocks
+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 { Video } from '@/components/ui/video'
+
+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.
+
+<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
+  <Video src="connections.mp4" width={700} height={450} />
+</div>
+
+## Core Block Types
+
+Sim provides seven core block types that handle the essential functions of AI workflows:
+
+### 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
+
+## How Blocks Work
+
+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>Receive Input</strong>: Block receives data from connected blocks or user input
+  </Step>
+  <Step>
+    <strong>Process</strong>: Block processes the input according to its configuration
+  </Step>
+  <Step>
+    <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" width={700} height={450} />
+</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 specific configuration options:
+
+**All Blocks**:
+- Input/output connections
+- Error handling behavior
+- Execution timeout settings
+
+**AI Blocks** (Agent, Router, Evaluator):
+- Model selection (OpenAI, Anthropic, Google, local)
+- API keys and authentication
+- Temperature and other model parameters
+- System prompts and instructions
+
+**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/en/blocks/loop.mdx

@@ -0,0 +1,207 @@
+---
+title: Loop
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+The Loop block is a container block in Sim that allows you to create iterative workflows by executing a group of blocks repeatedly. Loops enable iterative processing in your workflows.
+
+The Loop block supports two types of iteration:
+
+<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>
+  <Step>
+    <strong>Sequential processing</strong>: Handle data transformation in ordered iterations
+  </Step>
+  <Step>
+    <strong>Aggregate results</strong>: Collect outputs from all loop iterations
+  </Step>
+</Steps>
+
+## How It Works
+
+The Loop block executes contained blocks through sequential iteration:
+
+1. **Initialize Loop** - Set up iteration parameters (count or collection)
+2. **Execute Iteration** - Run contained blocks for current iteration
+3. **Collect Results** - Store output from each iteration
+4. **Continue or Complete** - Move to next iteration or finish loop
+
+## Configuration Options
+
+### Loop Type
+
+Choose between two types of loops:
+
+<Tabs items={['For Loop', 'ForEach Loop']}>
+  <Tab>
+    **For Loop (Iterations)** - A numeric loop that executes a fixed number of times:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/loop-1.png"
+        alt="For Loop with iterations"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    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>
+    **ForEach Loop (Collection)** - A collection-based loop that iterates over each item in an array or object:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/loop-2.png"
+        alt="ForEach Loop with collection"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    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/en/blocks/parallel.mdx

@@ -0,0 +1,227 @@
+---
+title: Parallel
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+The Parallel block is a container block in Sim that allows you to execute multiple instances of blocks concurrently for faster workflow processing.
+
+The Parallel block supports two types of concurrent execution:
+
+<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>
+    **Count-based Parallel** - Execute a fixed number of parallel instances:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/parallel-1.png"
+        alt="Count-based parallel execution"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    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>
+    **Collection-based Parallel** - Distribute a collection across parallel instances:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/parallel-2.png"
+        alt="Collection-based parallel execution"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    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>Collection-based parallel over a list of model IDs (e.g., ["gpt-4o", "claude-3.7-sonnet", "gemini-2.5-pro"])</li>
+    <li>Inside parallel: Agent's model is set to the current item from the collection</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/en/blocks/response.mdx

@@ -0,0 +1,247 @@
+---
+title: Response
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+The Response block is the final step in your workflow that formats and sends a structured response back to API calls. It's like the "return" statement for your entire workflow—it packages up results and sends them back.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/response.png"
+    alt="Response Block Configuration"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+<Callout type="info">
+  Response blocks are terminal blocks - they end the workflow execution and cannot connect to other blocks.
+</Callout>
+
+## Overview
+
+The Response block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Format API Responses</strong>: Structure workflow results into proper HTTP responses
+  </Step>
+  <Step>
+    <strong>Set Status Codes</strong>: Configure appropriate HTTP status codes based on workflow outcomes
+  </Step>
+  <Step>
+    <strong>Control Headers</strong>: Add custom headers for API responses and webhooks
+  </Step>
+  <Step>
+    <strong>Transform Data</strong>: Convert workflow variables into client-friendly response formats
+  </Step>
+</Steps>
+
+## How It Works
+
+The Response block finalizes workflow execution:
+
+1. **Collect Data** - Gathers variables and outputs from previous blocks
+2. **Format Response** - Structures data according to your configuration
+3. **Set HTTP Details** - Applies status codes and headers
+4. **Send Response** - Returns the formatted response to the API caller
+
+## When You Need Response Blocks
+
+- **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
+
+## 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
+
+### Response Data
+
+The response data is the main content that will be sent back to the API caller. This should be formatted as JSON and can include:
+
+- Static values
+- Dynamic references to workflow variables using the `<variable.name>` syntax
+- Nested objects and arrays
+- Any valid JSON structure
+
+### Status Code
+
+Set the HTTP status code for the response. Common status codes include:
+
+<Tabs items={['Success (2xx)', 'Client Error (4xx)', 'Server Error (5xx)']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li><strong>200</strong>: OK - Standard success response</li>
+      <li><strong>201</strong>: Created - Resource successfully created</li>
+      <li><strong>204</strong>: No Content - Success with no response body</li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li><strong>400</strong>: Bad Request - Invalid request parameters</li>
+      <li><strong>401</strong>: Unauthorized - Authentication required</li>
+      <li><strong>404</strong>: Not Found - Resource doesn't exist</li>
+      <li><strong>422</strong>: Unprocessable Entity - Validation errors</li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li><strong>500</strong>: Internal Server Error - Server-side error</li>
+      <li><strong>502</strong>: Bad Gateway - External service error</li>
+      <li><strong>503</strong>: Service Unavailable - Service temporarily down</li>
+    </ul>
+  </Tab>
+</Tabs>
+
+<div className="mt-4 text-sm text-gray-600 dark:text-gray-400">
+  Default status code is 200 if not specified.
+</div>
+
+### Response Headers
+
+Configure additional HTTP headers to include in the response.
+
+Headers are configured as key-value pairs:
+
+| Key | Value |
+|-----|-------|
+| Content-Type | application/json |
+| Cache-Control | no-cache |
+| X-API-Version | 1.0 |
+
+## Example Use Cases
+
+### API Endpoint Response
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Return structured data from a search API</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Workflow processes search query and retrieves results</li>
+    <li>Function block formats and paginates results</li>
+    <li>Response block returns JSON with data, pagination, and metadata</li>
+    <li>Client receives structured response with 200 status</li>
+  </ol>
+</div>
+
+### Webhook Confirmation
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Acknowledge webhook receipt and processing</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Webhook trigger receives external system data</li>
+    <li>Workflow processes the incoming data</li>
+    <li>Response block returns confirmation with processing status</li>
+    <li>External system receives acknowledgment</li>
+  </ol>
+</div>
+
+### Error Response Handling
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Return appropriate error responses</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Condition block detects validation failure or system error</li>
+    <li>Router directs to error handling path</li>
+    <li>Response block returns 400/500 status with error details</li>
+    <li>Client receives structured error information</li>
+  </ol>
+</div>
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Response Data</strong>: JSON structure for response body
+      </li>
+      <li>
+        <strong>Status Code</strong>: HTTP status code (default: 200)
+      </li>
+      <li>
+        <strong>Headers</strong>: Custom HTTP headers as key-value pairs
+      </li>
+      <li>
+        <strong>Mode</strong>: Builder or Editor mode for response construction
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>response.data</strong>: The structured response body
+      </li>
+      <li>
+        <strong>response.status</strong>: HTTP status code sent
+      </li>
+      <li>
+        <strong>response.headers</strong>: Headers included in response
+      </li>
+      <li>
+        <strong>response.success</strong>: Boolean indicating successful completion
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>HTTP Response</strong>: Complete response sent to API caller
+      </li>
+      <li>
+        <strong>Workflow Termination</strong>: Ends workflow execution
+      </li>
+      <li>
+        <strong>Access</strong>: Response blocks are terminal - no subsequent blocks
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Variable References
+
+Use the `<variable.name>` syntax to dynamically insert workflow variables into your response:
+
+```json
+{
+  "user": {
+    "id": "<variable.userId>",
+    "name": "<variable.userName>",
+    "email": "<variable.userEmail>"
+  },
+  "query": "<variable.searchQuery>",
+  "results": "<variable.searchResults>",
+  "totalFound": "<variable.resultCount>",
+  "processingTime": "<variable.executionTime>ms"
+}
+```
+
+<Callout type="warning">
+  Variable names are case-sensitive and must match exactly with the variables available in your workflow.
+</Callout>
+
+## Best Practices
+
+- **Use meaningful status codes**: Choose appropriate HTTP status codes that accurately reflect the outcome of the workflow
+- **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
+

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

@@ -0,0 +1,226 @@
+---
+title: Router
+---
+
+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 { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
+
+The Router block uses AI to intelligently decide which path your workflow should take next, routing workflow execution based on specific conditions or logic. Unlike Condition blocks that use simple rules, Router blocks can understand context and make smart routing decisions based on content analysis.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/router.png"
+    alt="Router Block with Multiple Paths"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+## Overview
+
+The Router block enables you to:
+
+<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:
+
+<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
+
+### Content/Prompt
+
+The content or prompt that the Router will analyze to make routing decisions. This can be:
+
+- A direct user query or input
+- Output from a previous block
+- A system-generated message
+
+### Target Blocks
+
+The possible destination blocks that the Router can select from. The Router will automatically detect connected blocks, but you can also:
+
+- Customize the descriptions of target blocks to improve routing accuracy
+- Specify routing criteria for each target block
+- Exclude certain blocks from being considered as routing targets
+
+### Model Selection
+
+Choose an AI model to power the routing decision:
+
+**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 
+
+<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
+  <Video src="router-model-dropdown.mp4" width={500} height={350} />
+</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.
+
+### Accessing Results
+
+After a router makes a decision, you can access its outputs:
+
+- **`<router.prompt>`**: Summary of the routing prompt used
+- **`<router.selected_path>`**: Details of the chosen destination block
+- **`<router.tokens>`**: Token usage statistics from the LLM
+- **`<router.cost>`**: Cost summary for the routing call (input, output, total)
+- **`<router.model>`**: The model used for decision-making
+
+## Advanced Features
+
+### Custom Routing Criteria
+
+Define specific criteria for each target block:
+
+```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"
+```
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables']}>
+  <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.prompt</strong>: Summary of routing prompt used
+      </li>
+      <li>
+        <strong>router.selected_path</strong>: Details of chosen destination
+      </li>
+      <li>
+        <strong>router.tokens</strong>: Token usage statistics
+      </li>
+      <li>
+        <strong>router.cost</strong>: Cost summary for the routing call (input, output, total)
+      </li>
+      <li>
+        <strong>router.model</strong>: Model used for decision-making
+      </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>
+
+
+## Best Practices
+
+- **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/en/blocks/workflow.mdx

@@ -0,0 +1,169 @@
+---
+title: Workflow
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+The Workflow block allows you to execute other workflows as reusable components within your current workflow. This enables modular design, code reuse, and the creation of complex nested workflows that can be composed from smaller, focused workflows.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/workflow.png"
+    alt="Workflow Block"
+    width={500}
+    height={350}
+    className="my-6"
+  />
+</div>
+
+<Callout type="info">
+  Workflow blocks enable modular design by allowing you to compose complex workflows from smaller, reusable components.
+</Callout>
+
+## Overview
+
+The Workflow block serves as a bridge between workflows, enabling you to:
+
+<Steps>
+  <Step>
+    <strong>Reuse existing workflows</strong>: Execute previously created workflows as components within new workflows
+  </Step>
+  <Step>
+    <strong>Create modular designs</strong>: Break down complex processes into smaller, manageable workflows
+  </Step>
+  <Step>
+    <strong>Maintain separation of concerns</strong>: Keep different business logic isolated in separate workflows
+  </Step>
+  <Step>
+    <strong>Enable team collaboration</strong>: Share and reuse workflows across different projects and team members
+  </Step>
+</Steps>
+
+## How It Works
+
+The Workflow block:
+
+1. Takes a reference to another workflow in your workspace
+2. Passes input data from the current workflow to the child workflow (available via start.input)
+3. Executes the child workflow in an isolated context
+4. Returns the result back to the parent workflow for further processing
+
+## Configuration Options
+
+### Workflow Selection
+
+Choose which workflow to execute from a dropdown list of available workflows in your workspace. The list includes:
+
+- All workflows you have access to in the current workspace
+- Workflows shared with you by other team members
+- Both enabled and disabled workflows (though only enabled workflows can be executed)
+
+
+### Execution Context
+
+The child workflow executes with:
+
+- Its own isolated execution context
+- Access to the same workspace resources (API keys, environment variables)
+- Proper workspace membership and permission checks
+- Nested tracespan in the execution log
+
+<Callout type="warning">
+  **Cycle Detection**: The system automatically detects and prevents circular dependencies between workflows to avoid infinite loops.
+</Callout>
+
+## Inputs and Outputs
+
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Workflow Selection</strong>: Choose which workflow to execute
+      </li>
+      <li>
+        <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>workflow.success</strong>: Boolean indicating completion status
+      </li>
+      <li>
+        <strong>workflow.childWorkflowName</strong>: Name of executed child workflow
+      </li>
+      <li>
+        <strong>workflow.result</strong>: Result returned by the child workflow
+      </li>
+      <li>
+        <strong>workflow.error</strong>: Error details if workflow failed
+      </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 Use Cases
+
+### Modular Customer Onboarding
+
+<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>
+
+## Best Practices
+
+- **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
+- **Test independently**: Ensure child workflows can be tested and validated independently from parent workflows
+- **Use semantic naming**: Give workflows descriptive names that clearly indicate their purpose and functionality

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

@@ -0,0 +1,44 @@
+---
+title: Connection Basics
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+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. In Sim, connections define how information passes from one block to another, enabling data flow throughout your workflow.
+
+<Callout type="info">
+  Each connection represents a directed relationship where data flows from a source block's output
+  to a destination block's input.
+</Callout>
+
+### Creating Connections
+
+<Steps>
+  <Step>
+    <strong>Select Source Block</strong>: Click on the output port of the block you want to connect
+    from
+  </Step>
+  <Step>
+    <strong>Draw Connection</strong>: Drag to the input port of the destination block
+  </Step>
+  <Step>
+    <strong>Confirm Connection</strong>: Release to create the connection
+  </Step>
+</Steps>
+
+### Connection Flow
+
+The flow of data through connections follows these principles:
+
+1. **Directional Flow**: Data always flows from outputs to inputs
+2. **Execution Order**: Blocks execute in order based on their connections
+3. **Data Transformation**: Data may be transformed as it passes between blocks
+4. **Conditional Paths**: Some blocks (like Router and Condition) can direct flow to different paths
+
+<Callout type="warning">
+  Deleting a connection will immediately stop data flow between the blocks. Make sure this is
+  intended before removing connections.
+</Callout>

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

@@ -1,12 +1,11 @@
 ---
 title: Connection Data Structure
-description: Understanding the data structure of different block outputs
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 
-When you connect blocks, the output data structure from the source block determines what values are available in the destination block. Each block type produces a specific output structure that you can reference in downstream blocks.
+When you connect blocks, understanding the data structure of different block outputs is important because the output data structure from the source block determines what values are available in the destination block. Each block type produces a specific output structure that you can reference in downstream blocks.
 
 <Callout type="info">
   Understanding these data structures is essential for effectively using connection tags and
@@ -71,7 +70,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 +77,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,
@@ -182,7 +179,7 @@ Some blocks may produce custom output structures based on their configuration:
 Many block outputs contain nested data structures. You can access these using dot notation in connection tags:
 
 ```
-<blockId.path.to.nested.data>
+<blockName.path.to.nested.data>
 ```
 
 For example:

apps/docs/content/docs/en/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/en/connections/tags.mdx

@@ -1,14 +1,14 @@
 ---
 title: Connection Tags
-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.
+Connection tags are visual representations of the data available from connected blocks, providing an easy way to reference data between blocks and 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?
@@ -65,12 +65,12 @@ There are two primary ways to use connection tags in your workflows:
 Connection tags use a simple syntax to reference data:
 
 ```
-<blockId.path.to.data>
+<blockName.path.to.data>
 ```
 
 Where:
 
-- `blockId` is the identifier of the source block
+- `blockName` is the name of the source block
 - `path.to.data` is the path to the specific data field
 
 For example:

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

@@ -0,0 +1,162 @@
+---
+title: Copilot
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Card, Cards } from 'fumadocs-ui/components/card'
+import { Image } from '@/components/ui/image'
+import { MessageCircle, Package, Zap, Infinity as InfinityIcon, Brain, BrainCircuit } from 'lucide-react'
+
+Copilot is your in-editor assistant that helps you build and edit workflows with Sim Copilot, as well as understand and improve them. 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>
+
+## Context Menu (@)
+
+Use the `@` symbol to reference various resources and give Copilot more context about your workspace:
+
+<Image
+  src="/static/copilot/copilot-menu.png"
+  alt="Copilot context menu showing available reference options"
+  width={600}
+  height={400}
+/>
+
+The `@` menu provides access to:
+- **Chats**: Reference previous copilot conversations
+- **All workflows**: Reference any workflow in your workspace
+- **Workflow Blocks**: Reference specific blocks from workflows
+- **Blocks**: Reference block types and templates
+- **Knowledge**: Reference your uploaded documents and knowledgebase
+- **Docs**: Reference Sim documentation
+- **Templates**: Reference workflow templates
+- **Logs**: Reference execution logs and results
+
+This contextual information helps Copilot provide more accurate and relevant assistance for your specific use case.
+
+## 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>
+
+### Mode Selection Interface
+
+You can easily switch between different reasoning modes using the mode selector in the Copilot interface:
+
+<Image
+  src="/static/copilot/copilot-models.png"
+  alt="Copilot mode selection showing Advanced mode with MAX toggle"
+  width={600}
+  height={300}
+/>
+
+The interface allows you to:
+- **Select reasoning level**: Choose from Fast, Auto, Advanced, or Behemoth
+- **Enable MAX mode**: Toggle for maximum reasoning capabilities when you need the most thorough analysis
+- **See mode descriptions**: Understand what each mode is optimized for
+
+Choose your mode based on the complexity of your task - use Fast for simple questions and Behemoth for complex architectural changes.
+
+## Billing and Cost Calculation
+
+### How Costs Are Calculated
+
+Copilot usage is billed per token from the underlying LLM:
+
+- **Input tokens**: billed at the provider's base rate (**at-cost**)
+- **Output tokens**: billed at **1.5×** the provider's base output rate
+
+```javascript
+copilotCost = (inputTokens × inputPrice + outputTokens × (outputPrice × 1.5)) / 1,000,000
+```
+
+| Component | Rate Applied         |
+|----------|----------------------|
+| Input    | inputPrice           |
+| Output   | outputPrice × 1.5    |
+
+<Callout type="warning">
+  Pricing shown reflects rates as of September 4, 2025. Check provider documentation for current pricing.
+</Callout>
+
+<Callout type="info">
+  Model prices are per million tokens. The calculation divides by 1,000,000 to get the actual cost. See <a href="/execution/costs">the Cost Calculation page</a> for background and examples.
+</Callout>
+

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

@@ -0,0 +1,536 @@
+---
+title: External API
+---
+
+import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { CodeBlock } from 'fumadocs-ui/components/codeblock'
+import { Video } from '@/components/ui/video'
+
+Sim provides a comprehensive external API for querying workflow execution logs and setting up webhooks for real-time notifications when workflows complete.
+
+## Authentication
+
+All API requests require an API key passed in the `x-api-key` header:
+
+```bash
+curl -H "x-api-key: YOUR_API_KEY" \
+  https://sim.ai/api/v1/logs?workspaceId=YOUR_WORKSPACE_ID
+```
+
+You can generate API keys from your user settings in the Sim dashboard.
+
+## Logs API
+
+All API responses include information about your workflow execution limits and usage:
+
+```json
+"limits": {
+  "workflowExecutionRateLimit": {
+    "sync": {
+      "limit": 60,        // Max sync workflow executions per minute
+      "remaining": 58,    // Remaining sync workflow executions
+      "resetAt": "..."    // When the window resets
+    },
+    "async": {
+      "limit": 60,        // Max async workflow executions per minute
+      "remaining": 59,    // Remaining async workflow executions
+      "resetAt": "..."    // When the window resets
+    }
+  },
+  "usage": {
+    "currentPeriodCost": 1.234,  // Current billing period usage in USD
+    "limit": 10,                  // Usage limit in USD
+    "plan": "pro",                // Current subscription plan
+    "isExceeded": false           // Whether limit is exceeded
+  }
+}
+```
+
+**Note:** The rate limits in the response body are for workflow executions. The rate limits for calling this API endpoint are in the response headers (`X-RateLimit-*`).
+
+### Query Logs
+
+Query workflow execution logs with extensive filtering options.
+
+<Tabs items={['Request', 'Response']}>
+  <Tab value="Request">
+    ```http
+    GET /api/v1/logs
+    ```
+
+    **Required Parameters:**
+    - `workspaceId` - Your workspace ID
+
+    **Optional Filters:**
+    - `workflowIds` - Comma-separated workflow IDs
+    - `folderIds` - Comma-separated folder IDs
+    - `triggers` - Comma-separated trigger types: `api`, `webhook`, `schedule`, `manual`, `chat`
+    - `level` - Filter by level: `info`, `error`
+    - `startDate` - ISO timestamp for date range start
+    - `endDate` - ISO timestamp for date range end
+    - `executionId` - Exact execution ID match
+    - `minDurationMs` - Minimum execution duration in milliseconds
+    - `maxDurationMs` - Maximum execution duration in milliseconds
+    - `minCost` - Minimum execution cost
+    - `maxCost` - Maximum execution cost
+    - `model` - Filter by AI model used
+
+    **Pagination:**
+    - `limit` - Results per page (default: 100)
+    - `cursor` - Cursor for next page
+    - `order` - Sort order: `desc`, `asc` (default: desc)
+
+    **Detail Level:**
+    - `details` - Response detail level: `basic`, `full` (default: basic)
+    - `includeTraceSpans` - Include trace spans (default: false)
+    - `includeFinalOutput` - Include final output (default: false)
+  </Tab>
+  <Tab value="Response">
+    ```json
+    {
+      "data": [
+        {
+          "id": "log_abc123",
+          "workflowId": "wf_xyz789",
+          "executionId": "exec_def456",
+          "level": "info",
+          "trigger": "api",
+          "startedAt": "2025-01-01T12:34:56.789Z",
+          "endedAt": "2025-01-01T12:34:57.123Z",
+          "totalDurationMs": 334,
+          "cost": {
+            "total": 0.00234
+          },
+          "files": null
+        }
+      ],
+      "nextCursor": "eyJzIjoiMjAyNS0wMS0wMVQxMjozNDo1Ni43ODlaIiwiaWQiOiJsb2dfYWJjMTIzIn0",
+      "limits": {
+        "workflowExecutionRateLimit": {
+          "sync": {
+            "limit": 60,
+            "remaining": 58,
+            "resetAt": "2025-01-01T12:35:56.789Z"
+          },
+          "async": {
+            "limit": 60,
+            "remaining": 59,
+            "resetAt": "2025-01-01T12:35:56.789Z"
+          }
+        },
+        "usage": {
+          "currentPeriodCost": 1.234,
+          "limit": 10,
+          "plan": "pro",
+          "isExceeded": false
+        }
+      }
+    }
+    ```
+  </Tab>
+</Tabs>
+
+### Get Log Details
+
+Retrieve detailed information about a specific log entry.
+
+<Tabs items={['Request', 'Response']}>
+  <Tab value="Request">
+    ```http
+    GET /api/v1/logs/{id}
+    ```
+  </Tab>
+  <Tab value="Response">
+    ```json
+    {
+      "data": {
+        "id": "log_abc123",
+        "workflowId": "wf_xyz789",
+        "executionId": "exec_def456",
+        "level": "info",
+        "trigger": "api",
+        "startedAt": "2025-01-01T12:34:56.789Z",
+        "endedAt": "2025-01-01T12:34:57.123Z",
+        "totalDurationMs": 334,
+        "workflow": {
+          "id": "wf_xyz789",
+          "name": "My Workflow",
+          "description": "Process customer data"
+        },
+        "executionData": {
+          "traceSpans": [...],
+          "finalOutput": {...}
+        },
+        "cost": {
+          "total": 0.00234,
+          "tokens": {
+            "prompt": 123,
+            "completion": 456,
+            "total": 579
+          },
+          "models": {
+            "gpt-4o": {
+              "input": 0.001,
+              "output": 0.00134,
+              "total": 0.00234,
+              "tokens": {
+                "prompt": 123,
+                "completion": 456,
+                "total": 579
+              }
+            }
+          }
+        },
+        "limits": {
+          "workflowExecutionRateLimit": {
+            "sync": {
+              "limit": 60,
+              "remaining": 58,
+              "resetAt": "2025-01-01T12:35:56.789Z"
+            },
+            "async": {
+              "limit": 60,
+              "remaining": 59,
+              "resetAt": "2025-01-01T12:35:56.789Z"
+            }
+          },
+          "usage": {
+            "currentPeriodCost": 1.234,
+            "limit": 10,
+            "plan": "pro",
+            "isExceeded": false
+          }
+        }
+      }
+    }
+    ```
+  </Tab>
+</Tabs>
+
+### Get Execution Details
+
+Retrieve execution details including the workflow state snapshot.
+
+<Tabs items={['Request', 'Response']}>
+  <Tab value="Request">
+    ```http
+    GET /api/v1/logs/executions/{executionId}
+    ```
+  </Tab>
+  <Tab value="Response">
+    ```json
+    {
+      "executionId": "exec_def456",
+      "workflowId": "wf_xyz789",
+      "workflowState": {
+        "blocks": {...},
+        "edges": [...],
+        "loops": {...},
+        "parallels": {...}
+      },
+      "executionMetadata": {
+        "trigger": "api",
+        "startedAt": "2025-01-01T12:34:56.789Z",
+        "endedAt": "2025-01-01T12:34:57.123Z",
+        "totalDurationMs": 334,
+        "cost": {...}
+      }
+    }
+    ```
+  </Tab>
+</Tabs>
+
+## Webhook Subscriptions
+
+Get real-time notifications when workflow executions complete. Webhooks are configured through the Sim UI in the workflow editor.
+
+### Configuration
+
+Webhooks can be configured for each workflow through the workflow editor UI. Click the webhook icon in the control bar to set up your webhook subscriptions.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="configure-webhook.mp4" width={700} height={450} />
+</div>
+
+**Available Configuration Options:**
+- `url`: Your webhook endpoint URL
+- `secret`: Optional secret for HMAC signature verification
+- `includeFinalOutput`: Include the workflow's final output in the payload
+- `includeTraceSpans`: Include detailed execution trace spans
+- `includeRateLimits`: Include the workflow owner's rate limit information
+- `includeUsageData`: Include the workflow owner's usage and billing data
+- `levelFilter`: Array of log levels to receive (`info`, `error`)
+- `triggerFilter`: Array of trigger types to receive (`api`, `webhook`, `schedule`, `manual`, `chat`)
+- `active`: Enable/disable the webhook subscription
+
+### Webhook Payload
+
+When a workflow execution completes, Sim sends a POST request to your webhook URL:
+
+```json
+{
+  "id": "evt_123",
+  "type": "workflow.execution.completed",
+  "timestamp": 1735925767890,
+  "data": {
+    "workflowId": "wf_xyz789",
+    "executionId": "exec_def456",
+    "status": "success",
+    "level": "info",
+    "trigger": "api",
+    "startedAt": "2025-01-01T12:34:56.789Z",
+    "endedAt": "2025-01-01T12:34:57.123Z",
+    "totalDurationMs": 334,
+    "cost": {
+      "total": 0.00234,
+      "tokens": {
+        "prompt": 123,
+        "completion": 456,
+        "total": 579
+      },
+      "models": {
+        "gpt-4o": {
+          "input": 0.001,
+          "output": 0.00134,
+          "total": 0.00234,
+          "tokens": {
+            "prompt": 123,
+            "completion": 456,
+            "total": 579
+          }
+        }
+      }
+    },
+    "files": null,
+    "finalOutput": {...},  // Only if includeFinalOutput=true
+    "traceSpans": [...],   // Only if includeTraceSpans=true
+    "rateLimits": {...},   // Only if includeRateLimits=true
+    "usage": {...}         // Only if includeUsageData=true
+  },
+  "links": {
+    "log": "/v1/logs/log_abc123",
+    "execution": "/v1/logs/executions/exec_def456"
+  }
+}
+```
+
+### Webhook Headers
+
+Each webhook request includes these headers:
+
+- `sim-event`: Event type (always `workflow.execution.completed`)
+- `sim-timestamp`: Unix timestamp in milliseconds
+- `sim-delivery-id`: Unique delivery ID for idempotency
+- `sim-signature`: HMAC-SHA256 signature for verification (if secret configured)
+- `Idempotency-Key`: Same as delivery ID for duplicate detection
+
+### Signature Verification
+
+If you configure a webhook secret, verify the signature to ensure the webhook is from Sim:
+
+<Tabs items={['Node.js', 'Python']}>
+  <Tab value="Node.js">
+    ```javascript
+    import crypto from 'crypto';
+
+    function verifyWebhookSignature(body, signature, secret) {
+      const [timestampPart, signaturePart] = signature.split(',');
+      const timestamp = timestampPart.replace('t=', '');
+      const expectedSignature = signaturePart.replace('v1=', '');
+      
+      const signatureBase = `${timestamp}.${body}`;
+      const hmac = crypto.createHmac('sha256', secret);
+      hmac.update(signatureBase);
+      const computedSignature = hmac.digest('hex');
+      
+      return computedSignature === expectedSignature;
+    }
+
+    // In your webhook handler
+    app.post('/webhook', (req, res) => {
+      const signature = req.headers['sim-signature'];
+      const body = JSON.stringify(req.body);
+      
+      if (!verifyWebhookSignature(body, signature, process.env.WEBHOOK_SECRET)) {
+        return res.status(401).send('Invalid signature');
+      }
+      
+      // Process the webhook...
+    });
+    ```
+  </Tab>
+  <Tab value="Python">
+    ```python
+    import hmac
+    import hashlib
+    import json
+
+    def verify_webhook_signature(body: str, signature: str, secret: str) -> bool:
+        timestamp_part, signature_part = signature.split(',')
+        timestamp = timestamp_part.replace('t=', '')
+        expected_signature = signature_part.replace('v1=', '')
+        
+        signature_base = f"{timestamp}.{body}"
+        computed_signature = hmac.new(
+            secret.encode(),
+            signature_base.encode(),
+            hashlib.sha256
+        ).hexdigest()
+        
+        return hmac.compare_digest(computed_signature, expected_signature)
+
+    # In your webhook handler
+    @app.route('/webhook', methods=['POST'])
+    def webhook():
+        signature = request.headers.get('sim-signature')
+        body = json.dumps(request.json)
+        
+        if not verify_webhook_signature(body, signature, os.environ['WEBHOOK_SECRET']):
+            return 'Invalid signature', 401
+        
+        # Process the webhook...
+    ```
+  </Tab>
+</Tabs>
+
+### Retry Policy
+
+Failed webhook deliveries are retried with exponential backoff and jitter:
+
+- Maximum attempts: 5
+- Retry delays: 5 seconds, 15 seconds, 1 minute, 3 minutes, 10 minutes
+- Jitter: Up to 10% additional delay to prevent thundering herd
+- Only HTTP 5xx and 429 responses trigger retries
+- Deliveries timeout after 30 seconds
+
+<Callout type="info">
+  Webhook deliveries are processed asynchronously and don't affect workflow execution performance.
+</Callout>
+
+## Best Practices
+
+1. **Polling Strategy**: When polling for logs, use cursor-based pagination with `order=asc` and `startDate` to fetch new logs efficiently.
+
+2. **Webhook Security**: Always configure a webhook secret and verify signatures to ensure requests are from Sim.
+
+3. **Idempotency**: Use the `Idempotency-Key` header to detect and handle duplicate webhook deliveries.
+
+4. **Privacy**: By default, `finalOutput` and `traceSpans` are excluded from responses. Only enable these if you need the data and understand the privacy implications.
+
+5. **Rate Limiting**: Implement exponential backoff when you receive 429 responses. Check the `Retry-After` header for the recommended wait time.
+
+## Rate Limiting
+
+The API implements rate limiting to ensure fair usage:
+
+- **Free plan**: 10 requests per minute
+- **Pro plan**: 30 requests per minute
+- **Team plan**: 60 requests per minute
+- **Enterprise plan**: Custom limits
+
+Rate limit information is included in response headers:
+- `X-RateLimit-Limit`: Maximum requests per window
+- `X-RateLimit-Remaining`: Requests remaining in current window
+- `X-RateLimit-Reset`: ISO timestamp when the window resets
+
+## Example: Polling for New Logs
+
+```javascript
+let cursor = null;
+const workspaceId = 'YOUR_WORKSPACE_ID';
+const startDate = new Date().toISOString();
+
+async function pollLogs() {
+  const params = new URLSearchParams({
+    workspaceId,
+    startDate,
+    order: 'asc',
+    limit: '100'
+  });
+  
+  if (cursor) {
+    params.append('cursor', cursor);
+  }
+  
+  const response = await fetch(
+    `https://sim.ai/api/v1/logs?${params}`,
+    {
+      headers: {
+        'x-api-key': 'YOUR_API_KEY'
+      }
+    }
+  );
+  
+  if (response.ok) {
+    const data = await response.json();
+    
+    // Process new logs
+    for (const log of data.data) {
+      console.log(`New execution: ${log.executionId}`);
+    }
+    
+    // Update cursor for next poll
+    if (data.nextCursor) {
+      cursor = data.nextCursor;
+    }
+  }
+}
+
+// Poll every 30 seconds
+setInterval(pollLogs, 30000);
+```
+
+## Example: Processing Webhooks
+
+```javascript
+import express from 'express';
+import crypto from 'crypto';
+
+const app = express();
+app.use(express.json());
+
+app.post('/sim-webhook', (req, res) => {
+  // Verify signature
+  const signature = req.headers['sim-signature'];
+  const body = JSON.stringify(req.body);
+  
+  if (!verifyWebhookSignature(body, signature, process.env.WEBHOOK_SECRET)) {
+    return res.status(401).send('Invalid signature');
+  }
+  
+  // Check timestamp to prevent replay attacks
+  const timestamp = parseInt(req.headers['sim-timestamp']);
+  const fiveMinutesAgo = Date.now() - (5 * 60 * 1000);
+  
+  if (timestamp < fiveMinutesAgo) {
+    return res.status(401).send('Timestamp too old');
+  }
+  
+  // Process the webhook
+  const event = req.body;
+  
+  switch (event.type) {
+    case 'workflow.execution.completed':
+      const { workflowId, executionId, status, cost } = event.data;
+      
+      if (status === 'error') {
+        console.error(`Workflow ${workflowId} failed: ${executionId}`);
+        // Handle error...
+      } else {
+        console.log(`Workflow ${workflowId} completed: ${executionId}`);
+        console.log(`Cost: $${cost.total}`);
+        // Process successful execution...
+      }
+      break;
+  }
+  
+  // Return 200 to acknowledge receipt
+  res.status(200).send('OK');
+});
+
+app.listen(3000, () => {
+  console.log('Webhook server listening on port 3000');
+});
+```

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

@@ -0,0 +1,132 @@
+---
+title: Execution Basics
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Card, Cards } from 'fumadocs-ui/components/card'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
+
+Understanding how workflows execute in Sim is key to building efficient and reliable automations. The execution engine automatically handles dependencies, concurrency, and data flow to ensure your workflows run smoothly and predictably.
+
+## How Workflows Execute
+
+Sim's execution engine processes workflows intelligently by analyzing dependencies and running blocks in the most efficient order possible.
+
+### Concurrent Execution by Default
+
+Multiple blocks run concurrently when they don't depend on each other. This parallel execution dramatically improves performance without requiring manual configuration.
+
+<Image
+  src="/static/execution/concurrency.png"
+  alt="Multiple blocks running concurrently after the Start block"
+  width={800}
+  height={500}
+/>
+
+In this example, both the Customer Support and Deep Researcher agent blocks execute simultaneously after the Start block, maximizing efficiency.
+
+### Automatic Output Combination
+
+When blocks have multiple dependencies, the execution engine automatically waits for all dependencies to complete, then provides their combined outputs to the next block. No manual combining required.
+
+<Image
+  src="/static/execution/combination.png"
+  alt="Function block automatically receiving outputs from multiple previous blocks"
+  width={800}
+  height={500}
+/>
+
+The Function block receives outputs from both agent blocks as soon as they complete, allowing you to process the combined results.
+
+### Smart Routing
+
+Workflows can branch in multiple directions using routing blocks. The execution engine supports both deterministic routing (with Condition blocks) and AI-powered routing (with Router blocks).
+
+<Image
+  src="/static/execution/routing.png"
+  alt="Workflow showing both conditional and router-based branching"
+  width={800}
+  height={500}
+/>
+
+This workflow demonstrates how execution can follow different paths based on conditions or AI decisions, with each path executing independently.
+
+## Block Types
+
+Sim provides different types of blocks that serve specific purposes in your workflows:
+
+<Cards>
+  <Card title="Triggers" href="/triggers">
+    **Starter blocks** initiate workflows and **Webhook blocks** respond to external events. Every workflow needs a trigger to begin execution.
+  </Card>
+  
+  <Card title="Processing Blocks" href="/blocks">
+    **Agent blocks** interact with AI models, **Function blocks** run custom code, and **API blocks** connect to external services. These blocks transform and process your data.
+  </Card>
+  
+  <Card title="Control Flow" href="/blocks">
+    **Router blocks** use AI to choose paths, **Condition blocks** branch based on logic, and **Loop/Parallel blocks** handle iterations and concurrency.
+  </Card>
+  
+  <Card title="Output & Response" href="/blocks">
+    **Response blocks** format final outputs for APIs and chat interfaces, returning structured results from your workflows.
+  </Card>
+</Cards>
+
+All blocks execute automatically based on their dependencies - you don't need to manually manage execution order or timing.
+
+## Execution Triggers
+
+Workflows can be triggered in several ways, depending on your use case:
+
+### Manual Testing
+Click "Run" in the workflow editor to test your workflow during development. Perfect for debugging and validation.
+
+### Scheduled Execution  
+Set up recurring executions using cron expressions. Great for regular data processing, reports, or maintenance tasks.
+
+### API Deployment
+Deploy workflows as HTTP endpoints that can be called programmatically from your applications.
+
+### Webhook Integration
+Respond to events from external services like GitHub, Stripe, or custom systems in real-time.
+
+### Chat Interface
+Create conversational interfaces hosted on custom subdomains for user-facing AI applications.
+
+<Callout type="info">
+  Learn more about each trigger type in the [Triggers section](/triggers) of the documentation.
+</Callout>
+
+## Execution Monitoring
+
+When workflows run, Sim provides real-time visibility into the execution process:
+
+- **Live Block States**: See which blocks are currently executing, completed, or failed
+- **Execution Logs**: Detailed logs appear in real-time showing inputs, outputs, and any errors
+- **Performance Metrics**: Track execution time and costs for each block
+- **Path Visualization**: Understand which execution paths were taken through your workflow
+
+<Callout type="info">
+  All execution details are captured and available for review even after workflows complete, helping with debugging and optimization.
+</Callout>
+
+## Key Execution Principles
+
+Understanding these core principles will help you build better workflows:
+
+1. **Dependency-Based Execution**: Blocks only run when all their dependencies have completed
+2. **Automatic Parallelization**: Independent blocks run concurrently without configuration
+3. **Smart Data Flow**: Outputs flow automatically to connected blocks
+4. **Error Handling**: Failed blocks stop their execution path but don't affect independent paths
+5. **State Persistence**: All block outputs and execution details are preserved for debugging
+
+## Next Steps
+
+Now that you understand execution basics, explore:
+- **[Block Types](/blocks)** - Learn about specific block capabilities
+- **[Logging](/execution/logging)** - Monitor workflow executions and debug issues
+- **[Cost Calculation](/execution/costs)** - Understand and optimize workflow costs
+- **[Triggers](/triggers)** - Set up different ways to run your workflows

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

@@ -0,0 +1,182 @@
+---
+title: Cost Calculation
+---
+
+import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+Sim automatically calculates costs for all workflow executions, providing transparent pricing based on AI model usage and execution charges. Understanding these costs helps you optimize workflows and manage your budget effectively.
+
+## 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>
+
+## Model Breakdown in Logs
+
+For workflows using AI blocks, you can view detailed cost information in the logs:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs-cost.png"
+    alt="Model Breakdown"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+The model breakdown shows:
+- **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
+
+## 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 September 10, 2025. Check provider documentation for current pricing.
+</Callout>
+
+## Cost Optimization Strategies
+
+<Accordions>
+  <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="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>
+  
+  <Accordion title="Caching and Reuse">
+    Store frequently used results in variables or files to avoid repeated AI model calls.
+  </Accordion>
+  
+  <Accordion title="Batch Processing">
+    Process multiple items in a single AI request rather than making individual calls.
+  </Accordion>
+</Accordions>
+
+## Usage Monitoring
+
+Monitor your usage and billing in Settings → Subscription:
+
+- **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
+
+### Programmatic Usage Tracking
+
+You can query your current usage and limits programmatically using the API:
+
+**Endpoint:**
+```text
+GET /api/users/me/usage-limits
+```
+
+**Authentication:**
+- Include your API key in the `X-API-Key` header
+
+**Example Request:**
+```bash
+curl -X GET -H "X-API-Key: YOUR_API_KEY" -H "Content-Type: application/json" https://sim.ai/api/users/me/usage-limits
+```
+
+**Example Response:**
+```json
+{
+  "success": true,
+  "rateLimit": {
+    "sync": { "isLimited": false, "limit": 10, "remaining": 10, "resetAt": "2025-09-08T22:51:55.999Z" },
+    "async": { "isLimited": false, "limit": 50, "remaining": 50, "resetAt": "2025-09-08T22:51:56.155Z" },
+    "authType": "api"
+  },
+  "usage": {
+    "currentPeriodCost": 12.34,
+    "limit": 100,
+    "plan": "pro"
+  }
+}
+```
+
+**Response Fields:**
+- `currentPeriodCost` reflects usage in the current billing period
+- `limit` is derived from individual limits (Free/Pro) or pooled organization limits (Team/Enterprise)
+- `plan` is the highest-priority active plan associated with your user
+
+## Plan Limits
+
+Different subscription plans have different usage limits:
+
+| Plan | Monthly Usage Limit | Rate Limits (per minute) |
+|------|-------------------|-------------------------|
+| **Free** | $10 | 5 sync, 10 async |
+| **Pro** | $100 | 10 sync, 50 async |
+| **Team** | $500 (pooled) | 50 sync, 100 async |
+| **Enterprise** | Custom | Custom |
+
+## Cost Management Best Practices
+
+1. **Monitor Regularly**: Check your usage dashboard frequently to avoid surprises
+2. **Set Budgets**: Use plan limits as guardrails for your spending
+3. **Optimize Workflows**: Review high-cost executions and optimize prompts or model selection
+4. **Use Appropriate Models**: Match model complexity to task requirements
+5. **Batch Similar Tasks**: Combine multiple requests when possible to reduce overhead
+
+## Next Steps
+
+- Review your current usage in [Settings → Subscription](https://sim.ai/settings/subscription)
+- Learn about [Logging](/execution/logging) to track execution details
+- Explore the [External API](/execution/api) for programmatic cost monitoring
+- Check out [workflow optimization techniques](/blocks) to reduce costs

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

@@ -0,0 +1,135 @@
+---
+title: Execution
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Card, Cards } from 'fumadocs-ui/components/card'
+
+Sim's execution engine brings your workflows to life by processing blocks in the correct order, managing data flow, and handling errors gracefully, so you can understand exactly how workflows are executed in Sim.
+
+<Callout type="info">
+  Every workflow execution follows a deterministic path based on your block connections and logic, ensuring predictable and reliable results.
+</Callout>
+
+## Documentation Overview
+
+<Cards>
+  <Card title="Execution Basics" href="/execution/basics">
+    Learn about the fundamental execution flow, block types, and how data flows through your
+    workflow
+  </Card>
+
+  <Card title="Logging" href="/execution/logging">
+    Monitor workflow executions with comprehensive logging and real-time visibility
+  </Card>
+  
+  <Card title="Cost Calculation" href="/execution/costs">
+    Understand how workflow execution costs are calculated and optimized
+  </Card>
+  
+  <Card title="External API" href="/execution/api">
+    Access execution logs and set up webhooks programmatically via REST API
+  </Card>
+</Cards>
+
+## Key Concepts
+
+### 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.
+
+### Path Tracking
+The engine actively tracks execution paths through your workflow. Router and Condition blocks dynamically update these paths, ensuring only relevant blocks execute.
+
+### 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.
+
+### 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
+
+## Execution Triggers
+
+Workflows can be executed through multiple channels:
+
+- **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
+
+### Deploy as API
+
+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
+
+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"}'
+```
+
+### Deploy as Chat
+
+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
+
+Each deployment method passes data to your workflow's starter block, beginning the execution flow.
+
+## Programmatic Execution
+
+Execute workflows from your applications using our official SDKs:
+
+```bash
+# TypeScript/JavaScript
+npm install simstudio-ts-sdk
+
+# Python
+pip install simstudio-sdk
+```
+
+```typescript
+// TypeScript Example
+import { SimStudioClient } from 'simstudio-ts-sdk';
+
+const client = new SimStudioClient({ 
+  apiKey: 'your-api-key' 
+});
+
+const result = await client.executeWorkflow('workflow-id', {
+  input: { message: 'Hello' }
+});
+```
+
+## Best Practices
+
+### Design for Reliability
+- Handle errors gracefully with appropriate fallback paths
+- Use environment variables for sensitive data
+- Add logging to Function blocks for debugging
+
+### Optimize Performance
+- Minimize external API calls where possible
+- Use parallel execution for independent operations
+- Cache results with Memory blocks when appropriate
+
+### Monitor Executions
+- Review logs regularly to understand performance patterns
+- Track costs for AI model usage
+- Use workflow snapshots to debug issues
+
+## What's Next?
+
+Start with [Execution Basics](/execution/basics) to understand how workflows run, then explore [Logging](/execution/logging) to monitor your executions and [Cost Calculation](/execution/costs) to optimize your spending.

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

@@ -0,0 +1,150 @@
+---
+title: Logging
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+Sim provides comprehensive logging for all workflow executions, giving you complete visibility into how your workflows run, what data flows through them, and where issues might occur.
+
+## Logging System
+
+Sim offers two complementary logging interfaces to match different workflows and use cases:
+
+### Real-Time Console
+
+During manual or chat workflow execution, logs appear in real-time in the Console panel on the right side of the workflow editor:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/console.png"
+    alt="Real-time Console Panel"
+    width={400}
+    height={300}
+    className="my-6"
+  />
+</div>
+
+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
+
+### Logs Page
+
+All workflow executions—whether triggered manually, via API, Chat, Schedule, or Webhook—are logged to the dedicated Logs page:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs.png"
+    alt="Logs Page"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+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)
+
+## Log Details Sidebar
+
+Clicking on any log entry opens a detailed sidebar view:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs-sidebar.png"
+    alt="Logs Sidebar Details"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+### Block Input/Output
+
+View the complete data flow for each block with tabs to switch between:
+
+<Tabs items={['Output', 'Input']}>
+  <Tab>
+    **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>
+    **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>
+
+### Execution Timeline
+
+For workflow-level logs, view detailed execution metrics:
+- Start and end timestamps
+- Total workflow duration
+- Individual block execution times
+- Performance bottleneck identification
+
+## Workflow Snapshots
+
+For any logged execution, click "View Snapshot" to see the exact workflow state at execution time:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs-frozen-canvas.png"
+    alt="Workflow Snapshot"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+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>
+
+## Log Retention
+
+- **Free Plan**: 7 days of log retention
+- **Pro Plan**: 30 days of log retention
+- **Team Plan**: 90 days of log retention
+- **Enterprise Plan**: Custom retention periods available
+
+## Best Practices
+
+### For Development
+- Use the real-time console for immediate feedback during testing
+- Check block inputs and outputs to verify data flow
+- Use workflow snapshots to compare working vs. broken versions
+
+### For Production
+- Monitor the Logs page regularly for errors or performance issues
+- Set up filters to focus on specific workflows or time periods
+- Use live mode during critical deployments to watch executions in real-time
+
+### For Debugging
+- Always check the execution timeline to identify slow blocks
+- Compare inputs between working and failing executions
+- Use workflow snapshots to see the exact state when issues occurred
+
+## Next Steps
+
+- Learn about [Cost Calculation](/execution/costs) to understand workflow pricing
+- Explore the [External API](/execution/api) for programmatic log access
+- Set up [Webhook notifications](/execution/api#webhook-subscriptions) for real-time alerts

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

@@ -0,0 +1,193 @@
+---
+title: Getting Started
+---
+
+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'
+import { Video } from '@/components/ui/video'
+import { Image } from '@/components/ui/image'
+
+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 tutorial takes about 10 minutes and covers the essential concepts of building workflows in Sim.
+</Callout>
+
+## What We're Building
+
+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
+
+<Image
+  src="/static/getting-started/started-1.png"
+  alt="Getting Started Example"
+  width={800}
+  height={500}
+/>
+
+## 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="getting-started/started-2.mp4" width={700} height={450} />
+    </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="getting-started/started-3.mp4" width={700} height={450} />
+    </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="getting-started/started-4.mp4" width={700} height={450} />
+    </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="getting-started/started-5.mp4" width={700} height={450} />
+    </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="getting-started/started-6.mp4" width={700} height={450} />
+    </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="AI model for text processing and analysis"
+  />
+</Files>
+
+### Core Workflow Concepts
+
+**Data Flow**: Variables flow between blocks by dragging connections
+
+**Chat Interface**: Test workflows in real-time using the chat panel with different output options
+
+**Tool Integration**: Enhance agent capabilities by adding external tools like Exa and Linkup
+
+**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/en/index.mdx

@@ -0,0 +1,60 @@
+---
+title: Documentation
+---
+
+import { Card, Cards } from 'fumadocs-ui/components/card'
+
+# Sim Documentation
+
+Welcome to Sim, a visual workflow builder for AI applications. Build powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas.
+
+## Quick Start
+
+<Cards>
+  <Card title="Introduction" href="/introduction">
+    Learn what you can build with Sim
+  </Card>
+  <Card title="Getting Started" href="/getting-started">
+    Create your first workflow in 10 minutes
+  </Card>
+  <Card title="Workflow Blocks" href="/blocks">
+    Learn about the building blocks
+  </Card>
+  <Card title="Tools & Integrations" href="/tools">
+    Explore 80+ built-in integrations
+  </Card>
+</Cards>
+
+## Core Concepts
+
+<Cards>
+  <Card title="Connections" href="/connections">
+    Understand how data flows between blocks
+  </Card>
+  <Card title="Variables" href="/variables">
+    Work with workflow and environment variables
+  </Card>
+  <Card title="Execution" href="/execution">
+    Monitor workflow runs and manage costs
+  </Card>
+  <Card title="Triggers" href="/triggers">
+    Start workflows via API, webhooks, or schedules
+  </Card>
+</Cards>
+
+## Advanced Features
+
+<Cards>
+  <Card title="Team Management" href="/permissions/roles-and-permissions">
+    Set up workspace roles and permissions
+  </Card>
+  <Card title="YAML Configuration" href="/yaml">
+    Define workflows as code
+  </Card>
+  <Card title="MCP Integration" href="/mcp">
+    Connect external services with Model Context Protocol
+  </Card>
+  <Card title="SDKs" href="/sdks">
+    Integrate Sim into your applications
+  </Card>
+</Cards>

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

@@ -0,0 +1,85 @@
+---
+title: Introduction
+---
+
+import { Card, Cards } from 'fumadocs-ui/components/card'
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Image } from '@/components/ui/image'
+
+Sim is a visual workflow builder for AI applications that lets you build AI agent workflows visually. Create powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas—no coding required.
+
+<div className="flex justify-center">
+  <Image
+    src="/static/introduction.png"
+    alt="Sim visual workflow canvas"
+    width={700}
+    height={450}
+    className="my-6"
+  />
+</div>
+
+## What You Can Build
+
+**AI Assistants & Chatbots**
+Create intelligent agents that can search the web, access your calendar, send emails, and interact with your business tools.
+
+**Business Process Automation**
+Automate repetitive tasks like data entry, report generation, customer support responses, and content creation.
+
+**Data Processing & Analysis**
+Extract insights from documents, analyze datasets, generate reports, and sync data between systems.
+
+**API Integration Workflows**
+Connect multiple services into unified endpoints, orchestrate complex business logic, and handle event-driven automation.
+
+## How It Works
+
+**Visual Canvas**
+Drag and drop blocks to build workflows. Connect AI models, databases, APIs, and business tools with simple point-and-click connections.
+
+**Smart Blocks**
+Choose from processing blocks (AI agents, APIs, functions), logic blocks (conditions, loops, routers), and output blocks (responses, evaluators).
+
+**Multiple Triggers**
+Start workflows via chat interface, REST API, webhooks, scheduled jobs, or external events from services like Slack and GitHub.
+
+**Team Collaboration**
+Work simultaneously with team members on the same workflow with real-time editing and permissions management.
+
+## Built-in Integrations
+
+Sim connects to 80+ services out of the box:
+
+- **AI Models**: OpenAI, Anthropic, Google, Groq, Cerebras, local Ollama models
+- **Communication**: Gmail, Slack, Teams, Telegram, WhatsApp  
+- **Productivity**: Notion, Google Sheets, Airtable, Monday.com
+- **Development**: GitHub, Jira, Linear, browser automation
+- **Search & Web**: Google Search, Perplexity, Firecrawl, Exa AI
+- **Databases**: PostgreSQL, MySQL, Supabase, Pinecone, Qdrant
+
+Need something custom? Use our [MCP integration](/mcp) to connect any external service.
+
+## Deployment Options
+
+**Cloud-hosted**: Get started instantly at [sim.ai](https://sim.ai) with managed infrastructure, automatic scaling, and built-in monitoring.
+
+**Self-hosted**: Deploy on your own infrastructure using Docker, with support for local AI models via Ollama for complete data privacy.
+
+## Next Steps
+
+Ready to build your first AI workflow?
+
+<Cards>
+  <Card title="Getting Started" href="/getting-started">
+    Create your first workflow in 10 minutes
+  </Card>
+  <Card title="Workflow Blocks" href="/blocks">
+    Learn about the building blocks
+  </Card>
+  <Card title="Tools & Integrations" href="/tools">
+    Explore 60+ built-in integrations
+  </Card>
+  <Card title="Team Permissions" href="/permissions/roles-and-permissions">
+    Set up workspace roles and permissions
+  </Card>
+</Cards>

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

@@ -0,0 +1,113 @@
+---
+title: Knowledgebase
+---
+
+import { Video } from '@/components/ui/video'
+import { Image } from '@/components/ui/image'
+
+The knowledgebase allows you to upload, process, and search through your documents with intelligent vector search and chunking. Documents of various types are automatically processed, embedded, and made searchable. Your documents are intelligently chunked, and you can view, edit, and search through them using natural language queries.
+
+## Upload and Processing
+
+Simply upload your documents to get started. Sim automatically processes them in the background, extracting text, creating embeddings, and breaking them into searchable chunks.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="knowledgebase-1.mp4" width={700} height={450} />
+</div>
+
+The system handles the entire processing pipeline for you:
+
+1. **Text Extraction**: Content is extracted from your documents using specialized parsers for each file type
+2. **Intelligent Chunking**: Documents are broken into meaningful chunks with configurable size and overlap
+3. **Embedding Generation**: Vector embeddings are created for semantic search capabilities
+4. **Processing Status**: Track the progress as your documents are processed
+
+## Supported File Types
+
+Sim supports PDF, Word (DOC/DOCX), plain text (TXT), Markdown (MD), HTML, Excel (XLS/XLSX), PowerPoint (PPT/PPTX), and CSV files. Files can be up to 100MB each, with optimal performance for files under 50MB. You can upload multiple documents simultaneously, and PDF files include OCR processing for scanned documents.
+
+## Viewing and Editing Chunks
+
+Once your documents are processed, you can view and edit the individual chunks. This gives you full control over how your content is organized and searched.
+
+<Image src="/static/knowledgebase/knowledgebase.png" alt="Document chunks view showing processed content" width={800} height={500} />
+
+### Chunk Configuration
+- **Default chunk size**: 1,024 characters
+- **Configurable range**: 100-4,000 characters per chunk
+- **Smart overlap**: 200 characters by default for context preservation
+- **Hierarchical splitting**: Respects document structure (sections, paragraphs, sentences)
+
+### Editing Capabilities
+- **Edit chunk content**: Modify the text content of individual chunks
+- **Adjust chunk boundaries**: Merge or split chunks as needed
+- **Add metadata**: Enhance chunks with additional context
+- **Bulk operations**: Manage multiple chunks efficiently
+
+## Advanced PDF Processing
+
+For PDF documents, Sim offers enhanced processing capabilities:
+
+### OCR Support
+When configured with Azure or [Mistral OCR](https://docs.mistral.ai/ocr/):
+- **Scanned document processing**: Extract text from image-based PDFs
+- **Mixed content handling**: Process PDFs with both text and images
+- **High accuracy**: Advanced AI models ensure accurate text extraction
+
+## Using The Knowledge Block in Workflows
+
+Once your documents are processed, you can use them in your AI workflows through the Knowledge block. This enables Retrieval-Augmented Generation (RAG), allowing your AI agents to access and reason over your document content to provide more accurate, contextual responses.
+
+<Image src="/static/knowledgebase/knowledgebase-2.png" alt="Using Knowledge Block in Workflows" width={800} height={500} />
+
+### Knowledge Block Features
+- **Semantic search**: Find relevant content using natural language queries
+- **Context integration**: Automatically include relevant chunks in agent prompts
+- **Dynamic retrieval**: Search happens in real-time during workflow execution
+- **Relevance scoring**: Results ranked by semantic similarity
+
+### Integration Options
+- **System prompts**: Provide context to your AI agents
+- **Dynamic context**: Search and include relevant information during conversations
+- **Multi-document search**: Query across your entire knowledgebase
+- **Filtered search**: Combine with tags for precise content retrieval
+
+## Vector Search Technology
+
+Sim uses vector search powered by [pgvector](https://github.com/pgvector/pgvector) to understand the meaning and context of your content:
+
+### Semantic Understanding
+- **Contextual search**: Finds relevant content even when exact keywords don't match
+- **Concept-based retrieval**: Understands relationships between ideas
+- **Multi-language support**: Works across different languages
+- **Synonym recognition**: Finds related terms and concepts
+
+### Search Capabilities
+- **Natural language queries**: Ask questions in plain English
+- **Similarity search**: Find conceptually similar content
+- **Hybrid search**: Combines vector and traditional keyword search
+- **Configurable results**: Control the number and relevance threshold of results
+
+## Document Management
+
+### Organization Features
+- **Bulk upload**: Upload multiple files at once via the asynchronous API
+- **Processing status**: Real-time updates on document processing
+- **Search and filter**: Find documents quickly in large collections
+- **Metadata tracking**: Automatic capture of file information and processing details
+
+### Security and Privacy
+- **Secure storage**: Documents stored with enterprise-grade security
+- **Access control**: Workspace-based permissions
+- **Processing isolation**: Each workspace has isolated document processing
+- **Data retention**: Configure document retention policies
+
+## Getting Started
+
+1. **Navigate to your knowledgebase**: Access from your workspace sidebar
+2. **Upload documents**: Drag and drop or select files to upload
+3. **Monitor processing**: Watch as documents are processed and chunked
+4. **Explore chunks**: View and edit the processed content
+5. **Add to workflows**: Use the Knowledge block to integrate with your AI agents
+
+The knowledgebase transforms your static documents into an intelligent, searchable resource that your AI workflows can leverage for more informed and contextual responses.

apps/docs/content/docs/en/knowledgebase/tags.mdx

@@ -0,0 +1,108 @@
+---
+title: Tags and Filtering
+---
+
+import { Video } from '@/components/ui/video'
+
+Tags provide a powerful way to organize your documents and create precise filtering for your vector searches. By combining tag-based filtering with semantic search, you can retrieve exactly the content you need from your knowledgebase.
+
+## Adding Tags to Documents
+
+You can add custom tags to any document in your knowledgebase to organize and categorize your content for easier retrieval.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="knowledgebase-tag.mp4" width={700} height={450} />
+</div>
+
+### Tag Management
+- **Custom tags**: Create your own tag system that fits your workflow
+- **Multiple tags per document**: Apply as many tags as needed to each document, there are 7 tag slots available per knowledgebase that are shared by all documents in the knowledgebase
+- **Tag organization**: Group related documents with consistent tagging
+
+### Tag Best Practices
+- **Consistent naming**: Use standardized tag names across your documents
+- **Descriptive tags**: Use clear, meaningful tag names
+- **Regular cleanup**: Remove unused or outdated tags periodically
+
+## Using Tags in Knowledge Blocks
+
+Tags become powerful when combined with the Knowledge block in your workflows. You can filter your searches to specific tagged content, ensuring your AI agents get the most relevant information.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="knowledgebase-tag2.mp4" width={700} height={450} />
+</div>
+
+## Search Modes
+
+The Knowledge block supports three different search modes depending on what you provide:
+
+### 1. Tag-Only Search
+When you **only provide tags** (no search query):
+- **Direct retrieval**: Fetches all documents that have the specified tags
+- **No vector search**: Results are based purely on tag matching
+- **Fast performance**: Quick retrieval without semantic processing
+- **Exact matching**: Only documents with all specified tags are returned
+
+**Use case**: When you need all documents from a specific category or project
+
+### 2. Vector Search Only
+When you **only provide a search query** (no tags):
+- **Semantic search**: Finds content based on meaning and context
+- **Full knowledgebase**: Searches across all documents
+- **Relevance ranking**: Results ordered by semantic similarity
+- **Natural language**: Use questions or phrases to find relevant content
+
+**Use case**: When you need the most relevant content regardless of organization
+
+### 3. Combined Tag Filtering + Vector Search
+When you **provide both tags and a search query**:
+1. **First**: Filter documents to only those with the specified tags
+2. **Then**: Perform vector search within that filtered subset
+3. **Result**: Semantically relevant content from your tagged documents only
+
+**Use case**: When you need relevant content from a specific category or project
+
+### Search Configuration
+
+#### Tag Filtering
+- **Multiple tags**: Use multiple tags for OR logic (document must have one or more of the tags)
+- **Tag combinations**: Mix different tag types for precise filtering
+- **Case sensitivity**: Tag matching is case-insensitive
+- **Partial matching**: Exact tag name matching required
+
+#### Vector Search Parameters
+- **Query complexity**: Natural language questions work best
+- **Result limits**: Configure how many chunks to retrieve
+- **Relevance threshold**: Set minimum similarity scores
+- **Context window**: Adjust chunk size for your use case
+
+## Integration with Workflows
+
+### Knowledge Block Configuration
+1. **Select knowledgebase**: Choose which knowledgebase to search
+2. **Add tags**: Specify filtering tags (optional)
+3. **Enter query**: Add your search query (optional)
+4. **Configure results**: Set number of chunks to retrieve
+5. **Test search**: Preview results before using in workflow
+
+### Dynamic Tag Usage
+- **Variable tags**: Use workflow variables as tag values
+- **Conditional filtering**: Apply different tags based on workflow logic
+- **Context-aware search**: Adjust tags based on conversation context
+- **Multi-step filtering**: Refine searches through workflow steps
+
+### Performance Optimization
+- **Efficient filtering**: Tag filtering happens before vector search for better performance
+- **Caching**: Frequently used tag combinations are cached for speed
+- **Parallel processing**: Multiple tag searches can run simultaneously
+- **Resource management**: Automatic optimization of search resources
+
+## Getting Started with Tags
+
+1. **Plan your tag structure**: Decide on consistent naming conventions
+2. **Start tagging**: Add relevant tags to your existing documents
+3. **Test combinations**: Experiment with tag + search query combinations
+4. **Integrate into workflows**: Use the Knowledge block with your tagging strategy
+5. **Refine over time**: Adjust your tagging approach based on search results
+
+Tags transform your knowledgebase from a simple document store into a precisely organized, searchable intelligence system that your AI workflows can navigate with surgical precision.

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

@@ -0,0 +1,140 @@
+---
+title: MCP (Model Context Protocol)
+---
+
+import { Video } from '@/components/ui/video'
+import { Callout } from 'fumadocs-ui/components/callout'
+
+The Model Context Protocol ([MCP](https://modelcontextprotocol.com/)) allows you to connect external tools and services using a standardized protocol, enabling you to integrate APIs and services directly into your workflows. With MCP, you can extend Sim's capabilities by adding custom integrations that work seamlessly with your agents and workflows.
+
+## What is MCP?
+
+MCP is an open standard that enables AI assistants to securely connect to external data sources and tools. It provides a standardized way to:
+
+- Connect to databases, APIs, and file systems
+- Access real-time data from external services
+- Execute custom tools and scripts
+- Maintain secure, controlled access to external resources
+
+## Adding MCP Servers
+
+MCP servers provide collections of tools that your agents can use. You can add MCP servers in two ways:
+
+### From Workspace Settings
+
+Configure MCP servers at the workspace level so all team members can use them:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-1.mp4" width={700} height={450} />
+</div>
+
+1. Navigate to your workspace settings
+2. Go to the **MCP Servers** section
+3. Click **Add MCP Server**
+4. Enter the server configuration details
+5. Save the configuration
+
+<Callout type="info">
+MCP servers configured in workspace settings are available to all workspace members based on their permission levels.
+</Callout>
+
+### From Agent Configuration
+
+You can also add and configure MCP servers directly from within an agent block:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-2.mp4" width={700} height={450} />
+</div>
+
+This is useful when you need to quickly set up a specific integration for a particular workflow.
+
+## Using MCP Tools in Agents
+
+Once MCP servers are configured, their tools become available within your agent blocks:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-3.mp4" width={700} height={450} />
+</div>
+
+1. Open an **Agent** block
+2. In the **Tools** section, you'll see available MCP tools
+3. Select the tools you want the agent to use
+4. The agent can now access these tools during execution
+
+## Standalone MCP Tool Block
+
+For more granular control, you can use the dedicated MCP Tool block to execute specific MCP tools:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-4.mp4" width={700} height={450} />
+</div>
+
+The MCP Tool block allows you to:
+- Execute any configured MCP tool directly
+- Pass specific parameters to the tool
+- Use the tool's output in subsequent workflow steps
+- Chain multiple MCP tools together
+
+### When to Use MCP Tool vs Agent
+
+**Use Agent with MCP tools when:**
+- You want the AI to decide which tools to use
+- You need complex reasoning about when and how to use tools
+- You want natural language interaction with the tools
+
+**Use MCP Tool block when:**
+- You need deterministic tool execution
+- You want to execute a specific tool with known parameters
+- You're building structured workflows with predictable steps
+
+## Permission Requirements
+
+MCP functionality requires specific workspace permissions:
+
+| Action | Required Permission |
+|--------|-------------------|
+| Configure MCP servers in settings | **Admin** |
+| Use MCP tools in agents | **Write** or **Admin** |
+| View available MCP tools | **Read**, **Write**, or **Admin** |
+| Execute MCP Tool blocks | **Write** or **Admin** |
+
+## Common Use Cases
+
+### Database Integration
+Connect to databases to query, insert, or update data within your workflows.
+
+### API Integrations
+Access external APIs and web services that don't have built-in Sim integrations.
+
+### File System Access
+Read, write, and manipulate files on local or remote file systems.
+
+### Custom Business Logic
+Execute custom scripts or tools specific to your organization's needs.
+
+### Real-time Data Access
+Fetch live data from external systems during workflow execution.
+
+## Security Considerations
+
+- MCP servers run with the permissions of the user who configured them
+- Always verify MCP server sources before installation
+- Use environment variables for sensitive configuration data
+- Review MCP server capabilities before granting access to agents
+
+## Troubleshooting
+
+### MCP Server Not Appearing
+- Verify the server configuration is correct
+- Check that you have the required permissions
+- Ensure the MCP server is running and accessible
+
+### Tool Execution Failures
+- Verify tool parameters are correctly formatted
+- Check MCP server logs for error messages
+- Ensure required authentication is configured
+
+### Permission Errors
+- Confirm your workspace permission level
+- Check if the MCP server requires additional authentication
+- Verify the server is properly configured for your workspace

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

@@ -0,0 +1,25 @@
+{
+  "title": "Sim Documentation",
+  "pages": [
+    "./introduction/index",
+    "./getting-started/index",
+    "---Building Workflows---",
+    "triggers",
+    "blocks",
+    "tools",
+    "connections",
+    "mcp",
+    "copilot",
+    "knowledgebase",
+    "---Configuration---",
+    "variables",
+    "---Execution---",
+    "execution",
+    "---Advanced---",
+    "permissions",
+    "yaml",
+    "---SDKs---",
+    "sdks"
+  ],
+  "defaultOpen": false
+}

apps/docs/content/docs/en/permissions/roles-and-permissions.mdx

@@ -0,0 +1,161 @@
+---
+title: "Roles and Permissions"
+---
+
+import { Video } from '@/components/ui/video'
+
+When you invite team members to your organization or workspace, you'll need to choose what level of access to give them. This guide explains what each permission level allows users to do, helping you understand team roles and what access each permission level provides.
+
+## How to Invite Someone to a Workspace
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="invitations.mp4" width={700} height={450} />
+</div>
+
+## Workspace Permission Levels
+
+When inviting someone to a workspace, you can assign one of three permission levels:
+
+| Permission | What They Can Do |
+|------------|------------------|
+| **Read** | View workflows, see execution results, but cannot make any changes |
+| **Write** | Create and edit workflows, run workflows, manage environment variables |
+| **Admin** | Everything Write can do, plus invite/remove users and manage workspace settings |
+
+## What Each Permission Level Can Do
+
+Here's a detailed breakdown of what users can do with each permission level:
+
+### Read Permission
+**Perfect for:** Stakeholders, observers, or team members who need visibility but shouldn't make changes
+
+**What they can do:**
+- View all workflows in the workspace
+- See workflow execution results and logs
+- Browse workflow configurations and settings
+- View environment variables (but not edit them)
+
+**What they cannot do:**
+- Create, edit, or delete workflows
+- Run or deploy workflows
+- Change any workspace settings
+- Invite other users
+
+### Write Permission  
+**Perfect for:** Developers, content creators, or team members actively working on automation
+
+**What they can do:**
+- Everything Read users can do, plus:
+- Create, edit, and delete workflows
+- Run and deploy workflows
+- Add, edit, and delete workspace environment variables
+- Use all available tools and integrations
+- Collaborate in real-time on workflow editing
+
+**What they cannot do:**
+- Invite or remove users from the workspace
+- Change workspace settings
+- Delete the workspace
+
+### Admin Permission
+**Perfect for:** Team leads, project managers, or technical leads who need to manage the workspace
+
+**What they can do:**
+- Everything Write users can do, plus:
+- Invite new users to the workspace with any permission level
+- Remove users from the workspace
+- Manage workspace settings and integrations
+- Configure external tool connections
+- Delete workflows created by other users
+
+**What they cannot do:**
+- Delete the workspace (only the workspace owner can do this)
+- Remove the workspace owner from the workspace
+
+---
+
+## Workspace Owner vs Admin
+
+Every workspace has one **Owner** (the person who created it) plus any number of **Admins**.
+
+### Workspace Owner
+- Has all Admin permissions
+- Can delete the workspace
+- Cannot be removed from the workspace
+- Can transfer ownership to another user
+
+### Workspace Admin  
+- Can do everything except delete the workspace or remove the owner
+- Can be removed from the workspace by the owner or other admins
+
+---
+
+## Common Scenarios
+
+### Adding a New Developer to Your Team
+1. **Organization level**: Invite them as an **Organization Member**
+2. **Workspace level**: Give them **Write** permission so they can create and edit workflows
+
+### Adding a Project Manager
+1. **Organization level**: Invite them as an **Organization Member** 
+2. **Workspace level**: Give them **Admin** permission so they can manage the team and see everything
+
+### Adding a Stakeholder or Client
+1. **Organization level**: Invite them as an **Organization Member**
+2. **Workspace level**: Give them **Read** permission so they can see progress but not make changes
+
+---
+
+## Environment Variables
+
+Users can create two types of environment variables:
+
+### Personal Environment Variables
+- Only visible to the individual user
+- Available in all workflows they run
+- Managed in user settings
+
+### Workspace Environment Variables
+- **Read permission**: Can see variable names and values
+- **Write/Admin permission**: Can add, edit, and delete variables
+- Available to all workspace members
+- If a personal variable has the same name as a workspace variable, the personal one takes priority
+
+---
+
+## Best Practices
+
+### Start with Minimal Permissions
+Give users the lowest permission level they need to do their job. You can always increase permissions later.
+
+### Use Organization Structure Wisely
+- Make trusted team leads **Organization Admins**
+- Most team members should be **Organization Members**
+- Reserve workspace **Admin** permissions for people who need to manage users
+
+### Review Permissions Regularly
+Periodically review who has access to what, especially when team members change roles or leave the company.
+
+### Environment Variable Security
+- Use personal environment variables for sensitive API keys
+- Use workspace environment variables for shared configuration
+- Regularly audit who has access to sensitive variables
+
+---
+
+## Organization Roles
+
+When inviting someone to your organization, you can assign one of two roles:
+
+### Organization Admin
+**What they can do:**
+- Invite and remove team members from the organization
+- Create new workspaces
+- Manage billing and subscription settings
+- Access all workspaces within the organization
+
+### Organization Member  
+**What they can do:**
+- Access workspaces they've been specifically invited to
+- View the list of organization members
+- Cannot invite new people or manage organization settings

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

@@ -1,6 +1,5 @@
 ---
 title: Python SDK
-description: The official Python SDK for Sim Studio
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,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'
 
-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 using the official Python SDK.
 
 <Callout type="info">
   The Python SDK supports Python 3.8+ and provides synchronous workflow execution. All workflow executions are currently synchronous.
@@ -32,7 +31,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 +49,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 +352,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 +368,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 +377,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/en/sdks/typescript.mdx

@@ -1,6 +1,5 @@
 ---
 title: TypeScript/JavaScript SDK
-description: The official TypeScript/JavaScript SDK for Sim Studio
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,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'
 
-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 provides full type safety and supports both Node.js and browser environments, allowing you to execute workflows programmatically from your Node.js applications, web applications, and other JavaScript environments. All workflow executions are currently synchronous.
 
 <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 +45,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 +68,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 +331,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 +428,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 +538,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/en/tools/airtable.mdx

@@ -51,13 +51,13 @@ 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 */}
 
 
 ## Usage Instructions
 
-Integrate Airtable functionality to manage table records. List, get, create, 
+Integrates Airtable into the workflow. Can create, get, list, or update Airtable records. Requires OAuth. Can be used in trigger mode to trigger a workflow when an update is made to an Airtable table.
 
 
 
@@ -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/en/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
+
+Integrates ArXiv into the workflow. Can search for papers, get paper details, and get author papers. Does not require OAuth or an API key.
+
+
+
+## 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/en/tools/browser_use.mdx

@@ -51,13 +51,13 @@ 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 */}
 
 
 ## Usage Instructions
 
-Execute browser automation tasks with BrowserUse to navigate the web, scrape data, and perform actions as if a real user was interacting with the browser. The task runs asynchronously and the block will poll for completion before returning results.
+Integrate Browser Use into the workflow. Can navigate the web and perform actions as if a real user was interacting with the browser. Requires API Key.
 
 
 
@@ -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/en/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,17 +188,17 @@ 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 */}
 
 
 ## Usage Instructions
 
-Populate Clay workbook with data using a JSON or plain text. Enables direct communication and notifications with channel confirmation.
+Integrate Clay into the workflow. Can populate a table with data. Requires an API Key.
 
 
 
@@ -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/en/tools/confluence.mdx

@@ -37,13 +37,13 @@ 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 */}
 
 
 ## Usage Instructions
 
-Connect to Confluence workspaces to retrieve and search documentation. Access page content, metadata, and integrate Confluence documentation into your workflows.
+Integrate Confluence into the workflow. Can read and update a page. Requires OAuth.
 
 
 
@@ -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/en/tools/discord.mdx

@@ -22,7 +22,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
       <g>
         <path
           d='M216.856339,16.5966031 C200.285002,8.84328665 182.566144,3.2084988 164.041564,0 C161.766523,4.11318106 159.108624,9.64549908 157.276099,14.0464379 C137.583995,11.0849896 118.072967,11.0849896 98.7430163,14.0464379 C96.9108417,9.64549908 94.1925838,4.11318106 91.8971895,0 C73.3526068,3.2084988 55.6133949,8.86399117 39.0420583,16.6376612 C5.61752293,67.146514 -3.4433191,116.400813 1.08711069,164.955721 C23.2560196,181.510915 44.7403634,191.567697 65.8621325,198.148576 C71.0772151,190.971126 75.7283628,183.341335 79.7352139,175.300261 C72.104019,172.400575 64.7949724,168.822202 57.8887866,164.667963 C59.7209612,163.310589 61.5131304,161.891452 63.2445898,160.431257 C105.36741,180.133187 151.134928,180.133187 192.754523,160.431257 C194.506336,161.891452 196.298154,163.310589 198.110326,164.667963 C191.183787,168.842556 183.854737,172.420929 176.223542,175.320965 C180.230393,183.341335 184.861538,190.991831 190.096624,198.16893 C211.238746,191.588051 232.743023,181.531619 254.911949,164.955721 C260.227747,108.668201 245.831087,59.8662432 216.856339,16.5966031 Z M85.4738752,135.09489 C72.8290281,135.09489 62.4592217,123.290155 62.4592217,108.914901 C62.4592217,94.5396472 72.607595,82.7145587 85.4738752,82.7145587 C98.3405064,82.7145587 108.709962,94.5189427 108.488529,108.914901 C108.508531,123.290155 98.3405064,135.09489 85.4738752,135.09489 Z M170.525237,135.09489 C157.88039,135.09489 147.510584,123.290155 147.510584,108.914901 C147.510584,94.5396472 157.658606,82.7145587 170.525237,82.7145587 C183.391518,82.7145587 193.761324,94.5189427 193.539891,108.914901 C193.539891,123.290155 183.391518,135.09489 170.525237,135.09489 Z'
-          fill='#5865F2'
+          fill='currentColor'
           fillRule='nonzero'
         />
       </g>
@@ -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
 
@@ -57,7 +57,7 @@ Discord components in Sim Studio use efficient lazy loading, only fetching data
 
 ## Usage Instructions
 
-Connect to Discord to send messages, manage channels, and interact with servers. Automate notifications, community management, and integrate Discord into your workflows.
+Integrate Discord into the workflow. Can send and get messages, get server information, and get a user’s information. Requires bot API key.
 
 
 
@@ -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/en/tools/elevenlabs.mdx

@@ -33,13 +33,13 @@ 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 */}
 
 
 ## Usage Instructions
 
-Generate realistic speech from text using ElevenLabs voices.
+Integrate ElevenLabs into the workflow. Can convert text to speech. Requires API key.
 
 
 
@@ -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/en/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
+Integrate Exa into the workflow. Can search, get contents, find similar links, answer a question, and perform research. Requires API Key.
 
 
 
@@ -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/en/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.
+Integrate File into the workflow. Can upload a file manually or insert a file url.
 
 
 
@@ -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/en/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,14 +44,22 @@ 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 */}
 
 
 ## Usage Instructions
 
-Extract content from any website with advanced web scraping or search the web for information. Retrieve clean, structured data from web pages with options to focus on main content, or intelligently search for information across the web.
+Integrate Firecrawl into the workflow. Can search, scrape, or crawl websites. Requires API Key.
 
 
 
@@ -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/en/tools/generic_webhook.mdx

@@ -0,0 +1,32 @@
+---
+title: Webhook
+description: Receive webhooks from any service by configuring a custom webhook.
+---
+
+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/en/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.
+Integrate Github into the workflow. Can get get PR details, create PR comment, get repository info, and get latest commit. Requires github token API Key. Can be used in trigger mode to trigger a workflow when a PR is created, commented on, or a commit is pushed.
 
 
 
@@ -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/en/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.
+Integrate Gmail into the workflow. Can send, read, and search emails. Requires OAuth. Can be used in trigger mode to trigger a workflow when a new email is received.
 
 
 
@@ -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/en/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 into the workflow. Can create, read, update, and list calendar events. Requires OAuth.
 
 
 
@@ -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/en/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,13 +75,13 @@ 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 */}
 
 
 ## Usage Instructions
 
-Integrate Google Docs functionality to manage documents. Read content from existing documents, write to documents, and create new documents using OAuth authentication. Supports text content manipulation for document creation and editing.
+Integrate Google Docs into the workflow. Can read, write, and create documents. Requires OAuth.
 
 
 
@@ -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/en/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,13 +67,13 @@ 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 */}
 
 
 ## Usage Instructions
 
-Integrate Google Drive functionality to manage files and folders. Upload new files, get content from existing files, create new folders, and list contents of folders using OAuth authentication. Supports file operations with custom MIME types and folder organization.
+Integrate Google Drive into the workflow. Can create, upload, and list files. Requires OAuth.
 
 
 
@@ -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/en/tools/google_forms.mdx

@@ -0,0 +1,86 @@
+---
+title: Google Forms
+description: Read responses from a Google Form
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="google_forms"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"  xmlns='http://www.w3.org/2000/svg' viewBox='0 0 48 65' fill='none'>
+      <path
+        d='M29.583 0H4.438C1.997 0 0 1.997 0 4.438v56.208C0 63.086 1.997 65.083 4.438 65.083h38.458c2.44 0 4.437-1.997 4.437-4.437V17.75L36.979 10.354 29.583 0Z'
+        fill='#673AB7'
+      />
+      <path
+        d='M29.583 0v10.354c0 2.45 1.986 4.438 4.438 4.438h13.312L36.979 10.354 29.583 0Z'
+        fill='#B39DDB'
+      />
+      <path
+        d='M19.229 50.292h16.271v-2.959H19.229v2.959Zm0-17.75v2.958h16.271v-2.958H19.229Zm-3.698 1.479c0 1.224-0.995 2.219-2.219 2.219s-2.219-0.995-2.219-2.219c0-1.224 0.995-2.219 2.219-2.219s2.219 0.995 2.219 2.219Zm0 7.396c0 1.224-0.995 2.219-2.219 2.219s-2.219-0.995-2.219-2.219c0-1.224 0.995-2.219 2.219-2.219s2.219 0.995 2.219 2.219Zm0 7.396c0 1.224-0.995 2.219-2.219 2.219s-2.219-0.995-2.219-2.219c0-1.224 0.995-2.219 2.219-2.219s2.219 0.995 2.219 2.219Zm3.698-5.917h16.271v-2.959H19.229v2.959Z'
+        fill='#F1F1F1'
+      />
+      <defs>
+        <linearGradient
+          id='gf-gradient'
+          x1='30.881'
+          y1='16.452'
+          x2='47.333'
+          y2='32.9'
+          gradientUnits='userSpaceOnUse'
+        >
+          <stop stopColor='#9575CD' />
+          <stop offset='1' stopColor='#7E57C2' />
+        </linearGradient>
+      </defs>
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[Google Forms](https://forms.google.com) is Google's online survey and form tool that allows users to create forms, collect responses, and analyze results. As part of Google's productivity suite, Google Forms makes it easy to gather information, feedback, and data from users.
+
+Learn how to integrate the Google Forms tool in Sim to automatically read and process form responses in your workflows. This tutorial walks you through connecting Google Forms, retrieving responses, and using collected data to power automation. Perfect for syncing survey results, registrations, or feedback with your agents in real-time.
+
+With Google Forms, you can:
+
+- **Create surveys and forms**: Design custom forms for feedback, registration, quizzes, and more
+- **Collect responses automatically**: Gather data from users in real-time
+- **Analyze results**: View responses in Google Forms or export to Google Sheets for further analysis
+- **Collaborate easily**: Share forms and work with others to build and review questions
+- **Integrate with other Google services**: Connect with Google Sheets, Drive, and more
+
+In Sim, the Google Forms integration enables your agents to programmatically access form responses. This allows for powerful automation scenarios such as processing survey data, triggering workflows based on new submissions, and syncing form results with other tools. Your agents can fetch all responses for a form, retrieve a specific response, and use the data to drive intelligent automation. By connecting Sim with Google Forms, you can automate data collection, streamline feedback processing, and incorporate form responses into your agent's capabilities.
+{/* MANUAL-CONTENT-END */}
+
+## Usage Instructions
+
+Integrate Google Forms into your workflow. Provide a Form ID to list responses, or specify a Response ID to fetch a single response. Requires OAuth.
+
+
+
+## Tools
+
+### `google_forms_get_responses`
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| formId | string | Yes | The ID of the Google Form |
+| responseId | string | No | If provided, returns this specific response |
+| pageSize | number | No | Max responses to return (service may return fewer). Defaults to 5000 |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | json | Response or list of responses |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `google_forms`