PR Summary

Medium Risk
Adds a new external integration that makes live HTTP calls to Ketch’s public Web API and parses user-provided JSON, so failures/malformed inputs could surface at runtime. Changes are additive and isolated to new tools/registry entries with minimal impact on existing integrations.

Overview
Adds Ketch as a new integration across the product: new KetchBlock with configurable operations (get/set consent, get/set subscriptions, invoke rights) and wiring into the block registry.

Implements five new Ketch tools that call Ketch’s public Web API endpoints and normalizes responses/errors, plus shared types.ts for tool inputs/outputs.

Updates docs and UI plumbing: introduces KetchIcon, maps ketch in docs/landing icon mappings, adds ketch.mdx and includes ketch in tools meta.json and landing integrations.json.

^{Written by Cursor Bugbot for commit 166f53b. Configure here.}

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 26, 2026 10:45pm

Greptile Summary

This PR adds a Ketch privacy consent integration with 5 tools covering the full Ketch Web API surface: get/set consent, get/set subscriptions, and invoke data subject rights. The implementation follows all established patterns in the codebase — block config, tool files, type definitions, icon registration, docs, and registry entries are all present and correctly wired.

Key changes:

• New apps/sim/tools/ketch/ directory with 5 tool implementations and shared types
• apps/sim/blocks/blocks/ketch.ts block config with conditional sub-blocks per operation
• Icons added to both apps/sim/components/icons.tsx and apps/docs/components/icons.tsx
• Block and tool registrations in their respective registry.ts files
• Documentation page at apps/docs/content/docs/en/tools/ketch.mdx
• Integration metadata added to integrations.json

Minor issues found:

• The get_consent tool supports an optional purposes filter parameter, but the block's params function only passes purposes to the API for set_consent. There is also no corresponding UI sub-block for this filter in the get_consent context, so the filtering capability is silently unavailable to users.
• Error-path output objects across several tools (get_consent, get_subscriptions, set_subscriptions) include an untyped error field not declared in the TypeScript response interfaces, creating a minor type-safety gap.

Confidence Score: 4/5

Safe to merge; the integration is well-structured and follows all codebase conventions with only minor P2 issues.

All 5 tools are correctly implemented and registered. Error handling, 204 responses, and JSON body construction are handled properly throughout. The two flagged issues (unexposed get_consent filter and error-output type mismatch) are non-blocking and don't affect the primary user path.

apps/sim/blocks/blocks/ketch.ts (purposes filter wiring) and the error response shapes across the tool files.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant KetchBlock as Ketch Block (UI)
    participant Params as params()
    participant Tool as Tool Handler
    participant API as Ketch Web API (global.ketchcdn.com)

    User->>KetchBlock: Select operation + fill fields
    KetchBlock->>Params: Resolve tool name (ketch_${operation})
    Params->>Params: Merge jurisdictionCode / jurisdictionCodeOptional
    Params->>Params: Parse JSON fields (identities, purposes, topics, etc.)
    Params->>Tool: Dispatch to ketch_get_consent / set_consent / get_subscriptions / set_subscriptions / invoke_right

    alt get_consent
        Tool->>API: POST /web/v2/consent/{org}/get
        API-->>Tool: 200 { purposes, vendors }
    else set_consent
        Tool->>API: POST /web/v2/consent/{org}/update
        API-->>Tool: 200 { purposes } or 204 No Content
    else get_subscriptions
        Tool->>API: POST /web/v2/subscriptions/{org}/get
        API-->>Tool: 200 { topics, controls }
    else set_subscriptions
        Tool->>API: POST /web/v2/subscriptions/{org}/update
        API-->>Tool: 200
    else invoke_right
        Tool->>API: POST /web/v2/rights/{org}/invoke
        API-->>Tool: 200 { message } or 204 No Content
    end

    Tool-->>User: Structured output (purposes / topics / success / message)

_{Reviews (3): Last reviewed commit: "fix(ketch): include errorMessage in erro..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review

All greptile findings addressed:

• P1 Missing response.ok checks — fixed in 3790a4b, all 5 tools now guard on response.ok
• P1 Error messages silently discarded — fixed in 166f53b, error: errorMessage included in all error outputs
• P2 Registry alphabetical order — fixed in 3790a4b, ketch entries moved after jina_search
• Optional purposes filter not wired for get_consent — fixed in f42a763, added purposesFilter subBlock (advanced mode) and wired it in params