Skip to content

Update configuring-post-get-steps.md #11273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zaipie wants to merge 2 commits into
base: development
Choose a base branch
from
Open

Update configuring-post-get-steps.md #11273

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0109e71
Update configuring-post-get-steps.md
zaipie May 29, 2026
1b5a63b
Update mendix-pipelines.md
zaipie May 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 19 additions & 4 deletions content/en/docs/deployment/general/mendix-pipelines/configuring-post-get-steps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,22 @@ The following table summarizes the available configuration fields.
| **Polling interval** | Yes (GET only) | Time in seconds between GET retries. Range: 5–300. | `10` |
| **Polling duration** | Yes (GET only) | Maximum time in seconds to poll before timing out and failing. Range: 0–10800. | `600` |

## Configuring Variables

### Variable Selector

To simplify inserting variables, Mendix Pipelines provides a **Variable Selector**.
Typing `$` in a supported input field opens a dropdown list with available variables. The list is dynamically populated with all step outputs from previous steps and also includes the user-defined variables.
Selecting a variable inserts it into the field.


### Benefits

- Reduces errors caused by manual typing
- Helps discover available variables
- Speeds up configuration


## API Endpoint

Both POST and GET request steps require an endpoint defined as a URL. Mendix Pipelines builds the endpoint as `Base URL Path + Additional URL Path`. The endpoint can be:
Expand All @@ -57,16 +73,15 @@ When you use a variable in the URL, the following rules apply:
* The variable must be the last part of the URL.
* You cannot append additional text after the variable (no concatenation).

## HTTP Headers
## HTTP Request Headers

HTTP headers can be added along with the API calls to provide metadata for the request, such as content type, authentication credentials, or other API-specific values. Mendix recommends storing secrets such as API keys or tokens as [pipeline variables](/developerportal/deploy/mendix-pipelines/#variable-tab).

POST and GET request steps support the following header rules:

* You can define up to five headers as key-value pairs.
* Header names must be static strings.
* Header values can be static strings or predefined pipeline variables.
* Header values do not support string concatenation.
* Header keys and values can be a static string or a pipeline variable.
* Header keys and values do not support string concatenation.
* Header values are resolved when the step starts.
* For GET request steps, header values are fixed and are not re-evaluated during polling.

Expand Down
6 changes: 6 additions & 0 deletions content/en/docs/releasenotes/deployment/mendix-pipelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,12 @@ To see the current status of the Mendix Pipelines, see [Mendix Status](https://s

## 2026

### May 28, 2026

#### New Features

* We have added a Variable Selector widget to the Post and Get request steps, which makes configuring variables a lot easier. For information about how to use the widget in these steps, refer to [Configuring Variables](/developerportal/deploy/configuring-post-get-request-steps/#configuring-variables).

### May 14, 2026

#### New Features
Expand Down