All integrationsSecurity
Druva
Manage Druva data protection: add, update, preserve and remove inSync users, follow their devices, backups and restores, start a restore, run legal holds, and read alerts and events.
- actions
- 25
- triggers
- 9
Triggers
Start a workflow when something happens in Druva.
- New userRuns for each person added to Druva inSync, by hand, by AD or LDAP sync, or by another workflow. Users there before the workflow is turned on don't start it.
- User preservedRuns for each inSync user who is preserved, such as when someone leaves: their backups stop but their data is kept. Runs again if they are activated and later preserved again.
- New deviceRuns for each laptop, desktop or phone added to inSync, when the inSync Client first connects from it.
- Device backed upRuns when a device finishes a successful backup, with how many files it backed up and missed. A device that backs up twice between checks runs it once, for the later backup.
- Restore finishedRuns for each restore of a device's data that finishes, whether it succeeded, failed or was cancelled, optionally only one outcome.
- New alertRuns for each new Enterprise Workloads alert, such as a failed job or a storage, CloudCache or licence problem. Alerts raised before the workflow is turned on don't start it.
- Backup failedRuns for each Enterprise Workloads backup job that fails, such as a virtual machine's or a file server's, with the job and the error.
- New legal holdRuns for each legal hold policy created in Druva, such as to tell records staff or open a matter.
- Person added to legal holdRuns for each person put on a legal hold, such as to send them a preservation notice.
Actions
Steps a workflow can run in Druva.
- List eventsRead the Druva Cloud Platform's events: sign-ins, admin actions, backup jobs and alerts across Druva's products, filtered by product, category, type or severity. Gets one page; run it again with the next page token for more.
- List usersList the people Druva inSync backs up, with their email, status, profile and quota, filtered by email, name, status, profile, storage or when they were added.
- Get userGet one inSync user: their email, status, profile, storage and quota.
- Create userAdd a person to Druva inSync so their devices and apps can be backed up, with a profile, a storage and optionally a quota.
- Update userChange an inSync user's name, profile or storage. Only the fields given change.
- Preserve userPreserve a user, such as when someone leaves: their backups stop and their devices are disabled, but their backed-up data is kept while they stay preserved.
- Activate userMake a preserved user active again: their devices are enabled and their backups resume.
- Delete userDelete a user with all their devices and backed-up data, freeing their licence. Druva lets an administrator roll this back for a while under Rollback Actions.
- List profilesList inSync's profiles: the backup settings each group of users shares.
- List devicesList the laptops, desktops and phones inSync backs up, with their owner, platform, status, client version and last connection, filtered by any of those.
- Get deviceGet one device: its owner, platform, status, inSync Client version, how much is backed up and when it last connected.
- Disable deviceDisable a device: its backups stop and nothing can be restored onto it. Its data stays in Druva and can be restored to the person's other devices.
- Enable deviceEnable a disabled device so it backs up and can be restored to again.
- List last backupsList each device's last successful backup: when it ran, how many files it backed up or missed, and its size. Filter by device, user or time.
- List restoresList restores of devices' data from the last year, with their status, size and who started them, filtered by device, user or time.
- Get restoreGet one restore: whether it is still running, succeeded or failed (and why), and how many files it restored.
- Start restoreRestore a device's latest backup onto it, or onto another of the same person's devices: to a new desktop folder, to where the files came from, or to a folder you name.
- List legal holdsList the legal hold policies, with their type, data access and how many people are on each, filtered by name, type or person.
- Get legal holdGet one legal hold policy: its type, what data it gives access to, how many people are on it and its WebDAV addresses.
- Create legal holdCreate a legal hold policy, so the data of the people put on it is kept and reviewers can reach it. Add people with 'Add people to legal hold'.
- Delete legal holdDelete a legal hold policy. The people on it come off hold, so Druva's usual retention applies to their data again.
- List people on legal holdList the people (custodians) on a legal hold, with how much of their data has been collected.
- Add people to legal holdPut people on a legal hold by their email address, so their backed-up data is kept. Says who was added, who already was, and who isn't an inSync user.
- Remove people from legal holdTake people off a legal hold by their email address. Says who was removed and who wasn't on it.
- List alertsList Enterprise Workloads alerts, such as failed backup jobs, storage or CloudCache problems, with their severity and status, filtered by organization, type, workload or time.
No actions match that.
Automate Druva with Lodol.
Connect Druva, then hand Lodol the job in Slack, Claude or ChatGPT.
We’re letting people in a few at a time.