Skip to content

Commit a5a00a9

Browse files
committed
Clarity edits
1 parent 8c986e5 commit a5a00a9

File tree

2 files changed

+14
-12
lines changed

2 files changed

+14
-12
lines changed

articles/logic-apps/logic-apps-http-endpoint.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -120,21 +120,21 @@ If you're new to logic apps, see [What is Azure Logic Apps](../logic-apps/logic-
120120

121121
![Copy endpoint URL from Azure portal](./media/logic-apps-http-endpoint/copy-manual-trigger-callback-url-post.png)
122122

123-
<a name="set-method"></a>
123+
<a name="select-method"></a>
124124

125-
## Set expected request method
125+
## Select expected request method
126126

127127
By default, the Request trigger expects a POST request. You can specify a different method to expect, but only a single method.
128128

129129
1. In the Request trigger, open the **Add new parameter** list, and select **Method**, which adds this property to the trigger.
130130

131131
![Add "Method" property to trigger](./media/logic-apps-http-endpoint/select-add-new-parameter-for-method.png)
132132

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.
134134

135135
For example, select the **GET** method so that you can test your endpoint's URL later.
136136

137-
![Select HTTPS method to use for trigger](./media/logic-apps-http-endpoint/select-method-request-trigger.png)
137+
![Select request method expected by the trigger](./media/logic-apps-http-endpoint/select-method-request-trigger.png)
138138

139139
## Accept parameters in endpoint URL
140140

@@ -144,17 +144,17 @@ When you want your endpoint URL to accept parameter values through the endpoint'
144144

145145
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.
146146

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.
148148

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.
150150

151151
<a name="get-parameters"></a>
152152

153153
### Accept values through GET parameters
154154

155155
1. In the Request trigger, open the **Add new parameter list**, add the **Method** property to the trigger, and select the **GET** method.
156156

157-
For more information, see [Set expected HTTPS method](#set-method).
157+
For more information, see [Select expected request method](#select-method).
158158

159159
1. Under the Request trigger, add the action where you want to use the parameter value. For this example, add the **Response** action.
160160

@@ -220,7 +220,7 @@ When you want your endpoint URL to accept parameter values through the endpoint'
220220

221221
![Specify the relative path for the parameter](./media/logic-apps-http-endpoint/relative-path-url-value.png)
222222

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.
224224

225225
1. Under the Request trigger, select **New step** > **Add an action**.
226226

@@ -230,13 +230,15 @@ When you want your endpoint URL to accept parameter values through the endpoint'
230230

231231
For example, suppose that you want the Response action to return `Postal Code: {postalCode}`.
232232

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.
234236

235-
![Add the specified parameter to response body](./media/logic-apps-http-endpoint/relative-url-with-parameter-token.png)
237+
![Add the specified parameter to response body](./media/logic-apps-http-endpoint/relative-url-with-parameter-token.png)
236238

237-
The **Body** property now includes the selected parameter:
239+
The **Body** property now includes the selected parameter:
238240

239-
![Example response body with parameter](./media/logic-apps-http-endpoint/relative-url-with-parameter.png)
241+
![Example response body with parameter](./media/logic-apps-http-endpoint/relative-url-with-parameter.png)
240242

241243
1. Save your logic app.
242244

0 Bytes
Loading

0 commit comments

Comments
 (0)