---
title: "Post Trigger Link Action"
slug: "compute-cloudfunctions-v2-posttriggerlinkaction"
tags: ["Cloud Functions"]
updated: 2026-09-17T10:05:57Z
published: 2026-09-17T10:05:57Z
canonical: "api.ncloud-docs.com/compute-cloudfunctions-v2-posttriggerlinkaction"
---

> ## 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 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 | /ncf/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](/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:

| 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 request example is as follows:

```
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

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 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": {
        "action": {
            "name": "act-01",
            "path": "oGX7O8Jbeodp/hsh"
        },
        "namespace": "oGX7O8Jbeodp",
        "status": "active",
        "trigger": {
            "name": "trg2-os",
            "path": "oGX7O8Jbeodp"
        }
    }
}
```