> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/components-and-data/connections/using-connections-in-flows.md).

# Using Connections in Flows

Connections are used in flows when configuring a networking node to communicate with an external system using HTTP, Kafka, or Pulsar.

The following node types support the use of Contextual Connections:

* Contextual HTTP Nodes
  * HTTP GET
  * HTTP POST
  * HTTP PUT
  * HTTP PATCH
  * HTTP DELETE
* GraphQL (GQL) Node
* Produce Message Node

Note that other (legacy) Node-RED nodes such as "HTTP Request" do not use Connections and require you to configure the URL, Authentication strategy, and headers as part of the node configuration.

The advantage of using the Contextual nodes listed above is that you do not need to be concerned about the details of how the API will be used in terms of URL or authentication, nor do you have to be concerned about token renewal for connection types that require it.

In a Contextual node that uses connections, you simply select the connection from the list as shown in the image below.

<figure><img src="https://2803907488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJF7AoTYz7NHacejws5p9%2Fuploads%2Fgit-blob-4cba0c78f10fb8aa0b589a4b043e0160447c91c9%2FScreenshot%202024-08-01%20at%2010.00.34.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.contextual.io/documentation-and-resources/components-and-data/connections/using-connections-in-flows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.