--- title: "Post Trigger" slug: "compute-cloudfunctions-v2-posttrigger" tags: ["Cloud Functions"] updated: 2026-09-17T10:05:57Z published: 2026-09-17T10:05:57Z canonical: "api.ncloud-docs.com/compute-cloudfunctions-v2-posttrigger" --- > ## Documentation Index > Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Post Trigger Available in Classic and VPC Run a trigger to execute the configured action. ## Request This section describes the request format. The method and URI are as follows: | Method | URI | | --- | --- | | POST | /ncf/api/v2/triggers/{triggerName} | Note Singapore and Japan Regions are available only in the VPC environment. ### Request headers For information about the headers common to all Cloud Functions APIs, see [Cloud Functions request headers](/docs/en/compute-cloudfunctions#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%94). ### Request path parameters You can use the following path parameters with your request: | Field | Type | Required | Description | | --- | --- | --- | --- | | `triggerName` | String | Required | Trigger name | ### Request query parameters You can use the following query parameters with your request: | Field | Type | Required | Description | | --- | --- | --- | --- | | `platform` | String | Optional | Platform type - `vpc` (default) \| `classic` | ### Request body You can include the following data in the body of your request: Depending on the type of the trigger, you can pass the runtime parameters of the required action in JSON format. | Field | Type | Required | Description | | --- | --- | --- | --- | | User-defined | Object | Optional | Action runtime parameter | ### Request example The request example is as follows: ``` curl --location --request POST 'https://cloudfunctions.apigw.ntruss.com/ncf/api/v2/triggers/trg1-os' \ --header 'x-ncp-apigw-timestamp: {Timestamp}' \ --header 'x-ncp-iam-access-key: {Sub Account Access Key}' \ --header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \ --header 'Content-Type: application/json' \ --data '{ "name": "Cloud Functions", "place": "NAVER Cloud" }' ``` ## Response This section describes the response format. ### Response body The response body includes the following data: | Field | Type | Required | Description | | --- | --- | --- | --- | | `content` | Object | - | Trigger execution information | | `content.activationId` | String | - | Trigger execution result ID | ### Response status codes For information about the HTTP status codes common to all Cloud Functions APIs, see [Cloud Functions response status codes](/docs/en/compute-cloudfunctions#%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C). ### Response example The response example is as follows: ``` { "content": { "activationId": "e251b49a25094dcd91b49a25093dcdb0" } } ```