Post Trigger Link Action
- Print
- PDF
Post Trigger Link Action
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
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 | /triggers/{triggerName}/link-action |
Request headers
For headers common to all Cloud Functions APIs, see Cloud Functions common headers.
Request path parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
triggerName | String | Required | Trigger name |
Request query parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
platform | String | Optional | Platform type
|
Request body
The following describes the request body.
{
"action": "String",
"package": "String"
}
| 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
|
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 '<See below>'
{
"action": "hsh/act-01",
"package": "-"
}
Response
The following describes the response format.
Response body
The following describes the response body.
| Field | Type | 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
The following describes the response status codes.
| HTTP status code | Code | Messages | Description |
|---|---|---|---|
| 400 | 80302 | ACTION_PLATFORM_MISMATCH | Action platform parameter error |
| 400 | 80324 | ACTION_RULE_EXCEED | Target action's trigger connection limit exceeded |
| 400 | 80502 | TRIGGER_PLATFORM_MISMATCH | Trigger platform parameter error |
| 400 | 80519 | TRIGGER_RULE_EXCEED | Target trigger's action connection limit exceeded |
| 400 | 80520 | RULE_BODY_INVALID_TYPE | Invalid request body field type |
| 400 | 80521 | RULE_BODY_MISSING_FIELD | Missing required fields in the request body |
| 400 | 80901 | DUPLICATED_RULE | Duplicated connection request |
| 403 | 80002 | SUB_ACC_NO_PERMISSION | Detailed permission error |
| 404 | 80301 | ACTION_NOT_FOUND | Action not found |
| 404 | 80501 | TRIGGER_NOT_FOUND | Trigger not found |
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"
}
}
}
Was this article helpful?