> For the complete documentation index, see [llms.txt](https://feniks.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://feniks.gitbook.io/doc/feniks/cloud.md).

# Cloud

Feniks has Google Drive and Telegram integration for now. Microsoft OneDrive, Dropbox and Amazon S3 integration is on the way. You can set up your cloud integration under the Configuration > Cloud Tab.

<figure><img src="/files/UurkXF1OkHIzYdC3eyKp" alt=""><figcaption></figcaption></figure>

Setting up the Telegram Integration is easy. Just input the Token and URl field correctly and you are ready to go. To start a bot subscription just write a ‘/start’ message and send it to your telegram bot. After that you will be getting AI detected images.

Google Drive integration is a little bit more difficult since it requires 2 steps. First, you need to enter Credentials Json and Auth Code. The cloud integration service uses these values to get a valid Token Json from Google If those fields were set correctly. The second step is done by the cloud integration service itself. You will see Token Json and URL fields in read only mode If everything goes as expected.&#x20;

Feniks save AI images to Google Drive as daily indexed directories as shown below:

<br>

<figure><img src="/files/BjRNZDWa7GTtcnADDILb" alt=""><figcaption></figcaption></figure>

<br>


---

# 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://feniks.gitbook.io/doc/feniks/cloud.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.