younifyd
Menu

List Deleted Users

List Deleted Users

GET/api/v2/deleted_users

Use it in a workflow

  1. Add a step and choose the Zendesk connector.
  2. Pick the List Deleted Users action (under Users).
  3. Fill in the fields below, then reference the result from later steps as {{listDeletedUsers.response.data}}.

Request

Query parameters

pageoneOf

Pagination parameter. Supports both traditional offset and cursor-based pagination: - Traditional: `?page=2` (integer page number) - Cursor: `?page[size]=50&page[after]=cursor` (deepObject with size, after, before) These are mutually exclusive - use one format or the other, not both.

per_pageinteger

Number of records to return per page. Note: Default and maximum values vary by endpoint. Check endpoint-specific documentation for limits.

sortstring

Field to sort results by. Prefix with `-` for descending order. When used with cursor pagination, this determines the cursor ordering. Example: `?sort=name` or `?sort=-created_at`

Response

Returns 200 with an object. Read it in later steps with {{listDeletedUsers.response.data.<field>}}.

deleted_usersarray<object>
activebooleanrequired
created_atstringrequired
emailstringrequired
idinteger (int64)required
localestringrequired
locale_idinteger (int64)required
namestringrequired
organization_idinteger (int64)required
phonestringrequired
photoobjectrequired
rolestringrequired
separationobject2 fields

Brand separation information for the deleted user

shared_phone_numberstringrequired
time_zonestringrequired
updated_atstringrequired
urlstringrequired
json
{
  "deleted_users": [
    {
      "active": false,
      "created_at": "string",
      "email": "string",
      "id": 0,
      "locale": "string",
      "locale_id": 0,
      "name": "string",
      "organization_id": 0,
      "phone": "string",
      "photo": {},
      "role": "string",
      "shared_phone_number": "string"
    }
  ]
}

Need more? See the Zendesk guide for connection setup and behaviour shared by every action.