> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/automations/designer-how-to-create-automations.md).

# How to Create Automations

Automations enable you to instantly trigger another action based on predefined conditions.

To set up an automation, select "Automations" from the vertical menu bar in Designer.

Click on "+New" in the upper right corner

Enter a title for your automation.

Next, select a Trigger Type: Event, Scheduled, or Recurring

Note: When you select a general trigger category with multiple options below, that trigger will fire when any of the below actions occur. For example, selecting "Data Type" will trigger for all of "Data Type Created, Data Type Updated, and Data Type Deleted."

***

## Assessment Conditions

When building automations that evaluate a patient's assessment status, the following condition types are available under the **Assessment** condition group:

| Condition                    | Description                                                                         |
| ---------------------------- | ----------------------------------------------------------------------------------- |
| **IS\_IN\_PROGRESS**         | The patient's most recent assessment of the specified name is currently in progress |
| **NOT\_IN\_PROGRESS**        | The patient has no assessment of the specified name currently in progress           |
| **IS\_PARTIALLY\_COMPLETED** | The most recent assessment has been partially completed                             |
| **IS\_COMPLETED**            | The most recent assessment has been completed                                       |
| **IS\_SUBMITTED**            | The most recent assessment has been submitted                                       |
| **IS\_EXPIRED**              | The most recent assessment has expired                                              |

For status-based conditions (`IS_PARTIALLY_COMPLETED`, `IS_COMPLETED`, `IS_SUBMITTED`, `IS_EXPIRED`), the automation checks the **newest** assessment record for the patient with the specified name.

***

## Related Topics

* [Create Advanced Automations](/designer/automations/create-advanced-automations.md) – complex automation patterns
* [Create Automated Appointment Reminders](/designer/automations/create-automated-appointment-reminders.md) – common automation use case
* [Automations that Trigger Outbound Communications](/designer/automations/automations-that-trigger-outbound-communications.md) – SMS/email automations
* [Create User Notifications](/designer/notifications-and-communications/create-user-notifications.md) – user-facing notifications
* [Programs and Phases](/designer/programs-and-profiles/programs-and-phases.md) – automations triggered by program enrollment


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.welkinhealth.com/designer/automations/designer-how-to-create-automations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.