The Send Web Request step allows you to send requests to REST endpoints to get data or post updates. If Workflow Manager is licensed with the ArcGIS Workflow Manager Server Advanced role, you can configure the REST endpoint's response as custom output values, save it as a file, and attach it to the job. The custom output values can be used to retrieve tokens for subsequent REST calls, determine the path the workflow follows, or be used as inputs for other steps throughout the workflow.
When the step is run, the web request is sent to the REST endpoint defined in the step.
The step can be finished by clicking the Complete Step button 
.
Configure the step
To configure the step, do the following:
Caution:
To reduce security vulnerabilities, only configure the Send Web Request step for trusted web pages and web apps.
- Create or edit a workflow diagram to access the Step Library panel.
- Drag Send Web Request from the Step Library panel to a connection arrow of a step on the workflow canvas.
The Step Details panel appears.
- Provide a name for the step in the Step Name text box.
- In the Arguments section, click Edit.
- Click the URL drop-down arrow and choose the type of request you want to send.
- Type the URL of the REST endpoint in the URL text box.
- Optionally, add path variables to the URL using the following syntax:
https://gisserver.domain.com/webadaptorname/apps/workflowmanager/:pathVariable/Path variables in the appear in the Path Variables section.
- If you added path variables to the URL, provide a value for each variable in the Path Variables section.
- Optionally, add query parameters to your request.
- Click Add Key & Value in the Query Parameters section.
- Provide a key in the Key text box.
- Provide a value in the Value text box.
- Leave the Enabled check box checked.
- Repeat substeps a through d to add more key-value pairs.
- Click the Authorization tab.
- Choose the REST endpoint's authentication method and provide authentication information as necessary.
Caution:
Authentication information you provide in the step is not encrypted. To secure the information, add an encrypted user-defined setting to store the information and reference it in the step using dynamic job properties.
- Optionally, click the Headers tab to add custom header key-value pairs to your request.
- Click Add Key & Value in the Custom Headers section.
- Provide a key in the Key text box.
- Provide a value in the Value text box.
- Leave the Enabled check box checked.
- Repeat substeps a through d to add more key-value pairs.
- Optionally, click the Body tab to add data to your request.
The request body supports form data key-value pairs, URL encoded key-value pairs, and raw data in JSON or plain text format.
Tip:
You can also use an Arcade expression to retrieve user-defined settings or provide a dynamic values in the body text.
- Optionally, if you have a license for ArcGIS Workflow Manager Server Advanced, configure the step's output settings.
- Click Save to close the Configure Web Request dialog box.
- Click the Options tab.
- Optionally, provide help text for the step in the Step Help text box.
You can also use the following example to display a dynamic value using ArcGIS Arcade expressions:
'For further assistance, please contact ' + jobCreator($job) + '.' - Optionally, click the Style tab to change the shape and color of the step.
- Optionally, click the About tab and provide a description for the step in the Step Description text box.
Note:
The About tab also contains the step's ID that can be used with dynamic job properties to obtain a step's output.
Configure output settings
License:
This functionality requires a license for the ArcGIS Workflow Manager Server Advanced role.
The ArcGIS Workflow Manager Server Advanced role allows you to save the REST endpoint's response as a file, attach it to the job, and configure it as custom output values. The output values can be used to determine the path the workflow follows or be used as inputs for other steps throughout the workflow. If an output value is not configured for the step, the HTTP status code is stored as the step's output value. To configure the step's output settings, do the following:
- Click the Output tab on the Configure Web Request dialog box.
If the Configure Web Request dialog box isn't available, click the Send Web Request step on the workflow canvas and click Edit in the Arguments section of the Step Details panel.
- Optionally, click the Enabled toggle button in the Attach Response section to save the REST endpoint's response as a file and attach it to the job.
- Optionally, perform these steps to configure the attachment name and folder in which it will be stored:
- Provide the name of the folder in
which the attachment will be stored in the Folder Name text box.
The folder name can't contain special characters.
Note:
If a folder name isn't provided, a folder named General is automatically created.
- Choose one of the following Attachment Name options:
- Autogenerated—Automatically names the attachment using the following syntax: <StepName>_<RunDate>_<RunTime>
- Custom—Allows a custom attachment name to be provided
- Provide the name of the folder in
which the attachment will be stored in the Folder Name text box.
- Optionally, perform these steps to configure custom output values for the REST endpoint's response:
- Click the Test Mode toggle button in the Output Values section.
- Paste an example of the REST endpoint's response in the Sample Response text box.
Example response in JSON format:
{"access_token": "", "expires_in":7199, "spatialReference": { "wkid": 4326, "latestWkid": 4326 }, "locations": [ { "name": "380 New York Street", "extent": { "xmin": -117.196701, "ymin": 34.055489 } } ]} - Click Add Output & Path.
- Provide a name for the output value in the Output Value text box.
This is the value name that is used to obtain the custom output value.
- Provide a JSONPath expression in dot notation or bracket notation for the value that you want to store in the Extraction Path text box.
Example JSONPath in dot notation:
$.access_tokenExample JSONPath in bracket notation:
$['locations'][0]['name']The value appears in the Sample Result column.
- Optionally, repeat substeps c through e to add more custom output values.
- Click Save to close the Configure Web Request dialog box.
Return value
When the step is completed, its return value is stored to indicate the result of the step. The return value can be immediately evaluated using paths to determine the next steps in the workflow. You can also retrieve the return value for completed steps throughout the workflow using ArcGIS Arcade expressions. The following table lists the step's return values:
| Return values | Description |
|---|---|
| S000001 | The step completed successfully. |
F000001 | The step failed to complete successfully. |
Output value
License:
This functionality requires a license for the ArcGIS Workflow Manager Server Advanced role.
When the step is completed, its output value is stored and can be used to determine the path the workflow follows or be used as inputs for other steps throughout the workflow. The following table shows the step's output value:
| Output | Description | ArcGIS Arcade expression syntax |
|---|---|---|
| Status | Returns the HTTP response code if an output value isn't configured for the step. | jobOutputValue($job, '<step_id>', 'Status') |
<CustomOutputValue> | Returns the custom output value you configured for the step. | jobOutputValue($job, '<step_id>', '<custom_output_value_name>') |