> For the complete documentation index, see [llms.txt](https://docs.facephi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.facephi.com/docs.facephi-en/products/idv-suite/flujos-and-integraciones/integraciones-no-code-low-code/integraciones-low-code.md). # Low-Code integrations The Low-Code Integration allows you to incorporate a verification Flow directly into your own web or mobile application. Unlike No-Code integration, here the client manages the experience in their channel, while IDV Suite orchestrates the Flow logic from the platform. The result of the configuration process is a **Integration ID** that your technical team will use to initialize the SDK Web or Mobile and run the Flow. {% hint style="info" %} **When to use Low-Code?** Ideal when you need native Integration in your web or app, greater control over the UX, or connection with the client's internal systems. A basic technical profile is required for SDK implementation. {% endhint %} *** ### Prerequisites Before creating a Low-Code Integration, make sure you have: * Access to the module **Flows & Integrations** on the IDV Suite platform. * A **published flow** in the Flow Designer (with its Workflow ID). * A technical team that will carry out the SDK implementation in the client's channel. *** ### Create a Low-Code Integration From the module **Flows & Integrations**, click **+ New integration**. In the type selection modal, choose **Low Code** and click **Continue**.

Integration type selector — Low-Code vs No-code

Next, select the published Flow you want to associate with the integration. Only the Flows in state **Published** status will be available.

flow selection modal

Once confirmed, the integration will be created with an automatic name of the type `XXXXXXXX` and it will remain in state **Draft**. The configuration process has four steps: **Choose → Customize → Connect → Configure**. *** ### Visual configuration (Customization) The tab **Customize** lets you adapt the appearance of the flow to the client's visual identity. Changes are reflected in real time in the **Preview**, showing how the experience will look on the end user's device.

Customization screen: color selection

Unlike No-Code integration, the Low-Code Customization includes a more complete color palette, organized into three groups: #### Main colors | Field | Required | Description | | -------------- | -------- | -------------------------------------------------------- | | **Primary** | ✅ Yes | Main interface color: buttons and highlighted elements. | | **Secondary** | ✅ Yes | Secondary color to highlight content or buttons. | | **Background** | ✅ Yes | General background color of the experience. | | **Neutral** | ✅ Yes | Neutral color for background elements or secondary text. | | **Accent** | ✅ Yes | Accent color for secondary elements. | #### Status colors | Field | Required | Description | | ----------- | -------- | ----------------------------------------------- | | **Error** | ✅ Yes | Color to indicate errors in the Flow. | | **Success** | ✅ Yes | Color to indicate successfully completed steps. | #### Text colors | Field | Required | Description | | --------------- | -------- | -------------------------------------- | | **Title text** | ✅ Yes | Color of the screen title or sections. | | **Body text** | ✅ Yes | Color of the main text. | | **Button text** | ✅ Yes | Color of the text inside SDK buttons. | {% hint style="info" %} The panel **Preview** simultaneously shows the success case and the error case of the Flow, reflecting in real time how the configured colors will look in the end-user experience. {% endhint %} {% hint style="warning" %} All colors must be entered in valid hexadecimal format (`#RRGGBB`). Improperly formatted values will prevent the configuration from being saved. {% endhint %} Once the appearance is configured, click **Next step** to continue. *** ### Webhook configuration (Connect) The step **Connect** allows you to configure a webhook so that your backend receives real-time notifications about flow events (start, OCR, validation, final result, etc.). This step is **optional**. If you do not need real-time notifications, you can skip directly to **Configure**.

Connect screen — webhook disabled and enabled with visible fields

By enabling the **Webhook**, the configuration fields will appear: | Field | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | | **URL** | Endpoint of your backend that will receive the events. | | **Webhook header** | Custom headers (key/value) to authenticate or identify calls. | | **OAuth Authentication** | Enable OAuth authentication on the webhook. | | **Health URL** | Endpoint health-check URL. | | **Events** | Select which events trigger the webhook: `Start`, `Change of Steps`, `OCR`, `Assets`, `Passive Liveness`, `Facial Matching`, `Operation Results`. | {% hint style="info" %} Detailed documentation of each event's payload and the structure of the notifications is available in the section [**Webhooks**](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/webhook.md) of this documentation. {% endhint %} Click **Next step** to continue. *** ### Application configuration (Configure) The step **Configure** is where the Low-Code integration differs most clearly from the No-Code one. Instead of generating a public URL, here the parameters needed by your application's SDK to execute the Flow correctly are defined.

Configure screen — Language, Platform and Bundle ID fields

| Field | Required | Description | | ------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Language** | ✅ Yes | Main language of the flow (`Spanish`, `English`, etc.). | | **Platform** | ✅ Yes | Client application's platform: `Android`, `iOS` or `Web`. | | **Bundle ID** | ✅ Yes | Unique identifier of the mobile application (for example: `com.empresa.app`). Required to validate that the SDK executing the Flow belongs to the authorized app. | Once the fields are completed, click **Finish integration**. The integration will move to state **Configured**. {% hint style="info" %} Once configuration is complete, the **Integration ID** will be available in the integration list. This identifier is the key piece your technical team needs to initialize the SDK and link the app with the Flow defined on the platform. {% endhint %} *** ### Status and available actions From the list of **Integrations** you can see the status of each integration and the available actions.

integration list with Low Code badge and Integration ID column visible

| Status | Description | Available actions | | -------------- | ----------------------------------------------------- | --------------------------------------- | | **Draft** | Configured. Not externally accessible. | Edit Flow · Edit configuration · Delete | | **Configured** | Configuration complete, pending publication. | Edit Flow · Edit configuration · Delete | | **In review** | Publication request sent, pending approval. | — (no actions available) | | **Published** | Active and operational. The SDK can execute the Flow. | Edit configuration · Unpublish | {% hint style="info" %} Unlike the No-Code integration, the Low-Code integration does not have the action **Play** once published, since Flow execution happens in the client's application through the SDK. {% endhint %} *** ### Next step: implementation in the channel Once the integration is published, your technical team can start the SDK implementation using the **Integration ID** obtained. * If you are integrating into a **web application**, see [SDK Web (Loader)](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/solucion-web/sdk-loader-idv.md). * If you are integrating into a **mobile application**, see [SDK Mobile](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/configuracion-tecnica-del-cliente/sdk-mobile.md). *** ### Summary With a Low-Code integration you connect your application with a verification Flow managed from IDV Suite: 1. **Create** the integration by selecting the Low-Code type and the published Flow. 2. **Customize** — adjust main, status, and text colors. 3. **Connect** — configure the webhook if you need real-time notifications. 4. **Configure** — define language, platform and Bundle ID, and finish the integration. 5. **Implement** the SDK in your channel using the Integration ID and the License (api-key) that the support team will provide you. 6. **Monitor** operations from the Operations module.