List Activity Logs
hudu_list_activity_logsRetrieve Hudu audit trail entries to see who changed a record, what they did, and when. Use filters for resource, user, or start date to narrow the log.
Instructions
List activity logs in Hudu. The activity log is Hudu's audit trail: one entry per action, recording who did it, what they did it to, and when.
This is the tool for "who changed this, and when". Each entry carries user_id and user_email (the actor), resource_type and resource_id (what they touched), and an action_message describing the action.
Combine the filters to answer a real question rather than paging the whole log:
History of one record:
resource_typeplusresource_idtogether. Sending one without the other does nothing.What one person did:
user_id, oruser_emailif you only have the address.A time window:
start_date. There is no end-date filter, so a log is bounded at the start only; to look at "last week" specifically, setstart_dateto the beginning of that week and read forward.One kind of action:
action_message.
Entries are ordered by Hudu, not by this server, and no total count is returned — so to find the most recent change to a record, request a page and read it rather than assuming the first entry is newest.
Reading the log never alters it. Purging it is a separate tool, hudu_purge_activity_logs, and is destructive.
Returns an object with items plus pagination facts. Note that the Hudu API returns no total count for any collection, so page_was_full is the only honest signal that more records exist — read pagination_note before concluding a list is complete.
Operation class: Read.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number. Hudu has no cursor or offset — only pages. | |
| fields | No | Return only these top-level fields on each record. Use it to keep large lists small — e.g. ["id","name","company_id"]. Unknown field names are ignored. | |
| user_id | No | Numeric id of the person whose actions you want. Resolve it with hudu_list_users. | |
| page_size | No | Records per page (1-100, default 25). Hudu publishes no maximum, so this client clamps at 100; larger values are rejected here rather than silently altered by the server. | |
| start_date | No | Return only entries from this moment onward. Hudu documents this as ISO-8601, e.g. "2026-03-01T00:00:00Z". Send an explicit UTC offset rather than a bare date — a date alone leaves the time of day to the server to decide. | |
| user_email | No | Email address of the person whose actions you want, when you have no user id. | |
| resource_id | No | Numeric id of the record whose history you want. Must be sent together with `resource_type`; on its own it is ignored. | |
| resource_type | No | Hudu record type, written exactly as Hudu spells it: "Asset", "AssetPassword", "Company", "Article", "Website" and so on. Must be sent together with the matching id — either one alone is ignored. | |
| action_message | No | Match on the text of the recorded action, e.g. the word used for a create, update or view. Hudu publishes no list of legal values, so treat this as a text filter and confirm against an unfiltered sample before relying on a particular wording. | |
| response_format | No | Output shape. 'json' (default) is compact and machine-readable; 'markdown' is easier for a person to read but larger. | json |