# Step 4 : Set up the communication

**Step 4 : Communication upon actions between users**

When certain actions take place, it is important that they are **communicated to the stakeholder**, something like the **employee** getting the notification of his reimbursement getting **approved**.

1. There are 2 ways to setup a communication layer, from the **workflow builder** and the **Alarm builder**.

* In this case we’ll use the **workflow builder**.

 2\. Open the workflow for the **reimbursement process** and click **edit**.

Now in the path 1 where we assigned the process to the department head, click the blue icon for ‘**configure alerts**’.

* This is how it would look like, now go on and select **send an alert** and click **configure on the right**.

![](https://4216568905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mc6E3BSGr4i8kVdH38k%2Fuploads%2FfUbovsPRzGcThF49mMKP%2Fimage_2022-01-18_170405.png?alt=media\&token=2596ede9-0c6e-4ef8-9959-058699686f47)

* Our purpose here is to **notify the department head** that a **reimbursement application** has been submitted and assigned to them.

![](https://4216568905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mc6E3BSGr4i8kVdH38k%2Fuploads%2FADmujapTNX5jj8QhBgrl%2Fimage_2022-01-18_170433.png?alt=media\&token=7510695a-3dc3-40f6-b5d6-a0a97f7f857f)

* In this step we’ll create the **title** and the **body** for the **alert** and assign it to the **department head**.

![](https://4216568905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mc6E3BSGr4i8kVdH38k%2Fuploads%2F7aZgt3CuY3k3r1KlURsi%2Fimage_2022-01-18_170645.png?alt=media\&token=59e40d31-4711-4e75-97b1-cffd8a0583b2)

* Lastly click **apply** to finish setting up this **alert**.
* In a similar manner you can add this to the **other path** where the **manager** gets a notification whenever they’re **assigned a reimbursement case**.

 3\. We will wrap this up by **communicating to the employee** the **status** of their **reimbursement application**.

* In all the workflows that end with either **approve** or **reject** we’ll **communicate accordingly** with the **employee**.

![](https://4216568905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mc6E3BSGr4i8kVdH38k%2Fuploads%2F1jU8G2SUdUJDcWk618T9%2Fimage_2022-01-18_170705.png?alt=media\&token=f70500ce-2432-4264-988c-9e2f754db129)

 4\. Here we will select the **initiator** of the workflow as we need to communicate the **output of the application**.

![](https://4216568905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mc6E3BSGr4i8kVdH38k%2Fuploads%2FyE1flXUSUybgnQxeC77h%2Fimage_2022-01-18_170732.png?alt=media\&token=0a0ef6e2-9db5-4897-8935-a296f597444f)

Once you’ve configured an alert for all the **possible outputs**, **Step 4 is complete**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.senpiper.com/digitize-a-sample-process/step-4-set-up-the-communication.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.