비공개 트리거를 사용하면 대규모 흐름을 다양한 하위 흐름으로 나눌 수 있습니다. Application Integration 내의 다른 통합 흐름에서만 비공개 트리거를 호출할 수 있습니다. 다른 통합에서만 호출할 수 있으면 보안이 향상되고 위험이 줄어듭니다. 호출자 통합 실행 로그에서 비공개 태스크의 실행 로그를 볼 수 있습니다.
다음 목록에는 비공개 트리거를 사용할 때의 이점이 나와 있습니다.
비용 최소화: 비공개 트리거는 실행 가격 책정에 포함되지 않습니다.
보안 강화: 비공개 트리거를 공개 API와 독립적으로 트리거할 수 없으므로 흐름을 다른 통합에서만 호출하도록 제한합니다.
성능 개선: 비공개 트리거는 하위 통합 콜아웃 간의 지연 시간을 줄여줍니다.
비공개 트리거 추가
비공개 트리거를 추가하려면 다음 단계를 수행합니다.
Google Cloud 콘솔에서 Application Integration 페이지로 이동합니다.
[[["이해하기 쉬움","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-09-04(UTC)"],[[["\u003cp\u003ePrivate triggers allow you to divide large integration flows into smaller, manageable subflows that are only invokable by other integrations.\u003c/p\u003e\n"],["\u003cp\u003eUsing private triggers can minimize costs, as they do not count towards execution run pricing, while also increasing security by restricting invocation to other integrations.\u003c/p\u003e\n"],["\u003cp\u003ePrivate triggers improve performance by reducing latency in sub-integration callouts, and their execution logs are visible within the invoker integration's logs.\u003c/p\u003e\n"],["\u003cp\u003ePrivate triggers must be tested in unpublished integrations, and they can be invoked from other integrations using specific flow control tasks such as 'Call Integration', 'For Each Loop', 'For Each Parallel', or 'While Loop'.\u003c/p\u003e\n"],["\u003cp\u003ePrivate triggers have a size limit of 25MB that they share with their parent integration, and the private workflow can not be called with a SYNC strategy if it includes async tasks such as 'Timer task', 'Suspend task' or 'Approval task'.\u003c/p\u003e\n"]]],[],null,["# Private triggers\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nPrivate triggers\n================\n\nPrivate triggers enable you to break large flows into various subflows. You can invoke private triggers only from other integration flows within Application Integration. Being invokable only from other integrations increases security and reduces the risk. You can view the execution logs for a private task in the execution logs of the invoker integration.\n\nThe following list states the benefits of using private triggers:\n\n- **Minimize cost:** Private triggers are not counted towards execution run pricing.\n- **Increases security:** Restrict flows to be invoked only from other integrations as private triggers cannot be triggered independently from public APIs.\n- **Improve performance:** Private triggers reduces the latency between sub-integration callout.\n\nAdd a Private trigger\n---------------------\n\nTo add a private trigger, 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 **Private** element to the designer.\n\nConfigure a Private trigger\n---------------------------\n\n- Click the **Private Trigger** element in the integration editor to view the trigger configuration pane.\n\n The configuration panel displays the **Trigger ID** , which is a\n machine-generated ID in the format `private_trigger/`\u003cvar translate=\"no\"\u003eTRIGGER_NAME\u003c/var\u003e.\n No further configuration is required for this trigger.\n\nTest Private trigger\n--------------------\n\nYou cannot test a published private trigger workflow. You must unpublish the integration to test the private trigger workflow.\n\nInvoke Private trigger from another integration\n-----------------------------------------------\n\nAfter you have published an integration that has a private trigger configured, you can invoke this trigger from another integration. You can have more than one private trigger in your integration. Each private trigger is assigned a unique **Trigger ID**.\n\nYou can view the execution logs for a private trigger in the logs of the main execution workflow.\nPrivate triggers can be invoked from the following flow control tasks:\n\n- [Call Integration](/application-integration/docs/configure-call-integration-task)\n- [For Each Loop](/application-integration/docs/configure-for-each-loop-task)\n- [For Each Parallel](/application-integration/docs/configure-for-each-parallel-task)\n- [While Loop](/application-integration/docs/configure-while-loop-task)\n\nQuotas and limits\n-----------------\n\nThe execution of private triggers shares the *Maximum cumulative size of all the integration data* limit, which is set to 25 MB, with the parent integration. For more information about limits, see [Usage limits](/application-integration/docs/quotas).\n\nLimitation\n----------\n\nIf your private trigger workflow contains any of the following async tasks, then you can't trigger the private workflow from the main workflow with the `SYNC` execution strategy:\n\n- [Timer task](/application-integration/docs/configure-timer-task)\n- [Suspend task](/application-integration/docs/configure-suspend-task)\n- [Approval task](/application-integration/docs/configure-approval-task)\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)."]]
