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

# How to

* [Inserir JSON em bancos de dados](https://docs.skyone.cloud/skyone-studio/how-to/inserir-json-em-bancos-de-dados.md)
* [Flattening: Transformação de dados utilizando JSONata](https://docs.skyone.cloud/skyone-studio/how-to/flattening-transformacao-de-dados-utilizando-jsonata.md)
* [Como utilizar o Form Data](https://docs.skyone.cloud/skyone-studio/how-to/como-utilizar-o-form-data.md)
* [Entendendo a recursividade no JSONata](https://docs.skyone.cloud/skyone-studio/how-to/entendendo-a-recursividade-no-jsonata.md)
* [Consolidação de output de módulos REST](https://docs.skyone.cloud/skyone-studio/how-to/consolidacao-de-output-de-modulo-rest.md)
* [Como configurar um timeout de um componente?](https://docs.skyone.cloud/skyone-studio/how-to/como-configurar-um-timeout-de-um-componente.md)
* [Isolar na execução: conceito e aplicação em variáveis](https://docs.skyone.cloud/skyone-studio/how-to/isolar-na-execucao-conceito-e-aplicacao-em-variaveis.md)
* [Parâmetros de URL no API Gateway](https://docs.skyone.cloud/skyone-studio/how-to/parametros-de-url-no-api-gateway.md)
* [Caso de uso: parâmetros de gatilho API Gateway](https://docs.skyone.cloud/skyone-studio/how-to/caso-de-uso-parametros-de-gatilho-api-gateway.md)
* [Caso de uso: Exception Handler em transações financeiras](https://docs.skyone.cloud/skyone-studio/how-to/caso-de-uso-exception-handler-em-transacoes-financeiras.md)
* [Caso de uso: utilizando Grupos para gerenciar acessos aos fluxos](https://docs.skyone.cloud/skyone-studio/how-to/caso-de-uso-utilizando-grupos-para-gerenciar-acessos-aos-fluxos.md)
* [É possível usar dois gatilhos em um único fluxo?](https://docs.skyone.cloud/skyone-studio/how-to/e-possivel-usar-dois-gatilhos-em-um-unico-fluxo.md)
* [Como criar endpoint para download e integrar com o Power BI](https://docs.skyone.cloud/skyone-studio/how-to/como-criar-endpoint-para-download-e-integrar-com-o-power-bi.md)
* [É possível usar dois gatilhos em um único fluxo?](https://docs.skyone.cloud/skyone-studio/how-to/e-possivel-usar-dois-gatilhos-em-um-unico-fluxo.md)
* [Criptografia: Funções de Hash no JSONata ($md5 e $sha256)](https://docs.skyone.cloud/skyone-studio/how-to/criptografia-funcoes-de-hash-no-jsonata-usdmd5-e-usdsha256.md)
* [Parâmetros de Geração no Skyone Studio](https://docs.skyone.cloud/skyone-studio/how-to/parametros-de-geracao-no-skyone-studio.md)
* [Utilizando os filtros no Skyone Studio](https://docs.skyone.cloud/skyone-studio/how-to/utilizando-os-filtros-no-skyone-studio.md)
* [Boas práticas de prompts para o Skyone Studio](https://docs.skyone.cloud/skyone-studio/how-to/boas-praticas-de-prompts-para-o-skyone-studio.md)


---

# 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.skyone.cloud/skyone-studio/how-to.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.
