> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/ticket.md).

# Ticket

Create a ticket from a rule chain.

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FnVC0pcEH3wBLpDSwml8U%2FTicket%20(1).png?alt=media&amp;token=23c505c7-fa69-4efd-ae68-780fdf14c1f8" alt="" width="375"><figcaption></figcaption></figure></div>

Use **Ticket** to create a service ticket from a rule chain.

This node helps turn detected issues into tracked work.

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fh4FVwdZUrnyp2RQELcDK%2Fimage%2058.png?alt=media&amp;token=eb3ed691-c1c1-4736-8cf6-2b1802c5fd95" alt="" width="307"><figcaption></figcaption></figure></div>

### What it does

The node creates a ticket that is linked to an asset.

Use it for faults, maintenance tasks, or follow-up actions.

### Inputs

* **Trigger input pin** — Starts the ticket action.

### Configurable settings

<div align="left"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FfzqGtuCBFOsLsi2eGsSU%2FTicket%20(2).png?alt=media&amp;token=98308db4-db38-4663-ade7-29bfa029a71d" alt="" width="375"><figcaption></figcaption></figure></div>

* **Asset** — Select the related asset.
* **Priority** — Set the urgency.
* **Assigned person** — Select the responsible recipient.
* **Reason** — Choose a predefined ticket reason.
* **Title** — Enter a short ticket title.
* **Description** — Add the detailed issue or task description.

### Typical use

Use **Ticket** after logic that detects a service case.

### Related documentation

* [Service Desk](/collection/platform/service-desk.md)
* [Create Tickets](/collection/platform/service-desk/create-tickets.md)
* [Nodes](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes.md)

For the full editor flow, see [Configure Rule Chain](/collection/platform/alarms-rules-and-escalations/rule-chains/configure-rule-chain.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/ticket.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.