---
title: "Remedy Module"
slug: "remedy"
description: "Learn how to use the Remedy Module in Decisions to create, modify, and close BMC Remedy incident tickets with Flow Steps"
updated: 2026-07-02T16:58:11Z
published: 2026-07-02T16:58:11Z
canonical: "documentation.decisions.com/remedy"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Remedy Module

## Overview

The **Remedy Module** allows Decisions to create, modify, and close incident tickets created within **BMC Remedy**. This is done through Flow steps provided by the Module, which can be used to create custom Flows that handle the required tasks.

### Prerequisites

- Installation of the Remedy Module.
- Access to an active Remedy account.
- Server host information for Remedy.
- A [Project dependency](https://documentation.decisions.com/version-10/docs/project-dependencies) is required.

### Considerations

Note for Third-Party Systems and SubscriptionsCustomers are responsible for securing and maintaining accounts with third-party systems and subscriptions.

---

## Remedy Settings

The Module settings are located under **System > Settings > Remedy Settings**. The Module requires access to a currently active account in Remedy, along with the server host information.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783011483943.png)

Once these values have been identified, they can be added under the correct property for the setting. Below is a table overview of each value.

| Property | Description |
| --- | --- |
| Host | The name of the Remedy host as it appears in Decisions. |
| Server Name | The name of the server hosting the Remedy environment. |
| User Name | The username for the Remedy account is used to establish a connection to the service. |
| Password | The password for the Remedy account is used to establish a connection to the service. |