Core Web App

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

Currently, the Microsoft Intune integration requires all synced devices to be imported into a single company in Hudu, since Intune itself operates on a per-tenant basis. There's no built-in way to automatically distribute synced assets across multiple companies based on device attributes -- like device name or naming convention -- during or after the sync process. It would be useful to have a mapping rule or filter option within the Intune integration settings that lets users define routing logic for incoming assets. For example, matching on a device name prefix or pattern to automatically assign assets to the correct company on sync, rather than requiring manual moves or custom API scripts after the fact.

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

Can you set a feature where we can schedule a tasks/process on repeat to specific member on daily, monthly basis? An email notification with due date/overdue/upcoming process would be most helpful.

Ability to create processes that automatically recur at a specified interval.

Would love to allow authors to flag archived items for deletion. Admins would be notified and can approve/disprove from that interface.

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.

When importing IP addresses, allow Hudu to automatically relate them to existing device assets based on matching IP or hostname, instead of requiring manual assignment for each one.

It would be great if when you add a date to an asset and select add to expirations that it offered a recurring schedule, weekly, monthly, yearly etc, so the date doesn't have to be manually updated each time it passes.

Maybe a bit of OCD, but, I like to keep everything as neat as possible! If I create an asset (e.g. router), I will create a linked credential. I sometimes forget the naming convention and have "Router xyz login", "Router xyz credential", "xyz login" or more... I then have to go back and edit it later. Can there be a possible auto complete/default "Standard"? e.g. a configuration field on an asset type called "Default credential name" and it would allow you to type something along the lines of "%Configuration% %Name% - Login", so that when you click add credential, it will automatically default to "Router xyz - Login", but still allow you to change if you want.