> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/automation/workflows/http-module.md).

# HTTP Module

The HTTP module connects your automation to virtually any external service on the internet. You pick the method you need — the module handles the rest.

### What you can do with it

* **Fetch data from outside** — for example, pull current exchange rates or weather data.
* **Send data out** — for example, post an update to social media.
* **Trigger other systems** — for example, kick off a workflow in another tool.

Whenever a pre-built component doesn't cover your use case, HTTP is your tool to close that gap yourself.

### HTTP methods at a glance

| Method     | What it does                                                                                                   |
| ---------- | -------------------------------------------------------------------------------------------------------------- |
| **GET**    | Retrieves data without changing anything. Example: fetch the current Bitcoin price and have it emailed to you. |
| **POST**   | Creates new data in an external system.                                                                        |
| **PUT**    | Updates existing data or records.                                                                              |
| **DELETE** | Removes data from an external system.                                                                          |

### Additional building blocks

* **RESPONSE** — sends a response back to the service that triggered the request. Useful for confirming receipt or reporting back a result.
* **UPTIME** — regularly checks whether a website or service is reachable, and notifies you if its status changes.

### How to set it up

1. **Check the API docs.** What endpoints exist, which method do you need, which parameters are required?
2. **Build the request.** In the HTTP module, set:
   * **URL** — the target endpoint
   * **Method** — GET, POST, PUT, or DELETE
   * **Headers** — e.g. authorization token, content type
   * **Body** — the data you're sending (if needed)
3. **Process the response.** The response usually comes back as JSON or XML. Extract the relevant values and use them in the next steps of your automation.

> **Tip:** Test new requests with a small amount of sample data first, before building them into a live automation — that way you'll immediately spot if headers or the body aren't set up right.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hub.equipme.io/equipme/automation/workflows/http-module.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.