automation: a connector_action node's connectorConfig.input is handed to the provider as written — a CEL envelope there passes os validate and is never evaluated, so a flow cannot send a per-record value to a declarative connector #27327

epic:#27293#1 · sunhaolin · session_017xRBcVBKAFk1ntXSjvPt7U

Filing gate: ① a product defect with a named location, finding class (c) (a trap that leads an AI author to write metadata the runtime silently does not honour). Found by the os-dev on #27223 (PR #27322) and re-measured by this seat. Child of #27293 (the declarative-integration road). ⛔ Not a claim.

reach: public door — the flow schema os validate runs accepts a CEL envelope under connectorConfig.input (the #27223 dev's FlowSchema.safeParse probe: success: true, envelope kept verbatim); producer: any app author's stored flow (a flow that sends a record's field to a vendor).

The defect

• packages/services/service-automation/src/builtin/connector-nodes.ts:108: handler((cfg.input ?? {}) as Record<string, unknown>, handlerCtx). The input goes to the provider exactly as authored.
• packages/services/service-automation/src/builtin/value-slot-map.ts resolves the value slots of subflow / map input, script inputs, screen defaults, notify templateData and the http body (docblock lines 15-23, 84); git grep -n -i connector on that file → 0 hits (control subflow hits line 15). Nothing in the history marks the connector slot as excluded on purpose ([v18] retire the {var} template dialect in flow assignment slots: refuse at registration with per-spelling remedies (the C half of #11182 ruling D, on the v18 train) #19939, the value-slot card, never mentions connectors).
• Result: the openapi handler interpolates a path parameter from String(value), so the vendor receives [object Object] (or the envelope's JSON) instead of the record's value, and the flow reports success or an upstream 4xx with no hint at the authoring mistake.

Read at origin/main 65b49208, 2026-10-28T16:40Z.

Business reason

Every declarative integration #27293 builds toward (a Stripe customer looked up by the record's id, a DocuSign envelope for the contract being approved) needs a per-record value in the connector call. Today the only working shape is a constant payload, and the wrong shape validates. #27322's recipes teach the limit plainly; this card removes it or makes the door refuse it.

Reader

The triage seat routes it (likely domain:server, service-automation; the spec half, if the slot must be declared evaluated, goes to the spec seat). Direction is enforce-or-remove: evaluate connectorConfig.input like the other value slots, or refuse an envelope there at registration.

Dedupe

• Semantic search "connector_action input not evaluated CEL expression flow variable passed verbatim to connector provider value slot", all states: 5 hits, none this defect ([finding] a connector_action flow node with no connectorConfig passes all three build doors and fails every run #20418 closed: a node with no connectorConfig; service-automation: evaluate a value-role CEL envelope in the assignment executor and validate it at registerFlow — the executor half of #14149 (spec half landed in PR #15113) #15137 closed: assignment executor; spec: the evaluated-slot rule of #15430 reaches only the flow-node ledger — every other ExpressionInputSchema slot an engine evaluates (formula expression, validation / hook / sharing condition, visibleWhen…) still accepts an ast-only or blank-source envelope #15811 closed: other ExpressionInputSchema slots; automation: connector triggers start flows, and a connector action's description / outputSchema reach the flow designer (7 keys) #20287, Bare-string flow conditions bypass the CEL engine and silently string-compare — wrong branches, no error #4336 closed).