Scheduling with Google Cloud | Scribe

    Scheduling with Google Cloud

    • Hafeez Baig |
    • 19 steps |
    • 35 seconds
    1
    Sign into the **Google Cloud Console**
    2
    Type "**Cloud Scheduler**" in the search bar and click on the **Cloud Scheduler** option
    information ordinal icon
    **What is Cloud Scheduler?**\ \ **Cloud Scheduler** is a fully managed service in Google Cloud that allows you to run arbitrary tasks on a schedule. It enables you to create and manage cron jobs, which can trigger various types of tasks such as HTTP requests, Pub/Sub messages, or Cloud Functions at specified times or intervals. Cloud Scheduler is used for automating repetitive tasks, running batch jobs, and orchestrating workflows, all without needing to manage the underlying infrastructure.
    3
    **Cloud Scheduler API** wizard will open, click on the **ENABLE** buton
    information ordinal icon
    **What is Cloud Scheduler API?**\ \ The **Cloud Scheduler API** is a Google Cloud API that allows you to programmatically create, manage, and execute scheduled tasks or jobs. Using the API, you can set up and control cron-like jobs to trigger HTTP requests, Pub/Sub messages, or Cloud Functions at specific times or intervals. It provides a way to integrate scheduling capabilities into your applications and workflows, automate tasks, and manage job schedules through code.
    4
    **Jobs** wizard will open, click on the **CREATE JOB** button
    information ordinal icon
    **What are Jobs?**\ \ **Jobs** in Cloud Scheduler are automated tasks that execute at scheduled times or intervals. They can trigger HTTP requests, Pub/Sub messages, or Cloud Functions, enabling task automation and workflow management.
    5
    **Create a job** wizard will open, give the name as - **"my-cloud-scheduler"**
    6
    Scroll to the **Region** dropdown section, here you can select the Region close to your location
    7
    Scroll to the **Frequency (Minute 0-59)** section, here you can give the Frequency
    information ordinal icon
    **What is Frequency (Minute 0-59)?**\ \ **Frequency (Minute 0-59)** refers to the specific minute of each hour when a scheduled job or task is set to run. In scheduling systems like Cloud Scheduler, you can specify a minute value between 0 and 59 to determine the exact minute within an hour that the job should be executed. This allows for precise timing and regular execution of tasks.
    8
    Scroll to the **Timezone** dropdown section, here you can add the Timezone
    information ordinal icon
    **What is Timezone?**\ \ **Timezone** refers to the region-specific setting that defines the local time offset from Coordinated Universal Time (UTC) for a particular area. In scheduling systems, the timezone determines the local time at which scheduled tasks or jobs will be executed, ensuring they align with the desired regional time. This helps synchronize tasks with local business hours or other time-based requirements.
    9
    Click on the **Configure the execution** section
    10
    Scroll to the **Target type** dropdown section and select the option **HTTP** **Note:** You can select the option as per your requirement.
    information ordinal icon
    **What is Target type HTTP?**\ \ **Target type HTTP** refers to a job configuration in Cloud Scheduler where the scheduled task sends an HTTP request to a specified URL. This target type is used to trigger web services or APIs at defined intervals or times. It allows you to automate HTTP-based interactions, such as calling webhooks, REST APIs, or other web services, as part of your scheduled tasks.
    11
    Scroll to the **URL** text input field, here you can give the URL of the Target
    12
    Scroll to the **HTTP method** dropdown section and select the option **POST** **Note:** You can select the option as per your requirement.
    information ordinal icon
    **What is HTTP method : POST?**\ \ **HTTP method: POST** is a request method used in HTTP to submit data to a specified resource, often to create or update resources on a server. When using POST, data is sent in the body of the request, and it is commonly used for actions such as form submissions, API interactions, or creating new records. Unlike GET requests, which retrieve data, POST requests are used to send data to the server for processing or storage.
    13
    Scroll to the **HTTP headers** section and click on the **ADD A HEADER** button