---
metadata:
  - name: generator
    content: Diplodoc Platform v5.66.1
  - property: og:type
    content: article
  - property: article:section
    content: API reference
  - property: og:title
    content: Getting trigger parameters
  - property: article:tag
    content: Technical guide
alternate:
  - https://yandex.ru/support/tracker/en/api/queues/get-trigger.md
  - https://yandex.ru/support/tracker/ru/api/queues/get-trigger.md
  - href: https://yandex.ru/support/tracker/en/api/queues/get-trigger.md
    type: text/markdown
    title: Markdown version
  - href: https://yandex.ru/support/tracker/en/llms.txt?revision=r22057024
    rel: describedby
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/tracker/en/llms.txt?revision=r22057024


# Getting trigger parameters

Use this request to get information about a queue [trigger](https://yandex.ru/support/tracker/en/user/create-trigger.md).

<div class="request_example yfm-code-floating-container method_get">
    <p>GET</p>
    <pre><code>https://api.tracker.yandex.net/v3/queues/{queue_ID}/triggers/{trigger_ID}</code></pre>
    <button class="yfm-clipboard-button"><svg width="16" height="16" viewBox="0 0 24 24" class="yfm-clipboard-icon" data-animation="15">
    <path fill="currentColor" d="M19,21H8V7H19M19,5H8A2,2 0 0,0 6,7V21A2,2 0 0,0 8,23H19A2,2 0 0,0 21,21V7A2,2 0 0,0 19,5M16,1H4A2,2 0 0,0 2,3V17H4V3H16V1Z"></path>
    <path stroke="currentColor" fill="transparent" strokewidth="1.5" d="M9.5 13l3 3l5 -5" visibility="hidden">
        <animate id="visibileAnimation-15" attributeName="visibility" from="hidden" to="visible" dur="0.2s" fill="freeze" begin=""></animate>
        <animate id="hideAnimation-15" attributeName="visibility" from="visible" to="hidden" dur="1s" begin="visibileAnimation-15.end+1" fill="freeze"></animate>
    </path>
</svg>
</button>
</div>

<!-- source: en/api/_assets/style/methods.md -->

<!-- endsource: en/api/_assets/style/methods.md -->

## Query format {#query}

Before making a request, [get permission to access the API](https://yandex.ru/support/tracker/en/api/access.md).

To get trigger parameters, use an HTTP `GET` request:

```json translate=no
GET /v3/queues/{queue_ID}/triggers/{trigger_ID}
Host: api.tracker.yandex.net
Authorization: OAuth API_TOKEN
X-Org-ID or X-Cloud-Org-ID: ORGANIZATION_ID
```

<!-- source: en/api/_includes/headings-no-body.md -->
{% cut "Headers" %}

* `Host`: address of the node that provides the API.

* <!-- source: en/api/_includes/authorization.md -->
  `Authorization`: Authorization token about these formats:

    - `OAuth OAUTH_TOKEN`: For authorization using the OAuth 2.0 protocol. [Learn more](https://yandex.ru/support/tracker/en/api/access.md#about_OAuth)

    - `Bearer IAM_TOKEN`: For authorization using an IAM token, if a Yandex Identity Hub organization is linked to Tracker. [Learn more](https://yandex.ru/support/tracker/en/api/access.md#iam-token)
  <!-- endsource: en/api/_includes/authorization.md -->


* <!-- source: en/api/_includes/org-id.md -->
  # ID types {#types}


  `X-Org-ID` or `X-Cloud-Org-ID`: Organization ID.

  - Use the `X-Org-ID` header if a Tracker organization is linked to Yandex 360 for Business.

  - Use the `X-Cloud-Org-ID` header if a Tracker organization is linked to Yandex Identity Hub.


  # Finding the ID {#find-id}


  To get the organization ID, go to **Administration** → [**Organizations**](https://tracker.yandex.com/admin/orgs) and copy the value from the **ID** field.
  <!-- endsource: en/api/_includes/org-id.md -->


{% endcut %}
<!-- endsource: en/api/_includes/headings-no-body.md -->

{% cut "Resource" %}

#|
|| **Parameter** | **Description** | **Data type** ||
|| `queue_ID` | Queue ID or key. The queue key is case-sensitive. | String or number ||
|| `trigger_ID` | Trigger ID. | Number ||
|#

{% endcut %}

## Response format {#answer}

{% list tabs %}

- Request executed successfully

  <!-- source: en/api/_includes/answer-200.md -->
  If the request is successful, the API returns a response with code `200 OK`.
  <!-- endsource: en/api/_includes/answer-200.md -->

  The response body contains information about the trigger in JSON format.

    ```json translate=no
    {
    "id": 16,
    "self": "https://api.tracker.yandex.net/v3/queues/DESIGN/triggers/16",
    "queue": {
        "self": "https://api.tracker.yandex.net/v3/queues/DESIGN",
        "id": "26",
        "key": "DESIGN",
        "display": "Design"
    },
    "name": "trigger_name",
    "order": "0.0002",
    "actions": [
        {
            "type": "Transition",
            "id": 1,
            "status": {
                "self": "https://api.tracker.yandex.net/v3/statuses/2",
                "id": "2",
                "key": "needInfo",
                "display": "Need Info"
            }
        }
    ],
    "conditions": [
        {
            "type": "Or",
            "conditions": [
                {
                    "type": "Event.comment-create"
                }
            ]
        }
    ],
    "version": 1,
    "active": true
    }
    ```

   {% cut "Response parameters" %}

   #|
   || **Parameter** | **Description** | **Data type** ||
   || id | Trigger ID. | Number ||
   || self | Link to the trigger. | String ||
   || [queue](#queue) | Queue where the trigger was created. | Can be set as an object, a string if the [queue key](*queuekey) is provided, or a number if the queue ID is provided. ||
   || name | Trigger name. | String ||
   || order | Trigger weight. This parameter affects the order of triggers in the interface. | String ||
   || [actions](#actions) | Array of trigger actions. | Array of objects ||
   || [conditions](#conditions) | Array of trigger conditions. | Array of objects ||
   || version | Trigger version. Each trigger update increases the version number. | Number ||
   || active | Trigger status. Acceptable values:<ul><li>`true`: Active.</li><li>`false`: Inactive.</li></ul> | Boolean ||
   |#

   **Fields of the** `queue` **object** {#queue}

   <!-- source: en/api/_includes/queue.md -->
   | Parameter | Description | Data type |
   ----- | ----- | -----
   | self | Address of the API resource with information about the queue. | String |
   | id | Queue ID. | String |
   | key | Queue key. | String |
   | display | Queue name displayed. | String |
   <!-- endsource: en/api/_includes/queue.md -->

   **Fields of objects in the** `actions` **array** {#actions}

   The set of parameters depends on the action type. For examples of action parameters, see [Trigger action objects](https://yandex.ru/support/tracker/en/api/queues/change-trigger-actions.md).

   #|
   || **Parameter** | **Description** | **Data type** ||
   || type | Action type. Acceptable values:<ul><li>`Transition`: Change the issue status.</li><li>`Update`: Change field values.</li><li>`Move`: Move the issue.</li><li>`CreateComment`: Add a comment.</li><li>`CreateChecklist`: Create a checklist.</li><li>`Webhook`: Send an HTTP request.</li><li>`CalculateFormula`: Calculate a value.</li><li>`CreateIssue`: Create an issue.</li></ul> | String ||
   || id | Action ID. | Number ||
   || [status](#status) | Status to transition the issue to. Returned for the `Transition` action. | Object ||
   || text | Comment text for the `CreateComment` action, if specified. | String ||
   |#

   **Fields of objects in the** `conditions` **array** {#conditions}

   Each object in the `conditions` array defines a check determined by its `type` field. The check can concern an event, such as issue creation, or issue and comment data. Objects with type `Or` or `And` combine checks into logical groups. Nested conditions are returned in the group’s own `conditions` array.

   #|
   || **Parameter** | **Description** | **Data type** ||
   || [type](#condition-types) | Condition type. See [acceptable values of the `type` field](#condition-types) | String ||
   || [conditions](#conditions) | Nested conditions. Returned for `Or` and `And` logical groups. Each element has the same structure as an object in the top-level `conditions` array | Array of objects ||
   |#

   The set of other fields depends on the `type` value. For examples of condition parameters, see [Trigger condition objects](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md).

   **Acceptable values of the condition object’s** `type` **field** {#condition-types}

   #|
   || **Condition group** | **`type` values** ||
   || Logical groups | <ul><li>`Or`: Logical OR. At least one nested condition is met.</li><li>`And`: Logical AND. All nested conditions are met.</li></ul> ||
   || Events | <ul><li>`Event.create`: An issue was created.</li><li>`Event.update`: An issue was updated.</li><li>`Event.comment-create`: A comment was created.</li><li>`CalculationFormulaWatch`: Formula fields were updated.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#events) ||
   || Checklist | <ul><li>`ChecklistDone`: All checklist items are complete.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#checklist) ||
   || Comment text | <ul><li>`CommentAnyMatchCondition`: Contains any of the fragments.</li><li>`CommentStringMatchCondition`: Contains the fragment.</li><li>`CommentNoneMatchCondition`: Does not contain any of the fragments.</li><li>`CommentStringNotMatchCondition`: Does not contain the fragment.</li><li>`CommentFullyMatchCondition`: Fully matches.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#comment-text) ||
   || Comment author | <ul><li>`CommentAuthor`: The comment author matches the specified user.</li><li>`CommentAuthorNot`: The comment author does not match the specified user.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#comment-author) ||
   || Comment type | <ul><li>`CommentMessageInternal`: A comment in Tracker.</li><li>`CommentMessageExternal`: An email.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#comment-type) ||
   || Link action | <ul><li>`CreatedLinkCondition`: A link was created.</li><li>`UpdatedLinkCondition`: A link was updated.</li><li>`RemovedLinkCondition`: A link was deleted.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#relationship) ||
   || Field value | <ul><li>`FieldChangedCondition`: The field value changed.</li><li>`FieldEquals`: Equal to.</li><li>`FieldBecameEqual`: Became equal to.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#task-fields) ||
   || Field state | <ul><li>`FieldIsNotEmpty`: The field is not empty.</li><li>`FieldIsEmpty`: The field is empty.</li><li>`FieldBecameEmpty`: The field value was deleted.</li><li>`FieldBecameNotEmpty`: The field value was set.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#task-fields) ||
   || Date | <ul><li>`DateEqualCondition`: The date matches.</li><li>`DateGreaterCondition`: Later than.</li><li>`DateGreaterOrEqualCondition`: Later than or equal to.</li><li>`DateLessCondition`: Earlier than.</li><li>`DateLessOrEqualCondition`: Earlier than or equal to.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#task-fields) ||
   || User groups | <ul><li>`UserInGroups`: The user belongs to one of the groups.</li><li>`UserNotInGroups`: The user does not belong to any of the groups.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#task-fields) ||
   || Number of items | <ul><li>`Container.SizeEquals`: The number of items is equal to.</li><li>`Container.SizeNotEquals`: The number of items is not equal to.</li><li>`Container.SizeGreater`: The number of items is greater than.</li><li>`Container.SizeGreaterOrEquals`: The number of items is greater than or equal to.</li><li>`Container.SizeLess`: The number of items is less than.</li><li>`Container.SizeLessOrEquals`: The number of items is less than or equal to.</li><li>`ContainerContainsAll`: Contains all items.</li><li>`ContainerContainsAny`: Contains any of the items.</li><li>`ContainerContainsNone`: Does not contain any items.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#task-fields) ||
   || Numeric values | <ul><li>`GreaterCondition`: Greater than.</li><li>`GreaterOrEqualCondition`: Greater than or equal to.</li><li>`LessCondition`: Less than.</li><li>`LessOrEqualCondition`: Less than or equal to.</li><li>`BecameGreaterCondition`: Became greater than.</li><li>`BecameGreaterOrEqualCondition`: Became greater than or equal to.</li><li>`BecameLessCondition`: Became less than.</li><li>`BecameLessOrEqualCondition`: Became less than or equal to.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#task-fields) ||
   || String values | <ul><li>`FieldEqualsString`: Equal to the string.</li><li>`ContainsAnyOfStrings`: Contains any of the fragments.</li><li>`ContainsNoneOfStrings`: Does not contain any of the fragments.</li></ul><br/>[Examples of condition definitions](https://yandex.ru/support/tracker/en/api/queues/change-trigger-conditions.md#task-fields) ||


   |#


   **Fields of the** `status` **object** {#status}

   <!-- source: en/api/_includes/status.md -->
   | Parameter | Description | Data type |
   ----- | ----- | -----
   | self | Address of the API resource with information about the status. | String |
   | id | Status ID. | String |
   | key | Status key. | String |
   | display | Status name displayed. | String |
   <!-- endsource: en/api/_includes/status.md -->

   {% endcut %}

- Request failed

    If the request fails, the response contains error details:

    <!-- source: en/api/_includes/answer-error-400.md -->
    400
    :   One or more request parameters have an invalid value.
    <!-- endsource: en/api/_includes/answer-error-400.md -->

    <!-- source: en/api/_includes/answer-error-403.md -->
    403
    :   You are not authorized to perform this action. You can check what rights you have in the Tracker interface. The same rights are required to perform an action via the API and interface.
    <!-- endsource: en/api/_includes/answer-error-403.md -->

    <!-- source: en/api/_includes/answer-error-404.md -->
    404
    :   The requested object was not found. You may have specified an invalid object ID or key.
    <!-- endsource: en/api/_includes/answer-error-404.md -->

    <!-- source: en/api/_includes/answer-error-422.md -->
    422
    :   JSON validation error, the request is rejected.
    <!-- endsource: en/api/_includes/answer-error-422.md -->

    <!-- source: en/api/_includes/answer-error-500.md -->
    500
    :   Internal service error. Try again later.
    <!-- endsource: en/api/_includes/answer-error-500.md -->

    <!-- source: en/api/_includes/answer-error-503.md -->
    503
    :   The API service is temporarily unavailable.
    <!-- endsource: en/api/_includes/answer-error-503.md -->

{% endlist %}

[*queuekey]: A queue key is a unique code for a queue consisting of Latin characters, for example `TEST`. The key is contained in the link to the queue and its issues, and you need to specify it in API requests and auto action settings. You can't change the key after creating the queue.