Skip to main content

Node - Get Single Personnel (Department/Organization Role)

Purpose: Retrieves a single member, department, or organization role object from a record field or the organization directory. The returned object is equivalent to a single record and exposes its properties for use in subsequent workflow nodes.

In a worksheet, Member, Department, and Organization Role are field types. Meanwhile, members, departments, and organization roles in your organization are independent data objects that contain their own attributes, similar to system tables.

  • A member object includes properties such as:

    Name, mobile number, email, department, primary department, job title, employee ID, work location, organization roles, user ID, direct manager, direct reports, all reports, created time, and more.

  • A department object includes properties such as:

    Department name, department manager, parent department, all parent departments, direct child departments, all child departments, department members, members in the department and all sub-departments, department ID, created time, and more.

    • The All Parent Departments and All Child Departments properties return department object arrays. These can be written directly to multi-select Department fields. When written to a text field, they are returned as an array of department names.

  • An organization role object includes properties such as:

    Role name, description, role members (member array), organization role ID, current role, created time, and more.

Only Organization Super Admins and Organization Account Admins can select Search from All Organization Members, Departments, and Organization Roles.

Example​

When creating a department task, automatically populate the Department Members field with all members from the task owner's department.

The Tasks worksheet is designed as follows:

Workflow idea: Retrieve the task owner's department from the member object, then use the department object to retrieve all members in that department.

Workflow Design​

Method 1​

  1. Create a workflow that is triggered when a new task record is created.

  2. Use the Get Single Personnel node to retrieve the task owner's member object.

    Select Get from Member Field to retrieve the member object stored in the Task Owner field of the newly created task. This returns the department the owner belongs to.

  3. Add another Get Single Department node to retrieve the department object.

    Select Search across Organization Departments, and set the condition so that the department name equals the Department property returned by the previous member object.

  4. After retrieving the department object, access its member list and update the Department Members field in the task record.

  5. The department member list also includes the task owner. If you do not want the task owner to appear in the Department Members field, remove them afterward.

Method 2​

This method follows the same logic as Method 1, but combines Steps 2 and 3.

Instead of retrieving the member object first, retrieve the department object directly from Organization Departments using the condition that Department Members contains the Task Owner. The remaining configuration is identical.

If this solution came to mind immediately, congratulations—you've already mastered the basic usage of this node.

Retrieve Reporting Relationships​

By default, this node does not retrieve reporting relationships when fetching member data.

If you need to use information such as the member's manager or direct reports, enable this option. Otherwise, leave it disabled to improve query performance.

Tips​

  1. This node always returns a single object, so its output cannot be passed directly to a subprocess. In this example, the retrieved department contains multiple members, which is equivalent to the value of a multi-select Member field. It can be written directly to a Member field, but it cannot be passed to a subprocess.

  2. If you need to create multiple records—one for each department member—use the Get Multiple Personnel/Departments/Organization Roles node, then combine it with a subprocess or Add Record node to create records in batches.

  3. Like the Get Data node, this node supports branch conditions based on whether a matching result is found.

  4. If the retrieved member is an external collaborator, organization-specific properties (such as employee ID, manager, direct reports, and similar fields) are returned as empty values.

  5. This node can retrieve member information regardless of whether the user's profile is set to Visible Only to Me or hidden from Contacts.

Was this document helpful?