Post Trigger Link Action

Available in Classic and VPC

Connect an action to a trigger you created without associating an action.

Request

This section describes the request format. The method and URI are as follows:

Method	URI
POST	/api/v2/triggers/{triggerName}/link-action

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.

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` \| `classic` (default)

Request body

You can include the following data in the body of your request:

Field	Type	Required	Description
`action`	String	Required	Name of the action to be connected with the trigger
`package`	String	Required	Name of the package for the action to be linked with the trigger

Request example

The request example is as follows:

curl --location --request POST 'https://cloudfunctions.apigw.ntruss.com/api/v2/triggers/trg2-os/link-action' \
--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 '{
    "action": "act-02",
    "package": "pckg"
}'

Response

This section describes the response format.

Response body

The response body includes the following data:

Field	Type	Required	Description
`content`	Object	-	Trigger connection action information
`content.action`	Object	-	Action information
`content.action.name`	String	-	Action name
`content.action.path`	String	-	Action path
`content.namespace`	String	-	Namespace of the user
`content.status`	String	-	Status of the link for the trigger and action
`content.trigger`	Object	-	Information of the trigger
`content.trigger.name`	String	-	Trigger name
`content.trigger.path`	String	-	Trigger path

Response status codes

For information about the HTTP status codes common to NAVER Cloud Platform, see Ncloud API response status codes.

Response example

The response example is as follows:

{
    "content": {
        "action": {
            "name": "act02",
            "path": "oGX7O8Jbeodp/pckg"
        },
        "namespace": "oGX7O8Jbeodp",
        "status": "active",
        "trigger": {
            "name": "trg2-os",
            "path": "oGX7O8Jbeodp"
        }
    }
}