---
title: "Flowise OpenAI Custom Model node with a Base Path | BroadRouter"
description: "Use BroadNet Inference in Flowise chatflows with the OpenAI Custom Model node, a Base Path, an OpenAI API credential and a typed BroadNet model name."
url: https://broadrouter.com/guides/flowise-openai-compatible/
lang: en
updated: 2026-11-16
publisher: BroadRouter (a BroadNet site); API by BroadNet Inference, https://inference.broadnet.ai
---

# Connect Flowise to BroadNet Inference (OpenAI Custom Model)

Updated 2026-11-16

In a Flowise chatflow, add the OpenAI Custom Model chat model node. Connect an OpenAI API credential that holds your BroadNet key, type a BroadNet model ID such as broadnet/glm-5.3 in Model Name, and under Additional Parameters set Base Path to https://inference.broadnet.ai/v1. The node uses chat completions. Pick GLM 5.3 or Qwen3.8 27B for agents that call tools.

Flowise is an open-source, low-code builder for LLM apps and agents. Its **OpenAI Custom Model** chat model node is built for OpenAI-compatible APIs: you type the model name and set a base path. BroadNet Inference serves chat completions at `https://inference.broadnet.ai/v1`, so that node is the one to use. BroadRouter is BroadNet’s own site; the steps follow the node’s source in Flowise 3.1.4, because Flowise’s docs have no page for this node.

## Setup

1.  **Create a credential.** In Flowise, open **Credentials**, add an **OpenAI API** credential, name it “BroadNet” and paste your BroadNet key into **OpenAI Api Key**.
    
2.  **Add the node.** In a chatflow, add **Chat Models → OpenAI Custom Model**.
    
3.  **Fill in the node:**
    
    | Field | Value |
    | --- | --- |
    | Connect Credential | the BroadNet credential |
    | Model Name | `broadnet/glm-5.3` |
    | Temperature | 0.9 by default; lower it for extraction |
    | Streaming (Additional Parameters) | on (the default) |
    | Max Tokens (Additional Parameters) | 4000 |
    | Base Path (Additional Parameters) | `https://inference.broadnet.ai/v1` |
    
4.  **Connect it** to a chain or agent node, save, and send a test message in the chat panel. A reply means the key, URL and model name are right.
    

## What the fields do

-   **Model Name** is sent as the model ID. Type BroadNet’s ID with the `broadnet/` prefix. The node doesn’t fetch a model list, so BroadNet’s `/v1/models`, which listed only the transcription models when we checked on 16 November 2026, doesn’t get in the way.
-   **Base Path** becomes the client’s base URL. Flowise appends `/chat/completions`.
-   **Max Tokens** is sent as `max_tokens`. DeepSeek V4.1 Flash, GLM 5.3 and Qwen3.8 27B reason before they answer, and the reasoning counts toward it, so don’t set it low.
-   **Base Options** takes JSON headers to add to every request. BroadNet doesn’t need any.

## Why not the standard ChatOpenAI node?

The ChatOpenAI node also has a Base Path field, but in Flowise 3.1.4 its Model Name is a drop-down filled by a `listModels` method, with `gpt-4o-mini` as the default. The OpenAI Custom Model node has a free-text Model Name instead, and its source describes it as being for an “OpenAI Chat compatible API”, which is what BroadNet provides.

## Which model to pick

| Flow | Model |
| --- | --- |
| Tool agents, structured output parsers | `broadnet/glm-5.3` |
| Agents that read images or Arabic text | `broadnet/qwen3.8-27b` |
| Conversational and retrieval chains, long documents | `broadnet/deepseek-v4.1-flash` |
| Trying Flowise on the starting credit | `broadnet/gemma-4-26b-a4b` (32,768-token context) |

BroadNet’s docs list tools and structured output for GLM 5.3 and Qwen3.8 27B only. [Prices for every model](https://broadrouter.com/pricing/).

## How we tested this

We did not run a Flowise server. On 2026-11-15 we read the OpenAI Custom Model node’s source at the flowise@3.1.4 tag, then built the same `ChatOpenAI` object it builds, using `@langchain/openai` 1.2.5, the version Flowise 3.1.4 pins. We sent a streamed message and a tool call to a local mock server that speaks BroadNet’s chat-completions shape. Both requests went to `/v1/chat/completions` with the model ID `broadnet/glm-5.3` unchanged, a Bearer key, `max_tokens: 4000`, `temperature: 0.9` and `stream: true`, and the tool call came back parsed. We had no BroadNet key, so we did not test real model output. The field labels come from the source; check them against your Flowise version.

## Troubleshooting

-   **401.** The credential holds the wrong key, or the key is expired or out of allowance.
-   **404.** Base Path must end in `/v1`. Model Name must match BroadNet’s ID exactly. Paid models need a top-up; the $5 credit covers only `broadnet/gemma-4-26b-a4b` and the two Transcribe models.
-   **Empty replies.** Raise Max Tokens. [Why answers come back empty](https://broadrouter.com/guides/reasoning-tokens-empty-response/).
-   **The agent answers without using tools.** Switch to `broadnet/glm-5.3` or `broadnet/qwen3.8-27b`.
-   **429 under load.** A pay-as-you-go key allows 30 requests a minute and 4 in flight. See [errors and retries](https://broadrouter.com/guides/errors-and-retries/).

## Terms in this guide

[Token](https://broadrouter.com/glossary/token/)

A token is the unit of text a language model reads and writes: a word, part of a word, a punctuation mark or a byte sequence produced by the model's tokenizer. LLM APIs count, limit and usually bill usage in tokens.

[Pay-as-you-go](https://broadrouter.com/glossary/pay-as-you-go/)

Pay-as-you-go is a pricing model in which you pay only for what you use, metered per unit such as tokens, requests or audio minutes, with no subscription or minimum commitment. Most LLM APIs bill this way, from a prepaid balance or a periodic invoice.

[Structured output](https://broadrouter.com/glossary/structured-output/)

Structured output is an LLM API feature that constrains a model's reply to a format the developer specifies, usually a JSON Schema, so code can parse it reliably. It is stricter than JSON mode, which guarantees valid JSON but not a particular shape.

[Tool calling](https://broadrouter.com/glossary/tool-calling/)

Tool calling, also called function calling, is an LLM API feature in which the model returns a structured request to run a function the developer has defined, with JSON arguments. The application runs the function and sends the result back; the model never runs code itself.

[API key](https://broadrouter.com/glossary/api-key/)

An API key is a secret string that identifies and authorizes a client calling an API. LLM APIs usually expect it in an Authorization: Bearer header, and anyone who holds the key can make requests that are billed to the account that owns it.

[Base URL](https://broadrouter.com/glossary/base-url/)

A base URL is the fixed root address of an API, such as https://api.example.com/v1, that a client puts in front of every endpoint path, such as /chat/completions. In OpenAI-compatible SDKs, changing the base URL, together with the API key and model ID, points the same code at a different provider.

[Chat Completions API](https://broadrouter.com/glossary/chat-completions-api/)

The Chat Completions API is OpenAI's HTTP endpoint, POST /v1/chat/completions, that takes a model name and a list of role-tagged messages and returns the model's next message. Its request and response shape became the common format that OpenAI-compatible providers and SDKs reuse.

[Concurrency](https://broadrouter.com/glossary/concurrency/)

Concurrency is the number of requests a client has in flight at the same time. LLM APIs often cap it per key or plan, separately from requests per minute, because each open request holds GPU capacity until its response has finished.

## Questions

### Which Flowise node should I use for BroadNet?

OpenAI Custom Model (chatOpenAICustom). Its source describes it as a custom model using an OpenAI chat-compatible API. Model Name is a free-text field, so you can type a BroadNet ID, and Base Path changes the URL.

### Where is the Base Path field in Flowise?

It is an optional field on the OpenAI Custom Model node, shown under Additional Parameters. Set it to https://inference.broadnet.ai/v1, with /v1 and no further path.

### Which credential does the OpenAI Custom Model node use?

An OpenAI API credential (openAIApi). Create one with your BroadNet key as the API key. Flowise sends it as a Bearer token to the Base Path.

### Why does the default temperature look high?

The node defaults to temperature 0.9. Lower it for extraction or classification flows.

## Related guides

-   [Use BroadNet Inference in n8n (OpenAI credential, Base URL)](https://broadrouter.com/guides/n8n-openai-compatible/)
-   [Add BroadNet Inference to Dify with the OpenAI-API-compatible plugin](https://broadrouter.com/guides/dify-openai-api-compatible/)
-   [Why a reasoning model returns an empty answer](https://broadrouter.com/guides/reasoning-tokens-empty-response/)
-   [BroadNet Inference error codes and when to retry](https://broadrouter.com/guides/errors-and-retries/)
-   [All tools that work with BroadNet Inference](https://broadrouter.com/integrations/): SDKs, coding agents, chat UIs and automation tools, with exact settings for each

Try it on your real workload. New accounts start with $5 of credit for Gemma and transcription. DeepSeek, GLM and Qwen3.8 need a top-up.

[Get started](https://inference.broadnet.ai/account/?utm_source=broadrouter&utm_medium=referral&utm_campaign=guides-flowise-openai-compatible&utm_content=page-cta) ·

**Sources**

-   [Flowise source, OpenAI Custom Model node (ChatOpenAICustom.ts) at flowise@3.1.4 (checked 2026-11-15)](https://github.com/FlowiseAI/Flowise/blob/flowise%403.1.4/packages/components/nodes/chatmodels/ChatOpenAICustom/ChatOpenAICustom.ts)
-   [Flowise releases on GitHub, flowise@3.1.4 latest (checked 2026-11-15)](https://github.com/FlowiseAI/Flowise/releases)
-   [BroadNet Inference API reference (checked 2026-11-15)](https://inference.broadnet.ai/docs?utm_source=broadrouter&utm_medium=referral&utm_campaign=guides-flowise-openai-compatible&utm_content=sources)
