improvement(triggers): revert to start block

[icecrasher321]

Summary

Bring start block back consolidating API, Chat, Input Form, Manual triggers into Start Block.

Type of Change

• Other: Platform Improvement

Testing

Manually across all legacy triggers + new start block with @aadamgough

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)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Skipped			Oct 31, 2025 7:22pm

[greptile-apps]

Greptile Overview

Greptile Summary

This PR introduces a unified Start block that replaces separate API, Chat, Input Form, and Manual triggers. The Start block handles all three execution contexts (manual editor runs, API deployments, and chat deployments) through a single interface.

Key Changes:

• Added new start_trigger block with reserved fields (input, conversationId, files) and extensible inputFormat sub-block
• Legacy trigger blocks (api_trigger, chat_trigger, input_trigger, manual_trigger) marked as legacy and hidden from toolbar
• Executor updated to pass through entire API payload for start_trigger while ensuring reserved fields are set
• API execution route changed from input: body.input || body to input: body for full payload access
• Status API now gracefully handles empty workflows instead of returning errors
• Deploy modal and workflow execution hooks updated to prioritize start_trigger over legacy triggers
• Documentation updated to recommend Start block as the primary trigger

Issues Found:

• Date.now() in control-bar's useMemo dependency breaks memoization, causing constant recomputation and defeating the debounce optimization

Confidence Score: 4/5

• Safe to merge with one performance issue to address in control-bar
• The PR is well-structured with comprehensive backward compatibility for legacy triggers. The logic is sound and consistently applied across executor, API routes, and UI components. Score reduced by 1 due to the Date.now() performance bug in control-bar.tsx that defeats debouncing.
• apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/control-bar/control-bar.tsx requires fixing the Date.now() issue on line 274

Important Files Changed

File Analysis

Filename	Score	Overview
apps/sim/blocks/blocks/start_trigger.ts	5/5	New unified start block config with input, conversationId, files fields for chat/manual/API runs
apps/sim/lib/workflows/triggers.ts	5/5	Updated trigger utilities to support start_trigger for all execution types (chat/manual/API)
apps/sim/executor/index.ts	4/5	Added start_trigger handling with pass-through payload logic and reserved field enforcement
apps/sim/app/api/workflows/[id]/execute/route.ts	5/5	Changed input extraction to pass entire body, prioritizes start_trigger over api_trigger
apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/control-bar/control-bar.tsx	3/5	Added debounced status check trigger using useMemo and useDebounce, but Date.now() breaks memoization

Sequence Diagram

sequenceDiagram
    participant User
    participant Editor
    participant API as Execute API
    participant Executor
    participant StartBlock as Start Trigger Block
    
    alt Manual Run from Editor
        User->>Editor: Click Run
        Editor->>Editor: Extract test values from inputFormat
        Editor->>API: POST /api/workflows/{id}/execute
        Note over API: body = { input: testValues, ... }
    end
    
    alt API Deployment Call
        User->>API: POST /api/workflows/{id}/execute
        Note over API: body = { customField: value, ... }
    end
    
    alt Chat Deployment
        User->>API: POST /api/workflows/{id}/execute
        Note over API: body = { input: message, conversationId, stream: true }
    end
    
    API->>API: Load deployed workflow blocks
    API->>API: Find start_trigger or api_trigger
    API->>API: Extract inputFormat schema
    API->>API: Pass entire body as input
    
    API->>Executor: Execute workflow
    Note over API,Executor: workflowInput = entire body
    
    Executor->>Executor: Find start_trigger block
    
    alt With inputFormat defined
        Executor->>Executor: Structure input per schema
        Executor->>Executor: Apply type coercion
        Executor->>StartBlock: Initialize with structured fields
    end
    
    alt Without inputFormat
        Executor->>StartBlock: Pass through entire payload
    end
    
    Executor->>StartBlock: Ensure reserved fields
    Note over StartBlock: input: '' (default)<br/>conversationId: '' (default)<br/>files: [] (optional)
    
    StartBlock->>Executor: Output with all fields
    Executor->>Executor: Execute downstream blocks
    Executor->>API: Return execution results
    API->>User: Response

Loading

_{19 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[waleedlatif1]

@icecrasher321 need to update docs as well to reflect this