> 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/get-member-department.md).

# 獲取單條人員／部門數據

### 1. 節點功能

在工作表中，成員或部門作為本表的一個屬性字段；但人員和部門也是一個獨立的數據對象，它們本身也包含很多屬性信息，這些數據都來自組織管理後台。

而人員／部門節點，就是可以從成員字段／團隊管理中獲取一個人員信息，也可以從部門字段或團隊管理中獲取一個部門信息。

* 一個人員的屬性信息有：姓名、手機號、郵箱、部門、職位、工號、工作地點等。
* 一個部門的屬性信息有：部門名稱、部門負責人。

![image.png](https://273888574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9WI4IMScYYFwRQSZY8Zr%2Fuploads%2FpKbv05is5DHW0WiWr51A%2F17685076923289.png?alt=media)

### 2. 場景舉例

提交一個部門任務後，自動將本部門人員加入到任務的【參與人】字段中。

**任務設計如下：**

![image.png](https://273888574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9WI4IMScYYFwRQSZY8Zr%2Fuploads%2FC2csrix3fWcRydfjOfRH%2F4240d674179a3c274eb80e8ee638ac1d.png?alt=media)

**工作流程配置思路：**

1. 要獲取到創建人所在部門的成員，首先需要獲取到創建人所在的部門。
2. 獲取創建人所在的部門有兩種方法：透過部門字段（本表沒有），或透過「獲取部門信息」節點。

### 3. 配置步驟

1. 新增任務表時觸發流程。
2. 透過【獲取單條成員／部門信息】來獲取創建人的信息，即部門。
3. 創建信息獲取後，其所在的部門就知曉了；繼續透過【獲取單條成員／部門信息】獲取部門的信息。

![image.png](https://273888574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9WI4IMScYYFwRQSZY8Zr%2Fuploads%2FjabvwKURNfbDA3tTmE4A%2Fe2a389f45dc2a2bbeb00e903fc7a5872.png?alt=media)

4. 部門信息獲取後，部門下的成員就知曉了，然後更新到參與人字段中。

![image.png](https://273888574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9WI4IMScYYFwRQSZY8Zr%2Fuploads%2FOhtkRt74rjzD9EO6jaMd%2Fdf326495042c6d3d93d5837e0663084e.png?alt=media)


---

# 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/get-member-department.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.
