> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/automation/workflows-overview.md).

# Workflows overview

A workflow is a method for organizing everyday tasks and activities in a specific order.

You can use workflows to automate sequentially occurring procedures and tasks. Workflows, for instance, allow you to send emails and make tasks when a Partner's invitation status changing.

{% hint style="info" %}
**IN THIS ARTICLE**

* [Key concepts](#key-concepts)
* [Examples](#examples)
* [Create your first workflow](#create-your-first-workflow)
  {% endhint %}

## Key concepts <a href="#key-concepts" id="key-concepts"></a>

### Triggers

To automate operations and processes, you can use a variety of triggers to react to events occurring within Kiflo to start sequences of actions.

[Learn more about triggers](/automation/triggers/workflows-triggers.md)

### Actions

Workflow [actions](/automation/actions/workflow-actions.md) are steps that can readily be automated as a workflow component.

[Learn more about actions](/automation/actions/workflow-actions.md)

### Enrollments

Enrollments help track the workflow progress of an entity and contain several statuses.

[Learn more about enrollments](/automation/workflow-enrollments.md)

## Examples <a href="#examples" id="examples"></a>

### Triggers example

Triggers can assist you in automatically detecting partner performance. For instance, the [*Metric changed* trigger](/automation/triggers/workflow-trigger-metric-changed.md) can help identify top or bad-performing partners.

The [*Partner properties* trigger](/automation/triggers/workflow-trigger-partner-properties.md) can also enable you to automatically detect inactive partners by using the Last seen date property.

You can also use triggers to activate new partner team members when you grant access to your Partner Portal. The [*Partner invitation status changed* trigger](/automation/triggers/workflow-trigger-partner-invitation-status-changed.md) will let you know when a partner’s invitation status has changed from **Pending** to **Accepted** so you can start a sequence of actions.

### Actions example

You can [send an automated welcome email](/automation/actions/workflow-action-send-email.md) whenever a new team member logs in to the partner portal for the first time. Another action you can perform includes [creating a task](/automation/actions/workflow-action-create-task.md) to book a meeting with a partner you last met with a while ago.

You can also [delay](/automation/actions/workflow-action-delay.md) actions to send a sequence of emails to new partner team members to explain how they can use Kiflo.

## Create your first workflow <a href="#create-your-first-workflow" id="create-your-first-workflow"></a>

Ready? Start creating your first workflow following this [step-by-step guide](/automation/workflow-examples-step-by-step-guide.md).


---

# 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-vnext.kiflo.com/automation/workflows-overview.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.
