> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhc2/general/tutorials.md).
# Tutorials
The tutorials section of iX Hello Customer v2 contains concise instructions for new users to get started quickly with basic features.
## 1. Build, validate and test a simple flow.
The starting point to learn about the [Flow Editor](/ixhc2/flows/flow-editor.md) of Customer v2. Learn how to add and configure nodes, validate what you've built, and how to test and tweak your flow.
Go to tutorial
## 2. Open Meteo REST API
A hands-on tutorial about configuring a REST API with two methods, which can be reused across multiple Flows by using variable substitution.
Go to tutorial
## 3. Weather flow with Open Meteo API
Combine your knowledge about Flow building and Rest API configuration in this agentic Weather flow, which retrieves the weather forecast based on input of the user.
Go to tutorial
## 4. MCP Connection Setup
The MCP integration behaves similarly to existing integrations such as REST—however, MCP connections follow a fixed structure aligned with the MCP standard.
Go to tutorial
---
# 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://docs.ixhello.com/ixhc2/general/tutorials.md?ask=&goal=
```
`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.