---
title: "Making Integrations Server Specific "
slug: "making-integrations-server-specific"
tags: ["Rest integration"]
updated: 2025-06-25T15:57:04Z
published: 2025-06-25T15:57:04Z
---

> ## 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.

# Making Integrations Server Specific

## Overview

By parameterizing a **REST****Integration**, Designers provide the ability to make Integration dynamic without having to create a new Integration each time. This parameterization allows an environment to be dynamic enough to point to the **Development**environment and provides the ability to change from one **Production**server to another. The following document demonstrates how to make an Integration more Server-specific via parameterization.

Additional Information The following example involves the creation and use of a REST Integration in Decisions. For more information on REST Integration see [REST Service Integration Overview.](https://documentation.decisions.com/v9/docs/rest-service-integration-overview)

---

### Example

1. From the **Decisions****Studio**, navigate to**System > Integrations > External Services**. Then select ADD REST SERVICE. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1749564321112.png)
2. From the **Add****REST****Service**window, provide a relevant **Service****Name**.
3. Under **Service****URL**, define the URL first by providing the **protocol**, and then by blocking off the URL with curly brackets, separating each element with periods (for this example "https://{Server}.{Domain}"). Additional Information on Parameterization As the **Note**on this window states, encapsulating a text value in curly brackets ({}) will turn that value into a Flow Input that can be dynamically changed via the Flow Designer. For this example, one Input will represent the desired Server, the other will represent the Domain.  
  
This allows Designers to use the same Integration Step to navigate to different specific without having to create separate Services for each one. 

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-24_15h56_37.png)
4. Unde**r AUTHENTICATION > Authentication** select/define the required Authentication type, then click SAVE INTEGRATION. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-24_15h58_12.png)
5. After the Service is added, select **Add Method to Service**.
6. From the **New REST Service Method**window, provide a **Name**. Then in the **URL**box, provide a parameterized element (for example "{Decisions}").

About Method and URL Adding a **Method**to a**REST Integration** will create a **Step**for the **Service**within the **Flow****Designer**.  
Note that the **URL**value of the Method represents a path relative to the **Service Base URL**. This value would follow a forward slash in the typical URL configuration.  
  
For example, in the URL https://support.decisions.com/decisions, the path "decisions" at the end of the entire URL would be represented by this value.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-24_16h00_30.png)
7. Select the desired **HTTP Method**, then click OK. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-24_16h02_27.png)
8. After the **Method**is successfully added, navigate to a **Designer****Project**, select CREATE FLOW, then CREATE a new **Flow**.
9. From the **Flow****Designer**, navigate to**Toolbox > INTEGRATION > REST SERVICES > [NAME OF SERVICE]**, and attach the defined Method step to the **Start**step. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-25_11h55_01.png)
10. From the **Properties** tab of the **Rest****Method**, **Constant**map the desired **Domain**, **Server**, and URL (Path) values. Then, connect the **Done**and **Error**paths to the **End**step.

Additional Information on Inputs If the **Method**calls for any additional **Inputs**(such as via POST), provide the respective value. 

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-25_11h56_00.png)
11. **Save** the Flow, then close via **X**.

Service Reuse Upon future uses, due to the parameterization of the URL for the **REST Service Method**, this step may be utilized in different Flows and mapped to navigate to different **Servers**/**Domains**/**URL****Paths**in an environment. 

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

---

For further information on Integrations, visit the [Decisions Forum](https://community.decisions.com/categories/Integrations).