user/getMany

When to Use

• Workspace member directory: Build a team directory by listing all person-type users, extracting their names and emails, and syncing the list to an HR system or a contact database.
• User picker population: At workflow startup, load all workspace members to populate a dropdown in an admin tool or BizFirst Form so users can select assignees by name instead of by UUID.
• HR system sync: Periodically compare Notion workspace members against an HR system's active employee list to identify discrepancies — for example, former employees still having workspace access.
• Integration access audit: List all users including bots to identify which integrations have workspace access. Compare against an approved integration list for security compliance.
• Name-to-ID resolution: When an external system provides a user's name rather than a Notion UUID, call user/getMany and find the match by name to resolve the user ID for subsequent page/update property assignments.

Configuration

Authentication

Operation Fields

Sample Configuration

{
  "resource": "user",
  "operation": "getMany",
  "AuthenticationMethod": "ApiToken",
  "ApiToken": "{{ $credentials.notionApiToken }}",
  "ReturnAll": true
}

Validation Errors

Output

Success Port

Error Port

On failure the error port receives errorCode, message, and httpStatus.

Sample Output

{
  "results": [
    {
      "id": "a1b2c3d4-1111-2222-3333-e5f678901234",
      "name": "Sarah Chen",
      "email": "sarah.chen@acmecorp.com",
      "avatarUrl": "https://s3.us-west-2.amazonaws.com/secure.notion-static.com/avatars/sarah.jpg",
      "type": "person"
    },
    {
      "id": "b2c3d4e5-2222-3333-4444-f6a789012345",
      "name": "Marcus Johnson",
      "email": "marcus.johnson@acmecorp.com",
      "avatarUrl": null,
      "type": "person"
    },
    {
      "id": "c3d4e5f6-3333-4444-5555-a7b890123456",
      "name": "BizFirstAI Integration",
      "email": null,
      "avatarUrl": null,
      "type": "bot"
    }
  ],
  "has_more": false,
  "next_cursor": null
}

Expression Reference

Node Policies & GuardRails

Workflow Examples

Example 1 — Build User Lookup Map for Bulk Notifications

Load all users once, build a map, then use it to resolve assignee IDs across many pages without additional API calls.

// Step 1: user/getMany (ReturnAll: true)
// Step 2: Function node — build lookup map
const userMap = {};
$output.getManyUsers.results
  .filter(u => u.type === 'person')
  .forEach(u => { userMap[u.id] = { name: u.name, email: u.email }; });
return { userMap };

// Step 3: database/query (all open tasks)
// Step 4: Loop over tasks
// Step 5 per task: lookup assignee from userMap (no extra API call)
const assignee = $vars.userMap[$json.properties.Assignee.people[0]?.id];
if (assignee?.email) {
  // send email to assignee.email
}

Example 2 — HR System Sync Audit

Compare Notion workspace members to the active employee list from an HR system and flag discrepancies.

// Step 1: user/getMany (ReturnAll: true)
// Step 2: Function node — filter person users only
const notionEmails = results.filter(u => u.type === 'person').map(u => u.email).filter(Boolean);
// Step 3: HttpRequest — fetch active employee emails from HR API
// Step 4: Function node — find users in Notion but not in HR
const departed = notionEmails.filter(e => !hrEmails.includes(e));
// Step 5: Slack/postMessage — alert IT/security team

Example 3 — Name-to-UUID Resolution for Page Update

An external form captures a task assignee by name. Resolve to Notion UUID before updating the page property.

// Step 1: FormTrigger — { assigneeName: "Sarah Chen", pageId: "..." }
// Step 2: user/getMany (ReturnAll: true)
// Step 3: Function node
const user = $output.getManyUsers.results.find(u => u.name === $json.assigneeName);
if (!user) throw new Error("User not found: " + $json.assigneeName);
return { userId: user.id };

// Step 4: page/update
{
  "Page": "{{ $json.pageId }}",
  "Properties": {
    "Assignee": { "people": [{ "object": "user", "id": "{{ $json.userId }}" }] }
  }
}