> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/appmixer-studio-features/flow-examples.md).

# Flow examples

By now, you should already know [what a flow means](/kb/appmixer-studio-features/what-is-flow.md), how you can [create one](/kb/appmixer-studio-features/creating-a-flow.md) and [share it with your colleagues](/kb/appmixer-studio-features/sharing-a-flow.md). As we already said, the sky is the limit in terms of flow complexity. Being able to use an unlimited number of components in a single flow, there is probably no business process that can not be designed and automated in Appmixer.

Let's go through some examples of how flows can be used, and most importantly, how they can help you automate processes and sync data between different platforms.

{% content-ref url="/pages/-Mf2wV\_KpyaTvRybDz3x" %}
[Forward customer support calls based on PIN](/kb/appmixer-studio-features/flow-examples/forward-customer-support-calls-based-on-pin.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mf2yaHmSRCNYnfRAcxF" %}
[Feed customer data to Mailchimp](/kb/appmixer-studio-features/flow-examples/feed-customers-to-mailchimp.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mf2ycK2wmhZNep7wsJW" %}
[Google Drive document approvals](/kb/appmixer-studio-features/flow-examples/google-drive-document-approvals.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.appmixer.com/kb/appmixer-studio-features/flow-examples.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.