> For the complete documentation index, see [llms.txt](https://docs-it.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-it.docbits.com/administration-and-setup/workflow/card-sdk.md).

# Card SDK

Il **Card SDK** consente a partner e sviluppatori di creare schede di workflow personalizzate per DocFlow. Confeziona una scheda come app partner e la carichi, oppure la importi direttamente da GitHub.

<figure><img src="/files/CmDc8THBSN8r9veoey5A" alt="Scheda Card SDK con Upload ZIP, GitHub Import e Submissions"><figcaption><p>Il Card SDK — carica uno ZIP di un'app partner, importa da GitHub o controlla le tue submission.</p></figcaption></figure>

## Come funziona

* **Download SDK Template** — parti dal template ufficiale che contiene la struttura prevista.
* **Upload ZIP** — lo ZIP deve contenere `app.json` e una cartella `.docflowcompose/flow/` con le definizioni delle schede (massimo 10 MB). Upload & Validate controlla il pacchetto prima che venga accettato.
* **GitHub Import** — importa una definizione di scheda direttamente da un repository GitHub.
* **Submissions** — monitora lo stato delle schede che hai inviato.

Una volta validate e accettate, le tue schede personalizzate appaiono nella libreria **Add Card** insieme alle schede integrate.


---

# 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-it.docbits.com/administration-and-setup/workflow/card-sdk.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.