Deletes a note. Caller must have the OWNER role on the note in Google Keep

What this operation does

Deletes a note. Caller must have the OWNER role on the note to delete. Deleting a note removes the resource immediately and cannot be undone. Any collaborators will lose access to…

• DELETEChanges data · noteskeep.googleapis.com/v1/{name}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Google Keep operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google Keep operations

• Creates a new notePOST · changes data
• Creates one or more permissions on the notePOST · changes data
• Deletes one or more permissions on the notePOST · changes data
• Lists notes. Every list call returns a page of resultsGET · reads data
• Gets a noteGET · reads data

All 6 Google Keep operations

Questions

Can HumDay deletes a note. caller must have the owner role on the note in Google Keep?

Yes. This operation is published in Google Keep's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Google Keep data?

Yes — this is a DELETE operation, so it changes something in Google Keep. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

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

Where this came from

Read from a published API description for Google Keep at keep.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.