---
title: "Services"
slug: "services"
updated: 2026-07-22T12:42:08Z
published: 2026-07-22T12:42:08Z
canonical: "kb.easysend.io/services"
---

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

# Services

## **Article Overview**

The following article describes the building blocks located under the Services category.

## Services

(See **Figure 1**)

The Services category contains the Integration building block.

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1739396058050.png)

**Figure 1: Services**

### Integration

(See **Figure 2**)

The Integration building block enables you to initiate and activate services. It contains the following options and fields:

- Service dropdown to select a specific service

NOTEServices are created in your environment, for additional information about services, click [here](https://kb.easysend.io/docs/the-services-screen-1).

- Unique Identifier
- Set Input/Outputs - becomes available after selecting a service
- Repeat:
  - When checked - enables to run the service for every item in a selected array
  - When not checked - the service will run only once
- Description

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1736451208035.png)

**Figure 2: Integration**

#### Set Inputs/Outputs

(See **Figure 3** to **Figure 7**)

Clicking the Set Inputs/Outputs button displays the Service Settings window. The window includes two sections:

- Inputs - this section defines the data that the integration needs to function by mapping the data of this workflow to the integration inputs below
- Outputs (optional) - this section defines if data that the integration generates and passes back to your workflow needs to be stored in the process model.

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1736452195457.png)

**Figure 3: Service Settings Window**

Inputs and Outputs will appear as they were defined in the selected service. If the service does not include inputs or outputs, indication messages will appear, for example:

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1736453980177.png)

**Figure 4: Service Without Outputs**

For Inputs, a source can be:

- Unset
- Process Data (and the value would be a data item or metadata item)
- Constant - static value

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1736454515936.png)

**Figure 5: Inputs**

For Outputs, if you store a value in a Model, the selected Model data item or metadata item must match the output type (for example, string and string). In addition, you can also use the Model Field to create new data items of the same type to match and store the output.

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1736454454965.png)

**Figure 6: Outputs**

**![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1769542849925.png)**

****Figure 7: Create a new Model Field****

NOTE

To learn more about services, click [here](https://kb.easysend.io/docs/the-services-screen-1).

## Integration Usage Example

(See **Figure 8** to **Figure 13**)

In the following flow, an email will be sent through an integration once a process is submitted.

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1741886643279.png)

**Figure 8: Simple Flow**

The service named Thank You Email that is used in the flow contains two inputs that are taken from the process:

- Customer name
- Customer email

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1741886911106.png)

**Figure 9: Integration Inputs**

In addition, the service also contains an Email step named sendEmail. The step utilizes three dynamic fields:

- inputs.email for the recipient's email address
- model.inputs.name for the recipient's name in the email subject
- inputs.name for the recipient's name in the email content

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1741887974674.png)

**Figure 10: Email Step**

To initiate the service as part of the flow, the Integration building block was added in the desired location. In this case, to be initiated once the process is submitted.

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1741888610332.png)

**Figure 11: Integration and Service**

The Inputs/Outputs were set as defined in the service:

- Inputs - two data items taken from the process

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1741888764331.png)

**Figure 12: Inputs**

- Outputs - not configured for this service

![](https://cdn.document360.io/45e1a1b1-1964-46f1-939e-f40bde9b50fa/Images/Documentation/image-1741888894619.png)

**Figure 13: Outputs**