Tutorial: Build your first workflow

Create a RESTful system

Set the base URL

Check the authorization

Add an endpoint

Open the Endpoints tab and click +. In the Add Endpoint dialog, pick the GET method and set the Name to getLatestRates, then confirm. On the endpoint page:

• Path: /latest
• On the Query tab, add one parameter: Name base, Value EUR, then click the green check to add the row. The value is the default the endpoint test uses; the workflow overrides it at runtime.

Back on the system page, the Endpoints tab now lists getLatestRates.

Test the endpoint

Click Test on the endpoint page. The Test GET getLatestRates modal shows the resolved URL and the query parameter. Click Test in the modal and read the response:

{
  "base": "EUR",
  "date": "2026-10-02",
  "rates": {
    "GBP": 0.85033,
    "JPY": 176.99,
    "USD": 1.1225
  }
}

The real response lists about 30 currencies; the rate values change daily. Click Use as Response Example to store the shape on the endpoint’s Response Example tab.

Create the workflow

Place the End node

Declare the data model, inputs, and outputs

Set the Start node sample input

{
  "baseCurrency": "EUR"
}

Add the REST API Call node

Drag a REST API Call node from the palette, connect Start to it, and name it Get rates (double-click the node title to rename it). Configure it:

• Endpoint: pick GET getLatestRates under the Exchange Rates system (the dropdown groups endpoints by system).
• Query Parameters → base: enter ${baseCurrency} in the field that reads Add value or variable. This replaces the test default with the workflow input.
• Response Key: rates

The Response Key is where the next node finds the call result: the node writes the whole HTTP response under input.rates, and the JSON body sits at input.rates.data.

Pick the rate with a Script node

Drag a Script node after Get rates, connect the two, and name it Pick USD rate. Keep the JS language tab and paste:

// input.rates = REST API Call result
const body = input.rates.data;
output.rate = body.rates.USD;
output.currency = "USD";

Scripts read the previous nodes’ data from input and publish their result by assigning keys on output. There is no return statement.

Connect the End node

Connect Pick USD rate to End Flow 001. The End node’s card shows an Output Schema with rate and currency. Whatever the previous nodes wrote under those keys is the workflow’s output, and it is what the calling process receives.

Run the workflow

Click Run Workflow in the top-right corner. On a draft project version the run starts immediately with the Start node’s JSON, and the Run Logs panel opens at the bottom: a Nodes list with the time each node took, and Logs, Input, and Output tabs. Open Output:

{
  "rate": 1.1225,
  "currency": "USD"
}

Each node card also gains Input and Output tabs with that run’s data, which is the quickest way to see what the REST call returned.

On a committed project version, Run Workflow opens a Test Workflow dialog first, where you edit the Test Input before running.

Create the process and its data model

Add the nodes

On the canvas, build: Start → Send Message Task named Get exchange rate → Receive Message Task named Receive exchange rate → End Process. Connect them in that order. To rename a node, select it and, in Node settings → Node Config, change Node name and click Save. The start and end nodes keep their default names, Start_001 and End_001.

The Start Integration Workflow action also works on Task and User Task nodes. The send-and-receive pair is the plain form: the send node fires the workflow, the receive node parks the token until the output arrives.

Add the Start Integration Workflow action

Select Get exchange rate, open Node settings → Actions, and click +. Give the action a name, check that Action Type is Start Integration Workflow (the default on a Send Message Task), and leave Trigger, Execution, and Navigation at their defaults, so the action runs on its own when the token arrives.In the workflow field (Search workflow by name), pick Get exchange rate. Under Data mapping, leave Legacy mapping off. The Input Mapping section lists the Workflow nodes that take input: click the wrench on the Start row.

Map the process data to the workflow input

The Data Mapping Integration Start Node Start modal opens. The left pane lists the process attributes sent to the workflow; the right pane lists the workflow’s input parameters.

1. If the left pane says No process Parameters, click Define parameters, tick selectedCurrency, and click Done.
2. In the right pane, click the field next to baseCurrency, type ${selectedCurrency}, and pick the suggestion that appears.
3. Click Confirm, then Save on the action form.

Receive the workflow output

Select Receive exchange rate and open Node settings → Node Config. Under Integration Output, click Add Stream and configure the Data Stream:

• Source: Workflow (the default)
• Select workflow: Get exchange rate
• Legacy Mapping: leave off

The Output Mapping section lists the workflow nodes that produce output. Click the wrench on the End Flow 001 row.

Map the workflow output to the process

The Data Mapping Integration End Node End Flow 001 modal opens, mirrored: the workflow’s output parameters on the left, the process attributes on the right.

1. Add the targets to the right pane: it says No process Parameters, so click Select from data model, tick rate and currency under exchangeResult, and click Done.
2. Next to exchangeResult.rate type ${rate} and pick the suggestion; next to exchangeResult.currency type ${currency} and pick the suggestion.
3. Click Confirm, then Save on the node.

Legacy Mapping is the alternative: turn it on and set a single Key Name, and the whole workflow output lands under that key without per-attribute mapping. The mapper is the default because it keeps the process data model explicit.

Start the process

{
  "selectedCurrency": "EUR"
}

Inspect the instance

Switch to Runtime and open Process Instances. The newest currencyLookup instance is FINISHED with End_001 as its current node. Open it: the diagram highlights the path Start → Get exchange rate → Receive exchange rate → End, the Variables tab shows the data, and the Tokens tab shows the single token with End_001 as its current node.