---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure a response processor

# Configure a response processor {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure a response processor to handle responses from datacenters.

## Before you begin

* The CI class types for your resources must already exist in the CMDB. If you created custom products or providers in CAPI, you must also create custom CI types so the response processor knows how to identify CIs. See [Create a CI class for a virtual cloud resource](https://servicenow-prod.fluidtopics.net/AncR85at9DOKMZf2_kB_CA "If the base system does not provide a CI type for cloud-based virtual resources, you can create a CI class based on the virtual machine object class.") for information on creating CI types.

{#configure-response-processor__ul_obq_fww_52b}

Role required: sn_cmp.cloud_service_designer

## About this task

After each step is completed, the datacenter sends a response to the ECC Queue of the
MID Server. For example, if a user provisions a virtual server on
an AWS datacenter, AWS sends information about the new virtual server to the ECC
Queue. The system needs to create a CI in the CMDB for the virtual server. It does
this using a response processor.  
Alternatively, you can use pattern-based targeted discovery to handle responses from the datacenters. For more information, see [Pattern-based targeted discovery](https://servicenow-prod.fluidtopics.net/2gWabfmYBf3yKM~CXiRSRw#pattern-based-targeted-discovery "Automatically discover the newly provisioned cloud resources and store their information in the ServiceNow ServiceNow Configuration Management Database (CMDB) by using pattern-based targeted discovery.").  
Note:  
The resource type for which you are adding the response processor script must exist in the \[sn_capi_resource_type\] table.

## Procedure

1. Open a resource block, and click the Resource Script tab.  
   Ensure that the resource block is not in the published state.
2. Click New.
3. In the Name field, enter the name for the resource script.
4. In the Script field, enter a script.
5. Click Submit.
6. Click the Operations tab on the resource block.
7. Click the Steps sub tab.
8. Click a step.
9. Click the Response Processor tab for the step.
10. Click the add icon (![Adding a response processor]()).
11. In the Script Name field, select the processor you just created.
12. Click Submit.  
    The response processor script can process the response from the cloud provider for the CI type of the resource block.
* **[Execute response processor for workflow](https://servicenow-prod.fluidtopics.net/y3~ESQw0JWz_aTOcmFlxLQ)**   
  Execute a response processor for a workflow to get the workflow data back into a configuration item (CI). The response processor picks up the data, sends the data to the CMDB which in turn puts the data in a CI.
* **[Virtual server response processor example](https://servicenow-prod.fluidtopics.net/A5wYPnfWTvbJFOq~afGE2w)**   
  The Create_Virtual_Server_Response_Processor script, which is available by default in Cloud Provisioning and Governance, is the response processor that handles the creation of AWS virtual machine CIs.

