Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


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). 

Image RemovedImage Added

Getting started


Create a new RINT REST Request action by clicking the "CREATE" button

Image RemovedImage Added

The user interface has 3 sections; Configuration, Triggers, and Execution Log. 




NAMEName of the RINT Rest integrations & automation
Parent actionSpecify a parent RINT Integration. Makes this integration a child to the parent. A child will be executed after successful execution of the parent.
MethodHTTP Method
UrlTarget endpoint URL
Authentication Method

Currently supported auth. methods.

  • Basic Auth
  • Bearer token
  • Parent - Uses the same authentication as the parent integration Only applicable for child integrations. 

HeadersSpecifies the request headers required for the target endpoint.
DescriptionGeneric description of what this integration does.
BodyREST body for the RINT integration REST request

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


You must specify a trigger for your RINT integration in order to wake up the integration.