---
title: "Execute custom action"
method: POST
path: "/api/{cloudId}/v1/alerts/{id}/action"
tags: ["Alerts"]
---

# Execute custom action

`POST /api/{cloudId}/v1/alerts/{id}/action`

This endpoint is used to execute custom actions on an existing alert. Custom actions allow for more flexible and specific responses to alerts, including integrations with external systems or triggering complex workflows. This operation is a powerful tool for extending the capabilities of the alert management process beyond predefined actions.

## Path parameters

- `id` string, required

## Request body

- ExecuteCustomActionRequest
  - `actionName` string, required — Action name that can be executed on the alert. This action is a custom to your organization and can be used to automate responses to specific alerts.

## Response `202`

Returned if the request is successful.

- SuccessResponse
  - `result` string — Indicates the outcome of the request.
  - `requestId` string — Identifier of the request. This ID can be used to trace or track the request in the system logs or for debugging purposes in case the request fails or causes an error.
  - `took` integer

## Other responses

- `401` — Returned if the authentication credentials are incorrect.
- `422` — Returned if the payload cannot be validated.

---

[API](https://skmtc.net/atlassian/apis/jsm-operations-api.md) · [All operations](https://skmtc.net/atlassian/apis/jsm-operations-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/jsm-operations-api/versions/ed65f017bcb8/schema)