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/logic-apps/logic-apps-http-endpoint.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,21 +120,21 @@ If you're new to logic apps, see [What is Azure Logic Apps](../logic-apps/logic-
120
120
121
121

122
122
123
-
<a name="set-method"></a>
123
+
<a name="select-method"></a>
124
124
125
-
## Set expected request method
125
+
## Select expected request method
126
126
127
127
By default, the Request trigger expects a POST request. You can specify a different method to expect, but only a single method.
128
128
129
129
1. In the Request trigger, open the **Add new parameter** list, and select **Method**, which adds this property to the trigger.
130
130
131
131

132
132
133
-
1. From the **Method** list, select another method that the trigger expects instead. Or, you can specify a custom method.
133
+
1. From the **Method** list, select the method that the trigger should expect instead. Or, you can specify a custom method.
134
134
135
135
For example, select the **GET** method so that you can test your endpoint's URL later.
136
136
137
-

137
+

138
138
139
139
## Accept parameters in endpoint URL
140
140
@@ -144,17 +144,17 @@ When you want your endpoint URL to accept parameter values through the endpoint'
144
144
145
145
These values are passed as name-value pairs when sending the request to the endpoint's URL. For this option, you need to use the GET method in your Request trigger. In a subsequent action, you can get the parameter values as trigger outputs by using the `triggerOutputs()` function in an expression.
146
146
147
-
* [Accept values through a relative path](#relative-path) for the parameter in your Request trigger.
147
+
* [Accept values through a relative path](#relative-path) for parameters in your Request trigger.
148
148
149
-
You need to explicitly [set the method](#set-method) that your HTTPS request expects.
149
+
These values are passed when sending the request to the endpoint's URL. You also need to explicitly [select the method](#select-method) that the trigger expects. In a subsequent action, you can get the parameter values as trigger outputs by referencing those outputs directly.
150
150
151
151
<a name="get-parameters"></a>
152
152
153
153
### Accept values through GET parameters
154
154
155
155
1. In the Request trigger, open the **Add new parameter list**, add the **Method** property to the trigger, and select the **GET** method.
156
156
157
-
For more information, see [Set expected HTTPS method](#set-method).
157
+
For more information, see [Select expected request method](#select-method).
158
158
159
159
1. Under the Request trigger, add the action where you want to use the parameter value. For this example, add the **Response** action.
160
160
@@ -220,7 +220,7 @@ When you want your endpoint URL to accept parameter values through the endpoint'
220
220
221
221

222
222
223
-
1. To use the parameter, find and add a **Response** action to your logic app.
223
+
1. Under the Request trigger, add the action where you want to use the parameter value. For this example, add the **Response** action.
224
224
225
225
1. Under the Request trigger, select **New step** > **Add an action**.
226
226
@@ -230,13 +230,15 @@ When you want your endpoint URL to accept parameter values through the endpoint'
230
230
231
231
For example, suppose that you want the Response action to return `Postal Code: {postalCode}`.
232
232
233
-
In the **Body** property, enter `Postal Code: ` with a trailing space. From the dynamic content list that appears, select the **postalCode** token.
233
+
1. In the **Body** property, enter `Postal Code: ` with a trailing space. Keep your cursor inside the edit box so that the dynamic content list remains open.
234
+
235
+
1. In the dynamic content list, from the **When a HTTP request is received** section, select the **postalCode** token.
234
236
235
-

237
+

236
238
237
-
The **Body** property now includes the selected parameter:
239
+
The **Body** property now includes the selected parameter:
238
240
239
-

241
+

0 commit comments