Can HumDay connect to Google Vault?

Yes. HumDay reads Google Vault's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 32 operations are documented.

Do I need to write code to automate Google Vault?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Vault account.

What can HumDay do in Google Vault?

22 of the 32 documented operations change something in Google Vault, and 10 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Vault account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Vault is held behind that approval.

Automate Google Vault

HumDay reads Google Vault’s own published API description and derives 32 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Vault is

Retention and eDiscovery for Google Workspace. To work with Vault resources, the account must have the [required Vault privileges](https://support.google.com/vault/answer/2799699) and access to the matter. To access a matter, the account must have created the matter, have the matter shared with them, or have the **View All Matters** privilege. For example, to download an export, an account needs t

API host: vault.googleapis.com

What HumDay can do in Google Vault

22 documented operations change something in Google Vault.

POSTCreates a matter with the given name and description./v1/matters
POSTCreates a saved query./v1/matters/{matterId}/savedQueries
POSTCounts the accounts processed by the specified query./v1/matters/{matterId}:count
POSTAdds an account as a matter collaborator./v1/matters/{matterId}:addPermissions
POSTCreates a hold in the specified matter./v1/matters/{matterId}/holds
DELETEDeletes a long-running operation./v1/{name}
POSTCreates an export./v1/matters/{matterId}/exports
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
DELETEDeletes the specified matter./v1/matters/{matterId}
PUTUpdates the specified matter./v1/matters/{matterId}
POSTCloses the specified matter./v1/matters/{matterId}:close
POSTReopens the specified matter./v1/matters/{matterId}:reopen
POSTUndeletes the specified matter./v1/matters/{matterId}:undelete
PUTUpdates the scope (organizational unit or accounts) and query parameters of a hold./v1/matters/{matterId}/holds/{holdId}
POSTRemoves an account as a matter collaborator./v1/matters/{matterId}:removePermissions
DELETEDeletes the specified saved query./v1/matters/{matterId}/savedQueries/{savedQueryId}
POSTAdds accounts to a hold./v1/matters/{matterId}/holds/{holdId}:addHeldAccounts
POSTAdds an account to a hold./v1/matters/{matterId}/holds/{holdId}/accounts
DELETERemoves the specified hold and releases the accounts or organizational unit covered by the hold./v1/matters/{matterId}/holds/{holdId}
DELETEDeletes an export./v1/matters/{matterId}/exports/{exportId}
POSTRemoves the specified accounts from a hold./v1/matters/{matterId}/holds/{holdId}:removeHeldAccounts
DELETERemoves an account from a hold./v1/matters/{matterId}/holds/{holdId}/accounts/{accountId}

What HumDay can read from Google Vault

These are the operations a schedule or a trigger can watch.

GETLists matters the requestor has access to./v1/matters
GETLists operations that match the specified filter in the request./v1/{name}
GETGets the specified matter./v1/matters/{matterId}
GETRetrieves the specified saved query./v1/matters/{matterId}/savedQueries/{savedQueryId}
GETLists the holds in a matter./v1/matters/{matterId}/holds
GETLists details about the exports in the specified matter./v1/matters/{matterId}/exports
GETLists the saved queries in a matter./v1/matters/{matterId}/savedQueries
GETGets the specified hold./v1/matters/{matterId}/holds/{holdId}
GETGets an export./v1/matters/{matterId}/exports/{exportId}
GETLists the accounts covered by a hold./v1/matters/{matterId}/holds/{holdId}/accounts

How automating Google Vault works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Vault account.
Grant access, then go live. You approve the specific Google Vault operations it may use — and only those.