# Human-in-the-Loop Steps ## Human-in-the-Loop (HITL) steps **Types of Human-in-the-Loop steps** Relay.app offers two kinds of HITL steps: 1. Request Approval (over Email or Slack) 2. Send input form (over Email or Slack) When any of these steps are encountered during a workflow run, the run will pause and wait until the assignee of the step has completed their task (i.e., given the approval to continue, provided the missing data, etc.). Human-in-the-Loop steps can be assigned to users in your Relay.app workspace. Assignees can be notified via interactive notifications over Slack or email when their action is needed in a HITL step. Each notification can be accompanied with a custom message with instructions. #### Approvals Approvals are the most basic Human-in-the-Loop step: they ask the assignee for approval to continue the run. When setting up this step, you can include any context (like variables) to aid the assignee in making the decision.

An approval step before an email is sent

#### **Data Input** Perhaps the most powerful Human-in-the-Loop step is ‘Get data input’. It sends a small “form” to the assignee and asks them to fill it out. You can add as many form inputs as needed, all typed data.

An example data input step that requests a Date

## Setting up a HITL step ### **HITL step parameters** All of the Human-in-the-Loop steps are easy to configure and share the same parameters: * A **medium** to notify the assignee that action is required from them before the workflow run will continue. Assignees can be notified via either Slack or email. * The **assignee** may be: * any member of the Relay.app workspace, * any email address * or a Slack channel. * The **message** with optional instructions that the assignee will receive with their notification. These instructions may contain references to variable data from other places in the workflow. * An optional **due date** for the action. * Optional **additional reminders** to the assignee, for example, to notify them again three days after the initial notification was sent if they still haven’t acted on it. * Optional **notifications to the run owner** (the Relay.app user that owns the workflow Trigger). For example, you may set up a run owner notification for every HITL notification that’s sent or when HITL actions are overdue. * Optional **escalation behavior** for overdue HITL actions. By default, the step will just continue waiting for the user to act, but it can also be configured to do any of the following after the due date: * Skip the HITL action and continue to the next step. * End the workflow run right away and not execute steps after this one. * Reassign the HITL step to another workspace user.

### **Slack notifications** Slack notifications for Human-in-the-Loop steps come from the Relay.app Slack bot and are interactive. This means that you can approve runs and even fill in data inputs right from Slack, even when you’re on the go! For example, if the medium of the HITL step is a Slack DM, the user can "Approve" directly within Slack. If the medium is a notification to a Slack Channel, any member of that channel can complete the HITL step.

Completing a HITL step from within Slack

--- # 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.relay.app/human-in-the-loop/human-in-the-loop-steps.md?ask= ``` 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.