> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/labs/limio-for-salesforce/data-parsers.md).

# Data Parsers

Data parsers for Limio for Salesforce that ingest and transform external data into Limio-compatible formats. Designed to reduce the integration glue code that's typically needed when connecting Salesforce workflows to Limio's subscription platform.

## How it works

Parsers sit between your external data sources and Limio, handling the transformation logic that would otherwise require custom middleware. They normalise incoming data — whether from Salesforce objects, external APIs, or file imports — into the formats that Limio's order processing and catalog systems expect.

## Why it matters

Every Limio for Salesforce implementation involves some degree of data transformation. Standardised parsers mean faster onboarding, less bespoke integration code, and a more predictable path from external data to Limio-ready records. This is particularly valuable for customers with complex Salesforce configurations or multiple data sources feeding into their subscription workflows.

***

{% hint style="info" %}
**This is a Labs feature.** We're experimenting with this and it's not yet part of the core platform. Interested in early access or want to help shape it?

[Request access →](mailto:hello@limio.com?subject=Labs%20—%20LFS%20Parsers)
{% endhint %}


---

# 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.limio.com/labs/limio-for-salesforce/data-parsers.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.
