Overview
Used to exchange data between Trava and external web applications via HTTP.
Description
The HTTP Notification step enables integration between Trava and external web applications by sending HTTP requests during scheme execution.
It allows you to send custom requests containing dynamic data from the processed PNR or ticket and optionally retrieve data from the HTTP response for use in subsequent workflow components.
The step sends an HTTP request using the configured method (POST, PUT, or PATCH) to the specified endpoint.
The request payload can consist of:
- custom text or JSON;
- one or more system variables;
- or a combination of both.
System variables are automatically populated with values from the processed PNR or ticket.
If configured, the response returned by the server can be parsed and stored in custom variables. These variables can then be used by subsequent workflow components, such as conditions, remarks, or additional HTTP Notification steps.
Settings
Use template
Applies a pre-saved configuration instead of manual setup. Useful when multiple schemes use HTTP Notification components with identical configurations.
ℹ️
Tip
Changing a shared template automatically updates all components using that template. For details on managing templates, see the
Templates section.
⚠️
Warning
Applying a template overwrites any settings entered manually in this step.
Endpoint url
Specifies the destination URL.
Supports:
- full path to an external HTTP/HTTPS resource, including the protocol (for example,
https://); - relative path when using the Trava API.
Authentication method
Specifies the authentication method used when sending the HTTP request.
Supports:
- Anonymous – no authentication.
- Basic authentication – uses a user name and password.
- Bearer token – uses a token obtained from an external service.
Selecting Basic authentication or Bearer token displays the corresponding additional fields.
⚠️
Warning
The selected authentication method and provided credentials must match the requirements of the receiving API.
Message
Specifies the content of the message to be sent.
Supports:
- plain text, or
- structured data (for example, JSON).
Can include custom variables to personalize the message content.
Variables
Selects one or more variables whose values are sent to the external application.
If at least one variable is selected, the system automatically generates the HTTP request body as JSON, where each variable name is used as a key and the value is populated from the processed PNR.
ℹ️
Tip
If
Message is also filled in, its content is added to the generated JSON under the
notificationMessage property.
HTTP custom headers
Allows adding custom HTTP headers to be sent with the request.
HTTP method
Specifies the HTTP method used to send the request.
Supports:
POST (default);PUT;PATCH.
Send as plain text
Specifies the format of the data sent in the HTTP request body.
- If enabled, the data is sent as plain text.
- If disabled, the data is sent in JSON format.
ℹ️
Tip
When custom variables are used in plain text mode, only the value of one variable is sent.
Number of notification attempts for erroneous responses
Specifies the maximum number of retry attempts before the system stops trying and raises an error.
Save response to custom variables
Allows capturing the server's response and storing a value from it in a custom variable. The stored value can be used as input for subsequent components or conditions in the workflow.
Preview
Allows testing the payload before scheme activation. Enter a specific PNR or select one from the list to view the exact JSON payload the system generates for that PNR.
Examples
Example 1
Sending a custom JSON message to an external web application (Postman) using a POST request.
Configured options:
- Endpoint URL:
https://postman-echo.com/post - Message:
{"sample_payload": "test"}
Payload:
{"sample_payload": "test"}
Response:
{
"args": {},
"data": {
"samplePayload": "test"
},
"files": {},
"form": {},
"headers": {
"host": "postman-echo.com",
"contentLength": "26",
"accept": "application/json",
"contentType": "application/json",
"traceparent": "00-a00bfb6096f35ea86ff902f0dd985ad9-e2cbcfb037f52ef6-01",
"acceptEncoding": "gzip, br",
"xForwardedProto": "https"
},
"json": {
"samplePayload": "test"
},
"url": "https://postman-echo.com/post"
}
Example 2
Sending JSON message with the values of the selected variables to an external web application (Postman) using POST request.
Configured options:
- Endpoint URL:
https://postman-echo.com/post - Selected variables
Payload:
{
"PNR": "HZJDOV",
"issuingCarriersCodes": ["AY"],
"destinationCityCode": "OSA"
}
Response:
{
"args": {},
"data": {
"PNR": "HZJDOV",
"issuingCarriersCodes": ["AY"],
"destinationCityCode": "OSA"
},
"files": {},
"form": {},
"headers": {
"host": "postman-echo.com",
"contentLength": "153",
"accept": "application/json",
"contentType": "application/json",
"traceparent": "00-af825e9bcd629cf2c3a1cc705f9111cc-8fd8fed62f3871e1-01",
"acceptEncoding": "gzip, br",
"xForwardedProto": "https"
},
"json": {
"notificationMessage": "{\"my_parameter\": \"value\"}",
"pNR": "HZJDOV",
"issuingCarriersCodes": ["AY"],
"destinationCityCode": "OSA"
},
"url": "https://postman-echo.com/post"
}
Example 3
Sending a message together with variables.
In this scenario, the component is used to send a JSON consisting of the value of the Message field and the values of the selected variables to an external web application using a POST request.
Payload:
{
"NotificationMessage": "{\"my_parameter\": \"value\"}",
"PNR": "WYDYES",
"IssuingCarriersCodes": ["AI"],
"DestinationCityCode": "KTM"
}
Response:
{
"args": {},
"data": {
"notificationMessage": "{\"my_parameter\": \"value\"}",
"pNR": "HZJDOV",
"issuingCarriersCodes": ["AY"],
"destinationCityCode": "OSA"
},
"files": {},
"form": {},
"headers": {
"host": "postman-echo.com",
"contentLength": "153",
"accept": "application/json",
"contentType": "application/json",
"traceparent": "00-af825e9bcd629cf2c3a1cc705f9111cc-8fd8fed62f3871e1-01",
"acceptEncoding": "gzip, br",
"xForwardedProto": "https"
},
"json": {
"notificationMessage": "{\"my_parameter\": \"value\"}",
"pNR": "HZJDOV",
"issuingCarriersCodes": ["AY"],
"destinationCityCode": "OSA"
},
"url": "https://postman-echo.com/post"
}
Note
Troubleshooting
If an issue occurs with the HTTP Notification component, take the following steps before submitting a bug report:
- Review the processing session log. Errors sending a request appear in the log with the status, response message, response content, endpoint URL, and variables used.
- Verify the error source. Server errors such as
500, 503, or 404 indicate a problem with the external application, not with Trava. - Confirm the outgoing request. If the request is formatted correctly and includes all required values, the request left the system as intended. Investigate the issue in the receiving service or your own infrastructure.
