# XML Helper

<figure><img src="/files/sHJYAv1lG68l69tjStN9" alt="" width="155"><figcaption></figcaption></figure>

## 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 `{{ }}`

<figure><img src="/files/MmlRG6N35UNCtYFpVdoB" alt="" width="563"><figcaption></figcaption></figure>

#### XML Attributes

If you want to include [XML attributes](https://www.w3schools.com/xml/xml_attributes.asp) in the outputted XML, e.g.:

```xml
<?xml version="1.0" encoding="utf-8"?>
<Example id="somevalue" type="text">
  <Content>Some Text</Content>
</Example>
```

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.&#x20;

{% 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 %}

<figure><img src="/files/vyafQdyV3Bzv8vnw28wg" alt="" width="563"><figcaption></figcaption></figure>

{% 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.

<figure><img src="/files/CR8dyDJYYEwCi8lLDczE" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.locoia.com/connectors/helpers/xml-helper.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.