> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/connectors/helpers/xml-helper.md).
# XML Helper
## Overview
The **XML Helper** converts XML to dictionaries or vice versa. It connects XML-based APIs to the integration platform.
## Actions
### 1. Convert dictionary to XML
To convert a dictionary to XML, e.g. for use in the REST helper, use the **Convert dictionary to XML** action. Just reference the object directly, without `{{ }}`
#### XML Attributes
If you want to include [XML attributes](https://www.w3schools.com/xml/xml_attributes.asp) in the outputted XML, e.g.:
```xml
Some Text
```
You need to include the attributes in the dictionary with an `@` prefix, e.g.:
```json
{
"Example": {
"@id": "somevalue",
"@type": "text",
"Content": "Some Text",
}
}
```
### 2. Convert XML to dictionary
To retrieve an XML file or endpoint, just include the internal Locoia reference or the external URL, like in the below screenshot the VAT-ID check of the EU commission.
{% hint style="info" %}
Since XML responses are sometimes "not so clean", please reference data as per the below. This is the better approach compared to JSONPath-notation.
`myOldErp["users"]["first_name"]`
{% endhint %}
{% hint style="info" %}
If an XML only contains one entry of an object, it will be output as a dictionary in JSON.\
However, if it has multiple entries of an object it will be output as a list of dictionaries. \
To check the output type dynamically in a flow you use the Jinja `mapping` test, e.g.:
```django
{% if dic1 is mapping %}
"Dict"
{% else %}
"List"
{% endif %}
```
{% endhint %}
### 3. Drop Namespaces
Sometimes you may want to drop the namespaces of an existing XML. This can be done with the **Drop Namespaces** action.
---
# 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.locoia.com/connectors/helpers/xml-helper.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.
