---
title: Requirements and Restrictions
description: Check requirements and restrictions for building integrations
documentId: ipaas-restrictions
locale: en-US
---

On this page, we present the requirements and restrictions that must be followed when developing and configuring integration flows. These guidelines are essential to ensure the correct implementation and expected functioning of your project.

- **File requirements**
  - File format: the file content must be a syntactically valid `.yaml`.

- **Route limit**: the file can have at most one route that is **not** of type `from: direct:xxx`.
  - This route will be the integration flow trigger.

- **Requirements for triggers and components in steps**

  - **Triggers**: the component informed in the trigger must be a consumer.
    - If a component that is not a consumer is used in the trigger, the flow can still proceed, but an error will be displayed during deployment.

  - **Components in steps**: the component informed in a flow _step_ must be a producer.
    - If a component that is not a producer is used in a flow _step_, the flow can still proceed, but an error will be displayed during deployment.

- **Rules for URLs and EIPs**

  - URLs in EIPs must reference [approved components](/docs/integrations/ipaas-connectors).

  - **Process EIP**: It is allowed to use processes already available natively in Camel, however, **the creation of new processes is currently disabled**.

- **Naming and prefixes**

  - Route names: it is not allowed to create routes with names that start with the prefix `sensedia_`.

- **Global configuration restrictions**
  - Prohibited configurations:

    - `beans`;
    - `errorHandler`;
    - `onException`;
    - `routeConfiguration`;
    - `route`;
    - `routeTemplate`;
    - `templatedRoute`;
    - `rest` (must use `from: rest`).