> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/admin-fr/applications-de-workflow/xmltojson.md). # XMLTOJSON L’application de workflow **XMLTOJSON** offre un moyen fiable de convertir du contenu XML structuré en contenu JSON équivalent. Elle est particulièrement utile lors du traitement de données de formulaire, de fichiers de configuration ou de réponses d’API initialement encodés en XML, mais qui doivent être utilisés dans des environnements ou des workflows où le format JSON est privilégié. ## Paramètres

Nom	Type	Direction	Description
`XML_STRING`	TEXT	IN	La chaîne XML à convertir
`XML_FILE`	FILE	IN	Le fichier XML à convertir
`REMOVE_DECLARATION`	TEXT	IN	Indique si la déclaration XML doit être supprimée du JSON : `Y` (par défaut) ou `N`
`REMOVE_SCHEMA`	TEXT	IN	Indique si le schéma XML doit être supprimé du JSON : `Y` (par défaut) ou `N`
`INDENT_JSON_OUTPUT`	TEXT	IN	Indique si la sortie JSON doit être indentée : `Y` ou `N` (par défaut)
`JSON_STRING`	TEXT	OUT	La chaîne de sortie JSON
`JSON_FILE`	FILE	OUT	Le fichier de sortie JSON

--- # 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.workflowgen.com/admin-fr/applications-de-workflow/xmltojson.md?ask=&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.