feat(components): add extra_body support to OpenAI-compatible chat models by manaskumar3003 · Pull Request #6250 · FlowiseAI/Flowise

manaskumar3003 · 2026-04-20T04:28:11Z

feat(components): add extra_body support to OpenAI-compatible chat model nodes

Adds an "Additional Body Params (JSON)" input to all OpenAI-compatible
chat model nodes. The JSON is merged into LangChain's modelKwargs, which
is spread into the final request body sent to the provider — matching
the semantics of the OpenAI SDK's extra_body parameter.

Enables use cases such as vLLM-served Qwen3 models where reasoning
behavior is controlled via non-standard fields, e.g.:

{ "chat_template_kwargs": { "enable_thinking": false } }
Affected nodes: ChatOpenAI, ChatOpenAICustom, ChatLocalAI,
AzureChatOpenAI, ChatOpenRouter, ChatCerebras, ChatCometAPI,
ChatNvdiaNIM, ChatSambanova, ChatLitellm, ChatFireworks.

The field is optional and additive , existing flows are unaffected.
Invalid JSON throws a clear error at node init.

…del nodes Adds an "Additional Body Params (JSON)" input to all OpenAI-compatible chat model nodes. The JSON is merged into LangChain's modelKwargs, which is spread into the final request body sent to the provider — matching the semantics of the OpenAI SDK's extra_body parameter. Enables use cases such as vLLM-served Qwen3 models where reasoning behavior is controlled via non-standard fields, e.g.: { "chat_template_kwargs": { "enable_thinking": false } } Affected nodes: ChatOpenAI, ChatOpenAICustom, ChatLocalAI, AzureChatOpenAI, ChatOpenRouter, ChatCerebras, ChatCometAPI, ChatNvdiaNIM, ChatSambanova, ChatLitellm, ChatFireworks. The field is optional and additive — existing flows are unaffected. Invalid JSON throws a clear error at node init.

gemini-code-assist

Code Review

This pull request introduces an "Additional Body Params" (extraBody) input field to various chat model components, allowing users to merge custom JSON fields into the API request body. This feature is implemented across multiple nodes including AzureChatOpenAI, ChatOpenAI, and several others. The feedback provided suggests a minor code simplification for merging these additional parameters into the model configuration, as spreading null or undefined values within an object literal is natively safe and does not require a null-coalescing fallback.

gemini-code-assist · 2026-04-20T04:33:39Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:39Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:39Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:39Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:40Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:40Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:40Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:40Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:40Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

gemini-code-assist · 2026-04-20T04:33:40Z

+        if (extraBody) {
+            try {
+                const parsedExtraBody = typeof extraBody === 'object' ? extraBody : JSON.parse(extraBody)
+                obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }


According to the general rules, spreading null or undefined within an object literal is safe and does not require a ?? {} fallback. You can simplify this line.

Suggested change

obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }

obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

References

Spreading null or undefined within an object literal is safe and does not require a ?? {} fallback, as it evaluates to an empty object.

…delKwargs Spreading null/undefined inside an object literal is a no-op per spec, so `{ ...(obj.modelKwargs ?? {}), ...parsedExtraBody }` simplifies to `{ ...obj.modelKwargs, ...parsedExtraBody }`. Addresses review feedback from gemini-code-assist.

nehaaprasad · 2026-04-20T09:04:29Z

AI Code Trust — ship readiness

Score: 100 · Verdict: SAFE · Model: deterministic-v1

No blocking issues detected by automated checks.

Top issues:

maintainability (low) — Very long line reduces readability. packages/components/nodes/chatmodels/ChatLocalAI/ChatLocalAI.ts:99
maintainability (low) — Very long line reduces readability. packages/components/nodes/chatmodels/ChatOpenAI/ChatOpenAI.ts:217
maintainability (low) — Very long line reduces readability. packages/components/nodes/chatmodels/ChatOpenAICustom/ChatOpenAICustom.ts:125

manaskumar3003 mentioned this pull request Apr 20, 2026

Support additional request body parameters in OpenAI-compatible nodes #6055

Open

gemini-code-assist bot reviewed Apr 20, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(components): add extra_body support to OpenAI-compatible chat models#6250

feat(components): add extra_body support to OpenAI-compatible chat models#6250
manaskumar3003 wants to merge 2 commits intoFlowiseAI:mainfrom
manaskumar3003:feature/openai-extra-body-support

manaskumar3003 commented Apr 20, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

gemini-code-assist bot Apr 20, 2026

Uh oh!

nehaaprasad commented Apr 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	obj.modelKwargs = { ...(obj.modelKwargs ?? {}), ...parsedExtraBody }
	obj.modelKwargs = { ...obj.modelKwargs, ...parsedExtraBody }

Uh oh!

Conversation

manaskumar3003 commented Apr 20, 2026

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Apr 20, 2026

Choose a reason for hiding this comment

Uh oh!

nehaaprasad commented Apr 20, 2026

AI Code Trust — ship readiness

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants