> For the complete documentation index, see [llms.txt](https://kb.stoque.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.stoque.com.br/zeev/apis/all/instances/adicionar-arquivos-base64-em-campos-de-formulario.md).

# Adicionar arquivos base64 em campos de formulário

Arquivos base64 podem ser inseridos no Zeev

Além do uso dos arquivos base64 nos anexos opcionais, é possível abrir instancias no Zeev, via API `(/api/2/instances)`, e enviar conteúdos em formato base64 nos campos de formulário que sejam do tipo "Arquivo" ou "Arquivo visualizador".&#x20;

O conteúdo do base64 deve respeitar as seguintes regras:

* Tamanho máximo de 50MB.
* O tipo do arquivo deve ser compatível com os permitidos via parâmetro do sistema.
* O arquivo deve estar válido.


---

# 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://kb.stoque.com.br/zeev/apis/all/instances/adicionar-arquivos-base64-em-campos-de-formulario.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.
