> 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/post-data.md).
# Post Data
Post a value to an asset attribute from a rule chain.
Use **Post Data** to send a value to an asset attribute.
This node writes configured data when triggered.
### What it does
The node posts a value to a selected asset attribute.
Use it to update asset data from a rule chain.
### Inputs
* **Trigger** — Starts the post action.
### Configurable settings
* **Asset** — Select the target asset.
* **Attribute** — Select the target attribute.
* **Value** — Enter the value to post.
### Typical use
Use **Post Data** after logic, schedules, or external events.
### Related documentation
* [Asset Data](/collection/mandatory-base/assets/asset-data.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/post-data.md?ask=&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.
.png?alt=media&token=42861965-e6f8-4a87-a63a-8e6495b9581d)
.png?alt=media&token=5b8a7492-b7bd-49d5-a15c-3eef38819ae5)