---
schema_version: "1"
id: cf4fe9b7d4d6ae4db87c12dbc9561c0f33114c5fe732323acd11e827a4fbebd0
title: Invoke an Omni-Channel Flow to Route Non-Real-Time Objects
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/omnichannel_use_flow_to_route.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.omnichannel_use_flow_to_route.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a98fcafabce59841d96576e384f54320aeeb6359e1a5be35fea6567f10d797f3
description: To route non-real-time objects, such as cases, leads, and custom objects, define the routing logic in an Omni-Channel flow, and then invoke the flow from a parent flow based on your business rules. For example, to trigger the flow to run when cases are created, add it as a subflow in a record-triggered flow. Or, to perform a custom transfer process, add it as a subflow in a screen flow.
products:
  - Service Cloud
release: "264"
---
# Invoke an Omni-Channel Flow to Route Non-Real-Time Objects

To route non-real-time objects, such as cases, leads, and custom objects, define the routing logic in an Omni-Channel flow, and then invoke the flow from a parent flow based on your business rules. For example, to trigger the flow to run when cases are created, add it as a subflow in a record-triggered flow. Or, to perform a custom transfer process, add it as a subflow in a screen flow.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small "><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.service_editions_reference.htm&amp;language=en_US" target="_blank">View supported editions</a>.</td></tr></tbody></table>

To show you one method for invoking an Omni-Channel flow for a non-real-time object, let’s look at how to use a record-triggered flow to invoke an Omni-Channel flow to route cases. To route cases in Email-to-Case, use an Omni-Channel flow instead of a record-triggered flow.

1. In the Quick Find box under Setup, enter Flows, and then select **Flows** under Process Automation.
2. Click **New Flow**.
    
    ![New Record Triggered Flow](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/support/images/omnichannel/omnichannel_flow_route_case.png)
3. Click **Record-Triggered Flow**, and then click **Create**.
4. In Object, select the non-real-time object. For example, to route cases, enter Case and select it.
5. In Trigger the Flow When, select when to trigger the subflow. For example, to route the case when it’s created, select **A record is created**.
6. Click **Done**.
    
    The record-triggered flow appears in the Flow Builder canvas.
    
    ![The flow contains the Start and End elements.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/support/images/omnichannel/voice_record_triggered_flow_case_routing.png)
7. Add a Subflow element to the flow by dragging the Subflow element from the Elements toolbox or clicking **+** in the flow.
8. In the New Subflow window, select the Omni-Channel flow.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/images/icon_tip.png)
    
    Tip To prevent a warning from appearing when you save the record-triggered flow, activate the Omni-Channel flow before adding it as a subflow.
9. Enter the label and API name for the subflow element.
10. In Select Input Values, select the case record ID in the recordId field.
    
    ![The subflow receives the case record ID as input.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/support/images/omnichannel/voice_record_triggered_flow_omniflow_subflow.png)
11. Click **Done**.
12. To connect the elements in the flow, drag the Start element onto the Subflow element.
    
    ![The line between the elements shows that they are connected.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/support/images/omnichannel/voice_record_triggered_flow_omniflow_with_subflow.png)
13. Save the record-triggered flow.