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

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Nov 30, 2025 7:39am

Greptile Overview

Greptile Summary

This PR adds Apify integration to Sim, enabling workflow automation and web scraping through Apify actors. It implements two tools: synchronous execution for quick tasks (max 5 minutes) and asynchronous execution with polling for long-running operations (up to 5 minutes of polling). The implementation includes proper error handling, dataset fetching, and parameter validation.

Key Changes:

• Added apify_run_actor_sync tool for synchronous actor execution with direct dataset retrieval
• Added apify_run_actor_async tool with 5-second polling intervals and configurable item limits (1-250,000)
• Created Apify block configuration with operation dropdown and conditional fields for async parameters
• Registered both tools in the tools registry and block in the blocks registry
• Added comprehensive documentation with usage examples and parameter tables
• Added ApifyIcon component and cleaned up unused icons (UsersIcon, SettingsIcon, Spinner, and 40+ other unused icons)
• API credentials correctly use user-only visibility per security guidelines

Implementation Quality:

• Follows established patterns in the codebase for tool and block configuration
• Proper TypeScript typing throughout
• Error handling for JSON parsing, API failures, and timeout scenarios
• Parameter validation (e.g., waitForFinish clamped to 0-60 seconds, itemLimit clamped to 1-250,000)
• Authorization headers use both Bearer token and query parameter for API compatibility

Confidence Score: 5/5

• This PR is safe to merge with no issues found
• The implementation follows established patterns, includes comprehensive error handling, proper TypeScript typing, and correctly implements security guidelines for API credentials. The code is well-structured, properly registered in all necessary registries, and includes thorough documentation. No logical errors, security vulnerabilities, or architectural concerns were identified.
• No files require special attention

Important Files Changed

File Analysis

Sequence Diagram

sequenceDiagram
    participant User
    participant Block as Apify Block
    participant Tool as Apify Tool
    participant API as Apify API
    participant Dataset as Apify Dataset

    User->>Block: Configure operation (sync/async)
    User->>Block: Provide API key & actor ID
    User->>Block: Set input parameters
    
    alt Synchronous Execution
        Block->>Tool: apify_run_actor_sync
        Tool->>API: POST /acts/{actorId}/run-sync-get-dataset-items
        API->>API: Execute actor
        API->>Dataset: Store results
        API-->>Tool: Return dataset items
        Tool-->>Block: Return success + items
        Block-->>User: Display results
    else Asynchronous Execution
        Block->>Tool: apify_run_actor_async
        Tool->>API: POST /acts/{actorId}/runs?waitForFinish=X
        API-->>Tool: Return run ID + initial status
        
        loop Poll every 5 seconds (max 5 minutes)
            Tool->>API: GET /acts/{actorId}/runs/{runId}
            API-->>Tool: Return run status
            alt Status is terminal (SUCCEEDED/FAILED/ABORTED/TIMED-OUT)
                break Exit polling loop
                end
            end
        end
        
        alt Run succeeded
            Tool->>Dataset: GET /datasets/{datasetId}/items?limit=X
            Dataset-->>Tool: Return items
            Tool-->>Block: Return success + items
            Block-->>User: Display results
        else Run failed/timed out
            Tool-->>Block: Return error status
            Block-->>User: Display error
        end
    end