> For the complete documentation index, see [llms.txt](https://docs.introist.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.introist.com/knowledge-base/learn/key-concepts/workflows.md).

# Workflows

Workflows serve as customizable templates to automate specific actions based on different employee scenarios. Think of a workflow as a series of steps planned out on a timeline that automatically handles actions without needing to manually intervene each time.

Workflows allow you to set up and automate actions for various situations. Whether it's onboarding a new employee, handling annual reviews, or managing leave requests, workflows ensure that the right actions occur at the right time, tailored to each employee's circumstances.

### Timing

A key feature of workflows is their ability to integrate timing flexibly. Actions within a workflow can be timed not only based on when the workflow is initiated but also in relation to significant dates specific to each employee, like their start date. This timing precision ensures that actions such as sending welcome emails or initiating onboarding processes are executed at the most appropriate time.

### Personalisation

Workflows can be extensively personalized using conditional actions that tailor the process to meet specific needs of each employee. This personalization extends to all actions within the workflow, allowing the content of messages and the details of actions to be customized using available employee data. This capability ensures that each automation feels relevant and specific to the individual.

### Types of actions

#### One-off actions

&#x20;These actions are executed at the right time and then considered complete. Sending an email is a typical example of a one-off action. Once the email is sent, the action is done and requires no further follow-up.

#### Monitored actions

&#x20;These actions require ongoing oversight until they are successfully completed. Examples include setting up calendar meetings or assigning tasks that need monitoring and follow-through. These actions are initiated through the workflow but need active management until they reach their conclusion. Introist can handle a bulk of this monitoring and even make adjustments when needed, e.g. by rescheduling a calendar meeting if an attendee declines. &#x20;

### Conclusion

Workflows in Introist simplify and enhance the management of employee-related actions by automating processes that are crucial yet repetitive, allowing teams to focus on more strategic activities. By integrating both one-off and monitored actions into these workflows, Introist ensures that every action, whether simple or complex, is completed successfully. The ability to personalize these workflows and schedule them around key dates further ensures that each action is executed in the most context-appropriate manner.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.introist.com/knowledge-base/learn/key-concepts/workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
