Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node interacts with the Hudu REST API to retrieve activity log entries. Specifically, the "Get Many" operation under the "Activity Log" resource fetches multiple activity log records based on user-defined filters and limits.
Use cases include:
- Auditing user actions within Hudu by retrieving logs of specific activities.
- Monitoring changes or events related to various resources such as articles, assets, companies, users, etc.
- Filtering logs by date range, user, action type, or resource to analyze system usage or troubleshoot issues.
For example, you could use this node to get all "Created Integration" actions performed in the last week or to list all activity logs related to a particular company or user.
Properties
| Name | Meaning |
|---|---|
| Return All ⚠️ | Whether to return all matching results or limit the number of returned records. Returning all may result in very large data sets. |
| Limit | Maximum number of results to return when "Return All" is false. Minimum value is 1. |
| Filters | Collection of optional filters combined with AND logic: |
| - Action Message | Filter by exact action message. Options include many predefined actions such as "Archived", "Created API key", "Deleted Company", "Signed In", "Updated Profile", "Viewed PDF", etc. |
| - Resource ID | Numeric filter for resource ID. Must be used together with Resource Type. |
| - Resource Type | Filter by resource type. Options include "Article", "Asset", "Company", "User", "Website", and others. Must be used together with Resource ID. |
| - Start Date | Filter logs starting from this ISO 8601 formatted date/time. |
| - User Email | Filter by exact user email match. |
| - User Name or ID | Select a user by name or ID from a loaded list or specify an ID via expression. |
Output
The output is a JSON array where each item represents an activity log entry matching the query parameters. Each entry contains fields describing the logged action, such as:
- The action message (e.g., "created integration", "signed in").
- Associated resource details (type and ID).
- User information who performed the action.
- Timestamp of the activity.
- Additional metadata relevant to the log entry.
No binary data output is produced by this node.
Dependencies
- Requires connection to the Hudu REST API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for the Hudu API must be set in the credentials.
- Optionally uses dynamic loading of users for filtering by user ID/name.
Troubleshooting
- Empty results: Check that filters are correctly set; ensure the date range and other filters match existing logs.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Large data volume: Using "Return All" can lead to very large responses; consider using limits or more specific filters to avoid performance issues.
- Invalid resource or operation: The node throws an error if an unknown resource or operation is specified.
- Filter dependencies: When filtering by Resource ID, Resource Type must also be specified; omitting it may cause no results or errors.
Links and References
- Hudu API Documentation (for detailed info on activity log endpoints)
- n8n Documentation - Expressions (for using expressions in property values)