Greptile Summary

Added comprehensive Jotform integration supporting both webhook triggers and API-based operations.

Key Changes:

• Webhook Support: Added multipart/form-data parsing to webhook processor (processor.ts:79-102) to handle Jotform's webhook format, with fallback for both rawRequest field and direct form field extraction
• Three API Tools: Implemented submissions, get_form, and list_forms tools for retrieving form data via Jotform API
• API Key Authentication: All tools correctly use visibility: 'user-only' for API key parameters, following custom instruction 2851870a (user-provided credentials should use user-only, not hidden)
• Webhook Trigger: Created webhook trigger with proper output structure using webhook.data.payload.* for accessing form fields with dynamic IDs (e.g., q3_q3_email1)
• Registry Integration: Properly registered in blocks, tools, and triggers registries with Jotform brand icon

Technical Implementation:

• Tools use GET requests with API key in query string following Jotform's API conventions
• Webhook processor enhancement is backward-compatible, only activating for multipart/form-data content type
• Block configuration supports both trigger mode (webhooks) and block mode (API operations) with conditional field visibility
• Network policy change (adding custom egress rules support) is unrelated to Jotform but included in same commit

Testing Confirmed:
Per PR description, end-to-end webhook testing was completed with live Jotform submissions via ngrok tunnel, and all three API tools are verified accessible in UI.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Implementation follows established patterns consistently across the codebase, uses proper authentication visibility (user-only for API keys per custom instructions), includes comprehensive error handling in webhook processor, and has been thoroughly tested end-to-end per PR description. The multipart/form-data parsing is backward-compatible and only activates for the specific content type.
• No files require special attention

Important Files Changed

Sequence Diagram

sequenceDiagram
 participant User as User (Jotform)
 participant Jotform as Jotform Service
 participant Webhook as Webhook Endpoint
 participant Processor as Webhook Processor
 participant Parser as multipart/form-data Parser
 participant DB as Database
 participant Queue as Task Queue
 participant Executor as Workflow Executor
 
 User->>Jotform: Submit form
 Jotform->>Webhook: POST /api/webhooks/{path}<br/>(multipart/form-data)
 Webhook->>Processor: parseWebhookBody()
 Processor->>Parser: Parse Content-Type: multipart/form-data
 
 alt Has rawRequest field
 Parser->>Parser: JSON.parse(rawRequest)
 else Direct form fields
 Parser->>Parser: Convert FormData to object
 end
 
 Parser-->>Processor: Return parsed body
 Processor->>DB: Find webhook by path
 DB-->>Processor: Return webhook + workflow config
 Processor->>Processor: checkWebhookPreprocessing()<br/>(rate limits, deployment)
 Processor->>Queue: Queue webhook execution
 Queue-->>Webhook: Return 200 OK
 Queue->>Executor: Execute workflow with webhook.data.payload
 Executor->>Executor: Access form fields<br/>(e.g., webhook.data.payload.q3_email1)