> 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-no-code.md). # No-code integrations No-Code integration is the fastest way to launch a verification flow. IDV Suite generates a web experience hosted and managed entirely by the platform: you configure the look and feel, language, and behavior, and get a URL or an embeddable code ready to use. No in-house development. No additional infrastructure. **When should you use No-Code?** Ideal for pilots, POCs, one-off campaigns, or any case where you need deployment speed and UX customization is not a critical requirement. *** {% hint style="info" %} ### Prerequisites Before creating a No-Code integration, make sure you have: * Access to the module **Flows & Integrations** on the IDV Suite platform. * A **tenant** active with the corresponding licenses. * A **published flow** in the Flow Designer (with its Workflow ID). {% endhint %} *** ### Create a No-Code integration From the module **Flows & Integrations**, click **+ New Integration**. The platform will show a modal with two steps: #### **Step 1 — Choose the integration type** Select **No-Code** among the available options and click **Continue**. ![Integration type selector — No-Code vs. Low-Code](/files/0bdb8df4c885708bd9b2c358b225da732d73834a) #### **Step 2 — Select the flow** Choose the published flow you want to associate the integration with. You can search by name or filter by type and status. Only flows in **Published** status will be available. ![Flow selection for the No-Code integration](/files/ca8a416ca2976ec1e862e6a0321ef2843aae41b3) Once confirmed, the integration will be created with an automatic name of the type `INT-NOCODE-001` and it will remain in state **Draft**. From here, the configuration process has three steps: **Customise → Connect → Set up**. *** ### Visual configuration (Customise) The tab **Customise** lets you adapt the appearance of the flow to the client's visual identity. Changes are reflected in real time in the **Preview** panel on the right. ![Customise screen — initial state and with logo loaded](/files/3f2e0f15ac1dcb7bcb3e13d7fcecb595f5ddc2ea) #### Images | Element | Required | Description | | ----------- | -------- | ------------------------------------------------------------------------------------------------- | | **Logo** | ✅ Yes | Logo that appears in the flow header. PNG or JPG format. | | **Favicon** | ❌ No | Browser tab icon. Enable the toggle **Use your logo as favicon** to reuse the logo automatically. | {% hint style="info" %} If you enable **Use your logo as favicon**, the favicon slot will be hidden. When you disable it, it will show again with the previously loaded image. {% endhint %} #### Typography Select the font applied to the entire flow. There are different types:
Expanded typography selector
#### Colors | Field | Required | Description | | -------------- | -------- | ------------------------------------- | | **Primary** | ✅ Yes | Buttons and main elements. | | **Secondary** | ✅ Yes | Secondary backgrounds and links. | | **Tertiary** | ✅ Yes | Labels and support elements. | | **Background** | ❌ No | General background color of the flow. | All colors must be entered in hexadecimal format (`#RRGGBB`). You can remove a color using the **X** next to the field; the Preview will reflect the resulting state. ![Customize with the applied colors — result in Preview](/files/6c74fd6a04e6ee1139ddb344292149e05b80d5ac) {% hint style="warning" %} The fields **Primary**, **Secondary** and **Tertiary** are required. Without them you will not be able to proceed to the next step {% 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 **Set up**. ![Connect screen — webhook disabled (left) and enabled with visible fields (right)](/files/42c5421967449e1a47a9920ccce189eff8c4bdaa) 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** of this documentation. {% endhint %} {% hint style="warning" %} No-Code integrations use exclusively **public flows**. If your use case requires sending sensitive data from the backend before starting the flow, contact your Facephi representative to assess the appropriate option. {% endhint %} Click **Next step** to continue. *** ### 1.3.4 Landing and publication configuration (Set up) The step **Set up** collects the flow's functional parameters and generates the integration ready to publish. ![Set up screen — landing page configuration](/files/237b879c49145d00ec9f828905031b0d6c7ae848) | Field | Required | Description | | ------------------------------------------- | -------- | ----------------------------------------------------------------------------- | | **Title** | ✅ Yes | Visible title in the flow header. | | **Output URL** | ❌ No | URL to which the user will be redirected when the flow is completed. | | **Language** | ✅ Yes | Main language of the flow (`English`, `Spanish`, etc.). | | **Restrict access from URLs** | ❌ No | List of domains from which the flow can be started (origin control). | | **API Key** | ✅ Yes | It is generated automatically. It identifies the integration in system calls. | | **Show QR Code to view the mobile version** | ❌ No | Displays a QR Code to start the flow from a mobile device. | {% hint style="warning" %} The **API Key** is generated automatically when the integration is created and must not be shared publicly. There is no technical reason for the end user to know it. {% endhint %} Once the fields are completed, click **Publish Integration**. The platform will show a confirmation and the integration will move to state **Configured**, starting the publication request process. {% hint style="info" %} Click ***Publish*** does not publish the integration immediately. The status changes to **Configured** and a publication request is generated that must be approved. Until it is in state **Published** the flow will not be externally accessible. {% endhint %} Once published, from the Integrations list you can view and copy the **Integration ID** associated with this integration. This identifier is what links your channel with the flow and appears in the generated operations log. ![Integration ID visible in the integrations list](/files/bebc507695fbec3446f47e83dbf07b6ef3ff2ffa) *** ### 1.3.5 Available statuses and actions From the list of **Integrations** you can see the status of each integration and the actions available at any given time. ![Integrations list with statuses and actions menu](/files/2b55155c7112e07379109c62b74efff6e464f5fe) | Status | Description | Available actions | | ------------------------ | -------------------------------------------------- | --------------------------------------- | | **Draft** | Configured. Not externally accessible. | Edit Flow · Edit Configuration · Delete | | **Configured** | Configuration complete, pending publication. | Edit Flow · Edit Configuration · Delete | | **Waiting for approval** | Publication request sent, pending review. | — (no actions available) | | **Published** | Active and operational. Users can access the flow. | Edit Configuration · Unpublish · Play | {% hint style="info" %} The action **Play** (only available in No-Code once published) allows you to preview and test the flow directly from the platform. {% endhint %} *** ### Operation tracking Each time a user completes or abandons the flow, IDV Suite records a **operation** in the Operations module. From there you can: * View the status and result of each verification. * Review the captured data (document, biometrics, validations). * Escalate to manual review if configured in the flow. *** ### Summary With a No-Code integration, you have a live verification flow in minutes: 1. **Create** the integration by selecting the No-Code type and the published flow. 2. **Customize** — adjust logo, colors, and typography. 3. **Connect** — configure the webhook if you need real-time notifications. 4. **Configure** — define title, language, output URL, and publish. 5. **Monitor** operations from the Operations module. Need native integration in your web or app? Check out [Low-Code Integration.](/docs.facephi-en/products/idv-suite/flujos-and-integraciones/integraciones-no-code-low-code/integraciones-low-code.md)