# Integration

## Introduction

Form Builder and Form Runner integrate with other systems through several means, summarized below.

## Plain URLs

See [URLs](/form-runner/link-embed/linking.md) for more details.

* Through URLs, you access Form Runner and Form Builder's pages.
* The URLs can be produced simply by using hyperlinks or redirects from other applications.

## Configurable persistence API

See [Persistence API](/form-runner/api/persistence.md) for more details.

* The API is based on REST (that is, through HTTP).
* It provides CRUD, search, and metadata operations.

See also [Accessing data captured by forms](/form-runner/architecture-and-integration/accessing-data.md)

## HTTP services

* The [HTTP Service Editor](/form-builder/advanced/services-and-actions/http-services.md) allows you to create and bind services from a form.
* With properties, you can tell Form Runner to load initial XML data.
* Configure processes to [submit data](/form-runner/advanced/buttons-and-processes/actions-form-runner.md#send).

See also [Accessing data captured by forms](/form-runner/architecture-and-integration/accessing-data.md).

## Embedding

Embedding allows you to integrate a form in another application's page.

See [Embedding](/form-runner/link-embed.md) for more details.

## User management

By integrating with a user management system, you make Orbeon Forms aware of users and roles which can be associated with permissions.

See [Access Control](/form-runner/access-control.md) for more details.

## XML representation of form data

See [Form Data Format](/form-runner/api/data-formats/form-data.md)

## See also

* [Form Builder Integration](/form-builder/advanced/extensibility/integration.md)


---

# 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://doc.orbeon.com/form-runner/architecture-and-integration/integration.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.