# IVR Data Dip Power Automate Flow Configuration

Below are the two actions that need to be present in any IVR data dip flow.

![](/files/-MTgke2DLLv9VNzkObW0)

#### When a HTTP Request is Received Configuration

Copy the HTTP post URL to the appropriate location in IVR data dip state.

The Request body JSON schema determines what data is expected to be sent from the Contact Center IVR.  In the IVR data dip state, the InputParameterNames object determines what data is sent to the Flow.

Below is an example default schema:

```
{
    "type": "object",
    "properties": {
        "CallerNumber": {
            "type": "string"
        },
        "CallerName": {
            "type": "string"
        },
        "ScenarioId": {
            "type": "string"
        },
        "ivrName": {
            "type": "string"
        }
    }
}
```

Below is an example custom schema:

```
{
    "type": "object",
    "properties": {
        "GatherAccountNumber_result": {
            "type": "string"
        }
    }
}
```

#### Response Configuration

Add a header:

![](/files/-MTljaJhAlAmW5bX2gh5)

Add a value to the body. The body can only contain **one** value. This value will be returned in the response to the IVR. 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cc.docs.landis.cloud/appendix/ivr-data-dip-power-automate-flow-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.