> For the complete documentation index, see [llms.txt](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/semi-structured-transformer.md). # Semi Structured Transformer The Transformers are scalable independent processors which use your model designs to make graph data. They can connect and ingest from virtually anything as a data source, where the Semi Structured Transformer handles: * CSV * JSON * XML Change Data Capture (CDC) is supported by the Semi Structured Transformers via an internal integration with Debezium. This allows your graphs to be always up to date and in sync with any changes made in the source data, for example in most SQL databases, Cassandra, or MongoDB. The Semi Structured Transformer can also perform any simple or complex data transformations via our plugin ‘Functions’ architecture. There is a vast library of built in functions, with the ability to also write and load in your own for any specific requirements that may not be covered. --- # 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.graph.build/EGeX4aTAJLlpg9Hh8kfl/semi-structured-transformer.md?ask=&goal= ``` `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.