You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/connectors/connectors-native-reqres.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -418,31 +418,31 @@ When you use the Request trigger to receive inbound requests, you can model the
418
418
419
419
1. In the workflow designer, under the step where you want to add the Response action, select **New step**.
420
420
421
-
For example, using the Request trigger from earlier:
421
+
Or, to add an action between steps, move your pointer over the arrow between those steps. Select the plus sign (**+**) that appears, and then select **Add an action**.
422
422
423
-

423
+
The following example adds the Response action after the Request trigger from the preceding section:
424
424
425
-
To add an action between steps, move your pointer over the arrow between those steps. Select the plus sign (**+**) that appears, and then select **Add an action**.
425
+

426
426
427
-
1. Under **Choose an action**, in the search box, enter `response` as your filter, and select the **Response** action.
427
+
1. On the designer, under the **Choose an operation** search box, select **Built-in**. In the search box, enter **response**. From the actions list, select the **Response** action.
428
428
429
-

429
+
For simplicity, the following examples show a collapsed Request trigger.
430
430
431
-
The Request trigger is collapsed in this example for simplicity.
431
+

432
432
433
-
1. Add any values that are required for the response message.
433
+
1. In the Response action information box, add the required values for the response message.
434
434
435
435
In some fields, clicking inside their boxes opens the dynamic content list. You can then select tokens that represent available outputs from previous steps in the workflow. Properties from the schema specified in the earlier example now appear in the dynamic content list.
436
436
437
-
For example, for the **Headers** box, include `Content-Type` as the key name, and set the key value to `application/json` as mentioned earlier in this topic. For the **Body** box, you can select the trigger body output from the dynamic content list.
437
+
For example, for the **Headers** box, include **Content-Type** as the key name, and set the key value to **application/json** as mentioned earlier in this article. For the **Body** box, you can select the trigger body output from the dynamic content list.

440
440
441
441
To view the headers in JSON format, select **Switch to text view**.
442
442
443
-

443
+

444
444
445
-
Here is more information about the properties that you can set in the Response action.
445
+
The following table has more information about the properties that you can set in the Response action.
446
446
447
447
| Property name | JSON property name | Required | Description |
@@ -451,7 +451,7 @@ When you use the Request trigger to receive inbound requests, you can model the
451
451
| **Body** | `body` | No | The response body |
452
452
|||||
453
453
454
-
1. To specify additional properties, such as a JSON schema for the response body, open the **Add new parameter** list, and select the parameters that you want to add.
454
+
1. To add more properties for the action, such as a JSON schema for the response body, open the **Add new parameter** list, and select the parameters that you want to add.
455
455
456
456
1. When you're done, save your logic app. On the designer toolbar, select **Save**.
0 commit comments