Deletes a job in Google Cloud Scheduler
A documented Google Cloud Scheduler operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Deletes a job.
- DELETEChanges data · projects
cloudscheduler.googleapis.com/v1beta1/{name}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Cloud Scheduler operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Google Cloud Scheduler operations
- Creates a jobPOST · changes data
- Updates a job. If successfulPATCH · changes data
- Forces a job to run nowPOST · changes data
- Pauses a job. If a job is paused then the system will stopPOST · changes data
- Resume a job. This method reenables a job after it has beenPOST · changes data
- Lists information about the supported locations for this serviceGET · reads data
Questions
- Can HumDay deletes a job in Google Cloud Scheduler?
- Yes. This operation is published in Google Cloud Scheduler'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 Cloud Scheduler data?
- Yes — this is a DELETE operation, so it changes something in Google Cloud Scheduler. 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 Cloud Scheduler account.
Where this came from
Read from a published API description for Google Cloud Scheduler at cloudscheduler.googleapis.com/$discovery/rest?version=v1beta1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.