> 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 hosted web experience managed entirely by the platform: you configure its appearance, language, and behavior, and get a URL that’s ready to use. You can redirect users to that URL, serve it from your own domain, or embed it in your website or app (iframe or WebView).

No custom development. No additional infrastructure.

**When should you use No-Code?** Ideal when you need to deploy quickly without custom development: pilots, POCs, campaigns, or production flows. With a custom domain and iframe or WebView integration, end users stay in your environment and don’t see the Facephi domain.

***

{% hint style="info" %}

### Prerequisites

Before creating a No-Code integration, make sure you have:

* Access to the **Flows & Integrations** module in the IDV Suite platform.
* An active **tenant** with the corresponding licenses.
* A **published flow** in the Flow Designer (with its Workflow ID).
* If using a **custom domain**, access to the domain’s DNS settings.
  {% endhint %}

***

### Create a No-Code integration

In the **Flows & Integrations**module, click **+ New Integration**. The platform will display a modal with two steps:

#### **Step 1 — Choose the integration type**

Select **No-Code** from the available options, then click **Continue**.

<figure><img src="https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2FaVghWgBBAIhQEKnxjMZh%2FPaso%201.png?alt=media&amp;token=95da16e9-3ee8-4205-9531-3408b9416818" alt=""><figcaption><p>Integration type selector</p></figcaption></figure>

#### **Step 2 — Select the flow**

Choose the published flow to associate with the integration. You can search by name or filter by type and status. Only flows with the status **Published** will be available.

![Selecting the flow for the No-Code integration](https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2Fgit-blob-b4a692948b1f7c51914e2e3e1015c1278071c5d2%2FNoCode_2.png?alt=media)

Once confirmed, the integration will be created with an automatically generated name in the format `INT-NOCODE-001` and will have the status **Draft**. From this point, the configuration process has three steps: **Customise → Connect → Set up**.

***

### Visual configuration (Customise)

The **Customise** tab lets you adapt the flow’s appearance 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 uploaded](https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2Fgit-blob-c613da059fa62dfd0fd12ddfb4211c2862fce8d6%2FNoCode_3.png?alt=media)

#### Images

| Element     | Required | Description                                                                                        |
| ----------- | -------- | -------------------------------------------------------------------------------------------------- |
| **Logo**    | ✅ Yes    | Logo displayed in the Flow header. PNG or JPG format.                                              |
| **Favicon** | ❌ No     | Browser tab icon. Turn on the toggle **Use your logo as favicon** to reuse the logo automatically. |

{% hint style="info" %}
If you turn on **Use your logo as favicon**, the favicon slot will be hidden. When you turn it off, the slot will reappear with the previously uploaded image.
{% endhint %}

#### Typography

Select the font applied to the entire Flow. There are different types:

<div align="left"><img src="https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2Fgit-blob-ba7fdafe138df15fbda785054c7a1a3212143f44%2FNoCode_4.png?alt=media" alt="Typography selector expanded" width="375"></div>

#### Colors

| Field          | Required | Description                      |
| -------------- | -------- | -------------------------------- |
| **Primary**    | ✅ Yes    | Buttons and primary elements.    |
| **Secondary**  | ✅ Yes    | Secondary backgrounds and links. |
| **Tertiary**   | ✅ Yes    | Labels and supporting elements.  |
| **Background** | ❌ No     | General Flow background color.   |

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](https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2Fgit-blob-6f97df5c665f77e9ba4dac136d8f94c4d9f4f9df%2FNoCode_5.png?alt=media)

{% hint style="warning" %}
The **Primary**, **Secondary** and **Tertiary** fields are required. Without them, you won't be able to proceed to the next step
{% endhint %}

Once you've configured the appearance, click **Next step** to continue.

***

### Webhook configuration (Connect)

The **Connect** step lets you configure a webhook so your backend can receive real-time notifications about Flow events (start, OCR, validation, final result, etc.).

This step is **optional**. If you don't need real-time notifications, you can skip directly to **Set up**.

![Connect screen — webhook disabled (left) and enabled with fields visible (right)](https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2Fgit-blob-369669c863fc4c85139754c4c59b749179bb3c5e%2FNoCode_6.png?alt=media)

When you turn on the **Webhook**toggle, the configuration fields will appear:

| Field                                     | Description                                                                                                                                       |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **URL**                                   | Backend endpoint that will receive the events.                                                                                                    |
| **Webhook header**                        | Custom headers (key/value) for authenticating or identifying the requests.                                                                        |
| **OAuth Authentication (in development)** | Enable OAuth authentication for the webhook.                                                                                                      |
| **Events**                                | Select which events trigger the webhook: `Start`, `Change of Steps`, `OCR`, `Assets`, `Passive liveness`, `Facial Matching`, `Operation Results`. |

{% hint style="info" %}
Detailed documentation on each event's payload and the structure of the notifications is available in the **Webhooks** section of this documentation.
{% endhint %}

{% hint style="warning" %}
No-Code integrations always use **private flows**: the session is created from your backend (backend-to-backend), and the end user receives a one-time access link. See the **No-code: Landing**.
{% endhint %}

Click **Next step** to continue.

***

### 1.3.4 Landing Configuration and Publishing (Set up)

The **Set up** step collects the flow's functional parameters and generates the integration, ready to publish.

<figure><img src="https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2F1KiwnXgapzUrZcAGRBOx%2FPaso%201.3.4.png?alt=media&amp;token=afef8aae-0ea6-4a60-a680-e3b3d207b11e" alt=""><figcaption><p>Set up screen — landing page configuration</p></figcaption></figure>

| Field                                  | Required | Description                                                                                                                                                                                |
| -------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Title**                              | ✅ Yes    | Title displayed in the flow header.                                                                                                                                                        |
| **Output URL**                         | ❌ No     | URL to which the user will be redirected after completing the flow.                                                                                                                        |
| **Language**                           | ✅ Yes    | The flow's primary language (`English`, `Spanish`, etc.).                                                                                                                                  |
| **API Key**                            | ✅ Yes    | Generated automatically. Identifies the integration in system requests.                                                                                                                    |
| **Show QR to view the mobile version** | ❌ No     | Displays a QR Code to start the flow from a mobile device.                                                                                                                                 |
| **Custom Domain**                      | ❌ No     | Lets you serve the landing page and session URLs under your own domain instead of the generic IDV domain (requires DNS record configuration and activation of the hostname in Cloudflare). |
| **Enable max attempts URL**            | ❌ No     | Enables automatic redirection to an alternative exit URL when the user reaches the maximum number of retries configured in the capture components.                                         |
| **Authorize URLs**                     | ❌ No     | Domains authorized to load or embed the landing page (for example, in an iframe).                                                                                                          |

{% 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 %}

**Custom domain (optional)**

You can serve the landing page from your own domain (for example, `verificacion.tuempresa.com`), instead of the Facephi domain.

1. Enable **Custom domain** and enter your domain.
2. The screen displays **3 DNS records** (2 CNAME and 1 TXT). Create them with your domain's DNS provider.
3. Wait until the domain appears as **Active, then publish the Integration**.

**Integration in an iframe or WebView (optional)**

To load the landing page within your website or app, add your domain to **Authorized URLs**. For more details, see **Embedding the landing page in an iframe or WebView.**

Once you have completed the fields, click **Publish Integration**.

The platform will display a confirmation, and the integration will move to the **Configured**state, initiating the publication request process.

**If you configured a custom domain:**

* **If the domain is not active yet**, the message *“Custom domain not active yet”*&#x61;ppears. You can **cancel** (the integration remains in Configured) or **continue** and publish it on the Facephi domain in the meantime.
* **If the domain is active**, the integration moves to **Waiting for approval** until Facephi enables the domain license.
* If you published to the Facephi domain and your domain becomes active later, the integration **does not switch domains automatically**: unpublish it and publish it again.

{% hint style="info" %}
Clicking ***Publish*** does not publish the integration immediately. Its status changes to **Configured** and a publication request is created, which must be approved. Until its status is **Published** , the flow will not be accessible externally.
{% endhint %}

Once published, you can view and copy the **Integration ID** associated with this integration from the Integrations list. This identifier links your channel to the flow and appears in the log of generated operations.

![Integration ID shown in the integrations list](https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2Fgit-blob-d77ed9e3433bc5bace13ef0839c60112c1c809c2%2FNoCode_8.png?alt=media)

***

### 1.3.5 Available statuses and actions

From the **Integrations** list, you can view the status of each integration and the actions available at any given time.

![List of integrations with statuses and actions menu](https://865101184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUo71Qbj6jZQDavjc0U5X%2Fuploads%2Fgit-blob-d6390da003c0b8bd4ed3d9984688dd4bfc1d4d86%2FNoCode_9.png?alt=media)

| State                    | Description                                                                                                                        | Available actions                       |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| **Draft**                | Being configured. Not accessible externally.                                                                                       | Edit Flow · Edit Configuration · Delete |
| **Configured**           | Configuration complete, pending publication.                                                                                       | Edit Flow · Edit Configuration · Delete |
| **Waiting for approval** | Publication request submitted, pending review. If the integration uses a custom domain, this includes enabling the domain license. | — (no actions available)                |
| **Published**            | Active and operational. Users can access the flow.                                                                                 | Edit Configuration · Unpublish · Play   |

{% hint style="info" %}
The **Play** action (only available in No-Code once published) lets you preview and test the flow directly from the platform.
{% endhint %}

***

### Operation tracking

Whenever a user completes or abandons the flow, IDV Suite records an **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 it is configured in the flow.

***

### Summary

With a No-Code integration, you can have an operational verification flow in minutes:

1. **Create** the integration by selecting the No-Code type and the published flow.
2. **Customize** — adjust the logo, colors, and typography.
3. **Connect** — configure the webhook if you need real-time notifications.
4. **Configure** — set the title, language, exit URL, authorized URLs, and, if needed, your custom domain. Then publish.
5. **Monitor** operations from the Operations module.

Need native integration into your website or app? See [Low-Code Integration.](https://docs.facephi.com/docs.facephi-en/products/idv-suite/flujos-and-integraciones/integraciones-no-code-low-code/integraciones-low-code.md)
