사용 가능한 모든 커넥터 이벤트 트리거의 목록은 커넥터 이벤트 트리거를 참조하세요. Integration Connectors의 이벤트 구독에 대한 자세한 내용은 이벤트 구독을 참조하세요.
통합에 여러 트리거 추가
통합에 하나 이상의 트리거를 추가하고 각 트리거에 서로 다른 태스크를 연결할 수 있습니다.
통합은 이벤트가 발생하는 트리거에서 시작됩니다. 예를 들어 통합에 Trigger-1이 Task-1와 연결되어 있고 Trigger-2가 다운스트림 태스크 Task-5와 연결된 두 개의 트리거가 있는 경우를 생각해 보세요.
이제 이벤트가 Trigger-2를 트리거하면 통합이 Task-5부터 실행합니다.
여러 트리거가 동시에 실행되는 경우 각 트리거는 통합의 복사본을 실행합니다. 앞의 예시에서 Trigger-1과 Trigger-2가 동시에 실행되면 Trigger-1은 Task-1부터 통합을 실행하며 Trigger-2는 Task-5부터 별도의 통합 복사본을 실행합니다. 두 통합의 실행 흐름 간에는 겹치는 부분이 없습니다.
실행 모드
트리거에 따라 통합이 동기 또는 비동기 모드로 실행됩니다.
동기 실행: 동기 모드에서는 통합 실행 직후에 통합 실행 결과를 사용할 수 있습니다. 동기 모드는 통합 실행 직후 실행 결과를 원하는 상황에 유용합니다. 동기 모드에서 통합을 실행하는 트리거에는 다음이 포함됩니다.
비동기 실행: 비동기 실행은 파이어 앤 포겟(fire and forget) 모델을 사용합니다. 비동기 모드는 통합이 실행하는 데 오랜 시간이 걸릴 수 있거나 통합 실행 직후 실행 결과가 필요하지 않은 상황에 유용합니다. 비동기 모드에서 통합을 실행하는 트리거에는 다음이 포함됩니다.
동기식이 아닌 모든 실행은 비동기 모드로 실행됩니다. 일반적인 비동기 모드 중 일부에는 다음이 포함되지만 이에 국한되지 않습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-06-16(UTC)"],[[["\u003cp\u003eA trigger is an external event that initiates a task or sequence of tasks within an integration, serving as the entry point for the integration's execution.\u003c/p\u003e\n"],["\u003cp\u003eConnector Event triggers are specialized triggers that allow integrations to be invoked based on event subscriptions in various business applications using Integration Connectors.\u003c/p\u003e\n"],["\u003cp\u003eMultiple triggers can be added to an integration, but only the trigger associated with the specific event that occurs will initiate its corresponding tasks.\u003c/p\u003e\n"],["\u003cp\u003eIntegrations can execute in either synchronous mode, where results are available immediately, or asynchronous mode, using a fire-and-forget model suitable for long-running processes.\u003c/p\u003e\n"],["\u003cp\u003eThere is a page available to review the quotas and limits for these integrations.\u003c/p\u003e\n"]]],[],null,["# Triggers\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nTriggers\n========\n\nA trigger is an external event that initiates a task, or sequence of tasks, in an integration.\nYou can think of a trigger as an entry point to your integration and the event tied to the trigger causes the\ntasks associated with the trigger to run.\n\nYou can add multiple triggers to your integration. However, when an event occurs, only the trigger\nassociated with the event begins executing its tasks. For more information, see [Adding multiple triggers in an integration](#multi-trigger).\n\nFor the list of all the available out-of-the-box triggers, see [All triggers](/application-integration/docs/all-triggers-tasks).\n\nConnector Event triggers\n------------------------\n\n\nConnector Event triggers are specialized triggers that let you invoke an integration based on the [event subscription](/integration-connectors/docs/eventsubscription) created in various business applications using [Integration Connectors](/integration-connectors/docs).\n\nFor the list of all the available Connector Event triggers, see [Connector Event triggers](/application-integration/docs/all-triggers-tasks#event_triggers). For more information about event subscriptions in Integration Connectors, see [Event subscriptions](/integration-connectors/docs/eventsubscription).\n\nAdding multiple triggers in an integration\n------------------------------------------\n\nYou can add one or more triggers in an integration where each trigger is associated with a different task. The integration starts from the trigger for which the event occurs. For example, consider your integration has two triggers where `Trigger-1` is associated with `Task-1`, and `Trigger-2` is associated with a downstream task `Task-5`. Now suppose an event triggers `Trigger-2`, the integration runs from `Task-5` onwards.\n\n\nIf multiple triggers run at the same time, each trigger runs its copy of the integration. In the\npreceding example, if both `Trigger-1` and `Trigger-2` run simultaneously,\n`Trigger-1` runs the integration from `Task-1` onwards, and `Trigger-2`\nruns a separate copy of the integration from `Task-5` onwards. There is no overlap between the execution flows of the two integrations.\n\nExecution modes\n---------------\n\nBased on the trigger, your integration is executed in either synchronous or asynchronous mode:\n\n- **Synchronous executions:** In synchronous mode, the execution result of the integration is available soon after the integration runs. Synchronous mode is helpful in scenarios where you want the execution result immediately after the integration runs. Triggers execute the integration in the synchronous mode include the following:\n - [Test or publish an integration](/application-integration/docs/test-publish-integrations)\n - Call the [`projects.locations.integrations.execute`](/application-integration/docs/reference/rest/v1/projects.locations.integrations/execute) API\n - Call the integration from a [sub-integration in the synchronous mode](/application-integration/docs/configure-call-integration-task)\n- **Asynchronous executions:** Asynchronous executions use the fire and forget model. Asynchronous mode is helpful in scenarios where integrations can take a long time to run, or the execution result is not required immediately after the integration runs. Triggers that execute the integration in the asynchronous mode include the following:\n - All execution that are not synchronous are executed in asynchronous mode. Some of the common asynchronous mode includes, but is not limited to:\n - [Schedule trigger](/application-integration/docs/configure-schedule-trigger)\n - [Cloud Scheduler trigger](/application-integration/docs/configure-cloud-scheduler-trigger)\n - [Cloud Pub/Sub trigger](/application-integration/docs/configure-pubsub-trigger)\n - [Salesforce trigger](/application-integration/docs/configure-salesforce-trigger)\n - Call the [`projects.locations.integrations.schedule`](/application-integration/docs/reference/rest/v1/projects.locations.integrations/schedule) API\n - Executions that are resumed from a suspension or a approval task are also executed in aynchronous mode, even if the initial execution was is synchronous mode.\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)."]]
