# Create custom actions

Supported in:
In [Build a custom integration](https://docs.cloud.google.com/chronicle/docs/soar/respond/ide/building-a-custom-integration), you created a Ping action for the Armis integration. This document outlines how to create a custom action for the Armis integration that enriches entities. It assumes you have a working knowledge of Python and object-oriented programming. For a prerequisite, refer to the SDK documentation and custom integration procedure, and explore the SDK modules.

## Create a custom action

To create a custom action, follow these steps:

1. Go to **Automation \> IDE** ; the **IDE** page appears.
2. Click **Create New Item** and select **Action**. Enter a name and select the integration.
3. Click **Create**. IDE creates a new template with code comments and explanations.

## The Siemplify action object


A Siemplify action requires these steps:

- An object must be instantiated from the `SiemplifyAction` class.
- The object must use the class's `end` method to return an output message and a result value.

### Result values

Every action has an **Output Name** that represents the result value returned by the SiemplifyAction's `end` method. By default, this is `is_success`, but you can change it in the Integrated Development Environment (IDE). You can also set a default **Return Value** for when an action fails.
For example, if the action times out after five minutes (or fails for any other reason),
the `ScriptResult` is set to `Timeout`.

> [!NOTE]
> **Note:** The default return value is crucial for controlling playbook flow. You can use it in a condition to branch the playbook if an action fails or times out.

#### JSON result value


You can also add a JSON result, which is useful for pivoting on data in
playbooks or for manual analysis. To do this, use the `add_result_json`
method on the `SiemplifyAction` result property or the
`add_entity_json` method to attach a JSON result directly to an entity.

### Imports and constants


The \`SiemplifyAction\` class from the \`SiemplifyAction\` module is always imported. Other common imports include:

- `output_handler` from `SiemplifyUtils` for debugging.
- `add_prefix_to_dict_keys` and `convert_dict_to_json_result_dict` for data transformation.
- `EntityTypes` to determine the type of entity an action will run on.

This action also reuses the \`ArmisManager\` created in the custom integration procedure and import the standard \`json\` library.

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)