Post Trigger Link Action

Available in Classic and VPC

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

Request

The following describes the request format for the endpoint. The request format is as follows:

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

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

Request body

The following describes the request body.

Field	Type	Required	Description
`action`	String	Required	Name of the action to be connected with the trigger
`package`	String	Optional	Package name of the action you want to connect with the trigger `-` (default)

Request example

The following is a sample request.

curl --location --request POST 'https://cloudfunctions.apigw.ntruss.com/ncf/api/v2/triggers/trg2-os/link-action?platform=vpc' \
--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": "hsh/act-01",
    "package": "-"
}'

Response

The following describes the response format.

Response body

The following describes the response body.

Field	Type	Required	Description
`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 all Cloud Functions APIs, see Cloud Functions response status codes.

Response example

The following is a sample example.

{
    "content": {
        "action": {
            "name": "act-01",
            "path": "oGX7O8Jbeodp/hsh"
        },
        "namespace": "oGX7O8Jbeodp",
        "status": "active",
        "trigger": {
            "name": "trg2-os",
            "path": "oGX7O8Jbeodp"
        }
    }
}