> ## Documentation Index
> Fetch the complete documentation index at: https://doc.qbilon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhook Composer

> Configure the Webhook Composer to process incoming webhook data.

## Overview

With the Qbilon Webhook Composer, you can ingest any JSON body into Qbilon. No specific graph format is required. Incoming JSON objects are automatically flattened into key-value pairs using slash notation for nested fields. The Composer's configurable settings provide flexible control over which part of the input is analyzed, how assets are generated, and which properties are filtered or ignored.

## Settings

| **Setting** | **Description** | **Example** |
| - | - | - |
| Entry Point (RFC 6901 String) | Defines the starting position for analyzing and transforming the target sub-object within the JSON payload. It should be provided as an RFC 6901 pointer string, using slashes to separate path segments. | `orders/events` |
| ID Field  | Specifies the property in the (sub-)object that defines each asset's unique identifier. This property must always be present to ensure uniqueness. | `id` |
| Name Field  | Indicates the property that provides the display name of each created asset. | `name` |
| Type  | Defines the fixed type string for each asset created by the Composer. This is not a JSON property, but an explicit string. | `Event` |
| Ignore Pattern (RFC 6901 Regex) | Defines a regular expression ("regex") pattern in RFC 6901 format. Any properties matching this pattern will be ignored and not assigned as asset properties. | `^temp_.*` (All properties whose name starts with `temp_` will be excluded) |

## Processing Details

* The JSON payload is flattened, with nested paths represented by slashes.
* Each key-value pair is interpreted as an asset property, unless it is excluded by the `Ignore Pattern`.
* The `Entry Point` restricts processing to a specific sub-object inside the payload.
* The `ID Field` and `Name Field` must both exist for every object to ensure correct identification and labeling.
* The same `Type` is assigned to all created assets for consistency.
* The `Ignore Pattern` allows selective omission of unwanted properties.
* If the incoming JSON is an array, each asset is processed as a separate asset. Arrays must have a consistent structure that includes all required fields, such as `ID` and `Name`.

## Example Configuration

| **Setting** | **Description** | **Example Value** |
| - | - | - |
| Entry Point | Only the sub-object at `orders/events` is analyzed for asset creation. | `orders/events` |
| ID Field | Each asset will use the `id` property as its unique identifier. | `id` |
| Name Field | Each asset will be named using the `name` property. | `name` |
| Type | All assets created will have the type `Event`. | `Event` |
| Ignore Pattern | Any property whose name starts with `temp_` will be ignored as an asset property. | `^temp_.*` |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.