Use this function to execute a JWT remote action.
executeRemoteAction(actionName) #Output: Text
Examples
|
Parser expression |
Description |
|---|---|
|
Bash
|
This example executes the action called "Great action" and returns the whole JSON response. |
Additional information
Parameters used in this function
|
Parameter |
Input (data type) |
Description |
|---|---|---|
|
|
text |
Name of the action to execute (case sensitive) |
Output
The function returns a text representing the following JSON:
{
"status": 200 // Returned status code from the executed action
"body": any // Response body that was returned from the executed action
}
Variant where you can specify a JMESPath.
executeRemoteAction(actionName, JMESPath) #Output: Text
Examples
|
Parser expression |
Description |
|---|---|
|
Bash
|
This example executes the action called "Great action" and returns only the body part of the JSON response. |
|
Bash
|
This example executes the action called "Great action" and returns only the data part of the JSON response's body object. |
|
Bash
|
This example executes the action called "Great action" and returns only the status code of the JSON response. |
Additional information
Parameters used in this function
|
Parameter |
Input (data type) |
Description |
|---|---|---|
|
|
text |
Name of the action to execute (case sensitive) |
|
|
text |
This parameter holds the JMESPath which is applied to the returned json object
|
Output
The function returns a text representing the following JSON (depending on the provided JMESPath):
{
"status": 200 // Returned status code from the executed action
"body": any // Response body that was returned from the executed action
}
Variant where you can specify additional parameters.
executeRemoteAction(actionName, parameterList) #Output: Text
Examples
|
Parser expression |
Description |
|---|---|
|
Bash
|
This example executes the action called "Great action" and returns the whole json response. In addition, the parameters "query" and "path" will be added to the request. |
|
Bash
|
This example executes the action called "POST action" and returns the whole json response. In addition, the action's request body will be populated with the provided JSON. |
Additional information
Parameters used in this function
|
Parameter |
Input (data type) |
Description |
|---|---|---|
|
|
text |
Name of the action to execute (case sensitive) |
|
|
Parameter list |
The parameter list's syntax is ["key": "value", "key2": "anotherValue", "key3": 12, ...]. The key must always be a text and unique within the parameter list. The value can be of type text or number. It is also possible to enter there parser expressions that return either a text or a number. The parameter list can be used to overwrite parameters set in the action configuration like the following:
|
Output
The function returns a text representing the following JSON:
{
"status": 200 // Returned status code from the executed action
"body": any // Response body that was returned from the executed action
}
Variant where you can specify additional parameters and another connection.
executeRemoteAction(actionName, parameterList, connectionName) #Output: Text
Examples
|
Parser expression |
Description |
|---|---|
|
Bash
|
This example executes the action called "Great action" and returns the whole json response. In addition, the parameters "query" and "path" will be added to the request and the connection called "Some other connection" is being used. |
Additional information
Parameters used in this function
|
Parameter |
Input (data type) |
Description |
|---|---|---|
|
|
text |
Name of the action to execute (case sensitive) |
|
|
Parameter list |
The parameter list's syntax is ["key": "value", "key2": "anotherValue", "key3": 12, ...]. The key must always be a text and unique within the parameter list. The value can be of type text or number. It is also possible to enter there parser expressions that return either a text or a number. The parameter list can be used to overwrite parameters set in the action configuration like the following:
|
|
|
text |
Name of the connection to use for the action (case sensitive) |
Output
The function returns a text representing the following JSON:
{
"status": 200 // Returned status code from the executed action
"body": any // Response body that was returned from the executed action
}
Variant where you can specify a JMESPath and additional parameters.
executeRemoteAction(actionName, JMESPath, parameterList) #Output: Text
Examples
|
Parser expression |
Description |
|---|---|
|
Bash
|
This example executes the action called "Great action" and returns only the data part of the response's body. In addition, the parameters "query" and "path" will be added to the request and the connection called "Some other connection" is being used. |
Additional information
Parameters used in this function
|
Parameter |
Input (data type) |
Description |
|---|---|---|
|
|
text |
Name of the action to execute (case sensitive) |
|
|
text |
This parameter holds the JMESPath which is applied to the returned json object
|
|
|
Parameter list |
The parameter list's syntax is ["key": "value", "key2": "anotherValue", "key3": 12, ...]. The key must always be a text and unique within the parameter list. The value can be of type text or number. It is also possible to enter there parser expressions that return either a text or a number. The parameter list can be used to overwrite parameters set in the action configuration like the following:
|
Output
The function returns a text representing the following JSON (depending on the provided JMESPath):
{
"status": 200 // Returned status code from the executed action
"body": any // Response body that was returned from the executed action
}
Variant where you can specify a JMESPath and another connection.
executeRemoteAction(actionName, JMESPath, connectionName) #Output: Text
Examples
|
Parser expression |
Description |
|---|---|
|
Bash
|
This example executes the action called "Great action" and returns the whole JSON response. In addition, the connection called "Different connection" is being used. |
Additional information
Parameters used in this function
|
Parameter |
Input (data type) |
Description |
|---|---|---|
|
|
text |
Name of the action to execute (case sensitive) |
|
|
text |
This parameter holds the JMESPath which is applied to the returned json object
|
|
|
text |
Name of the connection to use for the action (case sensitive) |
Output
The function returns a text representing the following JSON (depending on the provided JMESPath):
{
"status": 200 // Returned status code from the executed action
"body": any // Response body that was returned from the executed action
}
Variant where you can specify a JMESPath, a connection and additional parameters.
executeRemoteAction(actionName, JMESPath, connectionName, parameterList) #Output: Text
Examples
|
Parser expression |
Description |
|---|---|
|
Bash
|
This example executes the action called "Great action" and returns only the data part of the response's body. In addition, the parameters "query" and "path" will be added to the request and the connection called "cool connection" is being used. |
Additional information
Parameters used in this function
|
Parameter |
Input (data type) |
Description |
|---|---|---|
|
|
text |
Name of the action to execute (case sensitive) |
|
|
text |
This parameter holds the JMESPath which is applied to the returned json object
|
|
|
text |
Name of the connection to use for the action (case sensitive) |
|
|
Parameter list |
The parameter list's syntax is ["key": "value", "key2": "anotherValue", "key3": 12, ...]. The key must always be a text and unique within the parameter list. The value can be of type text or number. It is also possible to enter there parser expressions that return either a text or a number. The parameter list can be used to overwrite parameters set in the action configuration like the following:
|
Output
The function returns a text representing the following JSON (depending on the provided JMESPath):
{
"status": 200 // Returned status code from the executed action
"body": any // Response body that was returned from the executed action
}
📚 Use cases and examples
| Use case | JWT feature | Workflow function | Field type | Automated action | Parser functions |
|---|---|---|---|---|---|
| Display reporters of linked Cloud issues |
(input latin letters) |
Text | |||
| Sum of Tempo billable hours |
|
Number |