users_touches_list

Tool

users_touches_list

List a person's logged interactions, newest first — by when they were LOGGED, so a backdated touch still appears on the first page.

List a person's logged interactions, newest first — by when they were LOGGED, so a backdated touch still appears on the first page. Filter by channel. Paginate with the opaque `nextCursor`.

Behavior

HTTP: GET /users/users/:userId/touches

Arguments

Name	Type	Required	Description
limit	string	—	Page size, 1-100. Default 50.
cursor	string	—	Opaque cursor from a previous response's `nextCursor`. Omit for the first page.
userId	string	•	The end user whose touches to list.
channel	string	—	Only touches on this channel. Omit for all of them.

Response

Field	Type	Always	Description
items	array	•	The page of touches, newest first.
nextCursor	string	•	Pass as `cursor` for the next page. Null when this was the last one.

Try it

List a person's logged interactions, newest first — by when they were LOGGED, so a backdated touch still appears on the first page.

When to use

List a person's logged interactions, newest first — by when they were LOGGED, so a backdated touch still appears on the first page. Filter by channel. Paginate with the opaque `nextCursor`.

Example

Ask your agent something like this:

List a person's logged interactions, newest first — by when they were LOGGED, so a backdated touch still appears on the first page.

The agent will invoke users_touches_list with these arguments:

{
  "userId": "<userId>"
}