> For the complete documentation index, see [llms.txt](https://howto.erpbridge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://howto.erpbridge.io/readme.md).

# How-To ERP Bridge

Check out the most useful and popular topics to get you started with ERP Bridge.

The following sections provide information about which data import from your ERP and how to use them with ERP Bridge. All of this sections are thought as insights to exploit the software 100%: for example you will see a standard integration that we recommend tu use with best practice cases as creator.

[For all technical information, please refer to the software documentation section.](https://docs.erpbridge.io/)

After completing the software installation and configuration, it's time to set up all synchronization logic, called Operation, from the software homepage.

{% hint style="info" %}
Our advice is to follow this synchronization logic:

* [Companies](/readme/companies.md)
* [Deals](/readme/deal.md)
* Contacts
* Products
* Line Items
* Tickets
* CustomObject
  {% 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://howto.erpbridge.io/readme.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.