Jump to a Section

Events

  • New Request

    Start a Flow when a new request is created.

    Unless otherwise indicated, field types are text.

    Required fields are indicated by a red asterisk.

    Options

    • Service Desk (dropdown): Choose from the list of Jira Service Desks.
    • Request Type (dropdown): Choose from the list of request types for the selected Jira Service Desk.

    Important: Note the difference between Jira Service Desk request types and issue types. This event card monitors for a specified request type only, not an issue type.

    Output

    Request

    • Created Date: Date when the issue was created
    • Created Date ISO: Date when the issue was created in ISO format
    • Created Date Readable: Date when the issue was created in readable format
    • Created Date Unix: Date when the issue was created in Unix format
    • Issue ID: Unique identifier of the issue
    • Issue Key: Unique key assigned to the issue
    • Request Type ID: Unique identifier of the requested type
    • Service Desk ID: Unique identifier of the service desk
    • Description: Issue description
    • Due Date (date): Date when the issue is due
    • Priority: Priority of the issue
    • Attachment (list): Files attached to the issue
    • Summary: Issue summary

    Status

    • Status:The current status of the issue
    • Status Category: Category to which the issue is assigned to
    • Status Date: Date of the current status
    • Status Date ISO: Date of the current status in ISO format
    • Status Date Readable: Date of the current status in readble format
    • Status Date Unix: Date of the current status in Unix format

    Customer

    • Customer ID: Unique identifier of the customer
    • Email: Email of the customer
    • Display Name: Display name of the customer
    • Active? (true/false): If true, the customer is active
    • Timezone: Timezone of the customer

    Context

    • Execution ID: Unique identifier associated with the execution of the Flow
  • New Request in Queue

    Start a Flow when a new request is created in a queue.

    Unless otherwise indicated, field types are text.

    Required fields are indicated by a red asterisk.

    Options

    • Service Desk (dropdown): Choose from the list of Jira Service Desks.
    • Request Type (dropdown): Choose from the list of request types for the selected Jira Service Desk.
    • Queue (dropdown): Choose from the list of queues for the selected Jira Service Desk and Request Type.

    Important: Note the difference between Jira Service Desk request types and issue types. This event card monitors for a specified request type only, not an issue type.

    Output

    Request

    • Created Date: Date when the issue was created
    • Created Date ISO: Date when the issue was created in ISO format
    • Created Date Readable: Date when the issue was created in readable format
    • Created Date Unix: Date when the issue was created in Unix format
    • Issue ID: Unique identifier of the issue
    • Issue Key: Unique key assigned to the issue
    • Request Type ID: Unique identifier of the requested type
    • Service Desk ID: Unique identifier of the service desk
    • Description: Issue description
    • Due Date (date): Date when the issue is due
    • Priority: Priority of the issue
    • Attachment (list): Files attached to the issue
    • Summary: Issue summary

    Status

    • Status:The current status of the issue
    • Status Category: Category to which the issue is assigned to
    • Status Date: Date of the current status
    • Status Date ISO: Date of the current status in ISO format
    • Status Date Readable: Date of the current status in readble format
    • Status Date Unix: Date of the current status in Unix format

    Customer

    • Customer ID: Unique identifier of the customer
    • Email: Email of the customer
    • Display Name: Display name of the customer
    • Active? (true/false): If true, the customer is active
    • Timezone: Timezone of the customer

    Context

    • Execution ID: Unique identifier associated with the execution of the Flow
  • Request Updated

    Start a Flow when a request is updated.

    Unless otherwise indicated, field types are text.

    Required fields are indicated by a red asterisk.

    Options

    • Service Desk (dropdown): Choose from the list of Jira Service Desks.
    • Request Type (dropdown): Choose from the list of request types for the selected Jira Service Desk.

    Output

    Request

    • Created Date: Date when the issue was created
    • Created Date ISO: Date when the issue was created in ISO format
    • Created Date Readable: Date when the issue was created in readable format
    • Created Date Unix: Date when the issue was created in Unix format
    • Issue ID: Unique identifier of the issue
    • Issue Key: Unique key assigned to the issue
    • Request Type ID: Unique identifier of the requested type
    • Service Desk ID: Unique identifier of the service desk
    • Summary: Issue summary

    Status

    • Status:The current status of the issue
    • Status Category: Category to which the issue is assigned to
    • Status Date: Date of the current status
    • Status Date ISO Date of the current status in ISO format
    • Status Date Readable: Date of the current status in readble format
    • Status Date Unix: Date of the current status in Unix format

    Customer

    • Customer ID: Unique identifier of the customer
    • Email: Email of the customer
    • Display Name: Display name of the customer
    • Active? (true/false): If true, the customer is active
    • Timezone: Timezone of the customer

    Context

    • Execution ID: Unique identifier associated with the execution of the Flow

Actions

  • Create a Request

    Create a new request in Jira Service Desk.

    Unless otherwise indicated, field types are text.

    Required fields are indicated by a red asterisk.

    Options

    • Service Desk (dropdown): Choose from the list of Jira Service Desks.
    • Request Type (dropdown): Choose from the list of request types for the selected Jira Service Desk.

    Input

    The input fields in this card are dynamically generated based on your instance. Some of the fields are explained below:

    Request

    • Summary: issue summary
    • Components: list of components
    • Due date (date): date when the issue is due
    • Description: issue description
    • Priority (dropdown): priority of the issue
    • Labels (list): labels assigned to the issue
    • Affects Versions: list of affected versions

    Custom fields * Approvers (list): list of issue approvers

    Output

    • Issue ID: unique identifier for the issue
    • Issue Key: unique key assigned to the issue
  • Custom API Action

    Make a custom, authenticated HTTP call to the Jira Service Desk API.

    NOTE: This action is unlike other Jira Service Desk cards; refer to the Jira Service Desk API documentation.

    Options

    • Request Type (drop-down): one of five supported HTTP request methods (sometimes called verbs) in custom API calls:
      • GET retrieves data from a web server based on your parameters. GET requests a representation of the specified resource. If successful, GET will receive a 200 OK response message with the requested content. Refer to additional documentation here.
      • POST sends data to a web server based on your parameters. POST requests include actions like uploading a file. Multiple POSTs may result in a different outcome than a single POST, so you should be cautious about unintentionally sending multiple POSTs. If a POST is successful, you will receive a 200 OK response message. Refer to additional documentation here.
      • PUT sends data to a location in the web server based on your parameters. PUT requests include actions like uploading a file. The difference between a PUT and POST is that PUT is idempotent, meaning that the result of a single successful PUT is the same as many identical PUT’s. If a PUT is successful, you will receive a 200 response message (usually 201 or 204). Refer to additional documentation here.
      • PATCH applies partial modifications to a resource on a web server based on your parameters. PATCH is not idempotent, meaning that multiple PATCHs could have unintended consequences. If a PUT is successful, you will receive a 200 response message (usually 204). Refer to additional documentation here.
      • DELETE deletes the specified resource from the web server based on your parameters (if the resource exists). If a DELETE is successful, you will receive a 200 OK response message. Refer to additional documentation here.

    Input

    • Relative URL (text): The address on the web server you are attempting to interact with. Relative URL means that you don’t have to explicitly specify the protocol at the beginning of the URL (such as “http://“). This suggests to the web server that the interaction is occurring on the server (in this instance).

      Example: https://{{auth.domain}}.atlassian.net/rest/servicedeskapi{{input.Request.Relative URL}}
    • Query (object or text): JSON object that determines the action taken at the URL

      Example: {"name":"something-urgent"}
    • Headers (object): JSON object that determines the content type of the request. This will usually be a replica of the example below.

      Example: {"Content-type":"application/json"}

    Output

    • Status Code (number): success or failure of your HTTP request. Here is a list of all status codes.
    • Headers (object): A detailed context for the status code, unrelated to the output body. Response headers are dependent on your selected HTTP request option. Note that not all headers are response headers.
    • Body (object): data returned from your selected HTTP request (for example, the data from a GET request)
  • Read Queue Requests

    Read a list of all requests in a queue in Jira Service Desk using the queue ID.

    Unless otherwise indicated, field types are text.

    Required fields are indicated by a red asterisk.

    Options

    • Service Desk (dropdown): Choose from the list of Jira Service Desks.

    Input

    Queue

    • Queue ID: Unique identifier for the queue

    Output

    Queue

    • Requests(list)
      • Issue ID: Unique identifier of the issue
      • Issue Key: Unique key assigned to the issue
      • Summary: Issue summary
      • Description: Issue description
      • Components (list): List of components assigned to the issue
      • Due Date (date): Date when the issue is due
      • Labels (list): Labels assigned to the issue
      • Attachment (list): Files attached to the issue
      • Request Type ID: Unique identifier of the requested type
      • Service Desk ID: Unique identifier of the service desk
      • Created Date: Date when the issue was created
      • Created Date ISO: Date when the issue was created in ISO format
      • Created Date Readable: Date when the issue was created in readable format
      • Created Date Unix: Date when the issue was created in Unix format
      • Status:The current status of the issue
      • Status Category: Category to which the issue is assigned to
      • Status Date: Date of the current status
      • Status Date ISO: Date of the current status in ISO format
      • Status Date Readable: Date of the current status in readble format
      • Status Date Unix: Date of the current status in Unix format
      • Customer ID: Unique identifier of the customer
      • Customer Email: Email of the customer
      • Customer Display Name: Display name of the customer
      • Customer Active? (true/false): If true, the customer is active
      • Customer Timezone: Timezone of the customer
  • Read Request

    Read a request in Jira Service Desk using the issue ID or key.

    Unless otherwise indicated, field types are text.

    Required fields are indicated by a red asterisk.

    Options

    • Service Desk (dropdown): Choose from the list of Jira Service Desks.
    • Request Type (dropdown): Choose from the list of request types for the selected Jira Service Desk.

    Input

    Read by

    • Issue ID or Key: Unique identifier or key for the issue

    Output

    The output fields in this card are dynamically generated based on your instance. Some of the fields are explained below:

    Status

    • Status:The current status of the issue
    • Status Category: Category to which the issue is assigned to
    • Status Date: Date of the current status
    • Status Date ISO: Date of the current status in ISO format
    • Status Date Readable: Date of the current status in readble format
    • Status Date Unix: Date of the current status in Unix format

    Customer

    • Customer ID: Unique identifier of the customer
    • Email: Email of the customer
    • Display Name: Display name of the customer
    • Active? (true/false): If true, the customer is active
    • Timezone: Timezone of the customer
  • Subscribe to Request

    Subscribe to a request in Jira Service Desk.

    Unless otherwise indicated, field type is text.

    Required fields are indicated by a red asterisk.

    Input Fields

    Request

    • Issue Key or ID: unique key or identifier for the issue

    Output Fields

    Response * Status Code (number): success or failure of your HTTP request; here is a list of all status codes

  • Transition Request

    Transition a request in Jira Service Desk.

    Unless otherwise indicated, field type is text.

    Required fields are indicated by a red asterisk.

    Input Fields

    Request

    • Issue Key or ID: unique key or identifier for the issue
    • Transition ID: unique identifier for the transition
    • Comment: comment added to the transition request

    Output Fields

    Response * Status Code (number): success or failure of your HTTP request; here is a list of all status codes

  • Unsubscribe from Request

    Unsubscribe from a request in Jira Service Desk.

    Unless otherwise indicated, field type is text.

    Required fields are indicated by a red asterisk.

    Input Fields

    Request

    • Issue Key or ID: unique key or identifier for the issue

    Output Fields

    Response * Status Code (number): success or failure of your HTTP request; here is a list of all status codes