> 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/script.md).

# Script

<div align="left"><figure><img src="/files/y6n1onDc63oXnodmilro" alt="" width="367"><figcaption></figcaption></figure></div>

Use **Script** to run a script from **Script Engine** inside a rule chain.

This node lets you extend rule logic with script-based behavior.

<div align="left"><figure><img src="/files/uGsLT0UNtGQFpaZAkffh" alt="" width="306"><figcaption></figcaption></figure></div>

### What it does

The node executes a selected script.

Execution is controlled by a boolean input.

### Inputs

* **Trigger input pin** — Starts the script execution.

### Configurable settings

<div align="left"><figure><img src="/files/fWM6723renGFMoZq3iNK" alt="" width="375"><figcaption></figcaption></figure></div>

* **Script** — Select the script to execute.

{% hint style="warning" %}
Set the script trigger type to **Event triggered**.
{% endhint %}

### Typical use

Use **Script** when built-in blocks are not enough.

See [Script Engine](/collection/platform/platform-core/script-engine.md) for script setup.

### Related documentation

* [Script Engine](/collection/platform/platform-core/script-engine.md)
* [Writing Python Scripts](/collection/platform/platform-core/script-engine/writing-python-scripts.md)
* [Writing PL/PgSQL Scripts](/collection/platform/platform-core/script-engine/writing-pl-pgsql-scripts.md)

### All node pages

* [Get Data](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/get-data.md)
* [Get Aggregated Data](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/get-aggregated-data.md)
* [Post Data](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/post-data.md)
* [SQL Query](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/sql-query.md)
* [Alarm](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/create-alarm.md)
* [Ticket](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/ticket.md)
* [Send Email](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/send-e-mail.md)
* [Send Report](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/send-report.md)
* [Rule](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/rule.md)
* [LLM Call](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/llm-call.md)
* [Send Email LLM](/collection/platform/alarms-rules-and-escalations/rule-chains/nodes/send-e-mail-llm.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.