...
Since integrations can be triggered from either an issue event, scheduled job or (coming soon) a post function the possibilities are endless. REST Request actions can also be chained, using the response from the previous RINT REST request action as input for the chained integration(s).
Getting started
...
Create a new RINT REST Request action by clicking the "CREATE" button
The user interface has 3 sections; Configuration, Triggers, and Execution Log.
...
| Setting | Explanation |
|---|---|
| NAME | Name of the RINT Rest integrations & automation |
| Parent action | Specify a parent RINT Integration. Makes this integration a child to the parent. A child will be executed after successful execution of the parent. |
| Method | HTTP Method |
| Url | Target endpoint URL |
| Authentication Method | Currently supported auth. methods.
|
| Headers | Specifies the request headers required for the target endpoint. |
| Description | Generic description of what this integration does. |
| Body | REST body for the RINT integration REST request |
| Variables | Variables are only available for child integrations. This allows you to specify variables based on the parent REST response. Variables are configured by using JSONPath expressions. Read more about this in the chapter "Defining variables" All variables defined will be available in the variable scope that can be used when defining the urls, headers and body. Read more of this in the chapter "Using variables" JSON Path - Pick data from response Variables - Usage |
Triggers
You must specify a trigger for your RINT integration in order to wake up the integration.
...