HTTP Request Connection
The httpRequestConnection config node stores shared connection settings for
one or more HTTP Request nodes.
Properties
Section titled “Properties”| Property | Purpose |
|---|---|
| Name | Friendly label shown in HTTP Request connection selectors. |
| Base URL | API root joined with each HTTP Request node’s Path. |
| Auth Type | None, Basic, or Token. |
| Username | Username used by Basic authentication. |
| Password | Password used by Basic authentication. |
| Token Type | Authorization scheme, such as Bearer. |
| Token Value | Credential used by Token authentication. |
| Headers | Default key-value headers included with every request. |
The default headers include Content-Type: application/json. Add only headers
that should apply to every HTTP Request node using this connection.
Authentication
Section titled “Authentication”Basic sends an Authorization header containing the configured username
and password.
Token sends:
Authorization: <Token Type> <Token Value>Passwords and token values are stored as Node-RED credentials.
Shared Configuration
Section titled “Shared Configuration”A connection can be reused by multiple HTTP Request nodes. This is useful when several actions call the same API with different paths or methods.
Changing the Base URL, authentication, or headers affects every request node that references the connection. Review those dependent nodes before changing a shared production connection.
Security
Section titled “Security”- Do not place passwords or tokens in ordinary header values when a credential field is available.
- Do not expose connection credentials through flow messages, logs, screenshots, or agent tool results.
- Use separate connections when APIs require different trust boundaries or credentials.