TheSchedule triggerlets you run your integration periodically at specific time intervals.
This trigger is useful when you want to run your integration automatically without any manual
intervention. For example, you can consider using theSchedule triggerfor the
following type of tasks:
Uploading files from one system to another system at regular intervals
Sending periodic email reminders
Syncing database at regular intervals
Add a Schedule trigger
To add aSchedule triggerto a new or existing integration, perform the following steps:
In the Google Cloud console, go to theApplication Integrationpage.
TheIntegrations Listpage appears listing all the integrations available in the Google Cloud project.
Select an existing integration or clickCreate integrationto create a new one.
If you are creating a new integration:
Enter a name and description in theCreate Integrationpane.
Select a region for the integration.
Select a service account for the integration. You can change or update the service account details of an integration any time from theinfoIntegration summarypane in the integration toolbar.
ClickCreate.
The newly created integration opens in theintegration editor.
In theintegration editornavigation bar, clickTriggersto view the list of available triggers.
Click and place theSchedule triggerelement to the designer.
Configure a Schedule trigger
Click theSchedule triggerelement in the integration editor to view the trigger configuration
pane.
You can configure theSchedule triggerusing either of the following modes:
Basic: Provides a user interface to configure the frequency of the run.
Advanced: Uses a cron expression to configure the frequency of the run.
InBasicmode, you can choose to run the integration at a specific time
or at hourly intervals. If you want to run the integration at a specific time, select
theRun at a specific timefrom theTimesdrop-down
and set the following properties:
Time: The time (in 24-hour format) at which the integration must run.
Days: The days on which the integration must run. You can select to run
the integration every day, on specific days of the week, on a specific day of
the month, etc.
Months: The month(s) in which the integration must run. You can run the
integration every month or choose specific months.
InAdvancedmode, you can specify the frequency of the run using a cron expression.
The cron expression has five values that must be specified in the following order:
Minute (0-59)
Hour (0-23)
Day of the month (1-31)
Month, either of the following values:
A number 1-12
A three-letter month abbreviation (e.g. Jan, Feb, Mar, etc.)
Day of week, either of the following values:
A number from 0 - 6 starting with Sunday as 0
A three-letter day abbreviation (e.g. Mon, Tue, Wed, etc.)
For example, to run the integration on the first day of every month,
use the* * 1 * *cron expression.
Best practices
As a best practice, deactivateSchedule triggerswhen they are no longer needed.
If you leave a redundantSchedule triggeractive, it will continue to trigger the integration
automatically.
To deactivate aSchedule trigger, you can do one of the following:
Unpublish the integration containing theSchedule trigger. Your integration will no longer be
active and the trigger will not run.
Replace theSchedule triggerwith a different trigger and re-publish the integration.
The re-published, active version of the integration will not use theSchedule trigger.
Delete the current version of the integration. You can find theDeleteoption under the version list
next to the integration name.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThe Schedule trigger enables automatic, periodic execution of integrations without manual intervention, useful for tasks like file uploads, email reminders, and database syncing.\u003c/p\u003e\n"],["\u003cp\u003eSchedule triggers can be configured in either Basic mode, using a UI for frequency settings, or Advanced mode, using cron expressions for precise scheduling.\u003c/p\u003e\n"],["\u003cp\u003eIn Basic mode, the integration's run frequency can be set by choosing time, days and months to run it, while in Advanced mode it must be defined through cron expression.\u003c/p\u003e\n"],["\u003cp\u003eDeactivating unnecessary Schedule triggers is recommended to prevent unwanted automatic integration executions; options include unpublishing the integration, replacing the trigger, or deleting the integration.\u003c/p\u003e\n"],["\u003cp\u003eExecutions of active integrations that fail because of the schedule trigger will not be accounted for in the Application Integration SLA.\u003c/p\u003e\n"]]],[],null,["# Schedule trigger\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nSchedule trigger\n================\n\n\nThe **Schedule trigger** lets you run your integration periodically at specific time intervals.\nThis trigger is useful when you want to run your integration automatically without any manual\nintervention. For example, you can consider using the **Schedule trigger** for the\nfollowing type of tasks:\n\n- Uploading files from one system to another system at regular intervals\n- Sending periodic email reminders\n- Syncing database at regular intervals\n\nAdd a Schedule trigger\n----------------------\n\nTo add a **Schedule trigger** to a new or existing integration, perform the following steps:\n\n1. In the Google Cloud console, go to the **Application Integration** page.\n\n [Go to Application Integration](https://console.cloud.google.com/integrations)\n2. In the navigation menu, click **Integrations**\n\n\n The **Integrations List** page appears listing all the integrations available in the Google Cloud project.\n3. Select an existing integration or click **Create integration** to create a new one.\n\n\n If you are creating a new integration:\n 1. Enter a name and description in the **Create Integration** pane.\n 2. Select a region for the integration. **Note:** The **Regions** dropdown only lists the regions provisioned in your Google Cloud project. To provision a new region, Click **Enable Region** . See [Enable new region](/application-integration/docs/enable-new-region) for more information.\n 3. Select a service account for the integration. You can change or update the service account details of an integration any time from the info **Integration summary** pane in the integration toolbar. **Note:** The option to select a service account is displayed only if you have enabled integration governance for the selected region.\n 4. Click **Create**.\n\n\n The newly created integration opens in the *integration editor*.\n4. In the *integration editor* navigation bar, click **Triggers** to view the list of available triggers.\n5. Click and place the **Schedule trigger** element to the designer.\n\nConfigure a Schedule trigger\n----------------------------\n\nClick the **Schedule trigger** element in the integration editor to view the trigger configuration\npane.\n\nYou can configure the **Schedule trigger** using either of the following modes:\n\n- **Basic**: Provides a user interface to configure the frequency of the run.\n- **Advanced**: Uses a cron expression to configure the frequency of the run.\n\nIn **Basic** mode, you can choose to run the integration at a specific time\nor at hourly intervals. If you want to run the integration at a specific time, select\nthe **Run at a specific time** from the **Times** drop-down\nand set the following properties:\n\n- **Time**: The time (in 24-hour format) at which the integration must run.\n- **Days**: The days on which the integration must run. You can select to run the integration every day, on specific days of the week, on a specific day of the month, etc.\n- **Months**: The month(s) in which the integration must run. You can run the integration every month or choose specific months.\n\nIn **Advanced** mode, you can specify the frequency of the run using a cron expression.\nThe cron expression has five values that must be specified in the following order:\n\n- Minute (0-59)\n- Hour (0-23)\n- Day of the month (1-31)\n- Month, either of the following values:\n - A number 1-12\n - A three-letter month abbreviation (e.g. Jan, Feb, Mar, etc.)\n- Day of week, either of the following values:\n - A number from 0 - 6 starting with Sunday as 0\n - A three-letter day abbreviation (e.g. Mon, Tue, Wed, etc.)\n\nFor example, to run the integration on the first day of every month,\nuse the `* * 1 * *` cron expression.\n\nBest practices\n--------------\n\n\nAs a best practice, deactivate **Schedule triggers** when they are no longer needed.\nIf you leave a redundant **Schedule trigger** active, it will continue to trigger the integration\nautomatically.\n\nTo deactivate a **Schedule trigger**, you can do one of the following:\n\n- Unpublish the integration containing the **Schedule trigger**. Your integration will no longer be active and the trigger will not run.\n- Replace the **Schedule trigger** with a different trigger and re-publish the integration. The re-published, active version of the integration will not use the **Schedule trigger**.\n- Delete the current version of the integration. You can find the **Delete** option under the version list next to the integration name.\n\nSLA exclusions\n--------------\n\nAll executions of `active` integrations that fail because the Schedule trigger\ndidn't get scheduled for any reason, are excluded\nfrom the [Application Integration\nService Level Agreement (SLA)](https://cloud.google.com/application-integration/sla) terms and conditions.\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- Learn about [all tasks and triggers](/application-integration/docs/all-triggers-tasks).\n- Learn how to [test and publish an integration](/application-integration/docs/test-publish-integrations).\n\n- Learn about [error handling](/application-integration/docs/error-handling-strategy).\n- Learn about [integration execution logs](/application-integration/docs/introduction-logs)."]]
