Core Web App

Now there's no API to see which records (articles) are in the article folder. You need to loop over all articles to then have your list of articles in a specific folder. Like a: "Get all records in folder by folder ID" or so... Would be great if there would be a parameter to "include records in subfolders"!

When using the API to get an article for example it would be great to see which labels it has applied. This way labels could be used to automate flows for articles or assets.

It would be nice if assets integrated from RMM would be moved to archive automatically after being removed from RMM (Syncro)

We have been sharing the process for internal product updates etc. and have a few features we need to make the feature more practical to use. The ability to mark the process as "Aborted" or "Failed" so if anyone views the link they can see that it didn't just randomly stop in the middle, it failed or we aborted. A comment here would also be good. Either a single "Notes" box or notes next to each task the tech following the process can fill in to provide more detail on the task. Some items like an upgrade can take hours and people watching the process have no idea if the live process is stalled or what is going on. -Sub Processes/Manually triggered processes - Perhaps the upgrade failed and we have to revert to a snapshot or some backup method. The ability to trigger a sub process as needed to if the workflow take a non-standard or remediation route.

If a KB or asset is set to expire on a certain date allow for an update to the flag to review. If not updated or reviewed within a few days automatically update to another flag. I.e. expiration date based automations.

I would like an option to integrate with Atlassian Jira Service Management for tickets. The ability to link into a ticket based off user who reported a help desk issue could have the details we sync into Hudu from Azure AD and level.io . For instance, a custom field in Jira could be created to show a hudu link that we already get from our hudu and level.io sync to show the computer asset from hudu with the level.io remote access link. The user details already come from our O365 sync into hudu. 3/4 of this is all there. This would be a huge time saver for my team and I.

Would love to see some sort of method to maintain reoccurring tasks. For instance , Check xyz log monthly and abc log daily. Maybe some sort of radio button that could be checked with a time stamp indicating its been completed on x day for historical data but an obvious method to repeat. For a real world example- We have a excel file we use as an audit log. We have each item to be checked in its own column. Each row of column indicates a date for a total of 365, with tabs for every year. Dates that items are reviewed- the row is updated with the word "REVIEWED"....This just seems like a process that could implemented here in some way, and one that surely other shops deal with in one way or the other.

Please allow Hudu to send email notifications for process steps that need to be completed. These would function similar to website alerts.

It would be great to have a dedicated API endpoint to programmatically trigger a refresh of website assets in Hudu, similar to the "Refresh" button available in the web GUI. Use Case: Being able to trigger a refresh of all monitored website assets on a schedule (e.g., nightly) would allow us to ensure all expirations (like domain registration) are up to date for the alert emails. Currently, there's no way to trigger a refresh via the API - users must manually click "Refresh" on each website in the GUI, which doesn't scale. Proposed Solution: Add a new endpoint to the Hudu API: Option 1 (by ID): POST /api/v1/websites/{id}/refresh Option 2 (by slug): POST /api/v1/websites/{slug}/refresh Option 3 (bulk refresh): POST /api/v1/websites/refresh_all Response format: 200 OK (or 202 Accepted for async queueing) Why This Matters: Enables automation of website monitoring workflows Matches functionality available in the web GUI (/websites/{slug}/refresh) Particularly useful for MSPs managing multiple client sites who need scheduled refreshes Current Workaround (insufficient): Using the existing PUT endpoint /websites/{id} only updates metadata - it doesn't trigger a fresh scan of the website The GUI refresh endpoint exists but requires GUI session auth and isn't accessible via the documented REST API References: GUI refresh URL pattern: https://[instance]/websites/[slug]/refresh Current Website API endpoints: GET/POST/PUT/DELETE /websites and /websites/{id} Existing refreshed_at field in Website model (read-only) confirms refresh functionality exists internally

When using process templates, we need the ability to assign a specific person to a task at the template level so the assignment carries over automatically each time the process is run. Once assigned, the assignee should receive an email notification. Additionally, automated reminders should be sent a configurable number of days before the due date and again on the due date itself -- all without manual intervention.