> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/docs/frends-6.1.0/get-started/getting-started-guide/integration-development-part-2.md).

# Integration Development, Part 2

Next part for Integration Development path.

## Introducing the building blocks for Processes

Now that we have a functional Process that we're able to run and test, let's add some more complexity to it by introducing you the different building blocks available in Frends.

### Shape 1

Tähän reusable referencestä tälle shapelle.

### Shape 2

Tähän reusable referencestä tälle shapelle.

### Shape 3

Tähän reusable referencestä tälle shapelle.

## More features

Once you get going with multiple Processes and Environments, these features will help you out immensively.

### Creating and using Subprocesses

reusable

### How to use Environment Variables

reusable opas


---

# 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.frends.com/docs/frends-6.1.0/get-started/getting-started-guide/integration-development-part-2.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.