n8n-nodes-yandex-tracker

Community node for n8n that integrates with the Yandex Tracker API v3.

Manage issues, comments, attachments, links, worklogs, queues, boards and users directly from your workflows.

Installation

Community node (recommended)

In n8n go to Settings → Community Nodes → Install and enter:

n8n-nodes-yandex-tracker

Manual installation

# in your n8n custom extensions folder (~/.n8n/custom or N8N_CUSTOM_EXTENSIONS)
npm install n8n-nodes-yandex-tracker

Local development

git clone https://github.com/fuckseer/n8n-nodes-yandex-tracker.git
cd n8n-nodes-yandex-tracker
npm install --ignore-scripts
npm run build

Credentials

The node authenticates with a Yandex OAuth token plus an organization ID.

1. Register an application at oauth.yandex.ru and request the scopes:
   • tracker:read
   • tracker:write
2. Obtain an OAuth token (see Access to the API).
3. Find your organization ID in Tracker Administration → Organizations.
4. In n8n create new Yandex Tracker API credentials:
   • OAuth Token — your token
   • Organization ID — the org identifier
   • Organization Type — Yandex 360 (sends X-Org-ID) or Yandex Cloud (sends X-Cloud-Org-ID)

The credentials include a built-in test that calls GET /v3/myself.

Supported operations

Issue

• Create — create an issue (queue + summary + optional fields, custom JSON)
• Get — get an issue with optional fields and expand
• Update — update issue fields
• Delete — delete an issue
• Search — search by structured filter or Tracker query language
• Get Transitions — list available status transitions
• Execute Transition — move an issue to another status (optional comment/resolution)

Comment

• Create / Get Many / Update / Delete

Attachment

• Upload — attach a binary file to an issue
• Get Many — list attachments
• Download — download an attachment into a binary field
• Delete

Link

• Create — link two issues (relates, depends on, is subtask for, ...)
• Get Many / Delete

Queue

• Get / Get Many — with optional expand (projects, components, versions, ...)

Component

• Get Many — all components or filtered by queue

Board

• Get / Get Many

Worklog

• Create / Get Many / Update / Delete — duration in ISO 8601 (e.g. PT1H30M)

User

• Get Myself — current user
• Get — user by ID or login
• Get Many — all users

Trigger

Yandex Tracker Trigger is a polling trigger — it periodically queries the API and
starts the workflow when matching issues appear. Yandex Tracker does not expose webhook
registration via the API, so polling is used instead.

Events:

• Issue Created — fires for newly created issues
• Issue Updated — fires for issues updated since the last poll

Options:

• Queue Key — watch a single queue (empty = all queues)
• Issue Keys — watch only specific issues (comma-separated keys, e.g. TREK-1, TREK-2)
• Additional Query — extra Tracker query language conditions, combined with AND

Queue Key and Issue Keys can be combined — when both are set, an issue matching
either the queue or the listed keys is watched.

Notes:

• The first automatic poll records a baseline and does not emit historical issues.
• A manual (test) execution looks back 7 days so you can see sample data.
• Query dates use the organization's timezone; large clock skew between the n8n host and
  the org may cause edge-case misses.

Pagination

List and search operations support Return All (walks all pages via page/perPage)
or a Limit. Tracker returns pagination metadata in the X-Total-Pages / X-Total-Count
response headers.

Notes

• Dates/times are handled in UTC by the Tracker API.
• Object references (type, priority, status, ...) accept a key, ID or display name.
• v1 covers the core API. Out of scope: projects/portfolios/goals, dashboards, SLA,
  import, webhook trigger and IAM Bearer auth.

Resources

• Yandex Tracker API documentation
• n8n community nodes documentation

License

MIT