Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

This is where all the configuration is setup.

  • Name - The name of this integration Action
  • Auto-generate 1st level variables. If this action is a child or is triggered by an incoming rule, select this option to autogenerate variables from the response from its parent. Read more on JSON variables from a response here: JSON Path - Pick data from response and here: Automatic response variables
  • Variables, see link on json path variables in the bullet above
  • Select Parent - Optional, define a parent for this integration action.  Can be another Integration action or a Group for the folder structure
  • Method, URL, pagination - HTTP Method (POST, PUT, GET ie) and the target endpoint URL is entered here. Select pagination if the endpoint returns a paginated result. Read more: Paginated requests

URL

URL will be URL encoded in the background, dot add url encode. For instance use regular space instead of %20


  • Authentication  - A pre-defined authentication method that this Integration request uses. Read more here on how to configure authentication methods Credentials
  • Headers - Add one or more headers that will be sent in the request.
  • Description - General description of what this integration does
  • Issue attachments -  Specifies if this integration will include any attachments Note: When including attachments the content type will be multipart/data Read more: Attachments - Multipart data
    • Do not include - No attachments are sent
    • Lates - Includes the latest added attachment to the issue that triggers this integration action
    • All - Always includes all attachments
    • Incoming files, choose this option if this integration is part of an incoming rule and must support incoming files 
  • Encoding - Encoding of data that is sent / read from a parent

  • Body - The REST request body to send. This body will be evaluated and replace variables with actual values before the request is sent. Ihub uses Mustache to access the pre-defined variables above and or the default variables. Read more: Mustache Variables 
    • Use the lookup field syntax to lookup a variable name. 
    • Test the body by entering an issue key next to the resolve body button. The body will then be evaluated and displayed so that you can verify your syntax

Read more here: 


  • No labels