Skip to main content

Hello World Codelab 2

Part 2

In Part 1 of the Hello World code lab, we created a simple "Hello World" application with a Java worker in the Orkes Conductor Playground.

first workflow

In this section, we'll extend the workflow, adding another task to personalize our workflow.

Topics Covered

Improving on "Hello World"

The initial workflow was very simple, so in this version of Hello World, we'll use the user's IP to determine their location (and thus their time zone and current time).

Since all web requests include the requestor's IP, it can be assumed that the workflow will include the users IP address. We will add another task to make an API call to get the user's location from their IP address.

The HTTP Task

Conductor has several System Tasks that can be run on the Conductor server and do not need separate worker applications to complete the task. The HTTP task is one of these. We can use this task to ping with our users' IP addresses, and this API will respond with information that we can use as a part of our workflow.

Note: System Tasks do not require uniqueIds. They also do not require a separate definition: they can be defined inside the workflow.

Updating the workflow

To add the HTTP Task, we simply update the workflow. We make 2 changes to the workflow outside of the new task:

  1. Version is set to 2.
  2. We add an outputParameter from the new task.

Adding the HTTP Task

To add this task to the workflow, we add it after the hello_world_<uniqueid> task.

The parameters of this task are:

  1. The HTTP Request. There are 2 parameters, the URI and the method (in this case, GET).
  2. Type is defined as HTTP.

The URI parameter uses a Conductor variable in the string. The parameter ${workflow.input.ipaddress} indicates that the workflow will have an input parameter called ipaddress.

"name": "hello_world_<uniqueId>",
"description": "hello world Workflow",
"version": 2,
"tasks": [
"name": "hello_world_<uniqueid>",
"taskReferenceName": "hello_world_ref",
"inputParameters": {},
"type": "SIMPLE",
"decisionCases": {},
"defaultCase": [],
"forkTasks": [],
"startDelay": 0,
"joinOn": [],
"optional": false,
"defaultExclusiveJoinTask": [],
"asyncComplete": false,
"loopOver": []
"name": "Get_IP",
"taskReferenceName": "get_IP",
"inputParameters": {
"http_request": {
"uri": "${workflow.input.ipaddress}?fields=status,message,country,countryCode,region,regionName,city,zip,lat,lon,timezone,offset,isp,org,as,query",
"method": "GET"
"type": "HTTP"

"outputParameters": {

"hw_response": "${hello_world_ref.output.hw_response}",
"hw_location": "We hope the weather is nice near ${}"

"schemaVersion": 2,
"restartable": true,
"workflowStatusListenerEnabled": true,
"ownerEmail": "",
"timeoutPolicy": "ALERT_ONLY",
"timeoutSeconds": 0,
"variables": {},
"inputTemplate": {}

The get_IP task sends a GET request to the URL - with the user's IP address as part of the query string.

The response comes back with details about this IP address in JSON format. One of the parameters is the City where the IP address is located. We'll use the output of this API call to return the city name:

"hw_location": "We hope the weather is nice near ${}"

When this change is made to the workflow, there are now two versions of the workflow. In the screenshot below, there is a "2" in the URL path and as a dropdown next to the workflow name:

workflow version 2 screenshot

Running the new workflow

Clicking the Run Workflow button - now there are two options for the version. Let's pick version 2, and in the input, add:

{"ipaddress":"<your IP address>"}

To find your IP address: Google "What's my IP address?"

Click run workflow, and click on the workflowId. If either of the tasks is blue, click the refresh until they are green:

hello world 2 completed

Clicking the Workflow Input/Output tab should display something similar to the following:


"hw_location":"We hope the weather is nice near Kennebunk"
"hw_response":"Hello World!"

Task Results

From the completed workflow diagram, click on the get_IP green box. This will provide details about the task that ran during the workflow. A side panel will open on the right. If you click the Output tab, we can get more details on the API response that was generated by this task:

HTTP Task Response

The response is shown here in completion: with all the data in response.body. Here we see that the city is Kennebunk, ME, USA; the timezone, the offset from GMT (in seconds) and the ISP name (along with the IP address that was the initial query).

We'll use more of these details as we continue through the codelab.

Next Steps

We've completed part 2 of the codelab.

In Part 1, we created a workflow using the Netflix Conductor in the Orkes Playground.

In Part 2, we extended the workflow using versioning and added an HTTP Task.

In Part 3, we'll investigate using FORK tasks in your Workflow. Ready to continue? Let's go! On to Part 3