# Forward Data to Your Workflow

You can forward custom data when initializing your integrated Workflows. This option is available when the Workflow is initialized on your side via the `/omni/start` endpoint.

***

## Custom Fields

The `/omni/start` endpoint accepts a key-value map in the `customFields` parameter. To define these key-value pairs, go to **Configuration** > **General** > **Custom Fields**.


<Image src="https://files.readme.io/b1dd78dfa214a51ea0bc50f50de3f1d092a2206c4fd9790eb3c98133c60fde4a-Screenshot_2024-08-29_at_10.45.52.png" alt="Define custom fields in Configuration > General." align="center" />


Custom fields appear on the single session view.

***

## Use Cases

The two most common ways to use custom fields are crosschecking collected data and passing internal identifiers.

### Crosscheck Data

If you already have a user's first and last name in your system, you can use that data to confirm that the person completing verification matches the existing user. To do this, set up a crosscheck between the data from the ID and the data in your system.

1. Add a Process node to your Workflow and select **Cross Check** from the drop-down.


<Image src="https://files.readme.io/2ae9314d62084c754c1d718004177b98e1bbb842a25dcbce7fad615fb30c2794-Screenshot_2024-08-29_at_10.59.15.png" alt="Add Cross Check node to Workflow." align="center" width="200px" />


2. Configure the Cross Check node:
   1. Click **Add New Comparison**.
   2. Enter a **_CrossCheck Name_**. Do not include special characters.
   3. Use the drop-downs to select sources and fields to compare. One source should be _CUSTOM\_FIELDS_ and the other is usually _ID_.
   4. Set the **Comparison Severity**. This determines the minimum match level required to pass.
   5. Click **Save Comparison**.
   6. Add more comparisons to the same Cross Check node as needed or return to the Workflow.


<Image src="https://files.readme.io/8a6d3b9eb113fb2f20334211ede57de9c53d283470a33bdb520fd6b52a4fb494-Screenshot_2024-08-29_at_10.59.24.png" alt="Click Add New Comparison to add the Cross Check node." align="center" width="400px" caption="Add new comparison" />



<Image src="https://files.readme.io/32ef80710c73b7d73ba140afc74a544bf3e7fb2fc658d6b0d1a2164b94fe9d87-Screenshot_2024-08-29_at_10.59.47.png" alt="The configurable sources and fields for the Cross Check node." align="center" width="400px" />


3. Add a [Condition](https://developer.incode.com/docs/conditions-for-workflows-20) to set the Yes and No paths after the Cross Check node. For example, if you are checking that first names match, configure the Condition so that a matching first name returns OK.


<Image src="https://files.readme.io/a30d0996bf0618a5bc26e4e54a8edcaf74cde2c3310467f43d04f037498b62ad-Screenshot_2024-08-29_at_11.00.27.png" alt="First Name crosscheck comparison must equal OK." align="center" width="500px" caption="Use crosscheck in conditions" />


### Pass Internal Identifiers, Tags, and Markers

Internal identifiers, tags, and markers distinguish different Sessions or connect with internal systems.

#### External Customer ID

To connect an Incode Session with your own Session, use the `externalCustomerId` parameter. This is an optional string parameter in the `omni/start` call.

#### Configuration ID

This is the ID of the Workflow the user will go through. To find it, go to the Workflows page in Dashboard, find the Workflow you want, and click **...** > **Copy ID** in the Actions column.


<Image src="https://files.readme.io/e25292c3ad1dc17bfeff9d2561dd1daf7dd1640d692d4b9b2ab65dd6581b53d2-Screenshot_2024-08-29_at_09.49.41.png" alt="Copy ID is listed third in the Actions column." align="center" width="150px" />


#### Redirect URL

Override the **_Redirect URL_** from a Workflow's settings to redirect per user or group. Use the format: `https://your.url`.