> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-table/automation/data-nodes/data-node.md).

# 數據節點

數據節點用於在工作流程中自動操作業務數據，包括新增、更新、刪除記錄，獲取數據供後續節點使用，以及流程參數的傳遞。

### 本類型節點一覽

| 節點        | 說明                       |
| --------- | ------------------------ |
| 新增數據      | 自動向指定工作表添加一條新記錄          |
| 更新數據      | 更新本表或關聯他表記錄中的字段值         |
| 刪除數據      | 自動刪除工作表中的某條記錄            |
| 獲取單條數據    | 按條件獲取一條記錄供後續節點使用         |
| 獲取多條數據    | 按條件批量獲取多條記錄              |
| 更新流程參數    | 為流程參數賦值，實現流程內／跨流程數據傳遞    |
| 獲取記錄打印文件  | 依 Word 模板自動生成打印文件並寫入附件字段 |
| 獲取人員／部門數據 | 從成員／部門字段中取出完整人員屬性        |


---

# 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.coreway.com/coreway-table/automation/data-nodes/data-node.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.
