Activity logs record actions in your monday.com account. The GraphQL API exposes them in two ways:

• Board logs are board-first: you must pass a board ID. You can narrow rows with user_ids on the board field for people on that board.
• User logs are user-first: you pass user IDs. You can narrow with board_ids on the user field.
• Row shape, pagination, and limits differ between the two paths — validate for your use case before assuming parity.

Queries

Get board activity logs

• Required scope: boards:read
• Nested only under a boards query — see Board activity logs for full arguments, field definitions, and the ActivityLog shape for this path.
• Pagination: page and limit (default 25 rows); up to 10,000 log rows per query.

query {
  boards(ids: [1234567890]) {
    activity_logs(
      from: "2026-03-01T00:00:00Z"
      to: "2026-04-09T23:59:59Z"
      limit: 25
      page: 1
    ) {
      id
      event
      entity
      data
      user_id
      created_at
    }
  }
}

Get user activity logs

• Required scope: users:read
• Nested under a users query as activity_logs on type User. The response is UserActivityLogsPage: logs plus a cursor for the next page.
• API version: use API-Version: 2026-04 or later
• from / to: in the schema these are String — pass ISO 8601 datetimes (for example 2026-03-01T00:00:00Z). Invalid values may surface as field errors from the activity-log service.

First page

query UserActivityFirstPage(
  $userIds: [ID!]!
  $from: String!
  $to: String!
  $limit: Int
) {
  users(ids: $userIds) {
    id
    activity_logs(from: $from, to: $to, limit: $limit) {
      cursor
      logs {
        id
        account_id
        user_id
        event
        entity
        data
        created_at
      }
    }
  }
}

Variables (example):

{
  "userIds": ["1234567890"],
  "from": "2026-03-01T00:00:00Z",
  "to": "2026-04-09T23:59:59Z",
  "limit": 50
}

Pagination (cursor)

User activity logs use cursor pagination (not page numbers).

1. Call activity_logs without cursor (or with cursor: null) for the first page.
2. If cursor in the response is non-null, pass that string as cursor on the next request for the same user with the same from / to (and other filters).
3. Stop when cursor is null.

query UserActivityNextPage(
  $userIds: [ID!]!
  $from: String!
  $to: String!
  $cursor: String!
  $limit: Int
) {
  users(ids: $userIds) {
    id
    activity_logs(from: $from, to: $to, limit: $limit, cursor: $cursor) {
      cursor
      logs {
        id
        event
        created_at
      }
    }
  }
}

• Default page size: 50 rows.
• Maximum page size: 200 rows per activity_logs call.

Arguments

UserActivityLogsPage fields

ActivityLog fields (user activity path)

User activity logs — limitations and errors

Values below reflect the current design.

Time range

• Only activity within the last 90 days is queryable.
• If from is older than 90 days, the field may error for that user. Other users in the same request may still return data.

Pagination edge cases

• Rows are ordered by timestamp. There is no guaranteed order among rows that share the exact same timestamp.
• If a page break falls inside equal timestamps, you may see duplicates or gaps across pages — deduplicate by id and avoid strict totals without reconciliation.

Errors (GraphQL)

On failure, activity_logs may be null for that user while other fields still return. Check the errors array; paths look like users → <index> → activity_logs.

Choosing board vs user logs