> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/appcademy/appfarm-fundamentals/integration-fundamentals.md).

# Integration Fundamentals

Fundamentals level Module in Integrations

This Module covers the basic use cases for integrating with external systems, using the Action Node **Web Request. Web Request** is used for integrations, and you may use it to push data to an external endpoint (POST/PUT requests) or get data from an external endpoint (GET request)**.**

The **Web Request** Action Node may be used both from Apps or from Services. E.g. you may have an App with a Button for looking up a company organization number from an external endpoint, or you may have a Service that runs nightly for fetching all new/modified customers from an external endpoint (and saves them). Both of these scenarios use the Web Request action node, and the technical setup is in general the same - regardless of whether the Web Request is triggered from an App or a Service.

### Topics in this Module

{% content-ref url="/pages/sJaR7hPk0HoGfyC0AP9p" %}
[The web request action node](/appcademy/appfarm-fundamentals/integration-fundamentals/the-web-request-action-node.md)
{% endcontent-ref %}

{% content-ref url="/pages/gyaxAAlKwEfDJwIxEh8d" %}
[Fetch data from an endpoint](/appcademy/appfarm-fundamentals/integration-fundamentals/fetch-data-from-an-endpoint.md)
{% endcontent-ref %}

{% content-ref url="/pages/YEl8N7Sm8vvMSo6eQp9x" %}
[Map data to a data source](/appcademy/appfarm-fundamentals/integration-fundamentals/map-data-to-a-data-source.md)
{% endcontent-ref %}

{% content-ref url="/pages/iSmNjnyyBsBBXd4VNdSa" %}
[Modify the response](/appcademy/appfarm-fundamentals/integration-fundamentals/modify-the-response.md)
{% endcontent-ref %}

{% content-ref url="/pages/96v1FRMyLsRiCpu0XHM6" %}
[Nested data mapping](/appcademy/appfarm-fundamentals/integration-fundamentals/nested-data-mapping.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZDAlqRF0RPnjLo327Bz2" %}
[Authentication](/appcademy/appfarm-fundamentals/integration-fundamentals/authentication.md)
{% endcontent-ref %}

{% content-ref url="/pages/RmNlk7j7T2CnZWWYITx1" %}
[Send data to an endpoint](/appcademy/appfarm-fundamentals/integration-fundamentals/send-data-to-an-endpoint.md)
{% endcontent-ref %}


---

# 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.appfarm.io/appcademy/appfarm-fundamentals/integration-fundamentals.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.