Hudu icon

Hudu

Interact with Hudu REST API

Actions144

Activity Log → Get Many

AI-generated

Overview

This node operation retrieves multiple activity log entries from the Hudu system. It supports filtering by various criteria such as action messages, resource type and ID, user email, and date range. Users can choose to return all results or limit the number of results, and optionally wrap the results in a single item containing an array and count. This is useful for auditing, monitoring user actions, or tracking changes within the Hudu environment.

Use Case Examples

  1. Retrieve all activity logs related to a specific user email to monitor their actions.
  2. Fetch the latest 25 activity logs filtered by specific action messages like 'created' or 'deleted'.
  3. Get activity logs for a particular resource type and ID to audit changes on that resource.

Properties

Name Meaning
Return All ⚠️ Whether to return all results or only up to a given limit.
Limit Maximum number of results to return when not returning all.
Wrap Results in Single Item Whether to return all results as a single item with an 'items' array and 'count' field to prevent downstream nodes from executing once per result item, which can help avoid rate limiting issues.
Filters Collection of filters combined using AND logic to refine the activity logs returned. Includes filters like action message, fields to return, resource ID and type, start date, user email, and user ID.

Output

JSON

  • items - Array of activity log entries returned when results are wrapped in a single item.
  • count - Count of activity log entries returned when results are wrapped.
  • id - Unique identifier of the activity log entry.
  • action - Action performed in the activity log entry.
  • agent_string - Agent string from which the action was performed.
  • app_type - Type of application involved in the action.
  • company_name - Name of the company related to the activity log entry.
  • created_at - Timestamp when the activity log entry was created.
  • details - Additional details about the activity log entry.
  • device - Device used for the action.
  • formatted_datetime - Formatted date and time of the activity log entry.
  • ip_address - IP address from which the action was performed.
  • original_record_name - Original name of the record involved.
  • os - Operating system of the device used.
  • record_company_url - URL to the company record related to the activity log.
  • record_id - ID of the record involved in the activity log.
  • record_name - Name of the record involved.
  • record_type - Type of the record involved.
  • record_url - URL to the record involved.
  • record_user_url - URL to the user record related to the activity.
  • token - Token associated with the activity log entry.
  • url - URL related to the activity log entry.
  • user_email - Email of the user who performed the action.
  • user_id - ID of the user who performed the action.
  • user_initials - Initials of the user.
  • user_name - Name of the user.
  • user_short_name - Short name of the user.

Dependencies

  • Hudu REST API
  • API key credential for authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has sufficient permissions to access activity logs.
  • If filtering by user ID or resource ID, verify that the IDs are correct and exist in the system.
  • When using the 'Return All' option, be cautious of large data sets that may impact performance or cause rate limiting.
  • If no results are returned, check the filter criteria for accuracy and adjust date ranges or action messages as needed.

Links

Discussion