---
schema_version: "1"
id: 91574eaf520b997a0de046fb42516461c12b4f895d3998d02068aebb58d39e5d
title: Configure a Custom Asynchronous Callout
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_configure_a_custom_asynchronous_callout_236208.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_configure_a_custom_asynchronous_callout_236208.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c1c116c0cd5d1b3bed5894f315f6f8533fb6377f080c520b20391cf1f8ecb77a
description: You can configure a Callout Task capable of synchronously calling an Integration Procedure, but asynchronously awaiting one or more responses from a third party application.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Configure a Custom Asynchronous Callout

You can configure a Callout Task capable of synchronously calling an Integration Procedure, but asynchronously awaiting one or more responses from a third party application.

1. Create a System SObject:
    1. From the + tab, click Systems.
    2. Click New.
    3. Enter a dummy URL as it will be ignored by the implementation because you are calling an Integration Procedure instead of making a call to a REST endpoint.
    4. Save your work. The page for your new system appears.
2. In your new system, click New System Interface.
    
    System
    
    Create a system interface SObject
    
    Path
    
    Use the Integration Procedure key, which is typically, <type>\_<subtype>.
    
    Implementation
    
    Specify the class shown above without the .cls extension.
3. Create a new Callout Task for an Orchestration Plan:
    1. From the + tab, click Orchestration Plan Definitions.
    2. Select a plan.
    3. Click New Orchestration Item Definition.
    4. From Record Type of new records, select Callout.
    5. Set the System Interface to the one you just created.
    6. Save your work.
4. Verify the Integration Procedure you are attempting to call has been activated and proceed to create a test order with appropriate products to trigger the Orchestration Plan Definition. Decompose the order and start the orchestration plan to see the results.  In this case, the Orchestration Item should remain in an 'Active' state as shown in blue. Orchestration Item remains active until a successful callback is made.
5. Make a callback manually with Postman or another tool. Determine the callback URL.  Click the Orchestration Item and open it to capture the SObject ID of the Callout Task from the URL.  Use that Id to run a SOQL Query, such as:
    
    SELECT Name,Request\_\_c FROM vlocity\_cmt\_\_OrchestrationItem\_\_c WHERE Id = 'a2b1U0000001ZtLQAU'
    
    The Request\_\_c field contains the JSON payload that was sent to the third-party system and the callback URL, which is referred to as the responseUri, within the JSON string.  It is usually in the format:
    
    /services/apexrest/vlocity\_cmt/asyncCallback/<orchestration\_item\_id>

After you make a successful callback, the Orchestration Item changes to a Completed state. It may take a few seconds for it to update.