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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 14, 2026 12:51am

PR Summary

Medium Risk
Touches multiple public execution entry points and billing resolution; misconfiguration of flags or entitlement logic could block paid workspaces or leave free programmatic access open until the gate is enabled.

Overview
Adds a dark-rollout paywall for programmatic workflow execution on hosted when BILLING_ENABLED and FREE_API_DEPLOYMENT_GATE_ENABLED are both on. New helpers isApiExecutionEntitled / isWorkspaceApiExecutionEntitled check the workspace billed account’s plan (with org subscription rollup).

API enforcement: Workflow execute (API key and public access), MCP serve, A2A serve, and generic webhook triggers return 402 with a shared upgrade message when the workspace is on free. Provider webhooks are unchanged. Chat adds assertChatEmbedAllowed on GET/POST: cross-origin embeds (non–*.sim.ai / app URL) get 403 unless the workspace is paid; first-party and missing Origin are not gated.

Product UI: Deploy modal API/MCP/A2A tabs show DeployUpgradeGate for free users (after subscription loads); tab footers hide while gated. Upgrade copy updates (Pro feature “Deploy workflows as APIs”; comparison table shows 0 API endpoints on Free).

Tests cover entitlement helpers, embed rules, and route 402/403 behavior.

^{Reviewed by Cursor Bugbot for commit 9687476. Bugbot is set up for automated code reviews on this repo. Configure here.}

@greptile review

Greptile Summary

This PR gates programmatic workflow execution (API key, public API, MCP server, A2A agent server, generic webhooks, cross-origin chat embeds) behind a paid plan on hosted deployments, returning 402 for free-plan callers. Provider webhooks (Slack, GitHub, etc.), session-based runs, and self-hosted deployments are explicitly left unaffected.

• New isApiExecutionEntitled / isWorkspaceApiExecutionEntitled helpers in lib/billing/core/api-access.ts gate each route on the workspace billed account (consistent across all programmatic surfaces), guarded by a dual feature flag (BILLING_ENABLED + FREE_API_DEPLOYMENT_GATE_ENABLED) for dark rollout.
• The execute route was corrected to gate on wf.workspaceId rather than wf.userId (the workflow creator), matching the workspace-scoped approach used by MCP/A2A/webhooks.
• The deploy modal adds an upgrade gate component (DeployUpgradeGate) for API/MCP/A2A tabs with a loading-state guard to prevent flashing the wall at paid users before the subscription query resolves.

Confidence Score: 4/5

Safe to merge for security correctness; one UI/API mismatch in the deploy modal should be addressed before the dark-rollout flag is used in production.

All API routes correctly gate on the workspace billed account and return 402. The one concrete defect is in the deploy modal: its gate condition reads NEXT_PUBLIC_BILLING_ENABLED but not the new server-only FREE_API_DEPLOYMENT_GATE_ENABLED, so during the intended dark-rollout phase (billing on, gate off) the upgrade wall appears in the UI while the API still accepts free-plan requests. No unauthorised execution is possible — the API enforcement is sound — but users would see conflicting signals.

apps/sim/app/workspace/.../deploy-modal/deploy-modal.tsx — the gateProgrammaticDeploy condition needs a client-accessible counterpart of FREE_API_DEPLOYMENT_GATE_ENABLED to stay in sync with the API gate during dark rollout.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Incoming request] --> B{Auth type?}
    B -->|Session / Internal JWT| Z[Proceed - not gated]
    B -->|API key| C[isWorkspaceApiExecutionEntitled]
    B -->|Public API| C
    B -->|MCP serve| C
    B -->|A2A serve| D[isApiExecutionEntitled via billedUserId]
    B -->|Generic webhook| C
    B -->|Cross-origin chat embed| C

    C --> E{isBillingEnabled AND isFreeApiDeploymentGateEnabled?}
    D --> E
    E -->|No - self-hosted or gate off| Z
    E -->|Yes| F[getWorkspaceBilledAccountUserId]
    F -->|null| Z2[Fail-open - allow]
    F -->|userId| G[getHighestPrioritySubscription]
    G -->|paid plan| Z
    G -->|free / null| H[Return 402 / 403]

    style H fill:#f66,color:#fff
    style Z fill:#6a6,color:#fff
    style Z2 fill:#fa6,color:#fff

_{Reviews (6): Last reviewed commit: "feat(billing): add FREE_API_DEPLOYMENT_G..." | Re-trigger Greptile}

@greptile review

Greptile Summary

This PR gates programmatic workflow execution (API key, public execute, MCP, A2A, generic webhooks, cross-origin chat embeds) behind a paid plan on hosted deployments, returning 402/403 for free-tier accounts. New isApiExecutionEntitled / isWorkspaceApiExecutionEntitled helpers centralize the billing check, the deploy modal shows an upgrade prompt instead of the configuration tabs for free users, and the upgrade page copy is updated to reflect the restriction.

• lib/billing/core/api-access.ts introduces two entitlement helpers (self-hosted and missing-identity always pass); each route integrates the appropriate variant with good test coverage.
• The webhook route gates generic webhooks inside the per-webhook fan-out loop; the continue path leaves responses empty when all entries are blocked, resulting in a 500 instead of 402.
• The deploy modal derives gateProgrammaticDeploy from isFree(subscriptionData?.data?.plan) without guarding for the loading state, so paid users briefly see the upgrade gate while the subscription query resolves.

Confidence Score: 4/5

The core billing helpers and most route integrations are correct and well-tested; the two points of concern are an error-response regression in the multi-webhook fan-out path and a visual flash in the deploy modal that does not affect backend enforcement.

The webhook fan-out loop silently swallows 402 responses when multiple generic webhooks are all blocked, returning a misleading 500 to the caller. This is a real, reproducible failure: any credential-set fan-out with every entry being a blocked generic webhook triggers it. The execute route also uses the workflow creator's user ID for the public-API billing check rather than the workspace billing account, which could mismatch after org membership changes.

apps/sim/app/api/webhooks/trigger/[path]/route.ts — the fan-out billing gate; apps/sim/app/api/workflows/[id]/execute/route.ts — the public-API billing identity.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Incoming programmatic request] --> B{Route type?}
    B -->|API key / public execute| C[execute/route.ts]
    B -->|MCP server| D[mcp/serve/route.ts]
    B -->|A2A agent| E[a2a/serve/route.ts]
    B -->|Webhook| F[webhooks/trigger/route.ts]
    B -->|Chat embed| G[chat/utils.ts assertChatEmbedAllowed]
    C --> H{isApiExecutionEntitled userId}
    D --> I{isWorkspaceApiExecutionEntitled workspaceId}
    E --> J{isApiExecutionEntitled billedUserId}
    F --> K{provider === generic?}
    G --> L{isHosted AND cross-origin?}
    K -->|yes| M{isWorkspaceApiExecutionEntitled workspaceId}
    K -->|no provider webhook| N[Allow]
    H -->|not entitled| O[402]
    I -->|not entitled| O
    J -->|not entitled| O
    M -->|not entitled single webhook| O
    M -->|not entitled multi webhook| P[continue - may produce 500]
    L -->|yes| Q{isWorkspaceApiExecutionEntitled}
    H -->|entitled| R[Execute]
    I -->|entitled| R
    J -->|entitled| R
    M -->|entitled| R
    Q -->|not entitled| S[403]
    Q -->|entitled| R
    L -->|same origin| R

_{Reviews (2): Last reviewed commit: "test(billing): mock api-execution gate i..." | Re-trigger Greptile}

@greptile review

Addressed the Bugbot/Greptile findings in 57a0f47:

• Execute gates on caller's personal plan (High / P2): switched the execute route to gate on the workflow's workspace billed account (isWorkspaceApiExecutionEntitled), matching MCP/A2A/webhooks/chat. A paid workspace is no longer 402'd because the key holder / public-API workflow creator is on free.
• Multi-generic-webhook fan-out 500 (Medium / P1): all-generic-all-free now returns 402, not the No webhooks processed 500 fallback. Added a fan-out test.
• Deploy modal gate flash (P1/P2): gate is held closed until the subscription query resolves (isFree(undefined) is true), so paid users don't see an upgrade-wall flash.

Intentionally left as-is:

• Fail-open on missing billing identity (Bugbot High): the helpers allow when workspaceId/billed account can't be resolved. This is a deliberate fail-open for a revenue gate (not a security boundary) so a data gap never blocks a legitimate run; the affected entities (server.workspaceId, etc.) are non-null in practice and a workflow with no workspace can't execute anyway.
• Deploy modal uses viewer plan, not workspace billed account (Bugbot Medium): the client uses useSubscriptionData (the viewer's rolled-up plan) as a best-effort hint; the server is the source of truth and enforces the workspace-billed-account check. Resolving the workspace billing account client-side isn't worth the extra surface for a UI affordance.

Re-review on 57a0f47 re-raised a few items — status:

Already fixed in 57a0f47 (stale re-raises):

• "Workspace keys use wrong billing" (execute) — execute now gates on isWorkspaceApiExecutionEntitled(gateWorkspaceId) (the workflow's workspace billed account), not the caller's userId. See route.ts L441-461.
• "Multiple generic webhooks return 500" — now tracked via billingBlocked and returns 402 when the loop ends empty for that reason. Covered by a new fan-out test.

Fail-open findings (api-access.ts L39, chat utils L87) — not a real leak, leaving as-is:
workspace.billedAccountUserId is NOT NULL (schema.ts L1231-1233), so getWorkspaceBilledAccountUserId never returns null for a real workspace. The only path that fail-opens is a missing/archived workflow (no workspaceId), which can't execute or serve a chat anyway. So there's no paid-bypass; denying there would only add a failure mode for already-broken state.

@greptile review

@greptile review

Both Bugbot items on the latest commit are re-raises of already-addressed findings (Bugbot re-reviews the full diff each push):

• execute "wrong billing" — fixed in 57a0f47: the gate now calls isWorkspaceApiExecutionEntitled(gateWorkspaceId) (workspace billed account), not the caller's userId. See route.ts L446-461.
• "missing billing identity" (fail-open) — not a real leak: workspace.billedAccountUserId is NOT NULL, so the only fail-open path is a missing/archived workflow that can't execute anyway.

No new changes needed.